Package evidence

@heymp/[email protected]

Install-time lifecycle script: preinstall="echo 'Do not run yarn install directly. Use: yarn setup' && exit 1"

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: 92
Versions published: 30Mature · −50% score
First published: Jul 2023
Publisher: heymp

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":["@heymp/[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":["@heymp/[email protected]"],"fail_on":"high"}'

Publisherheymp

Artifact bytes22,530

Previous version1.0.0-next.20

Published2026-06-10T15:56:12.593Z

SHA-256e304f5c26df949abc4e985a760f33703d2941e9d8605d8d56a3ab737d4ea5629

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 1.0.0-next.22 vs 1.0.0-next.20: "echo 'Do not run yarn install directly. Use: yarn setup' && exit 1"

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

Availability ledger

available

high

25h agoLast checked

highRisk

45Score

1.0.0-next.22Version

Status history (1 event)

new → available25h ago · risk high · score 45 · status changed

Evidence

Static findings

1 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 1.0.0-next.22 vs 1.0.0-next.20: "echo 'Do not run yarn install directly. Use: yarn setup' && exit 1"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	preinstall added in 1.0.0-next.22 vs 1.0.0-next.20: "echo 'Do not run yarn install directly. Use: yarn setup' && exit 1"	40
low	Install-time lifecycle script	package.json	preinstall="echo 'Do not run yarn install directly. Use: yarn setup' && exit 1"	5

Manifest

Package metadata

Scripts6

buildtsc
build:watchtsc -w
preinstallecho 'Do not run yarn install directly. Use: yarn setup' && exit 1
releaseyarn changeset publish
setupyarn install --ignore-scripts && yarn allow-scripts
testyarn build && node --test src/*.test.js

Dependencies4

@commander-js/extra-typings^12.1.0
commander^12.0.0
esbuild^0.25.10
playwright^1.44.1