# CookCLI vs Reactive Resume

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

| | CookCLI | Reactive Resume |
|---|---|---|
| Score | 61/100 | 87/100 ✓ |
| Rank in category | #3 of 18 in Recipe Management | #1 of 46 in Document Management |
| GitHub stars | 1 424 | 45 040 ✓ |
| Stars, last 30 days | +33 | +1 639 ✓ |
| Stable releases, 12 months | 21 | 35 ✓ |
| Latest release | v0.39.0 · 24 Oct 2026 | v6.0.8 · 29 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Rust | Typescript |

## Which one should you pick?

Reactive Resume scores 87/100 against 61/100 for CookCLI, so it is the safer default.

Reactive Resume ships more often: 35 stable releases in the past year, against 21 for CookCLI.

If you want the quickest setup, CookCLI is easier to run; Reactive Resume needs more configuration.

Reactive Resume is growing faster right now (+1 639 stars in 30 days).

## Details

- [CookCLI](https://selfhost.directory/project/cookcli) (markdown: https://selfhost.directory/project/cookcli.md)
- [Reactive Resume](https://selfhost.directory/project/reactive-resume) (markdown: https://selfhost.directory/project/reactive-resume.md)

---
Source: https://selfhost.directory/compare/cookcli-vs-reactive-resume