Repowise · Codebase intelligence
glyphary / glyphary
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 9 (45%) actually needed a bug fix in the last 6 months — 3.9× better than picking files at random.
Languages
- typescript46.9%
- rust32.3%
- json9.4%
- markdown6.3%
- toml2.1%
- javascript2.1%
- makefile1.0%
Key modules1
- rust
src-tauri
src-tauri
Code health
Full report- Code health55
- Dead code
How glyphary/glyphary works
This page is an auto-generated, always-fresh map of the glyphary/glyphary repository, written primarily in typescript. 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 96 source files, 980 symbols, and 7 languages. Git churn analysis flags 9 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 34 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.