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
- 564
- Versions published
- 24
- First published
- Apr 2026
- Publisher
- shikhkarim
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
buildnpm run build:esm && npm run build:cjs && npm run postbuild:cjsbuild:cjstsc -p tsconfig.cjs.jsonbuild:esmtsc -p tsconfig.jsonpostbuild:cjsnode -e "require('node:fs').writeFileSync('dist-cjs/package.json', '{\"type\":\"commonjs\"}\n')"samplenode samples/runSample.mjstestnpm run build && node --test tests/*.test.mjs
Dependencies5
ajv^8.20.0ajv-formats^3.0.1axios^1.6.0crypto-js^4.2.0lodash^4.18.1