bunkerity/bunkerweb

🛡️ Open-source and cloud-native Web Application Firewall (WAF)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 60 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 20th, 2019
Open Issues & Pull Requests: 170 (+0)
GitHub issues: Enabled
Number of forks: 643
Total Stargazers: 10,914 (+0)
Total Subscribers: 92 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 111
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 386 days
Stale 30+ days: 18
Stale 90+ days: 16

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 10

Top labels

  • bug (397)
  • next minor (228)
  • enhancement (189)
  • core (47)
  • need more info (31)
  • next major (30)
  • documentation (29)
  • ui (22)

Detailed Description

BunkerWeb is an open-source Web Application Firewall that operates as a cloud-native reverse proxy, designed to protect web applications from common attacks and threats.

The tool addresses the need for accessible, deployable web application security by combining WAF capabilities with reverse proxy functionality. It integrates ModSecurity rules for threat detection and includes features for bot detection, DNS blocklist checking, and automatic HTTPS certificate management through Let's Encrypt. The architecture supports multiple deployment models including Docker, Kubernetes, and Docker Swarm, allowing it to fit into various infrastructure setups without requiring specialized hardware or licensing.

Teams should consider BunkerWeb when they need WAF protection that integrates directly into containerized or orchestrated environments rather than as a separate appliance. It suits organizations building DevSecOps pipelines where security tooling should be version-controlled and deployed alongside applications. The project works well for teams already using Nginx and wanting to extend it with security hardening, or those seeking an alternative to proprietary WAF solutions that require separate management infrastructure.

The project shows consistent development activity with regular updates addressing security and feature improvements. Maintenance includes active engagement with security concerns and refinement of deployment patterns across different platforms. The codebase receives ongoing attention to both core WAF functionality and the operational aspects of running it in containerized environments. Documentation and examples are maintained to support users deploying across Docker, Kubernetes, and Swarm orchestration platforms.