A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 21.5 · decisive
A · leads
97.9
161,357 stars · Apache-2.0
B
76.4
17,726 stars · license n/a
Dify versus lemo-opuscar 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; lemo-opuscar is written mainly in JavaScript. The composite score is 97.9 for Dify and 76.4 for lemo-opuscar.
Dify has 161,357 GitHub stars to lemo-opuscar's 17,726, a gap of 143,631 (9.10×). Forks are 25,515 for Dify and 2,224 for lemo-opuscar. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 76.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and lemo-opuscar was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 1 for lemo-opuscar (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
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. lemo-opuscar is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Dify and 30 for lemo-opuscar. This is a procurement signal, not legal advice.
Only Dify is marked self-hostable here (161,357 stars, deploy score 100). lemo-opuscar is not (17,726 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Dify is open source, lemo-opuscar is unpriced in this catalog.
The lead is split. Dify is furthest ahead on license flexibility (96 to 30), while lemo-opuscar is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against lemo-opuscar at 76.4, a 21.5 point decisive 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 | lemo-opuscar |
|---|---|---|
| GitHub stars | 161,357 | 17,726 |
| Forks | 25,515 | 2,224 |
| Open issues | 1,422 | 1 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 84 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 76.4 |
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.
A toolbox of film styles made in code for Claude Code: 99 ready to use, and your own. Each style is a style prompt plus a demo film made entirely in code by Claude Opus 5.5, with no video model. By Lemomo. · 一套用代码做片的风格工具箱:99 种现成风格,也能做出你自己的
Dify has more GitHub stars: 161,357 versus 17,726 for lemo-opuscar. The gap is 143,631 stars.
Both were last pushed on 17 November 2026.
Only Dify is marked self-hostable. lemo-opuscar is not.
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. lemo-opuscar is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Dify scores 97.9 and lemo-opuscar scores 76.4. This page calls that a decisive lead for Dify.