A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 26.7 · decisive
A · leads
99.1
305,069 stars · MIT
B
72.4
18,258 stars · Apache-2.0
ECC versus openfang 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; openfang is written mainly in Rust. The composite score is 99.1 for ECC and 72.4 for openfang.
ECC has 305,069 GitHub stars to openfang's 18,258, a gap of 286,811 (16.71×). Forks are 44,923 for ECC and 2,283 for openfang. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 72.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and openfang was last pushed on 02 July 2026 (138 days ago). Open issues stand at 149 for ECC (0.000 per star) and 136 for openfang (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 36.
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. openfang 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 openfang. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and openfang (18,258 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, openfang is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against openfang at 72.4, a 26.7 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 | openfang |
|---|---|---|
| GitHub stars | 305,069 | 18,258 |
| Forks | 44,923 | 2,283 |
| Open issues | 149 | 136 |
| Adoption | 100 | 78 |
| Activity | 100 | 36 |
| Community | 100 | 72 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 72.4 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Open-source Agent Operating System
ECC has more GitHub stars: 305,069 versus 18,258 for openfang. The gap is 286,811 stars.
ECC was pushed more recently: 17 November 2026 versus 02 July 2026 for openfang. That is 138 days apart.
Yes. This catalog marks both ECC and openfang 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. openfang 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 openfang scores 72.4. This page calls that a decisive lead for ECC.