A
Front-End-Checklist
92.8
74,760 stars · MIT
AI Agents
ragflow leads by 5.1 · narrow
A
92.8
74,760 stars · MIT
B · leads
97.9
94,309 stars · Apache-2.0
Front-End-Checklist versus ragflow 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; ragflow is written mainly in Go. The composite score is 92.8 for Front-End-Checklist and 97.9 for ragflow.
ragflow has 94,309 GitHub stars to Front-End-Checklist's 74,760, a gap of 19,549 (1.26×). Forks are 6,781 for Front-End-Checklist and 11,335 for ragflow. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 94 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 1,317 for ragflow (0.014 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. ragflow 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 ragflow. This is a procurement signal, not legal advice.
In AI Agents, both Front-End-Checklist (74,760 stars) and ragflow (94,309 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, ragflow is open source.
The lead is split. Front-End-Checklist is furthest ahead on issue health (96 to 84), while ragflow is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
ragflow finishes ahead at 97.9 against Front-End-Checklist at 92.8, a 5.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 | Front-End-Checklist | ragflow |
|---|---|---|
| GitHub stars | 74,760 | 94,309 |
| Forks | 6,781 | 11,335 |
| Open issues | 22 | 1,317 |
| Adoption | 98 | 100 |
| Activity | 78 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.8 | 97.9 |
🗂 The essential checklist for modern web development, for humans and AI agents
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
ragflow has more GitHub stars: 94,309 versus 74,760 for Front-End-Checklist. The gap is 19,549 stars.
ragflow 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 ragflow 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. ragflow 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.
ragflow scores 97.9 and Front-End-Checklist scores 92.8. This page calls that a narrow lead for ragflow.