Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 34c87fa (merge ref)

App install/install

run 36820315586

Execution chains

12 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[1984 · Runner.Worker]
          • bash
            • node[2426 · node]step: Install dependencies (lifecycle scripts execute here)
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3044169801[1885 · provjobd3044169801]
          • 20.75.202.224:443 (https) · tcp
    • systemd-resolved[408 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1245 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820315586
Profile UUID01a0f5f4-a338-76d0-99d5-b10ac86bf4c7
Commit SHA34c87fa6296e29327a0f824cac1b00b3c2fa624f(merge ref)
Refrefs/pull/69/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.

Read the docs