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
- 1
- First published
- Jun 2026
- Publisher
- 0dust
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
buildtsup src/cli.ts src/index.ts --format esm --dts --cleandemonode dist/cli.js demoformatprettier --write .linteslint .okfynode dist/cli.jsprepublishOnlypnpm build && pnpm test && pnpm typecheckpublish:npmnode scripts/publish-npm-readme.mjstestvitest runtypechecktsc --noEmit
Dependencies11
@modelcontextprotocol/sdk^1.13.3cheerio^1.0.0commander^12.1.0gray-matter^4.0.3minimatch^10.0.1minisearch^7.1.2p-limit^6.2.0picocolors^1.1.1robots-parser^3.0.1turndown^7.2.0zod^3.25.64