Airbyte vs Flowise
An independent, evidence-based trust comparison of Airbyte 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.
Airbyte leads on trust — 66.8/100 (Grade B) vs 65.5/100 (Grade B), a 1.3-point gap. Note: Airbyte's evidence coverage is thinner (coverage C vs B) — its score rests on fewer independent signal types. Full breakdown below.
| Signal | Airbyteairbytehq/airbyte | FlowiseFlowiseAI/Flowise |
|---|---|---|
| HVTrust score | 66.8 | 65.5 |
| Evidence grade | B | B |
| Coverage grade | C | B |
| Overall rank | #157 | #181 |
| Rank in Workflow Platforms | #8 | #11 |
| GitHub stars | 22.1k | 55.5k |
| Last updated | today | 39d ago |
| Build provenance | No | No |
| OSSF Scorecard | 5.1 / 10 | 6.0 / 10 |
| License | NOASSERTION | NOASSERTION |
| Downloads | — | 6.9M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 11.4 | 12.5 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 12.8 | 13.6 |
| Maintenance / 20 | 20.0 | 9.4 |
| Adoption / 20 | 10.4 | 20.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | 6 — Anthropic, Google Gemini, OpenAI, … |
| Requires API keys | No | No |
| Plugin surface | extensions | — |
| Provenance drift | — | 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 →