Trending repositories

Ranked by Attention Score: stars gained over the last 30 complete days

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

7 repositories by Attention Score · Oct 5, 2026 – Nov 3, 2026 (UTC)

Language: Go
Tag: Firewall
Clear all

1.TecharoHQ / anubis

Weighs the soul of incoming HTTP requests to stop AI crawlers

defense
security

Go MIT24K total807 forks

+904 stars

from 23,022 · score 6.81

2.chaitin / SafeLine

SafeLine is a self-hosted WAF(Web Application Firewall) / reverse proxy to protect your web apps from attacks and exploits.

firewall
http-flood
security
sql-injection
waf
web-application-firewall
+14 more

Go GPL-3.023K total1.6K forks

+500 stars

from 22,663 · score 6.22

3.crowdsecurity / crowdsec

Open-source IDS/IPS, WAF and bot detection for Linux, Windows, Docker and Kubernetes, with a crowdsourced blocklist of malicious IPs.

security
waf
anti-bot
blocklist
bot-detection
bot-protection
+12 more

Go MIT15K total755 forks

+397 stars

from 15,047 · score 5.99

4.v55448330 / lazy-balancer-v2

Caddy Reverse Proxy Balancer and WAF WebUI

Go APACHE-2.0642 total9 forks

+359 stars

from 283 · score 5.89

5.safing / portmaster

🏔 Love Freedom - ❌ Block Mass Surveillance

application-firewall
dns
firewall
go
golang
privacy
+5 more

Go GPL-3.014K total608 forks

+165 stars

from 13,855 · score 5.11

6.corazawaf / coraza

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

coraza
waf
coraza-waf
owasp-crs
modsecurity
coreruleset
+6 more

Go APACHE-2.04K total377 forks

+126 stars

from 3,866 · score 4.84

7.OpenNHP / opennhp

Make your infrastructure invisible to attackers. OpenNHP implements the Network-infrastructure Hiding Protocol (NHP): authenticate before connection, cryptographically. IETF draft.

cybersecurity
zero-trust
zero-trust-network-access
zero-trust-security

Go APACHE-2.014K total2.5K forks

+23 stars

from 13,930 · score 3.18

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index