CookCLIvsSparkyFitness
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | SparkyFitness | |
|---|---|---|
| Score | 61/100 | 66/100 |
| Rank in category | #3 of 18 in Recipe Management | #2 of 11 in Fitness Tracker |
| GitHub stars | 1 422 | 6 497 |
| Stars, last 30 days | +32 | +397 |
| Stable releases, 12 months | 21 | 26 |
| Latest release | v0.39.0 · 24 Oct 2026 | v1.9.0 · 21 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | Other |
| Main language | Rust | Typescript |
Which one should you pick?
SparkyFitness scores 66/100 against 61/100 for CookCLI, so it is the safer default.
SparkyFitness ships more often: 26 stable releases in the past year, against 21 for CookCLI.
If you want the quickest setup, CookCLI is easier to run; SparkyFitness needs more configuration.
SparkyFitness is growing faster right now (+397 stars in 30 days).
CookCLI details →SparkyFitness details →
Swap a project
Keep CookCLI, compare it with
Keep SparkyFitness, compare it with