Execution Profile

garnet-labs/express

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

App install/install

run 368167473182026-10-01 04:48 UTC

Execution chains

6 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2583 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.9.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2514699915[2098 · provjobd2514699915]
      - 20.75.202.224:443 (https) · tcp
- systemd-resolved[528 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1411 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[743 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816747318

Profile UUID01a0f5ca-e0b7-7e89-8c74-85b426677a28

Commit SHAb806a2d1d7dd444968b67a29d0045c49d7f2b6aa(merge ref)

Refrefs/pull/47/merge

Timestamp2026-10-01 04:48:28 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.