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
- May 2026
- Publisher
- abishek-meyicloud
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
Scripts3
buildtsc && vite builddevvite build --watchtypechecktsc --noEmit
Dependencies18
@hookform/resolvers^3.9.0@radix-ui/react-dialog^1.1.15@radix-ui/react-label^2.1.8@radix-ui/react-popover^1.1.15@radix-ui/react-scroll-area^1.2.10@radix-ui/react-separator^1.1.8@radix-ui/react-slot^1.2.4@tanstack/react-table^8.21.3axios^1.7.2class-variance-authority^0.7.1clsx^2.1.1cmdk^1.1.1date-fns^4.1.0lucide-react^0.469.0react-day-picker^9.11.1react-hook-form^7.52.0tailwind-merge^2.5.4zod^3.23.8