Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 405b48d (merge ref)

App install/install

run 36815737927

Execution chains

12 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2626 · node]step: Install dependencies (lifecycle scripts execute here)
            • dash
              • node[2646 · node]
                • binaries-failover.prisma.sh104.20.43.103:443 (https) · tcpalso recorded: binaries.prisma.sh, r2.prisma.sh, r2.prisma.sh.cdn.cloudflare.net
                • 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
        • provjobd562105980[2085 · provjobd562105980]
          • 20.75.202.224:443 (https) · tcp
    • systemd-resolved[500 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1324 · python3.12]
        • python3.12[2701 · python3.12]
          • 168.63.129.16:32526, 80 (http) · tcp
          • 169.254.169.254:80 (http) · tcp(cloud metadata)
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5be-e44c-7947-a311-38a389246a7a
Refrefs/pull/7/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.