Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 8563f83 (merge ref)

App install/install

run 368201693312026-10-01 05:32 UTC

Execution chains

6 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker[1963 · Runner.Worker]
      - bash
        node[3036 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd239784814[1882 · provjobd239784814]
      - 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[1251 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[512 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36820169331

Profile UUID01a0f5f3-104b-7d84-9ef5-bc378e953dd7

Commit SHA8563f83a6d02d906df95908a1b1b6d0f48708d8a(merge ref)

Refrefs/pull/62/merge

Timestamp2026-10-01 05:32:22 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.