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
- 123
- Versions published
- 2
- First published
- Jun 2026
- Publisher
- sena-labs
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
buildtsc && chmod +x dist/index.jsbuild:mcpbnode scripts/build-mcpb.mjsdevtsc --watchprepublishOnlynpm run build && npm run teststartnode dist/index.jsstart:httpnode dist/index.js --httptestnpm run build && node --test test/unit/*.test.mjs && node test/stdio-test.mjstest:stdionode test/stdio-test.mjstest:unitnode --test test/unit/*.test.mjs
Dependencies3
@modelcontextprotocol/sdk^1.29.0replicate^1.4.0zod^3.23.8