Not a task — informational heads-up for the maintainers, nothing to implement. Close it freely.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
ripwire earned a place on the map:
How we mapped it:
- alternative to
code-review-graph — Both compute a Tree-sitter-style call graph and blast-radius for agents; code-review-graph is a Python MCP with a persisted graph, ripwire is a single offline C++ binary that rebuilds in ~0.3s and adds tests-to-run and quality deltas.
- pairs well with
headroom — Two cuts at the same token bill: ripwire shrinks what the agent asks to read (ranked call graph instead of whole files), headroom compresses whatever it does read before the model sees it.
If you want it visible in your README, every mapped repo has a badge:
[](https://stackmap.shipwithai.xyz/repos/redhat-et/ripwire?utm_source=badge)
It renders as StackMap | ↔ 8 typed links and links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
ripwire earned a place on the map:
How we mapped it:
code-review-graph— Both compute a Tree-sitter-style call graph and blast-radius for agents; code-review-graph is a Python MCP with a persisted graph, ripwire is a single offline C++ binary that rebuilds in ~0.3s and adds tests-to-run and quality deltas.headroom— Two cuts at the same token bill: ripwire shrinks what the agent asks to read (ranked call graph instead of whole files), headroom compresses whatever it does read before the model sees it.If you want it visible in your README, every mapped repo has a badge:
It renders as
StackMap | ↔ 8 typed linksand links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.