repowise
faserf/tcl-discussion-telegram
FaserF / TCL-Discussion-Telegram
javascriptpythonmain70bb7577.8K linessynced 1mo ago
Code health
6.4out of 10Fair
Hotspots average 3.5, the place fixes pay off most.
Explore this codebase
- Code health map7hotspots across 72 files
- Ownership33sole-owned files: one author, no second reader
- Architecture4modules, 4 entry points
- Decisions4recorded, of which 0 accepted and 4 awaiting review
- Refactoring7open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 0
Nothing stands out in the week to Sep 1, the last indexed commit.
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 health106CriticalUntested hotspot · scripts/firmware_tracker/extractor.py36 findings · 8.7 deducted
- Refactoring7 open opportunitiesMediumwrite_markdown+1.0 health, L effort · scripts/firmware_tracker/writers.py
- Decisions4 to reviewMediumscripts/fetch_firmwares.py4 awaiting review, 0 drifting from the code
- Ownership33 sole-owned filesMediumscripts/fetch_firmwares.pyOne author, no second reader
- Dead code4Lowdocs/javascripts/telegram-widgets.jsUnreachable symbol (20 lines)