Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 099a2a1 (merge ref)

App install/install

run 368163935142026-10-01 04:43 UTC

Execution chains

5 destinations · 3 processes

systemd
- hosted-compute-agentRunner.ListenerRunner.Worker
  - bash
    - node[3322 · node]step: Install dependencies (lifecycle scripts execute here)
      - registry.npmjs.org104.16.0.34:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- python3.12
  - python3.12[1308 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[545 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816393514

Profile UUID01a0f5c6-bcee-7efa-8175-deb253cc5f78

Commit SHA099a2a154a172b5cb4c1503ca871e15d53f4153f(merge ref)

Refrefs/pull/34/merge

Timestamp2026-10-01 04:43:57 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.