repowiserepowise
Sign in
FaserF/ha-keyforsteam
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseFaserF/ha-keyforsteam
HA
HA

FaserF / ha-keyforsteam

pythonmain41ab2275.5K linessynced 1w ago
Since the previous index, 2w ago-0.1 defect risk+0.3 hotspot health

Code health

6.1out of 10Fair

This codebase scores 6.1 out of 10 on defect risk, which we rate fair. It also scores maintainability 7.8 and static performance risk 9.9 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 7 of 51 files are git hotspots, and they average 3.0.

Full health report →
Documentation41pages0 with model-written prose, 41 built from the indexScore validation16/202.55× baselineOf the 20 lowest-health files, 16 were bug-fixed in the last 6 months — 2.55× the 31% baselineDead code1exportsUnused exports that nothing in the graph reaches
Lines of code
5.5K
Files
51
Symbols
225
Modules
4
Languages
5

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Ensure no HTTP request during backoff guardproposed · 1w ago
  • Set Cloudflare backoff until approximately configured duration in the futureproposed · 1w ago
  • Backoff guard should prevent further requestsproposed · 1w ago
  • Allow only a single request attempt per Cloudflare backoff test caseproposed · 1w ago
  • Trigger immediate backoff on 403 Cloudflare marker responsesproposed · 1w ago
  • Trigger immediate backoff on Cloudflare challenge page (HTTP 200)proposed · 1w ago

Needs attention

24 open
  • medium severity. ProposedEnsure no HTTP request during backoff guardAuto-proposed decision awaiting review
  • medium severity. ProposedSet Cloudflare backoff until approximately configured duration in the futureAuto-proposed decision awaiting review
  • medium severity. ProposedBackoff guard should prevent further requestsAuto-proposed decision awaiting review
  • medium severity. ProposedAllow only a single request attempt per Cloudflare backoff test caseAuto-proposed decision awaiting review
  • medium severity. ProposedTrigger immediate backoff on 403 Cloudflare marker responsesAuto-proposed decision awaiting review

Where the risk concentrates

All 7 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
sensor.pycustom_components/keyforsteam96.4th8bug magnet2bus factor 121
config_flow.pycustom_components/keyforsteam92.9th41bus factor 18
version_manager.py.github/scripts89.3th6bug magnet214
update_templates.py.github/scripts85.7th02bus factor 112
__init__.pycustom_components/keyforsteam82.1th31bus factor 110

Composition

Open the graph →
python 55%yaml 20%json 16%markdown 8%toml 2%

Explore this codebase

  • Docs41 pages across 4 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files51 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 0 entry points→
  • Code healthPer-file scores, 160 open findings, coverage and refactoring targets→
  • Knowledge graphEntities, communities, and the paths between them→
  • Change couplingFiles that keep changing together, mined from commit history→
  • CommitsChange-risk ranked history with agent provenance→
  • ContributorsBus factor, per-file maintainers, and the human/agent split→
  • StatsSize class, origin, lifetime churn, rhythm and records→
  • CostsWhat indexing this snapshot cost, by model and by run→