Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 4 (20%) actually needed a bug fix in the last 6 months — 9.3× better than picking files at random.
Languages
- markdown34.7%
- typescript29.6%
- json11.9%
- javascript11.7%
- yaml5.5%
- python4.7%
- toml
Key modules2
- typescript
web
packages/web
- typescript
omo
plugins/omo
Code health
Full reportHow 2233admin/lazycodex works
This page is an auto-generated, always-fresh map of the 2233admin/lazycodex repository, written primarily in markdown. 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 929 source files, 2,895 symbols, and 9 languages, structured as a monorepo with 2 packages. Git churn analysis flags 93 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 546 tightly-coupled module communities.
Use the panels 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.