Package evidence
@cybearl/[email protected]
Install-time lifecycle script: postinstall="npm run hooks:install"
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
- 36
- Versions published
- 45Mature · −50% score
- First published
- Feb 2025
- 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":["@cybearl/[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":["@cybearl/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 1.11.7 vs 1.11.6: "npm run hooks:install"
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 1.11.7 vs 1.11.6: "npm run hooks:install" | 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 1.11.7 vs 1.11.6: "npm run hooks:install" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="npm run hooks:install" | 5 |
Manifest
Package metadata
Scripts11
buildtsuphooks:installnode -e "require('fs').existsSync('.git') && require('child_process').execSync('git config core.hooksPath .githooks')"knipkniplintbiome checklint:fixbiome check --fix && biome format --writepostinstallnpm run hooks:installreleasenpx semantic-releasetestnpm run test:unittest:benchtsx ./tests/benchmark.tstest:sandboxtsx ./tests/sandbox.tstest:unitvitest
Dependencies8
clsx^2.1.1colorette^2.0.20dateformat^5.0.3dedent-js^1.0.1pino^10.3.1pino-pretty^13.1.3slugify^1.6.9tailwind-merge^3.3.1
Optional dependencies2
@rollup/rollup-linux-x64-gnu^4.60.2@rollup/rollup-win32-x64-msvc^4.60.2