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
- 167
- Versions published
- 27
- First published
- Mar 2026
- Publisher
- arindam1729
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
buildnext builddevnext devlinteslintstartnext start
Dependencies23
@tailwindcss/postcss^4@types/node^20@types/react^19@types/react-dom^19class-variance-authority^0.7.1clsx^2.1.1cmdk^1.1.1date-fns^4.1.0jszip^3.10.1lucide-react^0.575.0next16.2.2radix-ui^1.4.3react19.2.3react-day-picker^9.14.0react-dom19.2.3react-markdown^10.1.0recharts^3.7.0remark-gfm^4.0.1swr^2.4.1tailwind-merge^3.5.0tailwindcss^4tw-animate-css^1.4.0typescript^5