Execution Profile

garnet-org/action

Kernel-recorded by the Garnet eBPF sensorpinned to commit e76e58f (merge ref)

CI/build-and-verify

run 31130101009

Network Egress

6 destinations · 7 flows · 6 processes
recorded without an execution chain:no_bad_egress_domain
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2327 · node]step: 3. Install dependencies
              • registry.npmjs.org104.16.3.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2295 · node]runner infrastructure
            • api.github.com140.82.114.6:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd758777199[1824 · provjobd758777199]runner infrastructure
          • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcpalso recorded: hosted-compute-watchdog-prod-eus-02.githubapp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[380 · systemd-resolved]runner infrastructure
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1186 · python3.12]runner infrastructure
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[641 · systemd-networkd]runner infrastructure
      • ip6-allroutersff02::2:0 (reserved) · icmpv6

Assertions

2 hits
ATTENTIONno_bad_egress_domain
FAILno_code_injection_via_proc_memory
Workload
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID019fd959-146a-7cf5-9b0a-87ae119a07e3
Refrefs/pull/82/merge
Timestamp
💡 How to read this
  • Runner.Worker
    • bash
      • curl
        • example.com
        • localhost(dns resolver)

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.