PkgRadar

Package evidence

[email protected]

no findings

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
12
First published
Jun 2026
Publisher
andrew78m

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publisherandrew78m
Artifact bytes17,751
Previous version0.9.0
Published2026-06-12T11:27:11.956Z
SHA-256f8602f847c793246d3cdad52ba5e3c3f0da0b5e03d2e85a9518c529c9e71d698

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

low
Last checked
lowRisk
0Score
0.9.1Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • build:mcpbnpm ci --omit=dev && npm run sync:manifest && node -e "require('fs').mkdirSync('../static/downloads',{recursive:true})" && npx -y @anthropic-ai/mcpb pack . ../static/downloads/poc-se-tools.mcpb
  • prepublishOnlynode --check index.js && node --check server.js
  • startnode index.js
  • sync:manifestnode -e "const fs=require('fs');const v=JSON.parse(fs.readFileSync('package.json','utf8')).version;const m=JSON.parse(fs.readFileSync('manifest.json','utf8'));m.version=v;fs.writeFileSync('manifest.json',JSON.stringify(m,null,2)+'\n');"
  • testnode --test
Dependencies2
  • @modelcontextprotocol/sdk^1.12.1
  • zod^3.24.2