Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 9896bd1 (merge ref)

TS CI/test

run 34659392742

Execution chains

19 destinations · 8 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker[3550 · Runner.Worker]
        • node[4521 · node]
          • dash
            • pnpm[4641 · pnpm]
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • pnpm[4571 · pnpm]
            • nodejs.org104.16.213.131:443 (https) · tcp
            • unofficial-builds.nodejs.org45.55.98.129:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • sudo[4512 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • blacksmith.blob.core.windows.net10.123.45.67:80 (http) · tcp
          • registry.npmjs.org104.16.7.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1875 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • nginx
      • nginx[3780 · nginx]
        • 192.168.127.1:1046 · tcp
    • systemd-resolved[1714 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowTS CI
Jobtest
Profile UUID01a092e2-1a4d-767a-a962-80716a7fe3b3
Refrefs/pull/61/merge
Timestamp

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.