Package evidence
@drewpayment/[email protected]
Install Lifecycle Suppresses Failure: postinstall="bun run build 2>/dev/null || true"
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
- 544
- Versions published
- 31
- First published
- Apr 2026
- Publisher
- drewpayment
Recommended action
Block this updateStatic 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":["@drewpayment/[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":["@drewpayment/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Install Lifecycle Suppresses Failure: postinstall="bun run build 2>/dev/null || true"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (5 events)
- available → available · risk high · score 25 · status available -> available, risk high -> high, score 17 -> 25
- available → available · risk high · score 17 · status available -> available, risk high -> high, score 25 -> 17
- available → available · risk high · score 25 · status available -> available, risk high -> high, score 119 -> 25
- available → available · risk high · score 119 · status available -> available, risk high -> high, score 144 -> 119
- new → available · risk high · score 144 · status changed
Related candidates
Linked campaigns and clusters
Install Lifecycle Suppresses Failure — postinstall="bun run build 2>/dev/null || true"
5 members · evidence strength 90Install-time lifecycle script — postinstall="bun run build 2>/dev/null || true"
5 members · evidence strength 90Install Lifecycle Remote Or Exec — postinstall="bun run build 2>/dev/null || true"
5 members · evidence strength 90Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install Lifecycle Suppresses Failure | package.json | postinstall="bun run build 2>/dev/null || true" | 20 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install Lifecycle Suppresses Failure | package.json | postinstall="bun run build 2>/dev/null || true" | 20 |
| low | Install-time lifecycle script | package.json | postinstall="bun run build 2>/dev/null || true" | 5 |
| low | Large Javascript Payload | package/dist/cli.js | 3980792 bytes | 0 |
Manifest
Package metadata
Scripts7
buildbun build src/cli.ts --outfile dist/cli.js --target node --format esm && node -e "const f=require('fs');let c=f.readFileSync('dist/cli.js','utf8');c=c.replace(/^#!.*\n/,'');f.writeFileSync('dist/cli.js','#!/usr/bin/env node\n'+c);f.chmodSync('dist/cli.js',0o755)"dashboard:buildcd dashboard && bun run builddashboard:devcd dashboard && bun run devpostinstallbun run build 2>/dev/null || truetestbun testtest:watchbun test --watchtypecheckbunx tsc --noEmit
Dependencies1
puppeteer-core^24.0.0
Optional dependencies1
@puppeteer/browsers^2.0.0