Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit b39666b (merge ref)

Kolbo integration build/build

run 315427996172026-08-11 22:35 UTC

Execution chains

7 destinations · 5 processes

systemd
- hosted-compute-agentRunner.Listener
  - Runner.Worker
    - bash
      - node[2609 · node]step: Install pinned @kolbo/mcp (npm install --save-exact "@kolbo/mcp@${KOLBO_MCP_VERSION}")
        registry.npmjs.org104.16.5.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
    - node[2572 · node]
      - github.com140.82.112.3:443 (https) · tcp
      - api.github.com140.82.113.6:443 (https) · tcp
      - release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[527 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1767 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-networkd[738 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/posthog

WorkflowKolbo integration build

Jobbuild

Run ID31542799617

Profile UUID019ff2f7-e08d-7c77-9c64-ed3794ecb404

Commit SHAb39666b0327bf13e99ddb18360b6e39136436171(merge ref)

Refrefs/pull/101/merge

Timestamp2026-08-11 22:35:56 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.