Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/extension-install

run 44357733280

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent[1945 · hosted-compute-agent]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2546 · node]
            • registry.npmjs.org104.16.11.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3526558311[1985 · provjobd3526558311]
          • 140.82.114.24:443 (https) · tcp
      • 140.82.114.23:443 (https) · tcp
    • python3.14
      • python3.14[1324 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[223 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobextension-install
Profile UUID01a1efae-7bd5-71e3-be39-0a3ac1132fb8
Refrefs/pull/160/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.