---
title: "self-repair vs code-review-graph"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/theoxo-self-repair-vs-tirth8205-code-review-graph"
tools: ["theoxo-self-repair", "tirth8205-code-review-graph"]
---

# self-repair vs code-review-graph

*GraphCanon updated Jul 11, 2026*

## Verdict

Pick self-repair when tags unique to self-repair: python; pick code-review-graph when tags unique to code-review-graph: ai-coding, claude, claude-code, code-review.

[self-repair](https://github.com/theoxo/self-repair) reports 15 GitHub stars, 3 forks, and 1 open issues, last pushed May 2, 2024. [code-review-graph](https://code-review-graph.com) has 19k stars, 2.1k forks, and 185 open issues, last pushed Jun 14, 2026. Figures are from public GitHub metadata via [self-repair's repository](https://github.com/theoxo/self-repair) and [code-review-graph's repository](https://github.com/tirth8205/code-review-graph).

| | [self-repair](/tools/theoxo-self-repair.md) | [code-review-graph](/tools/tirth8205-code-review-graph.md) |
| --- | --- | --- |
| Tagline | [ICLR 2024]: Is Self-Repair a Silver Bullet for Code Generation? | Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo w |
| Stars | 15 | 19,416 |
| Forks | 3 | 2,078 |
| Open issues | 1 | 185 |
| Language | Python | Python |
| Adopt for | - | - |
| Persona | - | - |
| Runtime | - | - |
| License | - | MIT |
| Categories | Evaluation & Observability | Developer Tools, Evaluation & Observability, LLM Frameworks |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [self-repair](/tools/theoxo-self-repair.md) | [code-review-graph](/tools/tirth8205-code-review-graph.md) |
| --- | --- | --- |
| Maintenance | Archived (8%) | Active (82%) |
| Days since push | 800d | 26d |
| Archived on GitHub | Yes | No |
| Open issues (now) | 1 | 185 |
| Security scan | No criticals | No MCP manifest |
| Full report | [trust report](/tools/theoxo-self-repair/trust.md) | [trust report](/tools/tirth8205-code-review-graph/trust.md) |

## Choose when

### Choose self-repair if…

- Tags unique to self-repair: python.
- Leaner open-issue backlog (1).

### Choose code-review-graph if…

- Tags unique to code-review-graph: ai-coding, claude, claude-code, code-review.
- Also covers Developer Tools, LLM Frameworks.
- More GitHub stars (19k vs 15) - visibility, not fit.

## When NOT to use self-repair

- self-repair is archived on GitHub. Prefer an active alternative unless you maintain a private fork or need a frozen dependency.
- Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers.

## When NOT to use code-review-graph

- Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
- Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers.
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

## Common questions

### What is the difference between self-repair and code-review-graph?

self-repair: [ICLR 2024]: Is Self-Repair a Silver Bullet for Code Generation?. code-review-graph: Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo w. See the comparison table for live GitHub stats and shared categories.

### When should I choose self-repair over code-review-graph?

Choose self-repair over code-review-graph when Tags unique to self-repair: python; Leaner open-issue backlog (1).

### When should I choose code-review-graph over self-repair?

Choose code-review-graph over self-repair when Tags unique to code-review-graph: ai-coding, claude, claude-code, code-review; Also covers Developer Tools, LLM Frameworks; More GitHub stars (19k vs 15) - visibility, not fit.

### When should I avoid self-repair?

self-repair is archived on GitHub. Prefer an active alternative unless you maintain a private fork or need a frozen dependency. Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers.

### When should I avoid code-review-graph?

Developer Tools: A gateway is overkill when you're pinned to a single provider and model. Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

### Is self-repair or code-review-graph more popular on GitHub?

code-review-graph has more GitHub stars (19,416 vs 15). Stars measure visibility, not whether either tool fits your constraints.

### Are self-repair and code-review-graph open source?

Yes - both are open-source projects on GitHub.

### Where can I find alternatives to self-repair or code-review-graph?

GraphCanon lists graph-backed alternatives at [self-repair alternatives](/tools/theoxo-self-repair/alternatives) and [code-review-graph alternatives](/tools/tirth8205-code-review-graph/alternatives) ([self-repair markdown twin](/tools/theoxo-self-repair/alternatives.md), [code-review-graph markdown twin](/tools/tirth8205-code-review-graph/alternatives.md)), ranked by typed relationship edges rather than popularity votes.

### Is there a machine-readable version of this comparison?

Yes. The markdown twin at [this comparison](/compare/theoxo-self-repair-vs-tirth8205-code-review-graph.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, self-repair or code-review-graph?

self-repair: Archived. code-review-graph: Active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.

### Where are the full trust reports for self-repair and code-review-graph?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [self-repair trust report](/tools/theoxo-self-repair/trust); [code-review-graph trust report](/tools/tirth8205-code-review-graph/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=theoxo-self-repair`](/api/graphcanon/graph?tool=theoxo-self-repair)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
