Execution Profile

garnet-org/action

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

CI/build-and-verify

run 389337294652026-10-16 16:40 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2476 · node]step: Install dependencies
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2442 · node]
        api.github.com140.82.113.6:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - sudo[1884 · sudo]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-02.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- python3
  - python3[1297 · python3]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolve[460 · systemd-resolve]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID38933729465

Profile UUID01a14596-65a8-7f67-bd64-531c50ef2c01

Commit SHAe8cab746efc2a8f06482c89ef472fea15a305976(merge ref)

Refrefs/pull/190/merge

Timestamp2026-10-16 16:40:36 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.