Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 89c0b65 (merge ref)

App install/install

run 36820272261

Execution chains

13 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2620 · 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)
      • sudo
        • provjobd2915157076[2085 · provjobd2915157076]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1496 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[561 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820272261
Profile UUID01a0f5f4-393b-76e5-bd87-11dc69e79ce6
Commit SHA89c0b65870f77121306de494f6ec56344172c791(merge ref)
Refrefs/pull/67/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