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
- 15
- Versions published
- 5
- First published
- May 2026
- Publisher
- chris2001
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
Scripts8
buildnode ./scripts/build.mjsdevnode --enable-source-maps dist/cli.jsprepublishOnlynpm run buildtestbun run test:srctest:artifactbun run build && vitest run -c vitest.artifact.config.tstest:srcvitest run -c vitest.config.tsverifybun run test:src && bun run verify:build && bun run test:artifactverify:buildtsc -p tsconfig.json --noEmit
Dependencies13
@clack/prompts1.4.0adm-zip^0.5.17arktype2.2.0commander14.0.3fflate0.8.2ignore7.0.5json52.2.3mime4.1.0ora9.4.0p-retry8.0.0picocolors^1.1.1semver7.8.0undici7.25.0