zenfiric / MultiNEAT
cpppythonmaster11d74f010.2K linessynced 1w ago
Code health
4.6out of 10Needs work
Hotspots average 1.7, the place fixes pay off most.
Explore this codebase
- Code health map9hotspots across 41 files
- Ownership28sole-owned files: one author, no second reader
- Architecture4modules, 1 entry points
- Decisions9recorded, of which 0 accepted and 9 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 · 1
1 thing worth doing in the week to Jun 28, the last indexed commit.
Worth planning
Tidy the code shape this week's commits left: 5 findings in 4 files
2 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
src/Genome.cpp(2 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 5
- files
- 4
- commits
- 2
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
4 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health277CriticalUntested hotspot · src/Species.cpp21 findings · 9.5 deducted
- Refactoring7 open opportunitiesLowDrawPhenotype+0.3 health, M effort · MultiNEAT/viz.py
- Decisions9 to reviewMediumsrc/Genome.cpp9 awaiting review, 0 drifting from the code
- Ownership28 sole-owned filesMediumsrc/Main.cppOne author, no second reader