FaserF / ha-tasmota-update
pythonmaineb5be7a7.3K linessynced 1mo ago
Code health
7.4out of 10Good
Hotspots average 3.9, the place fixes pay off most.
Explore this codebase
- Code health map5hotspots across 57 files
- Ownership32sole-owned files: one author, no second reader
- Architecture5modules, 0 entry points
- Decisions3recorded, of which 0 accepted and 3 awaiting review
- Refactoring9open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 1
1 thing worth doing this quarter.
Worth planning
Delete 15 unused symbols and files (205 lines)
Nothing in the graph reaches them, across 5 files; every reader and agent pays to skip them.
- symbols
- 15
- lines
- 205
- safe to delete
- Yes(inferred)
Small effort
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Everything we found
5 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health119CriticalCompound condition · .github/scripts/update_templates.py13 findings · 8.0 deducted
- Refactoring9 open opportunitiesMediumbump_version+1.5 health, S effort · .github/scripts/bump_version.py
- Decisions3 to reviewMedium.github/scripts/update_templates.py3 awaiting review, 0 drifting from the code
- Ownership32 sole-owned filesMedium.github/scripts/version_manager.pyOne author, no second reader
- Dead code16Lowset_by_pathUnreachable function (2 lines)