Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 8edcf36 (merge ref)

Garnet Proxy Routing/proxy-routing

run 37704739448

Execution chains

13 destinations · 5 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • bash
            • pnpm[15018 · pnpm]step: Ping the registry with proxy=false
              • registry.npmjs.org104.16.3.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node
          • sudo[14988 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1864 · chronyd]
      • 144.202.0.197:123 (ntp) · udp
      • 169.254.169.123:123 (ntp) · udp
      • 172.232.28.194:123 (ntp) · udp
      • 172.238.164.57:123 (ntp) · udp
      • 185.125.190.56:123 (ntp) · udp
      • 185.125.190.57:123 (ntp) · udp
      • 185.125.190.58:123 (ntp) · udp
      • 69.9.131.113:123 (ntp) · udp
      • 91.189.91.157:123 (ntp) · udp
    • sudo
      • blacksmithd[2319 · blacksmithd]
        • 192.168.127.1:1049 · tcp
    • systemd-resolved[1721 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Proxy Routing
Jobproxy-routing
Profile UUID01a118cb-072d-7c2f-baf4-bf62823b6c8f
Refrefs/pull/99/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.