HexSleeves / zorai
Code health
This codebase scores 6.0 out of 10 for code health, which we rate fair. It also scores maintainability 7.1 and static performance 9.7 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 234 of 4,985 files are git hotspots, and they average 3.3 — which is where the fixes pay off most.
Do next
1 suggested
12 things worth doing this quarter, 11 of them now.
Worth planning
Delete 8 unused symbols and files (446 lines)
Nothing in the graph reaches them, across 8 files; every reader and agent pays to skip them.
- symbols
- 8
- lines
- 446
- safe to delete
- Yes(inferred)
Medium effort
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effortReview the 11 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
- proposed
- 11
- accepted
- 0
Medium effort
- Lines of code
- 1.2M
Recent activity
All commitsCommits
- c3938a8fchore: bump version to v0.9.571mo ago
- f6073958feat(skill-recommendation): add filesystem skill variant listing and background sync1mo ago
- 178481cbfix(frontend): update ThreadsRail button text for clarity1mo ago
- 461680aefix(subagents): scope sibling internal DMs to active task threads + unique personas1mo ago
- 0718c37dfix(tools): honor explicit wait_for_completion=true in bash_command1mo ago
- 133b36c6chore: remove misplaced virtual-cell data1mo ago
Decisions
- Enhance MLflow tracing with event recording and payload managementproposed · 1mo ago
- Extend external runtime profiles and import session schemaproposed · 1mo ago
- Enhance tool filtering and approval inbox managementproposed · 1mo ago
- Enhance embedding job handling and error reportingproposed · 1mo ago
- Enhance governance constraints and transition handlingproposed · 1mo ago
- Enhance task completion contract handling and provider availability signalsproposed · 1mo ago
Everything we found
12,770 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is critical severity. Code health8,461Untested hotspot · crates/zorai-daemon/src/agent/tool_executor/terminal_runtime.rs34 findings · 10.0 deducted
- worst item is medium severity. Refactoring1,484TuiModel+1.7 health, XL effort · crates/zorai-tui/src/app/dismiss_active_main_pane_to_confirm_pending_chat_action_parts/execute_selected_inline_message_action_to_delete_notification.rs
- worst item is medium severity. Decisions245frontend/electron/main.cjs11 awaiting review · 234 hotspots ungoverned
- worst item is medium severity. Ownership2,507frontend/src/components/WorkspaceWorkbench.tsx86% single-owner concentration, 51 commits in 90d
- worst item is low severity. Dead code73workspaceActorOptionByValueUnreachable function (7 lines)
Composition
Open the graph- rust54%
- typescript25%
- python16%
- javascript3%
- shell<1%
Explore this codebase
- Docs3,570 pages across 7 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files4,985 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 18 entry points
- Code healthPer-file scores, 9,890 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.