zackees / transcribe-anything
Code health
Hotspots average 5.0, the place fixes pay off most.
Explore this codebase
- Code health map13hotspots across 111 files
- Ownership69sole-owned files: one author, no second reader
- Architecture3modules, 1 entry points
- Decisions24recorded, of which 0 in force and 24 background
- RefactoringNo refactoring analysis yet
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 2
2 things worth doing in the week to Jun 9, the last indexed commit.
Worth planning
Address the finding in run_insanely_fast_whisper
src/transcribe_anything/insanely_fast_whisper.py:385
run_insanely_fast_whisper has a bumpy road finding; function changed in 29 commits; changed 8 times in 90 days.
- gain
- up to under +0.1 health on this file(inferred)
- finding
- Bumpy road
- size
- CCN 21, 152 lines, nests 3 deep
- severity
- high
Medium effort, worth a checkAddress the finding in main
src/transcribe_anything/_cmd.py:302
main has a bumpy road finding; function changed in 23 commits; changed 10 times in 90 days.
- gain
- up to under +0.1 health on this file(inferred)
- finding
- Bumpy road
- size
- CCN 46, 158 lines, nests 3 deep
- severity
- high
Medium effort, worth a check
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
4 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health166 open findingsCriticalDeep nesting · src/transcribe_anything/whisper_mac.py11 findings · 8.1 deducted
- Decisions0 drifting from the codeMediumsrc/transcribe_anything/server_app.pyHigh-churn file with no governing decision
- Ownership69 sole-owned filesMediumsrc/transcribe_anything/server_app.pyOne author, no second reader
- Dead code13Lowlog_infoUnreachable function (3 lines)