Registry › Compare › Airbyte vs Dify

Airbyte vs Dify

Dify leads on trust: 75.5/100 (Grade B) against 63.5/100 (Grade C), a 12.0-point gap. Dify leads on supply-chain integrity and adoption, and rests on broader evidence.

C Airbyte 63.5

Open-source data movement for ELT pipelines and AI agents — from APIs, databases & files to warehouses, lakes, and AI applications. Both self-hosted and Cloud.

airbytehq/airbyte · #599 overall · #13 Workflow Platforms · coverage C (2/5)

Airbyte doesn't lead on any scored dimension in this pair.

B Dify 75.5

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.

langgenius/dify · #269 overall · #5 Workflow Platforms · coverage A (4/5)

Choose Dify if supply-chain integrity and adoption matter most.

  • +9.6Adoption: 161.7k GitHub stars against 22.4k
  • +0.6Safety / Integrity: OSSF Scorecard 5.0 against 4.5
  • +0.5Transparency: OSSF Scorecard 5.0 against 4.5
  • A vs CEvidence coverage: 4 of 5 independent signal types, against 2

Where they differ

10.6
Safety / IntegrityDify +0.6
11.2
12.3
TransparencyDify +0.5
12.8
10.4
AdoptionDify +9.6
20.0
-0.6
Runtime calibrationDify +1.3
+0.7

2 dimensions identical: Identity 10.8 · Maintenance 20.0 · Full evidence table

An independent, evidence-based trust comparison of Airbyte and Dify, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal Airbyteairbytehq/airbyte Difylanggenius/dify
HVTrust score 63.5 75.5
Evidence grade C B
Coverage grade C A
Overall rank #599 #269
Rank in Workflow Platforms #13 #5
GitHub stars 22.4k 161.7k
Last updated today today
Build provenance No No
OSSF Scorecard 4.5 / 10 5.0 / 10
License NOASSERTION NOASSERTION
Downloads — 26.4M/wk
Trust dimensions (points earned)
Safety / integrity / 25 10.6 11.2
Identity & provenance / 18 10.8 10.8
Transparency / 17 12.3 12.8
Maintenance / 20 20.0 20.0
Adoption / 20 10.4 20.0
Runtime capability surface (full matrix)
MCP server Declared Declared
External providers — —
Requires API keys No Yes
Plugin surface extensions plugins
Provenance drift — Partial
Open in the live compare tool → Airbyte profile Dify profile More Workflow Platforms →

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.4 →