Execution Profile

garnet-labs/express

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

App install/install

run 36820641970

Execution chains

11 destinations · 7 processes
  • systemd
    • hosted-compute-agent[2091 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2186 · Runner.Worker]
          • bash
            • node[2613 · node]step: Install dependencies (lifecycle scripts execute here)
              • registry.npmjs.org104.16.11.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3621573797[2111 · provjobd3621573797]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1442 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[535 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[717 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820641970
Profile UUID01a0f5f8-72f0-7f02-80fb-8ec8437214a2
Commit SHAd3a8b9f276252b1aa58c22f94a641772e318935d(merge ref)
Refrefs/pull/82/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