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
- 23
- First published
- Mar 2026
- Publisher
- kaminoikari
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
bundle:claude-aibash scripts/build-claude-ai-bundle.shevalnpm run eval:trigger && npm run eval:behavioraleval:behavioralpython3 evals/run_behavioral_eval.py --runs 3 --workers 2 --fail-on criticaleval:debtpython3 scripts/eval-debt-report.pyeval:quickpython3 evals/run_behavioral_eval.py --runs 1 --workers 2 --fail-on criticaleval:testpython3 -m unittest evals.test_compute_eval_scoreeval:triggerpython3 evals/run_trigger_test.py --runs 3 --workers 4 --fail-on criticaleval:zh-TWpython3 evals/run_behavioral_eval.py --eval-file evals/evals-zh-TW.json --runs 3 --workers 2 --fail-on critical