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
10
Versions published
8
First published
Aug 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.

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 bytes965,455
Previous version0.1.6
Published2026-05-26T00:59:29.510Z
SHA-25648305b85cbf7a1f0ec042255d79b30f73d41535ff1c2e936849ad12f1897542e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 0.1.7 vs 0.1.6: "./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.1.7Version

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.1.7 vs 0.1.6: "./bin/install-deps"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 0.1.7 vs 0.1.6: "./bin/install-deps"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="./bin/install-deps"5

Manifest

Package metadata

Scripts2
  • buildrimraf dist && node ./esbuild.mjs
  • preinstall./bin/install-deps
Dependencies2
  • ramda^0.28.0
  • recoil^0.7.5