Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 5eb0327 (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 409488684382026-10-29 20:34 UTC

Execution chains

4 destinations · 4 processes

systemd
- hosted-compute-agentRunner.ListenerRunner.Worker
  - bash
    - bash
      - node[2538 · node]
        registry.npmjs.org104.16.11.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[405 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1971 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-networkd[658 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID40948868438

Profile UUID01a1895f-2796-7cd0-8c66-f979bb589acc

Commit SHA5eb032778e0f017da90afb862d879cc2afbd34a9(merge ref)

Refrefs/pull/125/merge

Timestamp2026-10-29 20:34: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.