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
- 7
- First published
- May 2026
- Publisher
- mmgonnar
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
Scripts8
buildnext builddb:generateprisma generatedb:pushprisma db pushdevnext devlinteslintmmgnbun src/cli/index.tspredevkill -9 $(lsof -ti tcp:3000) || truestartnext start
Dependencies23
@clack/prompts^1.4.0@hookform/resolvers^5.2.2@prisma/adapter-pg^7.8.0@prisma/client^7.8.0@supabase/ssr^0.10.3@supabase/supabase-js^2.105.4@types/fs-extra^11.0.4class-variance-authority^0.7.1clsx^2.1.1fs-extra^11.3.5install^0.13.0lucide-react^1.8.0next15next-intl3.26.5next-themes^0.4.6pg^8.20.0picocolors^1.1.1react19.2.4react-dom19.2.4react-hook-form^7.73.1react-hot-toast^2.6.0tailwind-merge^3.5.0zod^4.3.6