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
- 1
- First published
- Jun 2026
- Publisher
- umdv
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":["@umdv/[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":["@umdv/[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
Scripts1
testecho "Error: no test specified" && exit 1
Dependencies76
accepts^2.0.0append-field^1.0.0body-parser^2.2.2buffer-from^1.1.2busboy^1.6.0bytes^3.1.2call-bind-apply-helpers^1.0.2call-bound^1.0.4concat-stream^2.0.0content-disposition^1.1.0content-type^1.0.5cookie^0.7.2cookie-signature^1.2.2debug^4.4.3depd^2.0.0dunder-proto^1.0.1ee-first^1.1.1encodeurl^2.0.0es-define-property^1.0.1es-errors^1.3.0es-object-atoms^1.1.2escape-html^1.0.3etag^1.8.1express^5.2.1finalhandler^2.1.1forwarded^0.2.0fresh^2.0.0function-bind^1.1.2get-intrinsic^1.3.0get-proto^1.0.1- …and 46 more.