Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 5e37493 (merge ref)

Garnet Runtime Visibility/install-test

run 44156219837

Execution chains

17 destinations · 6 processes
  • systemd
    • hosted-compute-Runner.Listener
      • Runner.Worker[2286 · Runner.Worker]
        • bash
          • node[2921 · node]step: Let sensor settle
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • uv[2997 · 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)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • Daemon
      • ExtHandler[1422 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolve[220 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[793 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1eaee-dc4f-73e0-821b-d0a0d2e8d1a2
Refrefs/pull/104/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.