Package evidence

[email protected]

Known Indicator Filename: package/scripts/bundle.js

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: 2
First published: May 2026
Publisher: yowaihito

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"}'

Publisheryowaihito

Artifact bytes46,590

Previous version0.1.2

Published2026-05-25T07:30:23.583Z

SHA-2569dc1245cf29aff4c1aee8c9eacea8fcc278f4c88996d8b5f1b55215a0c0758fa

Why flagged

What the scanner saw

Known Indicator Filename: package/scripts/bundle.js

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

Availability ledger

not present

status

3d agoLast checked

noneRisk

—Score

0.1.3Version

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

Status history (2 events)

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

Evidence

Static findings

3 static · 0 from release diff · showing high-signal first.

Severity	Kind	Path	Detail	Points
high	Known Indicator Filename	package/scripts/bundle.js	package/scripts/bundle.js	45
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node scripts/postinstall.js"	30

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	Known Indicator Filename	package/scripts/bundle.js	package/scripts/bundle.js	45
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node scripts/postinstall.js"	30
low	Install-time lifecycle script	package.json	postinstall="node scripts/postinstall.js"	5

Manifest

Package metadata

Scripts5

buildnode scripts/bundle.js
postinstallnode scripts/postinstall.js
prepublishOnlynpm run build
startnode dist/cli.js
testecho "Error: no test specified" && exit 1