Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 6cda3f2 (merge ref)

Garnet Runtime Visibility/install-test

run 44020075726

Execution chains

17 destinations · 7 processes
  • systemd
    • hosted-compute-Runner.ListenerRunner.Worker
      • bash
        • node[2650 · node]
          • registry.npmjs.org104.16.0.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • uv[2731 · uv]step: Let sensor settle
          • dualstack.python.map.fastly.net151.101.128.223:443 (https) · tcpalso recorded: files.pythonhosted.org
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • uv[2785 · uv]step: Let sensor settle
          • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
        • uv[2814 · uv]
          • dualstack.python.map.fastly.net151.101.192.223:443 (https) · tcpalso recorded: files.pythonhosted.org
    • systemd-resolve[220 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • Daemon
      • ExtHandler[1247 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-network[725 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1e7da-0172-7073-8907-7dd4042de609
Refrefs/pull/102/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.