Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 378806058692026-10-09 03:44 UTC

Execution chains

6 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2830 · node]step: First run of the Corepack entry point
        registry.npmmirror.com155.102.176.86:443 (https) · tcpalso recorded: registry.npmmirror.com.w.cdngslb.com
        cdn.npmmirror.com163.181.60.203:443 (https) · tcpalso recorded: cdn.npmmirror.com.w.cdngslb.com
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3862745014[2147 · provjobd3862745014]
      - 20.75.202.224:443 (https) · tcp
- python3.12
  - python3.12[1872 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[522 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[721 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID37880605869

Profile UUID01a11ec3-7428-7b31-9aa1-f00ca5d50224

Commit SHAc51dfba084301ee9c08c48ce4431f518cd59baf6(merge ref)

Refrefs/pull/102/merge

Timestamp2026-10-09 03:44:46 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.