PkgRadar

Package evidence

[email protected]

no findings

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

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":"review"}'

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":"review"}'
Publisherspeedsharma
Artifact bytes447,110
Previous version1.8.6
Published2026-04-26T08:52:05.532Z
SHA-25672729351031dd5e96275a3c1c31e9903da5a6eae29a183c8e842fb518081d23f

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low
Last checked
lowRisk
0Score
1.9.0Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts31
  • benchmarknpm run build && node benchmarks/run.mjs
  • buildtsdown
  • build:watchtsc --watch
  • checknpm run typecheck && npm run lint:check
  • cinpm run typecheck && npm run lint:check && npm run test:ci
  • cleanrm -rf dist
  • cli:buildtsc -p tsconfig.json --outDir dist/cli && cp -R src/cli/templates dist/cli 2>/dev/null || true
  • cli:devts-node src/cli/index.ts
  • dev:basic-usagets-node examples/basic-usage.ts
  • dev:custom-levelsts-node examples/custom-levels.ts
  • dev:expressts-node examples/express-example.ts
  • dev:fieldsts-node examples/field-configuration.ts
  • dev:intelligent-searchts-node examples/intelligent-search.ts
  • dev:nestjsts-node examples/nestjs-example.ts
  • dev:nestjs-appts-node --project examples/nestjs-app/tsconfig.json -r ./examples/nestjs-app/register.js examples/nestjs-app/src/main.ts
  • dev:performancets-node examples/performance-monitoring.ts
  • dev:searchts-node examples/search-quickstart.ts
  • formatprettier --write .
  • format:checkprettier --check .
  • linteslint src/
  • lint:checkeslint src/
  • lint:fixeslint src/ --fix
  • preparenode -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 validate
  • sizesize-limit
  • testjest
  • test:cijest --coverage --ci --bail --forceExit
  • test:coveragejest --coverage
  • test:watchjest --watch
  • typechecktsc --noEmit
  • …and 1 more.
Dependencies3
  • commander^11.1.0
  • fast-json-stringify^6.3.0
  • picocolors^1.1.1