Execution Profile

garnet-labs/actions

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

Garnet Runtime Visibility/dep-install

run 41158091896

Execution chains

9 destinations · 7 processes
  • systemd
    • hosted-compute-agent[2057 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2650 · node]
              • dash
                • node[2662 · node]
                  • nodejs.org104.16.212.131:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • registry.npmjs.org104.16.6.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2615 · node]
            • github.com140.82.112.4:443 (https) · tcp
            • api.github.com140.82.112.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3505417325[2076 · provjobd3505417325]
          • 140.82.113.23:443 (https) · tcp
      • 140.82.114.23:443 (https) · tcp
    • python3.12
      • python3.12[1482 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[515 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/actions
WorkflowGarnet Runtime Visibility
Jobdep-install
Profile UUID01a18fb2-135e-7ace-b7e7-bcf0f8cd29bb
Refrefs/pull/5/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.