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
- 7
- Versions published
- 3
- First published
- Sep 2025
- Publisher
- senhordrio
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":["@e-inscricao/[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":["@e-inscricao/[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
Scripts5
buildtsc -b && vite builddevvitelinteslint .previewvite previewpublishnpm publish --access=public
Dependencies15
@hookform/resolvers^5.2.2@radix-ui/react-label^2.1.7@radix-ui/react-slot^1.2.3@tanstack/react-query^5.89.0axios^1.12.2class-variance-authority^0.7.1clsx^2.1.1lucide-react^0.544.0react^19.1.1react-dom^19.1.1react-hook-form^7.63.0react-router-dom^7.9.1react-toastify^11.0.5tailwind-merge^3.3.1zod^4.1.11