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.
- Versions published
- 3
- First published
- Jul 2020
- Publisher
- adobrawy
- External confirmation
- MAL-2025-22076OSV match · pinned to high regardless of other signals
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":"high"}'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":"high"}'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 high · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Dependencies13
@apidevtools/json-schema-ref-parser^9.0.3array-back^3.1.0camel-case^4.1.1command-line-args^5.1.1command-line-usage^6.1.0h1-cli-framework^1.0.1-alpha.1jmespath^0.15.0js-yaml^3.14.0jsonwebtoken^8.5.1meant^1.0.1node-fetch^2.6.0tabula^1.10.0untildify^4.0.0