Execution Profile

garnet-labs/express

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

App install/install

run 36816794651

Execution chains

6 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2618 · node]step: Install dependencies (lifecycle scripts execute here)
            • registry.npmjs.org104.16.5.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3030110968[2076 · provjobd3030110968]
          • 20.75.202.224:443 (https) · tcp
    • systemd-resolved[493 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1384 · python3.12]
        • 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 UUID01a0f5cb-841e-7041-aa9c-dc25e37a5f56
Refrefs/pull/50/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.