gortex vs ripwire
Code-intelligence engine in one static Go binary: tree-sitter graph over 257 languages, compiler-grade resolution for 17, multi-repo, 175 configurable MCP tools — up to 50x fewer tokens. 100% local. — 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.
Same shape — one static binary, tree-sitter graph, compiler-grade resolution, many languages — ripwire differentiates on change-oriented ranking (`--for`), published evals against graph-DB MCPs, and an explicit lineage of the metrics it uses.
| gortex | ripwire | |
|---|---|---|
| Stars | 1.6k | 1.9k |
| Forks | 149 | 111 |
| Language | Go | C++ |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | yesterday |
| Topics | code-intel, local | code-intel, coding |
| Curated connections | 7 | 7 |
gortex — the curator's take
The coverage play on this shelf: 257 grammars, cross-repo and cross-SERVICE edges (HTTP routes, contracts) with a provenance/confidence tier the single-repo tools don't attempt, and one install that configures 19 coding agents. When NOT: 175 MCP tools is a context bill of its own — prune the toolset or your agent pays the index's price in schema tokens; benchmarks are self-published; and if you want memory as plain files, this is the opposite philosophy.
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.