Flowise vs Trigger.dev
An independent, evidence-based trust comparison of Flowise and Trigger.dev, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Trigger.dev leads on trust — 91.9/100 (Grade A) vs 73.2/100 (Grade B), a 18.7-point gap. Full breakdown below.
| Signal | FlowiseFlowiseAI/Flowise | Trigger.devtriggerdotdev/trigger.dev |
|---|---|---|
| HVTrust score | 73.2 | 91.9 |
| Evidence grade | B | A |
| Coverage grade | B | B |
| Overall rank | #100 | #5 |
| Rank in Workflow Platforms | #5 | #1 |
| GitHub stars | 55.4k | 16.0k |
| Last updated | 2d ago | today |
| Build provenance | No | Yes |
| OSSF Scorecard | 6.0 / 10 | 7.2 / 10 |
| License | NOASSERTION | Apache-2.0 |
| Downloads | 6.5M/wk | 608k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.5 | 21.5 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 13.6 | 14.6 |
| Maintenance / 20 | 17.1 | 20.0 |
| Adoption / 20 | 20.0 | 17.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 6 — Anthropic, Google Gemini, OpenAI, … | 4 — Anthropic, OpenAI, Postgres, … |
| Requires API keys | No | No |
| Plugin surface | — | extensions |
| Provenance drift | Unknown | Match |
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 →