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
- 88
- Versions published
- 35
- First published
- Feb 2026
- Publisher
- esakkimuthu1512
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":["@zohodesk/[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":["@zohodesk/[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
buildbabel src -d build/src --copy-files && babel index.js --out-file build/index.jscleanrm -rf build && npm run buildprepublishOnlynpm run buildtestnode --experimental-vm-modules node_modules/.bin/jest
Dependencies15
@babel/core7.29.0@babel/preset-env7.29.0@jest/core30.2.0@jest/types30.2.0@testing-library/react12.1.5@types/jest29.5.12@types/react16.14.70@types/react-dom16.9.25babel-jest30.2.0identity-obj-proxy3.0.0jest30.2.0jest-cli30.2.0jest-environment-jsdom30.2.0jest-html-reporter4.3.0jest-transform-stub2.0.0