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
- 115Mature · −50% score
- First published
- Jul 2016
- Publisher
- box-npm
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
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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"}'Why flagged
What the scanner saw
Known Indicator Filename: package/lib/bundle.js
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk review · score 16 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Known Indicator Filename | package/lib/bundle.js | package/lib/bundle.js | 45 |
| medium | Large Javascript Payload | package/lib/bundle.js | 2328362 bytes | 10 |
Manifest
Package metadata
Scripts7
buildnpm run build:cjs && npm run build:esmbuild:cjstsc --project tsconfig.json && tsc-alias -p tsconfig.jsonbuild:esmtsc --project tsconfig.esm.json && tsc-alias -p tsconfig.esm.jsonpostbuildrollup -cpostbuild:esmnode ./scripts/update-esm.mjsstartecho "Error: no start specified" && exit 1testjest
Dependencies8
buffer^6.0.3form-data^4.0.4hash-wasm^4.12.0jose^5.2.2node-fetch^2.6.3proxy-agent^6.4.0tslib^2.6.2uuid^11.1.1