Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 9bcbbf4 (merge ref)

Garnet Runtime Visibility/install-test

run 44012278972

Execution chains

17 destinations · 5 processes
  • systemd
    • hosted-compute-
      • Runner.ListenerRunner.Worker
        • bash
          • node[2651 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • uv[2716 · 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
        • provjobd1257866[2031 · provjobd1257866]
          • 140.82.113.23:443 (https) · tcp
    • systemd-resolve[219 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • Daemon
      • ExtHandler[1309 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/E2B
WorkflowGarnet Runtime Visibility
Jobinstall-test
Profile UUID01a1e79c-1925-783e-b5a6-46af9a58f6b6
Refrefs/pull/95/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.