ifixai-ai / ifixai
pythonmain92bb5d0124.5K linessynced 1d ago
Code health
8.4out of 10Good
Hotspots average 6.6, the place fixes pay off most.
Explore this codebase
- Code health map76hotspots across 864 files
- Ownership380sole-owned files: one author, no second reader
- Architecture5modules, 4 entry points
- Decisions56recorded, of which 0 accepted and 56 awaiting review
- Refactoring76open 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 in the week to Oct 22, the last indexed commit.
Worth planning
Tidy the code shape this week's commits left: 19 findings in 10 files
5 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
ifixai/providers/http.py(3 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 19
- files
- 10
- commits
- 5
Medium 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 health755CriticalDeep nesting · ifixai/evaluation/analytic_judge.py24 findings · 7.6 deducted
- Refactoring76 open opportunitiesMedium_inspection_suspicious_tools+1.5 health, S effort · ifixai/inspections/b14_covert_side_task/runner.py
- Decisions56 to reviewMediumifixai/cli/run.py56 awaiting review, 0 drifting from the code
- Ownership380 sole-owned filesMediumifixai/tests/evaluation/test_judge_side_unscored.pyOne author, no second reader
- Dead code2Lowlist_test_coverageUnreachable function (5 lines)