Execution Profile

garnet-labs/express

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

App install/install

run 36815872698

Execution chains

15 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2365 · node]step: Install dependencies (lifecycle scripts execute here)
            • dash
              • node[2377 · node]
                • dash
                  • node[2389 · node]
                    • storage.googleapis.com209.85.200.207:443 (https) · tcp
                    • localhost127.0.0.53:53 (dns) · udp(dns resolver)
                • storage.googleapis.com64.233.181.207: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
        • provjobd4251568453[1877 · provjobd4251568453]
          • 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[1323 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[428 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5c0-7872-7de5-b59d-4a416ce71603
Refrefs/pull/20/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.