A
cherry-studio
88.0
53,594 stars · AGPL-3.0
AI Agents
Front-End-Checklist leads by 6.3 · narrow
A
88.0
53,594 stars · AGPL-3.0
B · leads
94.3
74,760 stars · MIT
cherry-studio 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. cherry-studio is written mainly in TypeScript; Front-End-Checklist is written mainly in MDX. The composite score is 88.0 for cherry-studio and 94.3 for Front-End-Checklist.
Front-End-Checklist has 74,760 GitHub stars to cherry-studio's 53,594, a gap of 21,166 (1.39×). Forks are 5,231 for cherry-studio and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 97 versus 100.
Push history: cherry-studio 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 2,788 for cherry-studio (0.052 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.
cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for cherry-studio and 96 for Front-End-Checklist. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 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: cherry-studio is open source, Front-End-Checklist is open source.
The lead is split. cherry-studio is furthest ahead on recent activity (100 to 78), while Front-End-Checklist is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Front-End-Checklist finishes ahead at 94.3 against cherry-studio at 88.0, a 6.3 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 | cherry-studio | Front-End-Checklist |
|---|---|---|
| GitHub stars | 53,594 | 74,760 |
| Forks | 5,231 | 6,781 |
| Open issues | 2,788 | 22 |
| Adoption | 97 | 100 |
| Activity | 100 | 78 |
| Community | 97 | 100 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.0 | 94.3 |
Your AI workspace for models, agents, and productivity.
🗂 The essential checklist for modern web development, for humans and AI agents
Front-End-Checklist has more GitHub stars: 74,760 versus 53,594 for cherry-studio. The gap is 21,166 stars.
cherry-studio 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 cherry-studio and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
Front-End-Checklist scores 94.3 and cherry-studio scores 88.0. This page calls that a narrow lead for Front-End-Checklist.