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
- 3
- First published
- Jun 2026
- Publisher
- codewithrodi
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@voltstack/[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":["@voltstack/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts4
buildesbuild src/index.ts --bundle --platform=node --target=node20 --format=esm --outfile=dist/index.js --external:keytar --external:@mongodb-js/zstd --banner:js="import { createRequire } from 'node:module'; const require = createRequire(import.meta.url);"devtsx src/index.tsprepublishOnlynpm run buildtypechecktsc --noEmit
Dependencies11
@mongodb-js/zstd1.2.2chalk5.3.0commander12.1.0conf13.1.0keytar7.9.0kleur4.1.5ora8.1.1semver7.6.3tar7.4.3undici6.21.0zod3.23.8