Execution Profile

aleesikander/express

Recorded at the kernel by Garnetfor commit 2910fb4

Garnet Express Baseline/express-baseline

run 310443722372026-08-05 20:31 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2630 · node]step: Install dependencies
        registry.npmjs.org104.16.7.34:443 (https) · tcp
      - node[2678 · node]step: Controlled long-lived Node HTTPS request
        example.com172.66.147.243:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1003905691[2048 · provjobd1003905691]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-2a3c35-public-internal.githubapp.com140.82.114.23:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
- systemd-resolved[531 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1466 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-networkd[721 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositoryaleesikander/express

WorkflowGarnet Express Baseline

Jobexpress-baseline

Run ID31044372237

Profile UUID019fd39f-fe01-7136-9406-4f8ab8541ff5

Commit SHA2910fb45ab989055703edb438d69b68fedeb316a

Timestamp2026-08-05 20:31:45 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.