Execution Profile

garnet-labs/express

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

App install/install

run 36819978514

Execution chains

13 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2596 · node]step: Install dependencies (lifecycle scripts execute here)
            • dash
              • node[2609 · node]
                • api.nuget.org150.171.109.183:443 (https) · tcpalso recorded: apiprod-mscdn.afd.azureedge.net, apiprod-mscdn.azureedge.net, mr-afd-azuredge.tm-azurefd.net, nugetapiprod.trafficmanager.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
        • provjobd1707092534[2055 · provjobd1707092534]
          • 140.82.113.23:443 (https) · tcp
    • systemd-resolved[533 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1393 · 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
Run ID36819978514
Profile UUID01a0f5f1-2685-7590-863b-27285708e8e7
Commit SHAf7dc3f9bc864fa4e02f0df8f873f134066fbbba6(merge ref)
Refrefs/pull/58/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.

Read the docs