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
- May 2026
- Publisher
- suntc
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
Scripts7
buildtscconvert-testtsx src/cli/index.ts convert verify-work/dashboard.html --out verify-work/outputdevtsx watch src/cli/index.tsprepublishOnlynpm run buildtestvitest runtest-schematsx verify-work/test_schema.tstest:watchvitest
Dependencies15
@vitejs/plugin-react^4.7.0@vitejs/plugin-vue^6.0.7cheerio^1.2.0commander^12.1.0cosmiconfig^9.0.1css-tree^3.2.1dotenv^17.4.2fast-glob^3.3.3ora^9.4.0p-limit^7.3.0prettier^3.8.3react^18.3.1react-dom^18.3.1vite^6.0.0ws^8.20.1