Execution Profile

garnet-labs/pnpm

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

Garnet Execution Diff/execution-diff

run 358185356542026-09-23 04:29 UTC

Execution chains

5 destinations · 4 processes

systemd
- hosted-compute-agentRunner.Listener
  - Runner.Worker
    - bash
      - node[3352 · node]step: Run selected workload
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
    - node[3374 · node]
      - glb-db52c2cf8be544.github.com140.82.112.21:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
      - productionresultssa9.blob.core.windows.net20.150.88.228:443 (https) · tcpalso recorded: blob.bn9prdstrz04a.trafficmanager.net, blob.bn9prdstrz04a.store.core.windows.net
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[515 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1406 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Execution Diff

Jobexecution-diff

Run ID35818535654

Profile UUID01a0cc87-0842-7d31-8841-446c8e495e7c

Commit SHAd6ce4f1d2faad537a6a31ec90388194bf58a1b30(merge ref)

Refrefs/pull/65/merge

Timestamp2026-09-23 04:29:54 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.