Dify vs Flowise
An independent, evidence-based trust comparison of Dify and Flowise, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Dify leads on trust — 78.8/100 (Grade B) vs 75.1/100 (Grade B), a 3.7-point gap. Full breakdown below.
| Signal | Difylanggenius/dify | FlowiseFlowiseAI/Flowise |
|---|---|---|
| HVTrust score | 78.8 | 75.1 |
| Evidence grade | B | B |
| Coverage grade | A | B |
| Overall rank | #70 | #87 |
| Rank in Workflow Platforms | #5 | #6 |
| GitHub stars | 151.8k | 55.2k |
| Last updated | today | 1d ago |
| Build provenance | No | No |
| OSSF Scorecard | 6.1 / 10 | 6.8 / 10 |
| License | NOASSERTION | NOASSERTION |
| Downloads | 19.9M/wk | 6.5M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.6 | 13.5 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 13.7 | 14.3 |
| Maintenance / 20 | 20.0 | 17.3 |
| Adoption / 20 | 20.0 | 20.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Declared | Implemented |
| External providers | — | 6 — Anthropic, Google Gemini, OpenAI, … |
| Requires API keys | No | No |
| Plugin surface | plugins | — |
| Provenance drift | Partial | Unknown |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →