repowise vs Understand-Anything
Codebase intelligence for AI and humans: deterministic code-health scores calibrated on real defects, graph-aware refactoring plans agents can execute, auto-docs and git analytics over 9 MCP tools. — versus — Plugin for Claude Code and 16 other hosts that turns any codebase into an interactive knowledge graph — multi-agent analysis, layered dashboard, guided tours, diff-impact view, domain mapping.
Overlapping codebase-intelligence job: repowise leans quantitative — defect-calibrated health scores, refactoring plans, git analytics over MCP; Understand Anything leans pedagogical — teach the architecture through an explorable graph.
| repowise | Understand-Anything | |
|---|---|---|
| Stars | 3.7k | 75k |
| Forks | 438 | 6.2k |
| Language | Python | TypeScript |
| License | AGPL-3.0 | MIT |
| Last activity | yesterday | yesterday |
| Topics | coding | coding |
| Curated connections | 3 | 3 |
repowise — the curator's take
The interesting bet: defect-risk scoring with NO LLM — 25 deterministic markers calibrated against a real defect corpus (published ROC AUC 0.74), indexed in seconds, then the same dependency graph generates concrete refactoring plans (split the god class, break the cycle) your coding agent executes. Health→locate→fix as one loop is what linters and dashboards don't do. NOT a pure-open play: AGPL-3.0 with a hosted-teams funnel, and benchmark claims are self-published — reproduce them on your repo before quoting them; overlaps only partially with symbol-level code-graph MCPs.
Understand-Anything — the curator's take
The onboarding killer app, and its motto is the right one: graphs that teach, not graphs that impress. /understand runs a multi-agent pipeline over the repo, then the dashboard gives you architecture layers, dependency-ordered guided tours, semantic search, diff blast-radius, and a business-domain view that maps code to real processes. The team trick is the sleeper: the graph is plain JSON — commit it once and every teammate skips the analysis. Incremental re-runs + a post-commit auto-update hook keep it fresh. Budget real tokens for the first full run on a large repo (their own warning), or point it at a local model. NOT an agent context server — this graph is for humans first; when you want a code graph served TO agents over MCP, that's codegraph-mcp or tokensave territory.