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 — 76.7/100 (Grade B) vs 74.6/100 (Grade B), a 2.1-point gap. Full breakdown below.
| Signal | Difylanggenius/dify | FlowiseFlowiseAI/Flowise |
|---|---|---|
| HVTrust score | 76.7 | 74.6 |
| Evidence grade | B | B |
| Coverage grade | A | B |
| Overall rank | #68 | #79 |
| Rank in Workflow Platforms | #3 | #5 |
| GitHub stars | 151.3k | 55.1k |
| 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 | 16.9 |
| Adoption / 20 | 20.0 | 20.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Declared | Implemented |
| External providers | 2 — OpenAI, Postgres | 5 — Anthropic, OpenAI, Postgres, … |
| Requires API keys | No | No |
| Plugin surface | marketplace | 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.2 →