Execution Profile

garnet-labs/E2B

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

Garnet Runtime Visibility/install-test

run 44466933519

Execution chains

19 destinations · 6 processes
  • systemd
    • hosted-compute-
      • Runner.ListenerRunner.Worker
        • bash
          • node[2657 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • uv[2727 · 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)
      • sudo
        • provjobd2864605[1994 · provjobd2864605]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-gccus02-02.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • Daemon
      • ExtHandler[1229 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolve[231 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[728 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1f254-6381-78d2-8faf-47b63f4a71d3
Refrefs/pull/106/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.