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
99Mature · −50% score
First published
Mar 2020
Publisher
naugtur

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"}'
Publishernaugtur
Artifact bytes20,326
Previous version11.1.1
Published2026-05-13T21:40:57.519Z
SHA-25622f3a948c6c87161efbff4cb5cc7986125923b311f9c04a1f7a81b24da8ce1f9

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
11.1.2Version
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

Scripts6
  • lint:depsdepcheck
  • testnpm run test:npm; npm run test:yarn1; npm run test:resolve
  • test:npmnpm run test:prepare && ava
  • test:preparenode ./test/prepare.js
  • test:resolvecross-env LAVAMOAT_RESOLVE_NATIVE=1 npm run test:npm
  • test:yarn1cross-env COREPACK_ENABLE_PROJECT_SPEC=0 LAVAMOAT_PM=yarn@1 npm run test:prepare && cross-env COREPACK_ENABLE_PROJECT_SPEC=0 ava
Dependencies11
  • @babel/code-frame7.29.0
  • @babel/highlight7.25.9
  • @lavamoat/aa^5.0.1
  • bindings1.5.0
  • corepack0.34.6
  • htmlescape1.1.1
  • lavamoat-core^18.0.3
  • lavamoat-tofu^9.0.1
  • node-gyp-build4.8.4
  • resolve1.22.12
  • yargs17.7.2