Execution Profile

garnet-labs/pnpm

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

Garnet dot-form acceptance/reproduce

run 34266100218

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2580 · node]step: Workload with egress
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • curl[2578 · curl]step: Workload with egress
            • registry.npmjs.org104.16.5.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd4210685931[1967 · provjobd4210685931]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1334 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[524 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[719 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet dot-form acceptance
Jobreproduce
Profile UUID01a08262-808b-717d-9ca2-a35b5c2617bf
Refrefs/pull/44/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.