Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 4feb854 (merge ref)

CI/build-and-verify

run 38728199883

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2167 · Runner.Worker]
          • bash
            • node[2645 · node]step: Install dependencies
              • registry.npmjs.org104.16.8.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2612 · node]
            • api.github.com140.82.112.6:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2250594196[2106 · provjobd2250594196]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1490 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[494 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a13f57-8a94-728c-8988-53771c94ee94
Refrefs/pull/186/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.