Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 2eb9ce8 (merge ref)

Garnet jibril v2.18.0-rc.2 flush test/test

run 428780172072026-11-10 18:44 UTC

Execution chains

5 destinations · 6 processes

systemd
- bashbashbashbashRunner.ListenerRunner.Worker
  - bash
    - curl[4189 · curl]step: Generate workload
      - registry.npmjs.org104.16.1.34:443 (https) · tcp
    - git[4172 · git]step: Generate workload
      - git
        git
        git-remote-http[4183 · git-remote-http]
        github.com140.82.112.3:443 (https) · tcp
      - 192.168.127.1:1034 · tcp
- chronyd[1867 · chronyd]step: <unknown>
  - 169.254.169.123:123 (ntp) · udp
- sudo
  - blacksmithd[2220 · blacksmithd]step: <unknown>
    - 192.168.127.1:1034 · tcp
- systemd-resolved[1727 · systemd-resolved]step: <unknown>
  - 8.8.8.8:53 (dns) · udp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet jibril v2.18.0-rc.2 flush test

Jobtest

Run ID42878017207

Profile UUID01a1c6c6-4c56-7478-afa8-2511b817107e

Commit SHA2eb9ce86beaf5461fc085e90c06fad7317045d0f(merge ref)

Refrefs/pull/130/merge

Timestamp2026-11-10 18:44:06 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.