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
- 4
- First published
- Apr 2026
- Publisher
- mawdbotsonsolana
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
buildtscbuild:bunbun run tscdevbun run build && node dist/index.jsdev:tsxtsx src/index.tsinstall:bunbun installlinteslint . --ext .js,.jsx,.ts,.tsxstartnode dist/index.jsstart:bunbun run dist/index.jstypechecktsc --noEmit
Dependencies15
@modelcontextprotocol/sdk^1.17.0axios^1.7.0cfonts^3.3.0chalk^5.3.0commander^12.0.0dotenv^16.4.0enquirer^2.4.1fs-extra^11.2.0ink^4.4.1marked^15.0.12marked-terminal^7.3.0openai^5.10.1react^18.3.1ripgrep-node^1.0.0tiktoken^1.0.21