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
- 14
- First published
- Jan 2026
- Publisher
- chiragmer
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":["@testorgxyz/[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":["@testorgxyz/[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
buildtsc -bcleanrimraf distlinteslint . --ext .tspostpackrimraf oclif.manifest.jsonprepacknpm run clean && npm run build && oclif manifest && oclif readmetestnpx tsx node_modules/mocha/bin/mocha.js --forbid-only --timeout 10000 "test/**/*.test.ts"versionoclif readme && git add README.md
Dependencies9
@inquirer/prompts^8.2.0@oclif/core^4.0.0@oclif/plugin-help^6.0.0@oclif/plugin-plugins^5.0.0@oclif/plugin-update^4.0.0boxen^8.0.1chalk^5.6.2cli-table3^0.6.5validator^13.15.26