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.
- Weekly downloads
- 187
- Versions published
- 7
- First published
- May 2021
- Publisher
- spurreiter
Recommended action
Looks clean — keep monitoringNo 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":["[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
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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts10
allnpm-run-all test build pretty lint typesbuildnpm run clean && rollup -ccleanrm -rf dist/ coverage/linteslint .prettyprettier --write .servernode ./test/support/server.jsstart./scripts/certs.sh; DEBUG_LEVEL=debug node --watch example/index.jstestc8 -r text mochatest:devDEBUG_LEVEL=DEBUG DEBUG=*,-mocha*,-express* mochatypesrm -rf types; tsc
Dependencies4
debug-level^4.1.1express^5.2.1jsrsasign^11.1.3openid-client^6.8.0