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
- 21
- Versions published
- 7
- First published
- Apr 2026
- Publisher
- hdevlop
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
Scripts6
buildbun scripts/build.tsbuild:cssnode scripts/build-css.mjscleanrimraf dist tsconfig.tsbuildinfodevtsup --watchtestbun testtest:watchbun test --watch
Dependencies15
@hapi/boom^10.0.1@tanstack/react-router^1.170.8@whiskeysockets/baileys^6.7.0clsx^2.1.1lucide-react^0.468.0najm-cache^1.2.10najm-core^1.2.11najm-database^1.1.15najm-event^1.1.14najm-kit^0.0.13qrcode.react^4.0.0re2js^2.8.3react-window^2.2.7recharts^2.13.0tailwind-merge^2.5.5