A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 8.2 · clear
A · leads
99.1
305,069 stars · MIT
B
90.9
56,716 stars · Apache-2.0
ECC versus goose 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; goose is written mainly in Rust. The composite score is 99.1 for ECC and 90.9 for goose.
ECC has 305,069 GitHub stars to goose's 56,716, a gap of 248,353 (5.38×). Forks are 44,923 for ECC and 6,608 for goose. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 82.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and goose was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 530 for goose (0.009 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. goose 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 goose. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and goose (56,716 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, goose 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 fork community at 18 points (100 vs 82), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against goose at 90.9, a 8.2 point clear 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 | goose |
|---|---|---|
| GitHub stars | 305,069 | 56,716 |
| Forks | 44,923 | 6,608 |
| Open issues | 149 | 530 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 90.9 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
ECC has more GitHub stars: 305,069 versus 56,716 for goose. The gap is 248,353 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ECC and goose 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. goose 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 goose scores 90.9. This page calls that a clear lead for ECC.