a public repository, read by nittim
Is home-assistant/core production ready?
What nittim read in this repository, and what it found. Public repository, public reading — sourced from its own code and dependency manifests, nothing else.
Thousands of near-independent device integrations in one Python codebase.
Python · 90k stars
No verdict. The rule-based check reports hard evidence, or reports that it found none. Neither is a judgment on whether this code is safe to ship.
What was read — rule-based scan
Rule-based checks run on nittim's servers — a secret scanner and a dependency check, no model in the path. The code reached those two and stopped there.
Read 500 of 27128 eligible files. Commit f6c9b6f. 2026-08-21.
What the scanners found
- Committed secrets on production paths
- 0
- Vulnerable runtime dependencies
- 2
cryptography (GHSA-g6cj-pr64-35w5, GHSA-jwv3-5hgf-82ww)
Run it yourself
Scan any public repository in seconds — no sign-in, no card. Audit it to have a model read the code. Loop the report into your assistant to get the fixes applied and re-checked.
Scan your own repoQuestions
- What did nittim read in home-assistant/core?
- nittim read 500 of 27128 eligible files in home-assistant/core. The reading ran on August 21, 2026. It was taken at commit f6c9b6f.
- Did nittim find committed secrets or vulnerable dependencies in home-assistant/core?
- The rule-based scan found 0 committed secrets and 2 vulnerable dependencies in home-assistant/core. Affected: cryptography (GHSA-g6cj-pr64-35w5, GHSA-jwv3-5hgf-82ww).
- Is home-assistant/core production ready?
- A free scan is not a verdict. A full audit gives one.
More like this
Add the badge to your README
[](https://nittim.com/library/home-assistant/core)