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
- 1
- First published
- Jun 2026
- Publisher
- jamse_dev
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
Scripts5
lintstandardtestnpm run lint && npm run test-ci && npm run test-browsertest-browsernode tests/browser/start.jstest-citaper tests/test-*.jstest-covnyc --reporter=lcov tape tests/test-*.js
Dependencies21
aws-sign2~0.7.0aws4^1.8.0axios^1.14.0caseless~0.12.0combined-stream~1.0.6extend~3.0.2forever-agent~0.6.1form-data~2.3.2har-validator~5.1.3http-signature~1.2.0is-typedarray~1.0.0isstream~0.1.2json-stringify-safe~5.0.1mime-types~2.1.19oauth-sign~0.9.0performance-now^2.1.0qs~6.5.2safe-buffer^5.1.2tough-cookie~2.5.0tunnel-agent^0.6.0uuid^3.3.2