Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 6b64a45 (merge ref)

App install/install

run 368199783042026-10-01 05:30 UTC

Execution chains

6 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2492 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1727487093[1956 · provjobd1727487093]
      - 140.82.114.24:443 (https) · tcp
- systemd-resolved[553 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1253 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[717 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36819978304

Profile UUID01a0f5f1-2b5a-7487-bfbc-c3a7974722df

Commit SHA6b64a45281340cdd8b9c9e7c33b6356d3ba18f80(merge ref)

Refrefs/pull/53/merge

Timestamp2026-10-01 05:30:18 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.