Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/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
- 120
- Versions published
- 37Established · −30% score
- First published
- Sep 2025
- Publisher
- speedsharma
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":["[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 1.10.0 vs 1.9.0: "node scripts/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 1.10.0 vs 1.9.0: "node scripts/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 1.10.0 vs 1.9.0: "node scripts/postinstall.js" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="node scripts/postinstall.js" | 5 |
Manifest
Package metadata
Scripts32
benchmarknpm run build && node benchmarks/run.mjsbuildtsdownbuild:watchtsc --watchchecknpm run typecheck && npm run lint:checkcinpm run typecheck && npm run lint:check && npm run test:cicleanrm -rf distcli:buildtsc -p tsconfig.json --outDir dist/cli && cp -R src/cli/templates dist/cli 2>/dev/null || truecli:devts-node src/cli/index.tsdev:basic-usagets-node examples/basic-usage.tsdev:custom-levelsts-node examples/custom-levels.tsdev:expressts-node examples/express-example.tsdev:fieldsts-node examples/field-configuration.tsdev:intelligent-searchts-node examples/intelligent-search.tsdev:nestjsts-node examples/nestjs-example.tsdev:nestjs-appts-node --project examples/nestjs-app/tsconfig.json -r ./examples/nestjs-app/register.js examples/nestjs-app/src/main.tsdev:performancets-node examples/performance-monitoring.tsdev:searchts-node examples/search-quickstart.tsformatprettier --write .format:checkprettier --check .linteslint src/lint:checkeslint src/lint:fixeslint src/ --fixpostinstallnode scripts/postinstall.jspreparenode -e "if(process.env.HUSKY!=='0'&&process.env.CI!=='true'){try{require('child_process').execSync('husky install',{stdio:'inherit'})}catch(e){process.exit(0)}}"prepublishOnlynpm run validatesizesize-limittestjesttest:cijest --coverage --ci --bail --forceExittest:coveragejest --coveragetest:watchjest --watch- …and 2 more.
Dependencies3
commander^11.1.0fast-json-stringify^6.3.0picocolors^1.1.1