Execution Profile

garnet-org/action

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

CI/build-and-verify

run 311301010092026-08-06 23:11 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2327 · node]step: Install dependencies
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2295 · node]
        api.github.com140.82.114.6:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd758777199[1824 · provjobd758777199]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-eus-02.githubapp
- systemd-resolved[380 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1186 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-networkd[641 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID31130101009

Profile UUID019fd959-146a-7cf5-9b0a-87ae119a07e3

Commit SHAe76e58f67b200ac4d98feef7c85779844556c651(merge ref)

Refrefs/pull/82/merge

Timestamp2026-08-06 23:11:59 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.