Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 73985ae (merge ref)

App install/install

run 368206237392026-10-01 05:37 UTC

Execution chains

13 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2599 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.0.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2668134008[2108 · provjobd2668134008]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1447 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[514 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[720 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36820623739

Profile UUID01a0f5f8-3392-7eba-9e3e-44fd83889bed

Commit SHA73985aea697f6d7b2cbc39949896d3e380b4eb9a(merge ref)

Refrefs/pull/81/merge

Timestamp2026-10-01 05:37:58 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.