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
- 19
- Versions published
- 6
- First published
- Jul 2022
- Publisher
- richardnotabene
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":["@notabene/[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":["@notabene/[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
buildtscdevtsc --watchlinteslintreleasesemantic-releasestartnode dist/cli.js
Dependencies17
@ethersproject/providers^5.6.8@ethersproject/signing-key^5.6.2@notabene/nodejs^1.11.1@notabene/pii-sdk^1.14.0@stablelib/random^1.0.1@stablelib/x25519^1.0.2chalk^5.0.1colors^1.4.0debug^4.3.4did-jwt-vc^2.1.13did-resolver^3.2.2keytar^7.9.0prettyjson^1.2.5tslib^2.4.0uuid^8.3.2y18n^5.0.8yargs^17.5.1