Package evidence

[email protected]

Large Javascript Payload: 2179096 bytes

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: 20Mature · −50% score
First published: Oct 2023
Publisher: asteroiddao

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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 tarball Add 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 bytes1,671,746

Previous version3.0.0

Published2026-05-26T00:58:48.670Z

SHA-2562b6506f5f1d49736613e1dfd0cb0d310fb4ba1953dabcbcd3483cc0b096f195e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 3.0.1 vs 3.0.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

4d agoLast checked

noneRisk

—Score

3.0.1Version

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

Status history (2 events)

available → not_present21d ago · risk none · score — · [email protected] not present in registry metadata
new → available23d ago · risk high · score 55 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	preinstall added in 3.0.1 vs 3.0.0: "./bin/install-deps"	40
medium	Large Javascript Payload	package/bundles/web.bundle.min.js	2179096 bytes	10

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	preinstall added in 3.0.1 vs 3.0.0: "./bin/install-deps"	40
medium	Large Javascript Payload	package/bundles/web.bundle.min.js	2179096 bytes	10
low	Install-time lifecycle script	package.json	preinstall="./bin/install-deps"	5

Manifest

Package metadata

Scripts16

buildyarn run clean && tsc -b tsconfig.json && yarn compile:types
bundle:webnode bundle.js
cleanrimraf ./lib
compile:typestsc -b tsconfig.types.json
formatprettier --write 'src/**/*.ts'
linteslint . --ext .ts
lint:fixeslint . --ext .ts --fix
postversiongit push origin HEAD && git push --tags
preinstall./bin/install-deps
prepublishOnlyyarn lint:fix
prettier:formatprettier --config .prettierrc 'src/**/*.ts' --write
preversionyarn lint && yarn build
testjest
test:unitjest ./src/__tests__/unit
versionyarn format && git add -A src
yalc:publishyarn build && yalc publish --push

Dependencies2

arbundles^0.10.0
node-stdlib-browser^1.2.0