# trusted-cgi vs UUSEC WAF

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | trusted-cgi | UUSEC WAF |
|---|---|---|
| Score | 45/100 | 59/100 ✓ |
| Rank in category | #4 of 7 in Serverless | #2 of 3 in Web Application Firewall |
| GitHub stars | 249 | 1 718 ✓ |
| Stars, last 30 days | — | +6 |
| Stable releases, 12 months | 0 | 9 ✓ |
| Latest release | — | v7.2.6 · 12 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes ✓ | No |
| License | MIT | BSD-2-Clause |
| Main language | Go | Shell |

## Which one should you pick?

UUSEC WAF scores 59/100 against 45/100 for trusted-cgi, so it is the safer default.

UUSEC WAF ships more often: 9 stable releases in the past year, against 0 for trusted-cgi.

If you want the quickest setup, trusted-cgi is easier to run; UUSEC WAF needs more configuration.

UUSEC WAF is growing faster right now (+6 stars in 30 days).

## Details

- [trusted-cgi](https://selfhost.directory/project/trusted-cgi) (markdown: https://selfhost.directory/project/trusted-cgi.md)
- [UUSEC WAF](https://selfhost.directory/project/uusec-waf) (markdown: https://selfhost.directory/project/uusec-waf.md)

---
Source: https://selfhost.directory/compare/trusted-cgi-vs-uusec-waf