A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 17.2 · decisive
A · leads
99.1
305,069 stars · MIT
B
81.9
13,788 stars · MIT
ECC versus MiMo-Code 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; MiMo-Code is written mainly in TypeScript. The composite score is 99.1 for ECC and 81.9 for MiMo-Code.
ECC has 305,069 GitHub stars to MiMo-Code's 13,788, a gap of 291,281 (22.13×). Forks are 44,923 for ECC and 1,478 for MiMo-Code. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 68.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and MiMo-Code was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 1,191 for MiMo-Code (0.086 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
Both ECC and MiMo-Code are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and MiMo-Code (13,788 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, MiMo-Code 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 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against MiMo-Code at 81.9, a 17.2 point decisive 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 | MiMo-Code |
|---|---|---|
| GitHub stars | 305,069 | 13,788 |
| Forks | 44,923 | 1,478 |
| Open issues | 149 | 1,191 |
| Adoption | 100 | 76 |
| Activity | 100 | 100 |
| Community | 100 | 68 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 81.9 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
MiMo Code: Where Models and Agents Co-Evolve
ECC has more GitHub stars: 305,069 versus 13,788 for MiMo-Code. The gap is 291,281 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ECC and MiMo-Code 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. MiMo-Code 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ECC scores 99.1 and MiMo-Code scores 81.9. This page calls that a decisive lead for ECC.