cocoindex-code vs ripwire
The two are close in size: 2.7k stars for cocoindex-code, 2.4k for ripwire. Over the days we have tracked them cocoindex-code moved +10.4% and ripwire +165.1%, so ripwire is growing faster right now.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
AST-based semantic search that is extremely lightweight, agent-friendly (skill/MCP plugin), and can run fully locally with offline embeddings.
- Stars
- 2.7k
- Tracked growth
- +10.4%
- Maturity
- ●●●●●
- Last commit
- 12h ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Local embeddings free with the 'full' variant; slim/latest uses cloud embeddings and your API key.
A zero-dependency, fully local CLI that produces a ranked, token-budgeted call-graph and blast-radius map with disclosed uncertainty and deterministic results, avoiding index servers and heavy token costs.
- Stars
- 2.4k
- Tracked growth
- +165.1%
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- C++
- License
- Apache-2.0
- Cost to run
- Free, local binary
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | cocoindex-code | ripwire |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Path/lang filters | ●●●●● Confidence & disclosure |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config file options | ●●●●● CLI options & grammars |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully local run | ●●●●● Fully local |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● BYO key / local | ●●●●● Provider-agnostic |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One‑minute setup | ●●●●● One-line install |
Which one to pick
Pick cocoindex-code if…
Easy setup — install in ~1 minute with zero config and optional local embeddings for offline/private use.
Pick ripwire if…
Privacy-first — run a single self-contained binary offline to get a ranked, token-efficient map of your repo without sending code to the cloud.
What people want from each one
cocoindex-io/cocoindex-code
Hacker News: Show HN: CocoIndex-Code open source embedded AST-based code MCP drew 2 points and 1 comments.
redhat-et/ripwire
Questions people ask
Is cocoindex-code better than ripwire?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. cocoindex-code is worth picking when easy setup — install in ~1 minute with zero config and optional local embeddings for offline/private use.
Which of cocoindex-code and ripwire keeps my code private?
cocoindex-code: Fully local run (5/5). ripwire: Fully local (5/5).
What does each one cost to run?
cocoindex-code: Local embeddings free with the 'full' variant; slim/latest uses cloud embeddings and your API key.. ripwire: Free, local binary.
Full profiles: cocoindex-io/cocoindex-code and redhat-et/ripwire. Everything else in Codebase context.