Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 79c7a15 (merge ref)

App install/install

run 36820168778

Execution chains

6 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[1945 · Runner.Worker]
          • bash
            • node[2369 · node]step: Install dependencies (lifecycle scripts execute here)
              • registry.npmjs.org104.16.2.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1865322147[1886 · provjobd1865322147]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1218 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[436 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5f3-1f05-7a9a-a109-e072658dd614
Refrefs/pull/63/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.