repowise-dev / repowise
pythonmain8f69324691.5K linessynced 1d ago
Since the previous index, 2d ago+0.1 defect risk+0.1 hotspot health
Code health
6.9out of 10Fair
This codebase scores 6.9 out of 10 for code health, which we rate fair. It also scores maintainability 7.7 and static performance 9.7 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 714 of 4,343 files are git hotspots, and they average 4.7 — which is where the fixes pay off most.
- Lines of code
- 691.5K
Recent activity
All commitsCommits
No commits indexed yet.
Decisions
- Define risk scale semantics and split constant dictionary data via includeproposed · 1d ago
- Use composed opportunity as the unit across all surfacesproposed · 1d ago
- Preserve model-written pages on update; determine re-render mode per page by existing provenanceproposed · 1d ago
- Add repo-scoped provider API key settings and per-page AI generation actionsproposed · 1d ago
- Expose contract line/symbol/schema and link consumer/provider over RESTproposed · 1d ago
- Reuse exact betweenness scores using a churn budget to avoid rescoringproposed · 1d ago
Needs attention
4,479 open- medium severity. Needs reviewDefine risk scale semantics and split constant dictionary data via includeAuto-proposed decision awaiting review
- medium severity. Needs reviewUse composed opportunity as the unit across all surfacesAuto-proposed decision awaiting review
- medium severity. Needs reviewPreserve model-written pages on update; determine re-render mode per page by existing provenanceAuto-proposed decision awaiting review
- medium severity. Needs reviewAdd repo-scoped provider API key settings and per-page AI generation actionsAuto-proposed decision awaiting review
- medium severity. Needs reviewExpose contract line/symbol/schema and link consumer/provider over RESTAuto-proposed decision awaiting review
Where the risk concentrates
All 714 hotspotsRanked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.
| File | Prior fixes | Last fix | Maintainers | Commits 90d |
|---|---|---|---|---|
| tool_health.pypackages/server/src/repowise/server/mcp_server | 20bug magnet | 3d ago | 5bus factor 1 | 45 |
| answer.pypackages/server/src/repowise/server/mcp_server/tool_answer | 23bug magnet | 4w ago | 5 | 55 |
| command.pypackages/cli/src/repowise/cli/commands/update_cmd | 32bug magnet | 3d ago | 9 | 68 |
| tool_why.pypackages/server/src/repowise/server/mcp_server | 13bug magnet | 6d ago | 4bus factor 1 | 30 |
| call_resolver.pypackages/core/src/repowise/core/ingestion | 25bug magnet | 3d ago | 4bus factor 1 | 40 |
Composition
Open the graphpython 64%typescript 29%
markdown 4%json 2%yaml 0%Other 0%
Explore this codebase
- Docs5,558 pages across 12 modules
- ChatAsk this codebase a question and get an answer with its sources
- Files4,343 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 607 entry points
- Code healthPer-file scores, 15,727 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