Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 3f70f37 (merge ref)

App install/install

run 368205012612026-10-01 05:36 UTC

Execution chains

8 destinations · 7 processes

systemd
- hosted-compute-agent[2093 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker[2172 · Runner.Worker]
      - bash
        node[2600 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.1.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3598530565[2109 · provjobd3598530565]
      - 20.75.202.224:443 (https) · tcp
  - 20.75.202.224:443 (https) · tcp
- systemd-resolved[535 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1446 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[753 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36820501261

Profile UUID01a0f5f6-f975-7c47-a1aa-e90fa914bba6

Commit SHA3f70f3735331cc8a43bc917570f8a6b7cd74d38e(merge ref)

Refrefs/pull/74/merge

Timestamp2026-10-01 05:36:38 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.