Execution Profile

garnet-labs/express

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

App install/install

run 36820128779

Execution chains

10 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2158 · Runner.Worker]
          • bash
            • node[2637 · node]step: Install dependencies (lifecycle scripts execute here)
              • dash
                • dash
                  • node[2658 · node]
                    • nodejs.org104.16.212.131:443 (https) · tcp
                    • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • 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
        • provjobd2330453900[2096 · provjobd2330453900]
          • 140.82.112.23:443 (https) · tcp
    • python3.12
      • python3.12[1819 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[557 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Profile UUID01a0f5f2-b5ab-73b5-aaef-419db7a9efd8
Refrefs/pull/61/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.