Execution Profile

garnet-labs/garnet-runtime-review-demo

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

Garnet Record (install under sensor)/record

run 303042960552026-07-27 20:51 UTC

Execution chains

7 destinations · 4 processes

systemd
- hosted-compute-agent[2018 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2548 · node]step: Install dependencies (the workload)
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2502 · node]
        github.com140.82.116.4:443 (https) · tcp
        api.github.com140.82.116.5:443 (https) · tcp
        release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1535529067[2033 · provjobd1535529067]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-02.githubapp140.82.114.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
  - 140.82.113.24:443 (https) · tcp

Run details

Repositorygarnet-labs/garnet-runtime-review-demo

WorkflowGarnet Record (install under sensor)

Jobrecord

Run ID30304296055

Profile UUID019fa558-e2a3-7bba-a030-3c7bbbc7add4

Commit SHAa0aa1cfe6a292eefb3848c16b6ca51e1a12589a9(merge ref)

Refrefs/pull/3/merge

Timestamp2026-07-27 20:51:33 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.