Execution Profile

garnet-labs/pnpm

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

Garnet DNS egress/install

run 339345756142026-09-05 00:56 UTC

Execution chains

4 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2717 · node]step: Install pnpm (npm install -g pnpm@${PNPM_VERSION})
        registry.npmjs.org104.16.11.34:443 (https) · tcp
        168.63.129.16:53 (dns) · udp
      - getent[2715 · getent]step: Point resolv.conf at the configured nameserver
        168.63.129.16:53 (dns) · udp
  - sudo
    - provjobd4231177345[2024 · provjobd4231177345]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.112.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- systemd-resolved[509 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1390 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet DNS egress

Jobinstall

Run ID33934575614

Profile UUID01a06f11-48e6-7293-a8f6-e925faa20009

Commit SHAce656ec0f3b27360c6ca68e05e188f3a0de4cfc8(merge ref)

Refrefs/pull/38/merge

Timestamp2026-09-05 00:56:36 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.