mealie

mealie-recipes/mealie

Mealie is a self hosted recipe manager and meal planner with a RestAPI backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family. Easily add recipes into your database by providing the url and mealie will automatically import the relevant data or add a family recipe with the UI editor

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 8, 2026
1 day ago
Ship score
98/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,078 → 13,452 (Aug 25 – Oct 6, 2026)
+289 stars in the 28 days to 2026-10-06

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
13.5K
Forks
1.6K
Open issues
166
Watchers
47
Primary language
Python
Created
Dec 7, 2020
Owner
mealie-recipes · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 109 startups in the directory ship primarily in Python.

Topics

#meal-plans#recipe-manager#self-hosted

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 68%, self-hostable 97%, hosted offering 19%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-08This is the badge for mealie-recipes/mealie, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/mealie-recipes/mealie.svg)](https://ossean.com/mealie-recipes/mealie)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.