Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 1cab11d (merge ref)

Garnet DNS egress/install

run 339334498752026-09-05 00:35 UTC

Execution chains

4 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2866 · 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
      - pnpm[2892 · pnpm]step: Install the fixture
        registry.npmjs.org104.16.4.34:443 (https) · tcp
      - getent[2864 · getent]step: Point resolv.conf at the configured nameserver
        168.63.129.16:53 (dns) · udp
  - sudo
    - provjobd1911349119[2054 · provjobd1911349119]
      - 140.82.114.23:443 (https) · tcp
- python3.12
  - python3.12[1319 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[514 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet DNS egress

Jobinstall

Run ID33933449875

Profile UUID01a06efe-0352-7fe2-8b67-c59175a1ddc1

Commit SHA1cab11de46c5b2c747ad929708bd62e39c951f08(merge ref)

Refrefs/pull/38/merge

Timestamp2026-09-05 00:35:34 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.