udopia / gbdc
Instance Identification, Feature Extraction, and Problem Transformation
Code health
udopia/gbdc scores 6.8 out of 10 on defect risk, which Repowise rates Fair. Maintainability scores 7.5 out of 10. Static performance risk scores 10.0 out of 10. The three are scored separately and never blended into a single number. 1 of 64 files are git hotspots, the places where changes and bug fixes concentrate.
Full health report- Files
- 64
- Symbols
- 1.6k
- Modules
- 5
- Doc pages
- 155
- Dead exports
- 5
Where the risk concentrates
All 1 hotspotsRanked by prior bug fixes and change frequency, mined from the full git history rather than from the code alone.
| File | Churn | Prior fixes | Maintainers | Commits 90d |
|---|---|---|---|---|
| Main.ccsrc | 98.1th %ile | 0 | 5 | 3 |
Read more about udopia/gbdc
- OverviewFiles, symbols, languages, packages, git intelligence
- ArchitectureDependency graph, layered architecture, symbol index, and third-party dependencies
- Code healthPer-file health scores, hotspots, test coverage, dead code, and refactoring targets
- AI explanationsProModule-by-module documentation generated from source
- CommitsChange-risk ranked history with AI-agent provenance and hotspots
- ContributorsBus-factor, per-file maintainer maps, and human/agent collaboration
- DecisionsArchitectural decisions extracted from commits and PRs
- Chat with this repoSign inAsk grounded questions over the indexed code
Add a badge to your README
Both badges are public, cached, and update on their own after every index. Nothing to install.
Repowise badge
Links to this page. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/udopia/gbdc)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/udopia/gbdc)How udopia/gbdc works
Instance Identification, Feature Extraction, and Problem Transformation This page is an auto-generated, always-fresh map of the udopia/gbdc repository, written primarily in C++. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 64 source files, 1,637 symbols, and 5 languages, organised into 5 modules, led by cpp, markdown, yaml. Static analysis leaves 187 open findings across the three health dimensions.
Use the links above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.