# tg-spam vs trigger

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

| | tg-spam | trigger |
|---|---|---|
| Score | 52/100 | 76/100 ✓ |
| Rank in category | #3 of 4 in Anti-Spam | #7 of 32 in Workflow Automation |
| GitHub stars | 454 | 16 653 ✓ |
| Stars, last 30 days | +1 | +254 ✓ |
| Stable releases, 12 months | 15 | 51 ✓ |
| Latest release | v1.29.1 · 27 Oct 2026 | v4.8.2 · 29 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Go | Typescript |

## Which one should you pick?

trigger scores 76/100 against 52/100 for tg-spam, so it is the safer default.

trigger ships more often: 51 stable releases in the past year, against 15 for tg-spam.

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

trigger is growing faster right now (+254 stars in 30 days).

## Details

- [tg-spam](https://selfhost.directory/project/tg-spam) (markdown: https://selfhost.directory/project/tg-spam.md)
- [trigger](https://selfhost.directory/project/trigger) (markdown: https://selfhost.directory/project/trigger.md)

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