Execution Profile

garnet-labs/browser-use

Recorded at the kernel by Garnetfor commit 88a8bd3 (merge ref)

Garnet Dependency Replay/python-install

run 34272402643

Execution chains

13 destinations · 6 processes
  • systemd
    • hosted-compute-
      • Runner.Listener
        • Runner.Worker
          • bash
            • uv
              • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
              • pypi.org151.101.0.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • MainThread
            • github.com140.82.114.4:443 (https) · tcp
            • api.github.com140.82.114.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2549620
          • 140.82.113.24:443 (https) · tcp
      • 140.82.112.24:443 (https) · tcp
      • 140.82.113.23:443 (https) · tcp
    • systemd-network
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/browser-use
WorkflowGarnet Dependency Replay
Jobpython-install
Run ID34272402643
Profile UUID01a0829e-266d-7bd2-ab47-9f502d6e5c80
Commit SHA88a8bd3cf0c456e06a190e560947c8b0b3997138(merge ref)
Refrefs/pull/16/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.

Read the docs