bunkerweb

bunkerity/bunkerweb

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

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 7, 2026
4 days ago
Ship score
90/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 10,995 → 11,041 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
11.1K
Forks
650
Open issues
197
Watchers
90
Primary language
Python
Created
Aug 20, 2019
Owner
bunkerity · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 109 startups in the directory ship primarily in Python.

Topics

#antibot#cybersecurity#devops#devsecops#dnsbl#docker#hardening#hosting#kubernetes#letsencrypt#modsecurity#nginx#reverse-proxy#security#security-tuning#swarm#waap#waf#web-application-firewall#web-security

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 97%, self-hostable 80%, hosted offering 76%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.96. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-07This is the badge for bunkerity/bunkerweb, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/bunkerity/bunkerweb.svg)](https://ossean.com/bunkerity/bunkerweb)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.