repowise vs ripwire
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 — Red Hat's 'ripgrep of AI context': a zero-dependency C++23 CLI + MCP that hands a coding agent a ranked call graph — what to touch, blast radius, tests to run — with no index server.
Overlaps on the quality lens: both score code health from McCabe/Halstead/churn-style signals; repowise is the deeper health product, ripwire only reports deltas around the change you are about to make.
| repowise | ripwire | |
|---|---|---|
| Stars | 6.4k | 1.9k |
| Forks | 684 | 111 |
| Language | Python | C++ |
| License | AGPL-3.0 | Apache-2.0 |
| Last activity | yesterday | yesterday |
| Topics | code-intel | code-intel, coding |
| Curated connections | 6 | 7 |
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.
ripwire — the curator's take
Reach for this when you want code-context for an agent with the operational profile of ripgrep: one static binary, indexes a repo in well under a second on a few MB, no daemon, no embeddings, no API key — and it ships skills that tell Claude Code/Codex/Cursor/aider *when* to call it. The `--for="<change>"` mode (rank by intended change, then blast radius + tests-to-run + McCabe/Halstead quality deltas) is the differentiator over plain symbol graphs. Prefer the CLI; the MCP schema costs context every session. Not for you if you need a persistent, queryable graph across repos, natural-language-to-Cypher, or semantic search — it is deterministic and lexical/structural only.