Execution Profile

garnet-labs/express

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

App install/install

run 368162629222026-10-01 04:42 UTC

Execution chains

9 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2595 · 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
    - provjobd4136969974[2074 · provjobd4136969974]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1421 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[512 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[719 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36816262922

Profile UUID01a0f5c5-23e0-7726-943b-4d933e1866e4

Commit SHAa039c603695beae64037f004393289ef730da0df(merge ref)

Refrefs/pull/29/merge

Timestamp2026-10-01 04:42:12 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.