A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 7.6 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
90.3
74,760 stars · MIT
Dify 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. Dify is written mainly in Python; Front-End-Checklist is written mainly in MDX. The composite score is 97.9 for Dify and 90.3 for Front-End-Checklist.
Dify has 161,357 GitHub stars to Front-End-Checklist's 74,760, a gap of 86,597 (2.16×). Forks are 25,515 for Dify and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 87.
Push history: Dify 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,422 for Dify (0.009 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 78.
Dify 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. 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 96 for Dify and 96 for Front-End-Checklist. This is a procurement signal, not legal advice.
In AI Agents, both Dify (161,357 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: Dify is open source, Front-End-Checklist is open source.
The lead is split. Dify is furthest ahead on recent activity (100 to 78), while Front-End-Checklist is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against Front-End-Checklist at 90.3, a 7.6 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 | Dify | Front-End-Checklist |
|---|---|---|
| GitHub stars | 161,357 | 74,760 |
| Forks | 25,515 | 6,781 |
| Open issues | 1,422 | 22 |
| Adoption | 100 | 94 |
| Activity | 100 | 78 |
| Community | 100 | 87 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 90.3 |
Dify is a platform for building LLM apps: prompts, RAG pipelines, agents, and observability. It is aimed at teams that want that stack on their own machines.
🗂 The essential checklist for modern web development, for humans and AI agents
Dify has more GitHub stars: 161,357 versus 74,760 for Front-End-Checklist. The gap is 86,597 stars.
Dify 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 Dify and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
Dify 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. 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.
Dify scores 97.9 and Front-End-Checklist scores 90.3. This page calls that a clear lead for Dify.