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
- 940
- Versions published
- 30
- First published
- May 2026
- Publisher
- theanshsonkar
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
Scripts4
testnode test/test.jstest:bench-cinode test/bench-ci.jstest:benchmarknode test/benchmark.jstest:correctnessnode test/correctness.js
Dependencies14
@agentclientprotocol/sdk^0.22.1@babel/parser^7.29.3@modelcontextprotocol/sdk^1.0.0better-sqlite311.7.0chokidar^3.6.0tree-sitter0.25.0tree-sitter-c-sharp0.21.3tree-sitter-cpp0.23.4tree-sitter-go0.25.0tree-sitter-java0.23.5tree-sitter-javascript0.25.0tree-sitter-python0.25.0tree-sitter-rust0.24.0tree-sitter-typescript0.23.2