Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 6f6851c (merge ref)

App install/install

run 36820428002

Execution chains

12 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2163 · Runner.Worker]
          • bash
            • node[2599 · node]step: Install dependencies (lifecycle scripts execute here)
              • registry.npmjs.org104.16.11.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1195400056[2078 · provjobd1195400056]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1401 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[526 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820428002
Profile UUID01a0f5f6-0024-792b-81c3-6e2654320d18
Commit SHA6f6851ca7a3ba98a6967d4e607553e1dbd4adfdc(merge ref)
Refrefs/pull/73/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