Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit a8dff02 (merge ref)

App install/install

run 36816390708

Execution chains

7 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2109 · Runner.Worker]
          • bash
            • node[2553 · node]step: Install dependencies (lifecycle scripts execute here)
              • registry.npmjs.org104.16.3.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3815242753[2051 · provjobd3815242753]
          • 140.82.114.24:443 (https) · tcp
    • systemd-resolved[520 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1346 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[738 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5c6-b0b8-787c-84d7-54a52f94da2b
Refrefs/pull/32/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.