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
- 117
- Versions published
- 19
- First published
- May 2026
- Publisher
- xizhiabc
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":["@peekview/[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":["@peekview/[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
Scripts11
buildtscdevtsc --watchlinteslint src/**/*.tsprepublishOnlynpm run build && npm run test:unitservenode dist/index.js servestartnode dist/index.jstestvitest runtest:e2ecd ../../frontend-v3 && npx playwright test e2e/mcp-server.spec.tstest:integrationvitest run --config vitest.integration.config.ts --reporter=verbosetest:unitvitest run tests/server.test.ts tests/client.test.ts tests/config.test.tstest:watchvitest
Dependencies8
@modelcontextprotocol/sdk1.4.0commander^14.0.3cors^2.8.5express^4.18.0pino^8.0.0uuid^11.0.0yaml^2.9.0zod^3.23.0