PkgRadar

Package evidence

@npmcli/[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
226Mature · −50% score
First published
Jan 2020
Publisher
owlstronaut

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.

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":["@npmcli/[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":["@npmcli/[email protected]"],"fail_on":"review"}'
Publisherowlstronaut
Artifact bytes143,361
Previous version9.5.0
Published2026-05-20T20:27:46.634Z
SHA-25667de32d6119c27f305c1957a2bd7c8671cc28ef022cfb57540fc87514411c458

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
Last checked
lowRisk
0Score
9.6.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts11
  • benchcleanrm -rf scripts/benchmark/*/
  • benchmarknode scripts/benchmark.js
  • eslinteslint "**/*.{js,cjs,ts,mjs,jsx,tsx}"
  • lintnpm run eslint
  • lintfixnpm run eslint -- --fix
  • postlinttemplate-oss-check
  • posttestnpm run lint
  • snaptap
  • template-oss-applytemplate-oss-apply --force
  • testtap
  • test-proxyARBORIST_TEST_PROXY=1 tap --snapshot
Dependencies34
  • @gar/promise-retry^1.0.0
  • @isaacs/string-locale-compare^1.1.0
  • @npmcli/fs^5.0.0
  • @npmcli/installed-package-contents^4.0.0
  • @npmcli/map-workspaces^5.0.0
  • @npmcli/metavuln-calculator^9.0.2
  • @npmcli/name-from-folder^4.0.0
  • @npmcli/node-gyp^5.0.0
  • @npmcli/package-json^7.0.0
  • @npmcli/query^5.0.0
  • @npmcli/redact^4.0.0
  • @npmcli/run-script^10.0.0
  • bin-links^6.0.0
  • cacache^20.0.1
  • common-ancestor-path^2.0.0
  • hosted-git-info^9.0.0
  • json-stringify-nice^1.1.4
  • lru-cache^11.2.1
  • minimatch^10.0.3
  • nopt^9.0.0
  • npm-install-checks^8.0.0
  • npm-package-arg^13.0.0
  • npm-pick-manifest^11.0.1
  • npm-registry-fetch^19.0.0
  • pacote^21.0.2
  • parse-conflict-json^5.0.1
  • proc-log^6.0.0
  • proggy^4.0.0
  • promise-all-reject-late^1.0.0
  • promise-call-limit^3.0.1
  • …and 4 more.