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
- 10
- Versions published
- 13
- First published
- Jan 2026
- Publisher
- nanahira
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
Scripts12
buildnest buildformatprettier --write "src/**/*.ts" "test/**/*.ts"linteslint "{src,apps,libs,test}/**/*.ts" --fixstartnest startstart:debugnest start --debug --watchstart:devnest start --watchstart:prodnode dist/maintestjesttest:covjest --coveragetest:debugnode --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBandtest:e2ejest --config ./test/jest-e2e.jsontest:watchjest --watch
Dependencies4
aragami^1.2.10argon2^0.44.0crypto-random-string3.3.1nestjs-aragami^1.2.1