Execution Profile

garnet-labs/E2B

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

Garnet Runtime Visibility/install-test

run 44017779576

Execution chains

23 destinations · 6 processes
  • systemd
    • hosted-compute-[2148 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2815 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • uv[2935 · 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)
      • 140.82.113.24:443 (https) · tcp
    • systemd-resolve[670 · systemd-resolve]
      • 10.0.0.2:53 (dns) · udp
    • dash
      • dash[1376 · 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
    • systemd-network[1098 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1e7c7-61bb-74e1-9639-1285694739a0
Refrefs/pull/98/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.