PkgRadar

Package evidence

[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
53Mature · −50% score
First published
May 2011
Publisher
ljharb

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 tarballAdd 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":["[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":["[email protected]"],"fail_on":"review"}'
Publisherljharb
Artifact bytes13,699
Previous version4.0.2
Published2025-06-05T14:51:11.479Z
SHA-25685ab0caaa5d41dced5933759ad763b7af3755c7a2af6ddd15ecec0b5fed67a3d

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
4.0.3Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts21
  • browserbrowserify -t browserify-istanbul test/run-browser.js | obake --coverage
  • checkistanbul check-coverage coverage/coverage*.json
  • ci-lintis-node-modern 8 && npm run lint || is-node-not-modern 8
  • ci-testnpm run tests-only && npm run browser && npm run report
  • debugverbose=1 ./test/run.js
  • filespkgfiles --sort=name
  • get-versionnode -e "console.log(require('./package.json').version)"
  • linteslint --ext=js,mjs .
  • postpublishnpm run restore-readme
  • posttestnpx npm@'>=10.2' audit --production
  • posttests-onlyistanbul report lcov text
  • predebugrimraf coverage test/tmp
  • prepublishnot-in-publish || npm run prepublishOnly
  • prepublishOnlynpm run update-readme
  • pretestnpm run lint
  • pretests-onlyrimraf coverage test/tmp
  • reportistanbul report lcov text
  • restore-readmemv README.md.bak README.md
  • testnpm run tests-only
  • tests-onlyistanbul cover test/run.js
  • update-readmesed -i.bak 's/\/master\.svg/\/v'$(npm --silent run get-version)'.svg/g' README.md
Dependencies5
  • asynckit^0.4.0
  • combined-stream^1.0.8
  • es-set-tostringtag^2.1.0
  • hasown^2.0.2
  • mime-types^2.1.12