Execution Profile

garnet-labs/express

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

App install/install

run 368151624012026-10-01 04:27 UTC

Execution chains

7 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2553 · node]step: Install dependencies (lifecycle scripts execute here)
        registry.npmjs.org104.16.11.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3229671347[2034 · provjobd3229671347]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- systemd-resolved[555 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1379 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-networkd[723 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/express

WorkflowApp install

Jobinstall

Run ID36815162401

Profile UUID01a0f5b8-20d3-7e3c-8873-bb3b8cf52243

Commit SHAe4ae6628b1cae4eea26fe02b713cdd0dbaf426e8(merge ref)

Refrefs/pull/3/merge

Timestamp2026-10-01 04:27:59 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.