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
- 272
- Versions published
- 1
- First published
- Oct 2024
- Publisher
- asteroiddao
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 (2 events)
- available → available · risk low · score 0 · status available -> available, risk high -> low, score 45 -> 0
- new → available · risk high · score 45 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Dependencies24
@supercharge/promise-pool^1.7.0@textury/ardb^1.1.3arbundles^0.6.19arweave^1.15.5arweave-stream-tx^1.1.0axios^0.21.4blockweave^1.0.15clear^0.1.0cli-color^2.0.0clui^0.3.6community-js^1.1.68conf^10.0.2exponential-backoff^3.1.0fast-glob^3.2.7figlet^1.5.2fuse.js^6.4.6inquirer^8.1.2mime^2.5.2minimist^1.2.5normalize-path^3.0.0p-retry^4.6.1spdx-license-ids^3.0.10stream-chunker^1.2.8temp-dir^2.0.0