Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 41b6eea (merge ref)

demo — install-time metadata reach/install

run 311320730632026-08-06 23:44 UTC

Execution chains

8 destinations · 5 processes

systemd
- hosted-compute-agent[2032 · hosted-compute-agent]
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2576 · node]step: Read manifest and install pinned tarball
        dash
        node
        node[2595 · 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.0.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2525 · node]
        api.github.com140.82.112.6:443 (https) · tcp
        github.com140.82.114.4:443 (https) · tcp
        release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3379699539[2071 · provjobd3379699539]
      - 140.82.114.23:443 (https) · tcp
  - 140.82.114.23:443 (https) · tcp

Run details

Repositorygarnet-labs/posthog

Workflowdemo — install-time metadata reach

Jobinstall

Run ID31132073063

Profile UUID019fd976-d42b-788b-a9e4-d9756007f724

Commit SHA41b6eeae436fe1879e35807e690602cb7670433c(merge ref)

Refrefs/pull/94/merge

Timestamp2026-08-06 23:44:31 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.