Package evidence
@openparachute/[email protected]
Install-time lifecycle script: postinstall="if [ -d web/ui ]; then bun run build:spa; fi"
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
- 57
- First published
- Apr 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":["@openparachute/[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":["@openparachute/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 0.4.8-rc.8 vs 0.4.8-rc.6: "if [ -d web/ui ]; then bun run build:spa; fi"
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 high -> high, score 75 -> 45
- new → available · risk high · score 75 · 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.4.8-rc.8 vs 0.4.8-rc.6: "if [ -d web/ui ]; then bun run build:spa; fi" | 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.4.8-rc.8 vs 0.4.8-rc.6: "if [ -d web/ui ]; then bun run build:spa; fi" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="if [ -d web/ui ]; then bun run build:spa; fi" | 5 |
Manifest
Package metadata
Scripts8
build:spacd web/ui && bun install --frozen-lockfile && bun run buildclibun src/cli.tspostinstallif [ -d web/ui ]; then bun run build:spa; fiprepackbun run build:spastartbun src/server.tstestbun test ./src/test:corecd core && node --experimental-vm-modules node_modules/vitest/dist/cli.js runtypechecktsc --noEmit
Dependencies5
@modelcontextprotocol/sdk^1.12.1@openparachute/scope-guard^0.3.0jose^6.2.2otpauth^9.5.0qrcode-terminal^0.12.0