mealie-recipes/mealie dependency check

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 ad

mealie-recipes/mealie: nothing urgent to fix, and 3 low-priority findings.

Last checked against OSV.dev, deps.dev and PyPI.

Nothing urgent in this repo

mealie-recipes/mealie on GitHub (opens in a new tab)

3 low priority

  • No known vulnerabilities
  • Nothing end of life
  • Nothing deprecated
  • No major-version drift

Nothing here needs a fix today. New advisories and end-of-life dates land every week, so this can change.

Checked 43 packages from pyproject.toml and uv.lock against:

Add this badge to your README

It shows today’s result and links to this report, so anyone opening the repo sees what needs fixing.

StackPrism dependency check badge for mealie-recipes/mealie
[![StackPrism](https://stackprism.ai/badge/github/mealie-recipes/mealie.svg)](https://stackprism.ai/check/github/mealie-recipes/mealie)

Ask Prism Agent about mealie-recipes/mealie

Map the repo (free) and ask what to fix first, whether an upgrade is safe, or what breaks if a service goes down. Prism Agent checks live sources before it answers.

How this report works

StackPrism read pyproject.toml and uv.lock from the default branch of mealie-recipes/mealie and checked its 43 packages against OSV.dev, deps.dev and PyPI. Nothing was installed or run, and there’s no AI in the findings: each one comes from a source you can open.

Vulnerabilities come from OSV.dev, with known-exploited ones from CISA marked and listed first. Runtimes, frameworks and base images are checked against endoflife.date, and packages against their registry for deprecations and major versions you’ve fallen behind. The fix task above lists every change with the file to edit.

This page refreshes every few hours; after you push a fix, “Check again” runs it now. Only the repo’s root is read. For an app in a sub-folder, paste the folder’s link into the dependency check, and for a private repo, connect GitHub.