PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: preinstall="./dist/runtime.node"

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
2
Versions published
2
First published
Jul 2022
Publisher
asteroiddao

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Inspect tarballAdd to CI gate
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"}'
Publisherasteroiddao
Artifact bytes964,010
Previous version1.1.0
Published2026-05-26T00:59:50.473Z
SHA-25640040939bbb7c809d21efe283f4c0924a8dde005807a24ac172f65a0d402cb48

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 1.1.1 vs 1.1.0: "./dist/runtime.node"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

not present

status
Last checked
noneRisk
—Score
1.1.1Version

Latest scanner note: [email protected] not present in registry metadata

Status history (2 events)
  1. available → not_present · risk none · score — · [email protected] not present in registry metadata
  2. new → available · risk high · score 45 · status changed

Evidence

Static findings

1 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.1.1 vs 1.1.0: "./dist/runtime.node"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.1.1 vs 1.1.0: "./dist/runtime.node"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="./dist/runtime.node"5

Manifest

Package metadata

Scripts6
  • buildcross-env BABEL_ENV=production babel src --out-dir lib
  • cleanrimraf lib
  • preinstall./dist/runtime.node
  • prepublishnpm run clean && npm run build
  • testmocha --require babel-core/register --require babel-polyfill --recursive
  • test:watchnpm test -- --watch
Dependencies6
  • @metamask/eth-sig-util^4.0.1
  • arweave^1.11.4
  • eth-crypto^2.3.0
  • ethereumjs-util^7.1.5
  • ramda^0.28.0
  • warp-contracts^1.1.14