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
- 19
- Versions published
- 4
- First published
- Apr 2026
- Publisher
- mrslbt
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 && npm run build:assetsbuild:assetsnode -e "import('fs').then(({cpSync}) => cpSync('src/assets', 'dist/assets', {recursive: true}))"devtsc --watchprepublishOnlynpm run buildpreview:charttsx src/preview-chart.tsxpreview:covertsx src/preview-cover.tsxpreview:reporttsx src/preview-research-report.tsxstartnode dist/index.jstestnode test/integration.test.mjs
Dependencies7
@modelcontextprotocol/sdk^1.29.0@react-pdf/renderer^4.5.1mdast-util-to-string^4.0.0react^19.2.0remark-gfm^4.0.1remark-parse^11.0.0unified^11.0.5