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
- 262
- Versions published
- 3
- First published
- Jun 2026
- Publisher
- vexenbay
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 (3 events)
- available → available · risk high · score 60 · status available -> available, risk low -> high, score 0 -> 60
- available → available · risk low · score 0 · status available -> available, risk high -> low, score 60 -> 0
- new → available · risk high · score 60 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Optional dependencies5
@vexenbay/vex-mcp-darwin-arm640.2.0@vexenbay/vex-mcp-darwin-x640.2.0@vexenbay/vex-mcp-linux-arm640.2.0@vexenbay/vex-mcp-linux-x640.2.0@vexenbay/vex-mcp-win32-x640.2.0