A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 4.6 · narrow
A · leads
99.1
305,069 stars · MIT
B
94.5
149,362 stars · Apache-2.0
ECC versus graphify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ECC is written mainly in JavaScript; graphify is written mainly in Python. The composite score is 99.1 for ECC and 94.5 for graphify.
ECC has 305,069 GitHub stars to graphify's 149,362, a gap of 155,707 (2.04×). Forks are 44,923 for ECC and 14,362 for graphify. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 89.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and graphify was last pushed on 16 November 2026 (1 day ago). Open issues stand at 149 for ECC (0.000 per star) and 1,670 for graphify (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
ECC is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. graphify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for ECC and 96 for graphify. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and graphify (149,362 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ECC is open source, graphify is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against graphify at 94.5, a 4.6 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | ECC | graphify |
|---|---|---|
| GitHub stars | 305,069 | 149,362 |
| Forks | 44,923 | 14,362 |
| Open issues | 149 | 1,670 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 94.5 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
ECC has more GitHub stars: 305,069 versus 149,362 for graphify. The gap is 155,707 stars.
ECC was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both ECC and graphify as self-hostable. Confirm each project's deploy docs before you plan a migration.
ECC is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. graphify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ECC scores 99.1 and graphify scores 94.5. This page calls that a narrow lead for ECC.