Package evidence
[email protected]
New Account With Lifecycle Hook: package first published 1 day(s) ago, 2 total version(s), has lifecycle hook
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
- Jun 2026
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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.1 vs 0.0.0-bootstrap.0: "node ./install.js"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (2 events)
- available → available · risk high · score 45 · status available -> available, risk low -> high, score 0 -> 45
- new → available · risk low · score 0 · status changed
Evidence
Static findings
2 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.1 vs 0.0.0-bootstrap.0: "node ./install.js" | 40 |
| high | New Account With Lifecycle Hook | package.json | package first published 1 day(s) ago, 2 total version(s), has lifecycle hook | 25 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 0.1.1 vs 0.0.0-bootstrap.0: "node ./install.js" | 40 |
| high | New Account With Lifecycle Hook | package.json | package first published 1 day(s) ago, 2 total version(s), has lifecycle hook | 25 |
| low | Install-time lifecycle script | package.json | postinstall="node ./install.js" | 5 |
Manifest
Package metadata
Scripts3
fmtprettier --write **/*.jsfmt:checkprettier --check **/*.jspostinstallnode ./install.js
Dependencies1
detect-libc^2.1.2