Week 45, updated 2 Nov 2026

Compare Automation & agent frameworks

CrewAI vs Dify

Updated : the last week a score, rank or safety result on this page changed.

CrewAI

57

#18 overall, #3 in Automation & agent frameworks

Caution

  • Maintenance 30%6245
  • Adoption 30%4584
  • Docs 20%6929
  • Community 20%, not measured yet––

Dify

56

#20 overall, #4 in Automation & agent frameworks

Caution

CrewAI scores 1 point higher. CrewAI leads on maintenance and docs; Dify leads on adoption.

What this does not tell you

Scores are percentiles of public GitHub signals. Nobody here tested these tools hands-on, so the higher score is not a verdict on which suits your project. Yellow marks the higher value.

Which one fits you

From measured data and licences, not from testing.

Pick CrewAI if

  • Recent activity and releases matter most to you (maintenance 62).
  • You rely on thorough README docs (docs 69 vs 29).
  • You need a permissive open-source licence (MIT).

Pick Dify if

  • You want the more widely adopted option (adoption 84).

Safety side by side

Automated scan, 2 Nov 2026. Not a manual audit.

  • CautionCrewAI8 critical-severity known vulnerabilities in runtime dependencies (OSV)
  • CautionDify1 critical-severity known vulnerability in runtime dependencies (OSV)
Why different labels?

A label partly reflects how much of each tool is visible and scannable, not only how risky it is. A tool without a lockfile cannot get a dependency check.

  • CrewAI: 8 critical-severity known vulnerabilities in runtime dependencies (OSV)
  • Dify: 1 critical-severity known vulnerability in runtime dependencies (OSV)

Repo facts

Yellow = the higher value, where higher is better.

FactCrewAIDify
Score5756
Stars60,400160,191
Last push1 Nov2 Nov
Releases, 90 days10+6
LicenceMITDify Open Source License (modified Apache-2.0)
Open sourceOpen sourceSource-available (modified Apache-2.0)
LanguagePythonPython
TypeAgent frameworkAI tool
Runs locallyyesyes
Hosted optionunknownmentioned

“Runs locally” and “Hosted option” are read from each README automatically (or from the official docs where noted); “unknown” means no evidence was found, not that it is absent.

Questions about CrewAI vs Dify

Answers use this week's StackGrade data.

CrewAI or Dify: which scores higher on StackGrade?

CrewAI scores 1 point higher in Week 45: CrewAI 57, Dify 56 out of 100. The score combines maintenance, adoption and docs (percentiles of public GitHub signals): CrewAI 62, 45 and 69; Dify 45, 84 and 29. Community (20% weight) is not measured yet. It is not a hands-on test, so a higher score does not say which tool suits your project.

Is CrewAI or Dify safer to use?

Safety labels from the automated scan of 2 Nov 2026: CrewAI: Caution, 8 critical-severity known vulnerabilities in runtime dependencies (OSV); Dify: Caution, 1 critical-severity known vulnerability in runtime dependencies (OSV). It is an automated scan, not a manual audit.

Which is more widely used, CrewAI or Dify?

By GitHub stars: Dify 160,191, CrewAI 60,400. Adoption score (percentile among all 52 tracked tools): CrewAI 45, Dify 84. Stars are one public signal and do not measure real-world use.

Which licences do CrewAI and Dify use?

CrewAI: MIT; Dify: Dify Open Source License (modified Apache-2.0). Read each licence text before commercial use.

Should I pick CrewAI or Dify?

Pick CrewAI if recent activity and releases matter most to you (maintenance 62); you rely on thorough README docs (docs 69 vs 29); you need a permissive open-source licence (MIT). Pick Dify if you want the more widely adopted option (adoption 84). This comes from measured public data and licences only, not from hands-on testing.

Full comparison table, every criterion
CrewAI vs Dify, data from 2 Nov 2026
 CrewAIcrewAIInc/crewAIDifylanggenius/dify
Score57 56
Rank#18 overall · #3 in use case#20 overall · #4 in use case
Maintenance (30%)6245
Adoption (30%)4584
Docs (20%)6929
Community (20%)not measurednot measured
Safety Caution
  • 8 critical-severity known vulnerabilities in runtime dependencies (OSV)
Caution
  • 1 critical-severity known vulnerability in runtime dependencies (OSV)
LicenseMITDify Open Source License (modified Apache-2.0)
Open sourceOpen sourceSource-available (modified Apache-2.0)
LanguagePythonPython
Stars60,400160,191
Last push
TypeAgent frameworkAI tool
Runs locallyyes (README: "uv tool install")yes (README: "docker compose up")
Hosted optionunknownmentioned (README: "our Cloud")

Get the board every Monday

One email a week: the new top 10, the biggest score changes and every safety label that changed.

Free. Double opt-in: you confirm by email first, unsubscribe in one click.