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