CookCLIvsUglyFeed
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | UglyFeed | |
|---|---|---|
| Score | 61/100 | 44/100 |
| Rank in category | #3 of 18 in Recipe Management | #52 of 85 in Feed Reader |
| GitHub stars | 1 423 | 323 |
| Stars, last 30 days | +32 | +0 |
| Stable releases, 12 months | 21 | 1 |
| Latest release | v0.39.0 · 24 Oct 2026 | v0.0.52 · 5 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | AGPL-3.0 |
| Main language | Rust | Python |
Which one should you pick?
CookCLI scores 61/100 against 44/100 for UglyFeed, so it is the safer default.
CookCLI ships more often: 21 stable releases in the past year, against 1 for UglyFeed.
If you want the quickest setup, CookCLI is easier to run; UglyFeed needs more configuration.
CookCLI is growing faster right now (+32 stars in 30 days).
CookCLI details →UglyFeed details →
Swap a project
Keep CookCLI, compare it with
Keep UglyFeed, compare it with