Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 796020d (merge ref)

demo — install-time metadata reach/install

run 311319552422026-08-06 23:42 UTC

Execution chains

8 destinations · 4 processes

systemd
- hosted-compute-agent[2010 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2643 · node]step: Read manifest and install pinned tarball
        registry.npmjs.org104.16.9.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2592 · node]
        github.com140.82.114.3:443 (https) · tcp
        api.github.com140.82.114.5:443 (https) · tcp
        release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2720977271[2029 · provjobd2720977271]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-2a3c35-public-internal.githubapp.com140.82.112.23:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
  - 140.82.113.23:443 (https) · tcp
  - 140.82.114.24:443 (https) · tcp

Run details

Repositorygarnet-labs/posthog

Workflowdemo — install-time metadata reach

Jobinstall

Run ID31131955242

Profile UUID019fd974-8a50-7f7d-88a3-f072c7c6d778

Commit SHA796020dba5ad707048c79bc2915099975840f9f0(merge ref)

Refrefs/pull/94/merge

Timestamp2026-08-06 23:42:01 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.