Execution Profile

garnet-labs/deepsec-plugin

Recorded at the kernel by Garnetfor commit 8c2c10e (merge ref)

CI/build-and-test

run 33097828326

Execution chains

11 destinations · 6 processes
  • systemd
    • hosted-compute-Runner.ListenerRunner.Worker
      • bash
        • node[2542 · node]step: Install
          • registry.npmjs.org104.16.10.34:443 (https) · tcp
        • node[2789 · node]step: Run observable demo workload
          • example.net104.20.21.8:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • node[2492 · node]
          • glb-db52c2cf8be544.github.com140.82.112.21:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
          • blob.bnz49prdstrz09a.store.core.windows57.150.4.193:443 (https) · tcpalso recorded: blob.bnz49prdstrz09a.trafficmanager.net, productionresultssa7.blob.core.windows.net
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1466608176[2014 · provjobd1466608176]
          • 140.82.113.24:443 (https) · tcp
    • python3.12
      • python3.12[1375 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[566 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/deepsec-plugin
WorkflowCI
Jobbuild-and-test
Profile UUID01a0443d-96ef-7bb1-afb5-32c732876097
Refrefs/pull/2/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.