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
- 1
- First published
- Jun 2026
- Publisher
- vinniai
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
Scripts4
buildnode -e "require('node:fs').rmSync('dist', { recursive: true, force: true })" && cross-env NODE_ENV=production vp packdevvp pack --watchtestvp test runtypechecktsc --noEmit
Dependencies16
@babel/code-frame^7.29.0@sentry/node^10.54.0agent-install0.0.5conf^15.1.0confbox^0.2.4deslop-js^0.0.21eslint-plugin-react-hooks^7.1.1jiti^2.7.0magicast^0.5.3oxlint^1.66.0oxlint-plugin-react-convex-doctor0.1.0prompts^2.4.2typescript>=5.0.4 <7vscode-languageserver^9.0.1vscode-languageserver-textdocument^1.0.12vscode-uri^3.1.0