Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/repair-node-pty-spawn-helper.mjs"
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
- 551
- Versions published
- 13
- First published
- May 2026
- Publisher
- dn00
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":["[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"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 0.1.8 vs 0.1.7: "node scripts/repair-node-pty-spawn-helper.mjs"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · 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 | postinstall added in 0.1.8 vs 0.1.7: "node scripts/repair-node-pty-spawn-helper.mjs" | 40 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 0.1.8 vs 0.1.7: "node scripts/repair-node-pty-spawn-helper.mjs" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="node scripts/repair-node-pty-spawn-helper.mjs" | 5 |
Manifest
Package metadata
Scripts10
buildnpm run clean && tsccleannode -e "require('node:fs').rmSync('dist', { recursive: true, force: true })"parity:interruptnpm run build && node scripts/parity-stream.mjs --cases scripts/cases-interrupt.json --timeout-ms 120000parity:streamnpm run build && node scripts/parity-stream.mjspostinstallnode scripts/repair-node-pty-spawn-helper.mjsprepublishOnlynpm test && npm run build && npm pack --dry-runprobe:pty-interruptnode scripts/pty-interrupt-probe.mjsstartnode dist/cli.jstestvitest runtest:watchvitest
Dependencies1
node-pty^1.0.0