Execution Profile

garnet-labs/pnpm

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

Garnet DNS egress/install

run 33937809760

Execution chains

6 destinations · 2 processes
  • systemdbashbashbashbashRunner.ListenerRunner.Worker
    • bash
      • pnpm[4620 · pnpm]step: Path A - install a two-dependency fixture (cp -r .github/garnet/dns-egress "$RUNNER_TEMP/fixture-install")
        • 1.1.1.1:53 (dns) · udp
        • 104.16.8.34:443 (https) · tcp
        • 104.16.9.34:443 (https) · tcp
      • pnpm[4643 · pnpm]step: Path B - packageManager pin fetch by the installed binary
        • 104.16.3.34:443 (https) · tcp
        • 104.16.4.34:443 (https) · tcp
        • 104.16.7.34:443 (https) · tcp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet DNS egress
Jobinstall
Run ID33937809760
Profile UUID01a06f4c-9193-7ad8-bc7a-4da15a37a027
Commit SHAf263cf9f908f9e5ae50c60a2d7fd883ed269c770(merge ref)
Refrefs/pull/40/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