Execution Profile

garnet-labs/nodejs-goof

Recorded at the kernel by Garnetfor commit 7258df0 (merge ref)

Garnet Runtime Visibility/dep-install

run 44467540877

Execution chains

7 destinations · 8 processes
  • systemd
    • hosted-compute-[1972 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • npm ci[2562 · npm ci]
            • registry.npmjs.org104.16.11.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2562 · node]
            • dash
              • dash
                • node[2577 · node]
                  • nodejs.org104.16.212.131:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.11.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1184543[1996 · provjobd1184543]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3.14
      • python3.14[1256 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolve[222 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[724 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/nodejs-goof
WorkflowGarnet Runtime Visibility
Jobdep-install
Profile UUID01a1f259-5751-7854-a7ae-5558d12df72a
Refrefs/pull/12/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.