| FMRS | 42 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 |
|---|
| Security and permissions | 4 / 20 | 16 / 20 |
|---|
| Maintenance | 9 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 |
|---|
| Best for | - Authorized security researchers and red/blue team engineers who want verify-before-report workflows
- Agent users who want a full penetration-testing flow driven by one call inside an MCP client
- Developers and security reviewers needing code audit (taint analysis, source-to-sink, variant analysis)
- Teams that want a structured methodology plus knowledge base (manuals, playbooks, escalation chains) instead of scattered scripts
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Anyone wanting to test external systems without explicit owner authorization
- Anyone treating a scan hit as a confirmed vulnerability and skipping STRIKE validation
- Users expecting everything to work offline out of the box — payloads and templates need `blitzstrike sync-data`, and fofa_search needs FOFA_EMAIL/FOFA_KEY
- Users looking for an official or vendor-endorsed product; this is a community project
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Read the source directory or files being audited
- Run a local process over stdio (command `blitzstrike`, args `serve --mcp`)
- Make outbound HTTP requests to the audited target for live validation and recon
- Write to client MCP config files (install merges into existing config, never overwrites)
- Read/write memory and data cache under ~/.blitzstrike (overridable via BLITZSTRIKE_HOME / BLITZSTRIKE_DATA)
- Optional: FOFA_EMAIL / FOFA_KEY for FOFA access, and H1_USERNAME to add the X-HackerOne-Research header
- ensure_tool may auto-install missing security tools on the local machine
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Live validation and live_recon send real requests to targets; misconfigured scope or missing authorization can cause harm or legal exposure
- ensure_tool auto-installation modifies the local environment and introduces supply/version risk
- Payloads, nuclei templates, and exploitation manuals are offensive material that can be misused
- Memory is stored append-only as JSONL at ~/.blitzstrike/memory.jsonl and may accumulate sensitive target data
- FOFA and HackerOne credentials are supplied via environment variables and can leak
- Automated scan results can still be false positives — the README insists every finding stays a hypothesis until strike_verify confirms it
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, OpenCode, Hermes, Gemini, Windsurf, GitHub Copilot, Cline | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 52 | 19 |
|---|