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
- 113
- Versions published
- 7
- First published
- May 2026
- Publisher
- cdw0424
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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
Credential file access: matched "aws_access_key"
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 review · score 5 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/security/redaction.js | matched "aws_access_key" | 5 |
Manifest
Package metadata
Scripts42
buildtsc -p tsconfig.build.json && node scripts/chmod-bin.mjscleanrm -rf dist coverage .atlas-wiki tmp/wiki tmp/package-smoke tmp/type-consumerformatnode scripts/format-check.mjsgoal:coveragenode scripts/generate-task-coverage.mjshardening:verifynode scripts/verify-production-hardening.mjslintnode scripts/lint.mjspackage:dry-runnode scripts/package-dry-run.mjspackage:published-smokenode scripts/published-package-smoke.mjspackage:smokenpm run build && node scripts/package-smoke.mjspackage:verifynpm run build && node scripts/package-verify.mjspackchecknpm run package:verify && npm run package:dry-run && npm run package:smokeprepacknpm run buildprepublishOnlynode scripts/publish-guard.mjsrag:evalnpm run build && node scripts/run-rag-eval.mjsrelease:checknpm run typecheck && npm run build && npm run lint && npm run test && npm run test:security && npm run test:context-leakage && npm run test:mcp && npm run test:audit && npm run test:structured && npm run test:rag && npm run test:cli-setup && npm run test:store-contract && npm run test:supabase:mock && npm run test:integration && npm run test:hardening && npm run test:types && npm run schemas:validate && npm run hardening:verify && npm run package:verify && npm run package:dry-run && npm run package:smoke && npm run release:next-stable-verifyrelease:next-stable-generatenpm run build && node scripts/generate-next-stable-release-evidence.mjsrelease:next-stable-verifynpm run release:next-stable-generate && node scripts/verify-next-stable-release.mjsrelease:published-checknpm run package:published-smokeschemas:validatenode scripts/validate-schemas.mjsselftestnode scripts/selftest.mjstestvitest runtest:accessvitest run tests/security.test.tstest:auditvitest run tests/security.test.ts tests/audit-hardening.test.tstest:cli-setupvitest run tests/cli-setup.test.tstest:context-leakagevitest run tests/security.test.ts tests/context-hardening.test.tstest:dbvitest run tests/migrations-hardening.test.ts tests/integration.test.tstest:hardeningvitest run tests/production-hardening-completion.test.tstest:integrationvitest run tests/integration.test.tstest:integrityvitest run tests/migrations-hardening.test.ts tests/integration.test.tstest:mcpvitest run tests/mcp-hardening.test.ts- …and 12 more.
Dependencies2
@modelcontextprotocol/sdk^1.29.0zod^4.4.3