PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: preinstall="./bin/install-deps"

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
3
Versions published
2
First published
Feb 2023
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.

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 bytes966,949
Previous version0.21.0
Published2026-05-26T00:59:54.351Z
SHA-2568ef829a9d200302a14a3005cca8f61a8b4d183f8d8f86bc93bfdf1e06e7dccd7

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 0.21.1 vs 0.21.0: "./bin/install-deps"

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
0.21.1Version

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

Status history (2 events)
  1. availablenot_present · risk none · score · [email protected] not present in registry metadata
  2. newavailable · 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 0.21.1 vs 0.21.0: "./bin/install-deps"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 0.21.1 vs 0.21.0: "./bin/install-deps"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="./bin/install-deps"5

Manifest

Package metadata

Scripts1
  • preinstall./bin/install-deps
Dependencies20
  • @aws-amplify/api^5.0.14
  • @metamask/eth-sig-util^5.0.2
  • @metamask/legacy-web3^2.0.0
  • @paralleldrive/cuid2^2.2.0
  • arweave^1.11.4
  • buffer^6.0.3
  • fpjson-lang^0.1.1
  • json-logic-js^2.0.2
  • md5^2.3.0
  • ramda^0.28.0
  • redis^4.6.4
  • shortid^2.2.16
  • tweetnacl^1.0.3
  • warp-contracts1.2.48
  • warp-contracts-lmdb^1.1.9
  • warp-contracts-oldnpm:[email protected]
  • warp-contracts-plugin-subscription^1.0.5
  • warp-contracts-pubsub^1.0.5
  • weavedb-base^0.21.1
  • weavedb-contracts^0.21.0