Our take
- Activity
- 61
- Community
- 79
- Issues
- 60
- Pull requests
- 55
+125 stars in the last 30 days
- Merges more pull requests than 76% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
4,034Forks
386Change since Nov 16, 2026: +9 stars·+2 forks
Overview
Coraza is a Go web application firewall engine for applications and server deployments that need to inspect HTTP traffic against security rules. It supports ModSecurity-compatible SecLang rules and the OWASP Core Rule Set (CRS) v4, which helps protect against common web attacks.
Unlike a standalone proxy, Coraza is a library at its core. Teams can embed it in Go services or use maintained integrations to add WAF capabilities to supported servers. It is a fit when you want to use CRS rules with a Go-based engine and can manage rule configuration and deployment yourself.
Key Features
- Processes ModSecurity-compatible SecLang rules.
- Supports OWASP Core Rule Set v4; the README reports full CRS compatibility.
- Embeds in Go applications as a library.
- Offers extension points for components such as audit loggers, persistence engines, operators, and actions.
- Provides integrations for Caddy, Proxy-WASM, Traefik, HAProxy, and a C library, with differing maturity levels.
- Includes a playground for testing rules and an end-to-end testing utility.
- Supports Go FIPS 140-3 mode, with documented restrictions on MD5 and SHA-1 transformations.
Use Cases
- Go application teams can add request inspection and rule-based blocking as middleware without switching to a separate WAF engine.
- Operators of supported proxies can use Coraza integrations to apply SecLang and CRS rules at the traffic layer.
- Security teams can evaluate CRS rules against sample requests in the Coraza Playground before deploying changes.
- Developers maintaining WAF rules or integrations can use the project’s testing utilities and Go-based extension points.
Getting Started
Add Coraza to a Go application by importing github.com/corazawaf/coraza/v3, then create a WAF configuration and transaction. The README includes a minimal usage example and further setup guidance.
Considerations
- Coraza has partial compatibility with the ModSecurity engine, so compatibility should be checked for rules or behaviors that rely on specific engine details.
- The README states that older CRS versions are not compatible; use CRS v4.
- Integration maturity varies: some listed integrations are experimental or need a maintainer.
- Development requires a recent Go version or TinyGo. Review the README’s build-tag and FIPS notes for configuration-specific behavior.
Found this useful?
Share it with someone who would like coraza.