Execution Profile

garnet-labs/express

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

App install/install

run 36815869699

Execution chains

14 destinations · 7 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[1905 · Runner.Worker]
          • bash
            • node[2375 · node]step: Install dependencies (lifecycle scripts execute here)
              • dash
                • node[2387 · node]
                  • raw.githubusercontent.com185.199.109.133: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)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1486582837[1773 · provjobd1486582837]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • systemd-resolved[407 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1232 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[634 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5c0-6e09-7aed-ab03-32a8dcb3d53b
Refrefs/pull/21/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.