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