Execution Profile

pnpm/pnpm

Recorded at the kernel by Garnetfor commit bac8077

Tag/tag-in-registry

run 37154090235

Execution chains

9 destinations · 8 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • pn[4003 · pn]step: Update tag
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
          • pn[3991 · pn]step: Update tag
            • registry.npmjs.org104.16.3.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • pn[4015 · pn]step: Update tag
            • registry.npmjs.org104.16.7.34:443 (https) · tcp
        • node[3912 · node]
          • pnpm
            • pnpm[3953 · pnpm]
              • nodejs.org104.16.212.131:443 (https) · tcp
              • unofficial-builds.nodejs.org45.55.98.129:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • sudo[3903 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • registry.npmjs.org104.16.3.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1684 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • systemd-resolved[1420 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorypnpm/pnpm
WorkflowTag
Jobtag-in-registry
Run ID37154090235
Profile UUID01a1039a-99ca-77b9-9cfc-1e5e34ad557b
Commit SHAbac8077715ac5af3857b1df970a014875d89b86c
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