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
- 6
- First published
- May 2026
- Publisher
- andre-na
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":["@jumpgroup/[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":["@jumpgroup/[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
startnode bin/tools.js
Dependencies16
@aws-sdk/client-cloudfront^3.924.0@aws-sdk/client-iam^3.924.0@aws-sdk/client-route-53^3.1046.0@aws-sdk/client-s3^3.924.0@aws-sdk/client-sts^3.924.0@aws-sdk/credential-provider-ini^3.924.0@inquirer/prompts^8.5.2@inquirer/select^5.2.1@jumpgroup/secret-fetcher^2.5.0cli-table3^0.6.3commander^10.0.0dotenv^16.0.0glob^10.2.2hostile^1.3.3js-yaml^4.1.0keytar^7.9.0