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
- 9
- First published
- Jun 2026
- Publisher
- uthyagent
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
Scripts8
generate:assertionsnode src/index.js generate:assertions https://example.comprovisionnode src/index.js provision ./testsrecord:tracenode src/index.js record:trace https://example.com -d 5shellnode src/index.js shellstartnode src/index.jstestnode --test tests/*.test.jstest:flakinessnode src/index.js test:flakiness https://example.com --iterations 3test:visualnode src/index.js test:visual https://example.com --update-baseline
Dependencies8
axe-core^4.9.1axios^1.6.0chrome-launcher^1.0.0commander^12.0.0js-yaml^4.1.0lighthouse^11.0.0playwright^1.44.0pngjs^7.0.0