CookCLIvsUUSEC WAF
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | UUSEC WAF | |
|---|---|---|
| Score | 61/100 | 59/100 |
| Rank in category | #3 of 18 in Recipe Management | #2 of 3 in Web Application Firewall |
| GitHub stars | 1 423 | 1 719 |
| Stars, last 30 days | +32 | +7 |
| Stable releases, 12 months | 21 | 9 |
| Latest release | v0.39.0 · 24 Oct 2026 | v7.2.6 · 12 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | MIT | BSD-2-Clause |
| Main language | Rust | Shell |
Which one should you pick?
CookCLI scores 61/100 against 59/100 for UUSEC WAF, so it is the safer default.
CookCLI ships more often: 21 stable releases in the past year, against 9 for UUSEC WAF.
If you want the quickest setup, CookCLI is easier to run; UUSEC WAF needs more configuration.
CookCLI is growing faster right now (+32 stars in 30 days).
CookCLI details →UUSEC WAF details →
Swap a project
Keep CookCLI, compare it with
Keep UUSEC WAF, compare it with