Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 99f4f4a

Garnet Control Run/garnet-control

run 310743605872026-08-06 05:31 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - curl[2725 · curl]step: Generate network egress
        registry.npmjs.org104.16.6.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2727 · node]step: Generate network egress
        api.github.com140.82.113.5:443 (https) · tcp
  - sudo
    - provjobd3180013074[2178 · provjobd3180013074]
      - 20.75.202.224:443 (https) · tcp
- python3.12
  - python3.12[1838 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[556 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Control Run

Jobgarnet-control

Run ID31074360587

Profile UUID019fd58e-4aff-7651-8e47-1bc1150040a7

Commit SHA99f4f4a0d49c8ef840ee143222d0cc57e1374aba

Timestamp2026-08-06 05:31:39 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.