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
- 738
- Versions published
- 12
- First published
- Apr 2026
- Publisher
- gronxb
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
buildtsdowndevNODE_ENV=development tsx watch src/cli.tsstartnode dist/cli.jstestvitest runtypechecktsc --noEmit
Dependencies16
@commander-js/extra-typings^14.0.0@hono/node-server^1.19.6@lydell/node-pty1.2.0-beta.12@modelcontextprotocol/sdk^1.24.0@noble/ciphers2.2.0@noble/curves2.2.0@noble/hashes2.2.0@openai/codex-sdk^0.130.0@tursodatabase/database^0.5.3base64-js1.5.1commander^14.0.3es-git^0.6.0hono^4.10.7picocolors^1.1.1qrcode-terminal^0.12.0zod^4.1.12