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: 298Mature · −50% score
First published: Jun 2022
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 bytes16,266

Previous version1000.3.50

Published2026-06-11T17:02:10.028Z

SHA-25670618662d82580cda8820d9336af034b239aa910c956ea9cbdd695073a3866c0

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

1000.3.51Version

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

Scripts5

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

Dependencies33

@pnpm/cli-utils1001.3.14
@pnpm/config1004.11.4
@pnpm/config.config-writer1000.1.5
@pnpm/constants1001.3.1
@pnpm/crypto.hash1000.2.2
@pnpm/error1000.1.0
@pnpm/fs.packlist1000.0.0
@pnpm/lockfile.fs1001.1.35
@pnpm/lockfile.utils1004.0.6
@pnpm/modules-yaml1002.0.2
@pnpm/parse-wanted-dependency1001.0.0
@pnpm/patching.apply-patch1000.0.9
@pnpm/pick-fetcher1001.0.1
@pnpm/plugin-commands-installation1004.10.3
@pnpm/read-package-json1000.1.9
@pnpm/read-project-manifest1001.2.7
@pnpm/store-connection-manager1002.3.23
@pnpm/store-path1000.0.6
@pnpm/types1001.3.1
@pnpm/workspace.read-manifest1000.3.2
chalk^4.1.2
enquirer^2.4.1
escape-string-regexp^4.0.0
is-windows^1.0.2
make-empty-dir^3.0.2
normalize-path^3.0.0
ramdanpm:@pnpm/[email protected]
realpath-missing^1.1.0
render-help^1.0.3
safe-execa^0.1.4
…and 3 more.