CookCLI vs RecipeSage

Both are self-hosted recipe management projects. This page compares how well each one is actually maintained — the part you cannot see from a feature list.

RecipeSage scores 83 against CookCLI's 74, putting it slightly ahead on the strength of a higher commit volume. That measures project health, not feature fit — CookCLI may still be the right choice if it does what you need.

	CookCLI	RecipeSage
Health score	74/100	83/100
Commits (11 mo)	548	2261
Commits (last 3 mo)	166	962
Stars	1.4k	968
Latest release	25 Sept 2026	23 Sept 2026
Licence	MIT	AGPL-3.0
Built with	Rust	Nodejs
Typical RAM	1 GB	1 GB

CookCLI

Command-line tool for automating meal planning and shopping with Cooklang recipes, scriptable for UNIX workflows, includes web server.

74/100

Healthy

Actively maintained with regular releases.

Maintenance 26/40

Releases 25/25

Community 8/20

Momentum 15/15

Commit activity more than 66% of tracked projects; popularity more than 40%. How this is calculated.

Commits, last 11 months

RecipeSage

A recipe keeper, meal plan organizer, and shopping list manager that can import recipes directly from any URL.

83/100

Thriving

High commit volume, frequent releases and growing activity.

Maintenance 36/40

Releases 25/25

Community 7/20

Momentum 15/15

Commit activity more than 91% of tracked projects; popularity more than 34%. How this is calculated.

Commits, last 11 months

How to read this

Everything above is measured, not opinion: commit counts and release dates come from the public repositories, and the health score ranks each project against all 1352 projects we track. Read the full method.

What this comparison deliberately does not do is tell you which has the better feature set. Maintenance health tells you which project will still be receiving security fixes in two years. Decide that first, then compare features on the projects that survive the filter.

See every option in this category: self-hosted recipe management.