Execution Profile

garnet-org/action

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

CI/build-and-verify

run 344592780352026-09-10 09:12 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent[2019 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2645 · node]step: Install dependencies
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2612 · node]
        api.github.com140.82.114.6:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2607870484[2057 · provjobd2607870484]
      - 20.75.202.224:443 (https) · tcp
  - 20.75.202.224:443 (https) · tcp
- python3.12
  - python3.12[1403 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[526 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID34459278035

Profile UUID01a08a96-e514-774f-88e5-7bfe2771a27d

Commit SHAa0afbcf78ee6a544420e37f898fe6d2276165133(merge ref)

Refrefs/pull/160/merge

Timestamp2026-09-10 09:12:19 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.