Repowise · Codebase intelligence
temporalio / temporal
Temporal service
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 16 (80%) actually needed a bug fix in the last 6 months — 3.6× better than picking files at random.
Languages
- go76.4%
- external8.0%
- json3.7%
- sql3.5%
- proto2.4%
- yaml2.3%
- markdown1.7%
Code health
Full report- Doc coverage100
- Code health66
- Dead code97
- Hotspot density87
How temporalio/temporal works
Temporal service This page is an auto-generated, always-fresh map of the temporalio/temporal repository, written primarily in Go. 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 3,156 source files, 35,464 symbols, and 12 languages. Git churn analysis flags 210 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 480 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.