Dify vs Flyte
An independent, evidence-based trust comparison of Dify and Flyte, 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.6/100 (Grade B) vs 72.4/100 (Grade B), a 6.2-point gap. Full breakdown below.
| Signal | Difylanggenius/dify | Flyteflyteorg/flyte |
|---|---|---|
| HVTrust score | 78.6 | 72.4 |
| Evidence grade | B | B |
| Coverage grade | A | B |
| Overall rank | #162 | #283 |
| Rank in Workflow Platforms | #5 | #6 |
| GitHub stars | 156.3k | 7.5k |
| Last updated | today | today |
| Build provenance | No | No |
| OSSF Scorecard | 6.0 / 10 | 5.9 / 10 |
| License | NOASSERTION | Apache-2.0 |
| Downloads | 23.9M/wk | 99k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.5 | 12.4 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 13.6 | 13.5 |
| Maintenance / 20 | 20.0 | 20.0 |
| Adoption / 20 | 20.0 | 16.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Declared | — |
| External providers | — | — |
| Requires API keys | No | No |
| Plugin surface | plugins | 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 →