A · leads
CrewAI
95.9
61,027 stars · MIT
AI Agents
CrewAI leads by 2.1 · narrow
A · leads
95.9
61,027 stars · MIT
B
93.8
74,760 stars · MIT
CrewAI 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. CrewAI is written mainly in Python; Front-End-Checklist is written mainly in MDX. The composite score is 95.9 for CrewAI and 93.8 for Front-End-Checklist.
Front-End-Checklist has 74,760 GitHub stars to CrewAI's 61,027, a gap of 13,733 (1.23×). Forks are 9,211 for CrewAI and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 97.
Push history: CrewAI 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 1,276 for CrewAI (0.021 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 78.
Both CrewAI 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 CrewAI (61,027 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: CrewAI is open source, Front-End-Checklist is open source.
The lead is split. CrewAI is furthest ahead on recent activity (100 to 78), while Front-End-Checklist is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
CrewAI finishes ahead at 95.9 against Front-End-Checklist at 93.8, a 2.1 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 | CrewAI | Front-End-Checklist |
|---|---|---|
| GitHub stars | 61,027 | 74,760 |
| Forks | 9,211 | 6,781 |
| Open issues | 1,276 | 22 |
| Adoption | 98 | 100 |
| Activity | 100 | 78 |
| Community | 100 | 97 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.9 | 93.8 |
CrewAI is a framework for multi-agent workflows where role-based agents delegate tasks. It is a code library first, used by teams building their own agent systems.
🗂 The essential checklist for modern web development, for humans and AI agents
Front-End-Checklist has more GitHub stars: 74,760 versus 61,027 for CrewAI. The gap is 13,733 stars.
CrewAI 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 CrewAI and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
CrewAI 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.
CrewAI scores 95.9 and Front-End-Checklist scores 93.8. This page calls that a narrow lead for CrewAI.