Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 8c9def5 (merge ref)

App install/install

run 368162642282026-10-01 04:42 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agentRunner.Listener
  - Runner.Worker[1960 · Runner.Worker]
    - bash
      - node[2392 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.5.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
    - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[401 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1296 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[643 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816264228

Profile UUID01a0f5c5-1015-704b-b1de-a4f70072fd8a

Commit SHA8c9def5df24ec0dec5e07a40362e55470c976e12(merge ref)

Refrefs/pull/30/merge

Timestamp2026-10-01 04:42:07 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.