Repowise · Codebase intelligence
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 19 (95%) actually needed a bug fix in the last 6 months — 3.6× better than picking files at random.
forge_api
crates/forge_api
forge_app
crates/forge_app
forge_ci
crates/forge_ci
forge_config
crates/forge_config
forge_display
This page is an auto-generated, always-fresh map of the vzwjustin/forgecode repository, written primarily in rust. 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 673 source files, 11,004 symbols, and 9 languages, structured as a monorepo with 23 packages. Git churn analysis flags 0 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 211 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.
Files, symbols, languages, packages, git intelligence
Dependency graph, layered architecture, symbol index, and third-party dependencies
Per-file health scores, hotspots, test coverage, dead code, and refactoring targets
Module-by-module documentation generated from source
Change-risk ranked history with AI-agent provenance and hotspots
Bus-factor, per-file maintainer maps, and human/agent collaboration
Architectural decisions extracted from commits and PRs
Ask grounded questions over the indexed code
crates/forge_display
forge_domain
crates/forge_domain
forge_embed
crates/forge_embed
forge_fs
crates/forge_fs
forge_infra
crates/forge_infra
forge_json_repair
crates/forge_json_repair
forge_main
crates/forge_main
forge_markdown_stream
crates/forge_markdown_stream