corazawaf/coraza

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on May 27th, 2020
Open Issues & Pull Requests: 123 (+0)
GitHub issues: Enabled
Number of forks: 358
Total Stargazers: 3,827 (+0)
Total Subscribers: 36 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.1 hours
Mean response time: 34.9 days
90th percentile: 102.3 days
Tracked items: 122

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 19% of issues opened in the past year have never received a reply. 54% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Only 59% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 57
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 448 days
Stale 30+ days: 45
Stale 90+ days: 32

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (13)
  • enhancement (10)
  • fix (5)
  • security (5)
  • awaiting feedback (4)
  • documentation (4)
  • good first issue (3)
  • seclang (3)

Detailed Description

Coraza is a Web Application Firewall library written in Go that provides ModSecurity-compatible protection for web applications.

Coraza addresses the need for high-performance application-layer security by implementing a WAF engine compatible with industry-standard SecLang rulesets. It runs the OWASP Core Rule Set v4 to defend against common attack categories including SQL injection, cross-site scripting, code injection, and bot detection. The tool is designed as a library at its core, allowing developers to embed it directly into Go applications or deploy it through various server integrations rather than requiring a separate WAF appliance.

Teams should adopt Coraza if they need WAF protection with minimal performance overhead and want to avoid vendor lock-in through standard rulesets. It suits projects ranging from small blogs to large websites and works across Linux, Windows, and macOS. The tool is particularly valuable for organizations already using Go or those deploying to environments like Kubernetes through proxy-wasm integrations with Envoy, or to reverse proxies like Caddy and Traefik. The README identifies it as an alternative to the OWASP ModSecurity Engine, with the key distinction being Coraza's Go implementation and broader ecosystem of maintained integrations.

Development activity shows consistent engagement with the community through GitHub Discussions and OWASP Slack channels. The project maintains multiple official integrations at varying maturity levels, with some marked as stable and others as experimental, indicating ongoing expansion of deployment options. Several integrations are explicitly noted as needing maintainers, suggesting the core team prioritizes community contribution over maintaining every plugin themselves.