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
- 5
- First published
- Apr 2026
- Publisher
- zywavepobrien
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":["@zywave/[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":["@zywave/[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
Scripts8
analyzenpm run build:databuildnpm run build:tsbuild:datanode scripts/build-data.mjsbuild:tstsc --build tsconfig.jsondevnpm run build && npm run build:data && npx cross-env CLIENT_PORT=6284 SERVER_PORT=6287 npx @modelcontextprotocol/inspector node dist/index.jsprepacknpm run build && npm run build:datastartnode dist/index.jstestnpm run build && npm run build:data && node --test test/*.test.mjs
Dependencies5
@modelcontextprotocol/sdk^1.29.0@zywave/zui-app-styles^4.3.1-pre.0@zywave/zui-base-styles^4.3.2-pre.0@zywave/zui-components-all^4.0.59-pre.13zod^3.25.0