Execution Profile

garnet-labs/deepsec-plugin

Recorded at the kernel by Garnetfor commit 7ca096e (merge ref)

CI/build-and-test

run 339064516052026-09-04 18:33 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2576 · node]step: Install
        registry.npmjs.org104.16.6.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2532 · node]
        glb-db52c2cf8be544.github.com140.82.114.21:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3081010104[2031 · provjobd3081010104]
      - 140.82.114.23:443 (https) · tcp
- python3
  - python3[1396 · python3]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[554 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-resolve[554 · systemd-resolve]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/deepsec-plugin

WorkflowCI

Jobbuild-and-test

Run ID33906451605

Profile UUID01a06db2-a511-7ddb-a188-0f246a694e47

Commit SHA7ca096e5ea79d1a8e7fa883d77cefac55c6e5704(merge ref)

Refrefs/pull/3/merge

Timestamp2026-09-04 18:33:34 UTC

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.