Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 69abdd5 (merge ref)

App install/install

run 368164006532026-10-01 04:44 UTC

Execution chains

5 destinations · 4 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2537 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.8.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3883284752[2052 · provjobd3883284752]
      - 140.82.113.23:443 (https) · tcp
- systemd-resolved[522 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1337 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816400653

Profile UUID01a0f5c6-c9bb-7f18-aa2b-9b1a53e49ccb

Commit SHA69abdd5e9ad2bb74b27049c91ac010b7a7f23779(merge ref)

Refrefs/pull/37/merge

Timestamp2026-10-01 04:44:00 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.