Execution Profile

garnet-labs/express

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

App install/install

run 368207137412026-10-01 05:39 UTC

Execution chains

7 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2380 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.10.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd4066747195[1877 · provjobd4066747195]
      - 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
- systemd-resolved[399 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1234 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[639 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36820713741

Profile UUID01a0f5f9-3b69-743f-8b3e-c0d3a20c3954

Commit SHAff9d4d4afe5445898563c0794c202794494bec2b(merge ref)

Refrefs/pull/84/merge

Timestamp2026-10-01 05:39:06 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.