Execution Profile

garnet-labs/express

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

App install/install

run 36820125435

Execution chains

9 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2377 · node]step: Install dependencies (lifecycle scripts execute here)
            • dash
              • dash
                • node[2390 · node]
                  • nodejs.org104.16.213.131:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.1.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2854444978[1868 · provjobd2854444978]
          • 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
    • systemd-resolved[428 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1179 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[643 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5f2-9f9f-7a0d-9fa3-a913ad9de3d8
Refrefs/pull/59/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.