A
Front-End-Checklist
92.0
74,760 stars · MIT
AI Agents
gemini-cli leads by 5.9 · narrow
A
92.0
74,760 stars · MIT
B · leads
97.9
108,897 stars · Apache-2.0
Front-End-Checklist versus gemini-cli is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Front-End-Checklist is written mainly in MDX; gemini-cli is written mainly in TypeScript. The composite score is 92.0 for Front-End-Checklist and 97.9 for gemini-cli.
gemini-cli has 108,897 GitHub stars to Front-End-Checklist's 74,760, a gap of 34,137 (1.46×). Forks are 6,781 for Front-End-Checklist and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 92 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 96 and 84; activity scores are 78 and 100.
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. gemini-cli 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 Front-End-Checklist and 96 for gemini-cli. This is a procurement signal, not legal advice.
In AI Agents, both Front-End-Checklist (74,760 stars) and gemini-cli (108,897 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: Front-End-Checklist is open source, gemini-cli is open source.
The lead is split. Front-End-Checklist is furthest ahead on issue health (96 to 84), while gemini-cli is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
gemini-cli finishes ahead at 97.9 against Front-End-Checklist at 92.0, a 5.9 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 | Front-End-Checklist | gemini-cli |
|---|---|---|
| GitHub stars | 74,760 | 108,897 |
| Forks | 6,781 | 14,956 |
| Open issues | 22 | 739 |
| Adoption | 97 | 100 |
| Activity | 78 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.0 | 97.9 |
🗂 The essential checklist for modern web development, for humans and AI agents
An open-source AI agent that brings the power of Gemini directly into your terminal.
gemini-cli has more GitHub stars: 108,897 versus 74,760 for Front-End-Checklist. The gap is 34,137 stars.
gemini-cli 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 Front-End-Checklist and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. gemini-cli 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.
gemini-cli scores 97.9 and Front-End-Checklist scores 92.0. This page calls that a narrow lead for gemini-cli.