Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit baa0c03 (merge ref)

App install/install

run 368201274552026-10-01 05:31 UTC

Execution chains

5 destinations · 4 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2365 · 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)
  - sudo
    - provjobd3850645381[1862 · provjobd3850645381]
      - 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
- systemd-resolved[421 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1217 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36820127455

Profile UUID01a0f5f2-9aca-78b8-bdd2-5be4979319bd

Commit SHAbaa0c03bac5b83c6872d2e8d5493266039b40c6c(merge ref)

Refrefs/pull/64/merge

Timestamp2026-10-01 05:31:51 UTC

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.