Execution Profile

garnet-labs/pnpm

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

Garnet DNS egress/install

run 339357257672026-09-05 01:18 UTC

Execution chains

4 destinations · 5 processes

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

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet DNS egress

Jobinstall

Run ID33935725767

Profile UUID01a06f25-59ff-7e61-9252-eec0e2cf55e3

Commit SHAa26567f98bacf78b456e875988ac074b86a41b63(merge ref)

Refrefs/pull/38/merge

Timestamp2026-09-05 01:18:28 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.