Execution Profile

garnet-labs/garnet-runtime-review-demo

Recorded at the kernel by Garnetfor commit 64283ea

Garnet Record (install under sensor)/record

run 303042932942026-07-27 20:51 UTC

Execution chains

8 destinations · 5 processes

systemd
- hosted-compute-agent[1991 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2565 · node]step: Install dependencies (the workload)
        dash
        curl[2578 · curl]
        httpbin.org32.194.128.236:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2530 · node]
        github.com140.82.116.3: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
    - provjobd4073049148[2007 · provjobd4073049148]
      - 140.82.114.24:443 (https) · tcp
  - 140.82.112.24:443 (https) · tcp
  - github.com140.82.116.3:443 (https) · tcp

Run details

Repositorygarnet-labs/garnet-runtime-review-demo

WorkflowGarnet Record (install under sensor)

Jobrecord

Run ID30304293294

Profile UUID019fa558-f02d-7744-bae2-27af1389ab34

Commit SHA64283ea0edf76eb17d41be0a6c49776cd85ee4fe

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