Package evidence
@bytevion/[email protected]
Install-time lifecycle script: postinstall="node ./bin/postinstall.js"
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
- 1,359Niche · −30% score
- Versions published
- 14
- First published
- May 2026
- Publisher
- bytevion
Effective trust discount applied: −30% (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":["@bytevion/[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":["@bytevion/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 0.4.1 vs 0.4.0: "node ./bin/postinstall.js"
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.4.1 vs 0.4.0: "node ./bin/postinstall.js" | 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.1 vs 0.4.0: "node ./bin/postinstall.js" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="node ./bin/postinstall.js" | 5 |
Manifest
Package metadata
Scripts10
buildtsc -b && node scripts/tui-pkg.js && oclif manifestcleantsc -b --cleanpack:tarballsoclif pack tarballs --no-xzpostinstallnode ./bin/postinstall.jspostpacknode -e "require('fs').rmSync('oclif.manifest.json',{force:true})"prepacknpm run buildprepublishOnlynode -e "const fs=require('fs');for(const f of (fs.existsSync('dist')?fs.readdirSync('dist'):[])){if(f.endsWith('.tar.gz')||f.endsWith('.tar.xz')||f.startsWith('SHA256SUMS'))fs.rmSync('dist/'+f,{force:true})}"testnpm run build && npm run test:unit && npm run test:tuitest:tuinode --test "src/**/*.test.mts"test:unittsx --test "src/**/*.test.ts" "src/**/*.test.tsx"
Dependencies8
@clack/prompts^1.5.0@oclif/core^4.0.0cli-table3^0.6.5ink^7.0.5ink-spinner^5.0.0ink-text-input^6.0.0picocolors^1.1.1react^19.2.6