Execution Profile

garnet-labs/posthog

Kernel-recorded by the Garnet eBPF sensorpinned to commit 0c60f6f

demo — keyv Shai-Hulud install-time replica/install

run 30943456707

Network Egress

8 destinations · 8 flows · 4 processes
  • systemd
    • hosted-compute-agent[2005 · hosted-compute-agent]runner infrastructure
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2564 · node]step: 1. Read manifest and install pinned tarball
              • dash
                • node
                  • node[2587 · node]
                    • example.com172.66.147.243:443 (https) · tcp
                    • httpbin.org44.222.0.225:443 (https) · tcp
                    • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • registry.npmjs.org104.16.8.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2514 · node]runner infrastructure
            • github.com140.82.114.3:443 (https) · tcp
            • api.github.com140.82.114.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
Workload
Repositorygarnet-labs/posthog
Workflowdemo — keyv Shai-Hulud install-time replica
Jobinstall
Run ID30943456707
Profile UUID019fce41-777e-7c8a-b6af-b95345080ccf
Commit SHA0c60f6ff9cc4d19f69e5ca4a7faa46fe9dc163ff
Timestamp
💡 How to read this
  • Runner.Worker
    • bash
      • curl
        • example.com
        • localhost(dns resolver)

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.

Read the docs