Execution Profile

garnet-org/action

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

CI/build-and-verify

run 334734006892026-09-01 05:24 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent[2009 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2582 · node]step: Install dependencies
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2550 · node]
        api.github.com140.82.113.5:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd924478989[2029 · provjobd924478989]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-2a3c35-public-internal.githubapp.com140.82.114.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
  - 140.82.114.23:443 (https) · tcp
- systemd-resolved[557 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1454 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID33473400689

Profile UUID01a05b6c-a530-77c9-adc5-5210ac112bd3

Commit SHAbcff1d68a256c48f78802f37b1729c0caea7ce03(merge ref)

Refrefs/pull/143/merge

Timestamp2026-09-01 05:24:00 UTC

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.