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
- 10
- First published
- Mar 2026
- Publisher
- koder15
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
Scripts7
checktsc -p tsconfig.build.json --noEmitcleanrm -rf distdistbun clean && tsc -p tsconfig.build.jsonkey:generatebun ./src/pipes/crypto/genkey.ts --genkeylinterbiome check ./srclinter:fixbiome check ./src --writelinter:fixfbiome check ./src --write --unsafe
Dependencies13
@faker-js/faker^10.4.0@hono/zod-openapi^1.4.0@scalar/hono-api-reference^0.10.20cac^7.0.0chalk^5.6.2dotenv^17.4.2dotenv-expand^13.0.0hono^4.12.23hono-rate-limiter^0.5.3lib15link:libsodium-wrappers^0.8.4ora^9.4.0prompts^2.4.2