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
- 5
- Versions published
- 3
- First published
- Apr 2026
- Publisher
- prabindersinghh
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
Scripts9
buildtscdevtsc --watchevalnpx tsx evals/run-evals.tseval:reportnpx tsx evals/report.tslinttsc --noEmitprepublishOnlynpm run buildstartnode dist/bin/cmdr.jstestvitest runtest:watchvitest
Dependencies14
chalk^5.3.0highlight.js^11.11.1inknpm:@jrichman/[email protected]ink-spinner^5.0.0ink-text-input^6.0.0lowlight^3.3.0marked^14.0.0marked-terminal^7.2.0ora^8.0.0react^19.2.0smol-toml^1.6.1string-width^8.1.0strip-ansi^7.1.0zod^3.23.0