Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 040ebc5 (merge ref)

demo — install-time metadata reach/install

run 314331607382026-08-10 21:20 UTC

Execution chains

7 destinations · 3 processes

systemdhosted-compute-agentRunner.Listener
- Runner.Worker
  - bash
    - node[2602 · node]step: Read manifest and install pinned tarball
      - dash
        node
        node[2621 · node]
        example.com172.66.147.243:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
        169.254.169.254:80 (http) · tcp(cloud metadata)
      - registry.npmjs.org104.16.10.34:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - node[2551 · node]
    - api.github.com140.82.112.6:443 (https) · tcp
    - github.com140.82.114.3:443 (https) · tcp
    - release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
    - localhost127.0.0.53:53 (dns) · udp(dns resolver)

Run details

Repositorygarnet-labs/posthog

Workflowdemo — install-time metadata reach

Jobinstall

Run ID31433160738

Profile UUID019fed8c-5d2d-7be4-a009-252937504f4b

Commit SHA040ebc5def8b3e290b0bf56e8ac212a34d573a80(merge ref)

Refrefs/pull/94/merge

Timestamp2026-08-10 21:20:26 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.