Execution Profile

garnet-labs/express

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

App install/install

run 368163943282026-10-01 04:43 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2674 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd383238318[2130 · provjobd383238318]
      - 20.75.202.224:443 (https) · tcp
- python3.12
  - python3.12[1479 · python3.12]
    - python3.12[2731 · python3.12]
      - 168.63.129.16:32526, 80 (http) · tcp
      - 169.254.169.254:80 (http) · tcp(cloud metadata)
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[516 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816394328

Profile UUID01a0f5c6-c129-70ca-9067-305f4096919b

Commit SHAe0be6ba9c51dd9e81f6f9cacac08a529574e05b6(merge ref)

Refrefs/pull/35/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.