waf-detector

Use when the user wants to understand the codebase, find streamlining opportunities, explore architecture, or map module dependencies.

Use when adding a new WAF/CDN provider or extending detection logic.

Use when scans fail early, the environment looks unhealthy, or the user wants shell completions.

Use when the user wants a structured security review, hardening pass, or pre-release audit.

Use when the user wants final formatting, lint, test, and build validation before merge or push.

Use when the user wants an end-to-end WAF assessment workflow instead of a single CLI command.