# tg-spam vs UUSEC WAF

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

| | tg-spam | UUSEC WAF |
|---|---|---|
| Score | 52/100 | 59/100 ✓ |
| Rank in category | #3 of 4 in Anti-Spam | #2 of 3 in Web Application Firewall |
| GitHub stars | 453 | 1 719 ✓ |
| Stars, last 30 days | +0 | +7 ✓ |
| Stable releases, 12 months | 15 ✓ | 9 |
| Latest release | v1.29.1 · 27 Oct 2026 ✓ | 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 52/100 for tg-spam, so it is the safer default.

tg-spam ships more often: 15 stable releases in the past year, against 9 for UUSEC WAF.

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

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

## Details

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

---
Source: https://selfhost.directory/compare/tg-spam-vs-uusec-waf