recolabs / gnata
gomaindee7a5639.9K linessynced on Nov 21, 2026
Code health
6.9out of 10Fair
Hotspots average 5.7, the place fixes pay off most.
Explore this codebase
- Code health map18hotspots across 1,479 files
- Ownership72sole-owned files: one author, no second reader
- Architecture7modules, 7 entry points
- Decisions28recorded, of which 0 in force and 28 background
- Refactoring28open 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 18, the last indexed commit.
Worth planning
Review why fixes keep landing in
gnata.go: tests reach itChanged 12 times in 90 days, and 3 of those commits were bug fixes.
- commits in 90 days
- 12
- bug-fix commits
- 3
- line coverage
- Unknown, no report
- tests that reach it
- 24 test files, inline(inferred)
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 health377 open findingsCriticalChange entropy · internal/evaluator/path.go49 findings · 9.9 deducted
- Refactoring28 open opportunitiesLowevalCore+0.5 health, S effort · gnata.go
- Decisions0 drifting from the codeMediumgnata.goHigh-churn file with no governing decision
- Ownership72 sole-owned filesMediumbuiltins_test.goOne author, no second reader