Execution Profile

aleesikander/express

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

ci/test

run 31212595622

Network Egress

5 destinations · 6 flows · 6 processes
recorded without an execution chain:no_bad_egress_domain
  • systemd
    • hosted-compute-agent[1995 · hosted-compute-agent]runner infrastructure
      • Runner.Listener
        • Runner.Worker[2107 · Runner.Worker]runner infrastructure
          • bash
            • node[2656 · node]step: 3. Install dependencies
              • registry.npmjs.org104.16.1.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd827052426[2011 · provjobd827052426]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)
      • 140.82.116.3:443 (https) · tcp
    • systemd-resolved[495 · systemd-resolved]runner infrastructure
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1357 · python3.12]runner infrastructure
        • 168.63.129.16:32526, 80 (http) · tcp

Assertions

2 hits
ATTENTIONno_bad_egress_domain
FAILno_code_injection_via_proc_memory
Workload
Repositoryaleesikander/express
Workflowci
Jobtest
Profile UUID019fddc1-c54b-7cb2-adb6-c4bf44dffd48
Refrefs/pull/4/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.