Execution Profile

aleesikander/express

Recorded at the kernel by Garnetfor commit 860befe

Garnet Express Baseline/express-baseline

run 310533563572026-08-05 22:36 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent[2034 · hosted-compute-agent]
  - Runner.ListenerRunner.Worker
    - bash
      - node[2648 · node]step: Install dependencies
        dash
        node[2712 · node]step: Controlled indirect npm Node HTTPS request
        example.com104.20.23.154:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd4019445745[2072 · provjobd4019445745]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-2a3c35-public-internal.githubapp.com140.82.113.23:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-01.githubapp
  - 140.82.114.23:443 (https) · tcp
- systemd-resolved[532 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1426 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositoryaleesikander/express

WorkflowGarnet Express Baseline

Jobexpress-baseline

Run ID31053356357

Profile UUID019fd412-75f3-7298-bfc7-3e5640742daf

Commit SHA860befe84ed5adab2c9af8f34cc717b1404f7125

Timestamp2026-08-05 22:36:46 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.