PkgRadar

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.

Weekly downloads
3
Versions published
2
First published
Oct 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.

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 bytes1,671,748
Previous version1.0.10
Published2026-05-26T00:59:46.697Z
SHA-2567b7fa80f436a7c3ba92c199771600f484e206a1408dfa18d6c204ffa9813fedf

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 1.0.11 vs 1.0.10: "./tools/setup"

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.0.11Version

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 55 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.0.11 vs 1.0.10: "./tools/setup"40
mediumLarge Javascript Payloadpackage/bundles/web.bundle.min.js2179096 bytes10
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.0.11 vs 1.0.10: "./tools/setup"40
mediumLarge Javascript Payloadpackage/bundles/web.bundle.min.js2179096 bytes10
lowInstall-time lifecycle scriptpackage.jsonpreinstall="./tools/setup"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./tools/setup
  • 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