Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 2a50691 (merge ref)

App install/install

run 36821824841

Execution chains

12 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2168 · Runner.Worker]
        • bash
          • node[2596 · 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)
    • python3.12
      • python3.12[1429 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[539 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36821824841
Profile UUID01a0f605-efc7-796a-91ed-5adf7538f768
Commit SHA2a50691f04cfa67a1c9392a02b9bbdaccdd3aefe(merge ref)
Refrefs/pull/86/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