Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 56af2d4 (merge ref)

Dependency install and test (recorded)/install-test

run 422701155912026-11-06 18:23 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - node[2404 · node]
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3801259012[1897 · provjobd3801259012]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1284 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[458 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[649 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/litellm

WorkflowDependency install and test (recorded)

Jobinstall-test

Run ID42270115591

Profile UUID01a1b21a-08f0-7ca3-b7eb-218a7c3551da

Commit SHA56af2d49632e08f2abd6da5d019c5978f00f9aaa(merge ref)

Refrefs/pull/70/merge

Timestamp2026-11-06 18:23: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.