Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 0d473ca (merge ref)

App install/install

run 36820419499

Execution chains

11 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • node[2546 · 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)
    • systemd-resolved[538 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1723 · 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 ID36820419499
Profile UUID01a0f5f5-f72f-73bb-a666-6a34442cb1b9
Commit SHA0d473ca9667ec07046b802ddcc0e6b6d4ac210d7(merge ref)
Refrefs/pull/72/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