Execution Profile

garnet-labs/litellm

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

Dependency install and test (recorded)/install-test

run 422700347942026-11-06 18:23 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent[2101 · hosted-compute-agent]
  - Runner.ListenerRunner.Worker
    - bash
      - node[2663 · node]
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2777603600[2120 · provjobd2777603600]
      - 20.75.202.224:443 (https) · tcp
  - 20.75.202.224:443 (https) · tcp
- python3.12
  - python3.12[1373 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[522 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/litellm

WorkflowDependency install and test (recorded)

Jobinstall-test

Run ID42270034794

Profile UUID01a1b219-c487-73d7-af0f-607559dfa876

Commit SHAf29f159e42a0a339a1e4c3c6c5bf127d713945ef(merge ref)

Refrefs/pull/59/merge

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