Execution Profile

garnet-labs/action

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

CI/build-and-verify

run 366047941022026-09-29 17:25 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2367 · node]step: Install dependencies
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2332 · node]
        api.github.com140.82.114.6:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd4145099719[1845 · provjobd4145099719]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1105 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[401 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/action

WorkflowCI

Jobbuild-and-verify

Run ID36604794102

Profile UUID01a0ee33-bc7e-7a2d-bc61-7703954e6b4d

Commit SHAca1829f83e97f041e89c49102acd2e286a405c01(merge ref)

Refrefs/pull/4/merge

Timestamp2026-09-29 17:25:57 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.