Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 7743f8b (merge ref)

App install/install

run 36817255560

Execution chains

8 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2385 · node]step: Install dependencies (lifecycle scripts execute here)
            • dash
              • dash
                • node[2398 · node]
                  • nodejs.org104.16.213.131:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd4173619940[1882 · provjobd4173619940]
          • 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[1320 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[485 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[650 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5d0-ece2-7dcc-9b40-e23695f4fd5b
Refrefs/pull/52/merge
Timestamp

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.