Execution Profile

garnet-labs/posthog

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

Vendored packages/install

run 31542155044

Execution chains

9 destinations · 7 processes
  • systemd
    • hosted-compute-agent[1971 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2505 · node]step: Install pinned tarball
              • registry.npmjs.org104.16.9.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2455 · node]
            • api.github.com140.82.116.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
            • github.com20.29.134.23:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd455572109[1986 · provjobd455572109]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1341 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[575 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[715 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/posthog
WorkflowVendored packages
Jobinstall
Profile UUID019ff2ed-caa5-7dd9-9ab4-a6786c38e8cd
Refrefs/pull/123/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.