Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 6fb915b (merge ref)

App install/install

run 36815737530

Execution chains

16 destinations · 7 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[1889 · Runner.Worker]
          • bash
            • node[2324 · node]step: Install dependencies (lifecycle scripts execute here)
              • dash
                • node[2336 · node]
                  • bin.equinox.io13.248.244.96:443 (https) · tcpalso recorded: bin.equinox.io.herokudns.com
                  • 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)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3359066421[1831 · provjobd3359066421]
          • 140.82.112.23:443 (https) · tcp
    • python3.12
      • python3.12[1162 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[417 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[637 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5be-d457-7a6d-98c4-6117b1a3d6d1
Refrefs/pull/9/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.