A · leads
deer-flow
97.9
85,441 stars · MIT
AI Agents
deer-flow leads by 4.9 · narrow
A · leads
97.9
85,441 stars · MIT
B
93.0
74,760 stars · MIT
deer-flow 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. deer-flow is written mainly in Python; Front-End-Checklist is written mainly in MDX. The composite score is 97.9 for deer-flow and 93.0 for Front-End-Checklist.
deer-flow has 85,441 GitHub stars to Front-End-Checklist's 74,760, a gap of 10,681 (1.14×). Forks are 12,046 for deer-flow and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 94.
Push history: deer-flow 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,117 for deer-flow (0.013 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.
Both deer-flow 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 deer-flow (85,441 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: deer-flow is open source, Front-End-Checklist is open source.
The lead is split. deer-flow 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.
deer-flow finishes ahead at 97.9 against Front-End-Checklist at 93.0, a 4.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 | deer-flow | Front-End-Checklist |
|---|---|---|
| GitHub stars | 85,441 | 74,760 |
| Forks | 12,046 | 6,781 |
| Open issues | 1,117 | 22 |
| Adoption | 100 | 99 |
| Activity | 100 | 78 |
| Community | 100 | 94 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.0 |
An open-source long-horizon SuperAgent harness that researches, codes, and creates. With the help of sandboxes, memories, tools, skill, subagents and message gateway, it handles different levels of tasks that could take minutes to hours.
🗂 The essential checklist for modern web development, for humans and AI agents
deer-flow has more GitHub stars: 85,441 versus 74,760 for Front-End-Checklist. The gap is 10,681 stars.
deer-flow 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 deer-flow and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
deer-flow 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.
deer-flow scores 97.9 and Front-End-Checklist scores 93.0. This page calls that a narrow lead for deer-flow.