Execution Profile

garnet-org/action

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

CI/build-and-verify

run 314624144642026-08-11 05:40 UTC

Execution chains

7 destinations · 8 processes

systemd
- hosted-compute-agent[2211 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker[2289 · Runner.Worker]
      - bash
        node[2731 · node]step: Install dependencies
        registry.npmjs.org104.16.6.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2698 · node]
        api.github.com140.82.112.6:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd76839895[2227 · provjobd76839895]
      - 140.82.112.23:443 (https) · tcp
  - 140.82.114.23:443 (https) · tcp
- python3.12
  - python3.12[1830 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[494 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[733 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID31462414464

Profile UUID019fef56-973f-7e02-a7eb-b9977eafd7fb

Commit SHAf7aab2e49afc282d52cc57555493d0fb60e342fd(merge ref)

Refrefs/pull/130/merge

Timestamp2026-08-11 05:40:56 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.