home-assistant/core dependency check

house_with_garden: Open source home automation that puts local control and privacy first.

home-assistant/core: 1 finding to fix, none critical, fixed by upgrading packaging to 26.3.

Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, PyPI and endoflife.date.

1 thing your coding agent doesn’t know about this repo

home-assistant/core on GitHub (opens in a new tab)

1 warning9 low priority

One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.

4 versions come from a range because no lockfile pinned them, so we checked the lowest version each range allows. Where that changes the advice, the finding says so.

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 home-assistant/core
[![StackPrism](https://stackprism.ai/badge/github/home-assistant/core.svg)](https://stackprism.ai/check/github/home-assistant/core)

Ask Prism Agent about home-assistant/core

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, requirements.txt, Dockerfile and .python-version from the default branch of home-assistant/core and checked its 60 packages against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, PyPI and endoflife.date. 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.