Package evidence
@kvell007/[email protected]
Install-time lifecycle script: preinstall="node dist/install-progress.js preinstall"
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
- 87
- First published
- May 2026
- Publisher
- kvell007
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":["@kvell007/[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":["@kvell007/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: preinstall added in 0.1.0-alpha.39 vs 0.1.0-alpha.38: "node dist/install-progress.js preinstall"
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 90 · status available -> available, risk high -> high, score 150 -> 90
- new → available · risk high · score 150 · status changed
Evidence
Static findings
2 static · 2 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 0.1.0-alpha.39 vs 0.1.0-alpha.38: "node dist/install-progress.js preinstall" | 40 |
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 0.1.0-alpha.39 vs 0.1.0-alpha.38: "node dist/install-progress.js postinstall" | 40 |
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 0.1.0-alpha.39 vs 0.1.0-alpha.38: "node dist/install-progress.js preinstall" | 40 |
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 0.1.0-alpha.39 vs 0.1.0-alpha.38: "node dist/install-progress.js postinstall" | 40 |
| low | Install-time lifecycle script | package.json | preinstall="node dist/install-progress.js preinstall" | 5 |
| low | Install-time lifecycle script | package.json | postinstall="node dist/install-progress.js postinstall" | 5 |
Manifest
Package metadata
Scripts2
postinstallnode dist/install-progress.js postinstallpreinstallnode dist/install-progress.js preinstall
Dependencies3
@embed-labs/local-bridgenpm:@kvell007/[email protected]@embed-labs/protocolnpm:@kvell007/[email protected]qrcode-terminal^0.12.0