Package evidence

@pnpm/[email protected]

no findings

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published: 500Mature · −50% score
First published: Jan 2020
Publisher: pnpmuser

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarball Add to CI gate

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@pnpm/[email protected]"],"fail_on":"review"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@pnpm/[email protected]"],"fail_on":"review"}'

Publisherpnpmuser

Artifact bytes17,158

Previous version1008.0.17

Published2026-06-11T17:01:11.561Z

SHA-2565e6992be43a00c92e90c53faf8f1be5ab79e66c174a5d878e62c0e4c0bed5057

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low

5h agoLast checked

lowRisk

0Score

1008.0.18Version

Status history (1 event)

new → available5h ago · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts4

_testjest
compiletsc --build && pnpm run lint --fix
linteslint "src/**/*.ts" "test/**/*.ts"
testpnpm run compile && pnpm run _test

Dependencies34

@pnpm/builder.policy1000.1.3
@pnpm/calc-dep-state1003.0.6
@pnpm/cli-utils1001.3.14
@pnpm/common-cli-options-help1000.0.2
@pnpm/config1004.11.4
@pnpm/constants1001.3.1
@pnpm/core-loggers1001.0.10
@pnpm/dependency-path1001.1.11
@pnpm/deps.graph-sequencer1000.0.0
@pnpm/error1000.1.0
@pnpm/exec.pkg-requires-build1000.0.17
@pnpm/get-context1001.2.11
@pnpm/lifecycle1001.0.39
@pnpm/link-bins1000.3.9
@pnpm/lockfile.types1002.1.2
@pnpm/lockfile.utils1004.0.6
@pnpm/lockfile.walker1001.0.28
@pnpm/modules-yaml1002.0.2
@pnpm/normalize-registries1000.1.10
@pnpm/npm-package-arg^2.0.0
@pnpm/read-package-json1000.1.9
@pnpm/sort-packages1000.0.17
@pnpm/store-connection-manager1002.3.23
@pnpm/store-controller-types1004.5.3
@pnpm/store.cafs1000.1.6
@pnpm/types1001.3.1
@pnpm/workspace.find-packages1000.0.69
load-json-file^6.2.0
mem^8.1.1
p-limit^3.1.0
…and 4 more.