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
- 1
- First published
- Jun 2026
- Publisher
- circuitshield
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":["[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"}'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
Scripts13
apitsx src/server.tsapi:builtnode dist/server.jsapp:buildnpm run build && npm run web:buildbaseline:exampletsx src/cli.ts baseline create --ref audited-v1.0.0 --target examples --config examples/circuitshield.ymlbenchmarktsx src/cli.ts benchmark benchmarksbuildtsc -p tsconfig.jsondemo:baselinetsx src/cli.ts demo baseline-driftdevtsx src/cli.tsprepacknpm run buildscan:exampletsx src/cli.ts scan examples --config examples/circuitshield.yml --format markdowntestnpm run build && node tests/init-and-report.test.mjs && node dist/cli.js scan examples --config examples/circuitshield.yml --format json --out .tmp/scan.json && node dist/cli.js benchmark benchmarks --format json --out .tmp/benchmark.json && npm run web:buildweb:buildvite build --config web/vite.config.jsweb:devvite --config web/vite.config.js
Dependencies4
commander^12.1.0dotenv^16.4.7pg^8.13.1yaml^2.5.1