Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 67e82cd (merge ref)

Garnet Runtime Visibility/install-test

run 44467718644

Execution chains

21 destinations · 4 processes
  • systemd
    • hosted-compute-Runner.ListenerRunner.Worker
      • bash
        • node[2810 · node]
          • registry.npmjs.org104.16.0.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • uv[2874 · uv]
          • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolve[671 · systemd-resolve]
      • 10.0.0.2:53 (dns) · udp
    • dash
      • dash[1369 · dash]
        • 169.254.169.123:123 (ntp) · udp
        • 185.125.190.122:123 (ntp) · udp
        • 185.125.190.123:123 (ntp) · udp
        • 91.189.91.111:123 (ntp) · udp
        • 91.189.91.112:123 (ntp) · udp
        • 91.189.91.113:123 (ntp) · udp
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1f25a-bbff-7ad8-809b-1a27e2581471
Refrefs/pull/108/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.