repowise
mengto/kage
mengto / kage
main43994874.6K linessynced 2mo ago
Code health
Health scores land with the first index: complexity, duplication, coverage, churn and ownership across every file.
Do next
0 suggested
Nothing stands out in the week to Aug 9, the last indexed commit.
Repowise ran 3 checks over this index and none of them produced work for this time frame.
No accepted decisions to drift. Too few files for coverage to change the list.
- Lines of code
- 4.6K
Recent activity
All commitsCommits
- 4399487dStop the sections widening the page2mo ago
- 7f6bda72Revert the overflow changes and pin the nav to the layout viewport2mo ago
- a6b329cdLock horizontal scrolling on the root, and only there2mo ago
- 4d0f7ba6Undo the nested scroll container2mo ago
- 6e917878Drop A Long Expected Party from the project links2mo ago
- dbdb36ceOpen the mobile menu without the second of wrong geometry2mo ago
Decisions
No decisions extracted yet.
Everything we found
1 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
Explore this codebase
- Docs3 pages across 0 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files3 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 0 entry points
- Code healthPer-file scores, 0 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.