A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 11.1 · clear
A · leads
99.1
305,069 stars · MIT
B
88.0
74,760 stars · MIT
ECC versus Front-End-Checklist 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; Front-End-Checklist is written mainly in MDX. The composite score is 99.1 for ECC and 88.0 for Front-End-Checklist.
ECC has 305,069 GitHub stars to Front-End-Checklist's 74,760, a gap of 230,309 (4.08×). Forks are 44,923 for ECC and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 82.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and Front-End-Checklist was last pushed on 31 October 2026 (17 days ago). Open issues stand at 149 for ECC (0.000 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 78.
Both ECC and Front-End-Checklist 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 Front-End-Checklist (74,760 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, Front-End-Checklist is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against Front-End-Checklist at 88.0, a 11.1 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 | Front-End-Checklist |
|---|---|---|
| GitHub stars | 305,069 | 74,760 |
| Forks | 44,923 | 6,781 |
| Open issues | 149 | 22 |
| Adoption | 100 | 89 |
| Activity | 100 | 78 |
| Community | 100 | 82 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.0 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
🗂 The essential checklist for modern web development, for humans and AI agents
ECC has more GitHub stars: 305,069 versus 74,760 for Front-End-Checklist. The gap is 230,309 stars.
ECC was pushed more recently: 17 November 2026 versus 31 October 2026 for Front-End-Checklist. That is 17 days apart.
Yes. This catalog marks both ECC and Front-End-Checklist 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. Front-End-Checklist 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 Front-End-Checklist scores 88.0. This page calls that a clear lead for ECC.