Flowise vs Sim
Both are Grade C and 3.5 points apart, so choose on what you weigh most. Flowise leads on supply-chain integrity and adoption, and rests on broader evidence; Sim leads on maintenance. Note: Sim's evidence coverage is thinner (coverage C vs B) — its score rests on fewer independent signal types.
Build AI Agents, Visually
Choose Flowise if supply-chain integrity and adoption matter most.
- +9.2Adoption: 55.6k GitHub stars against 30.2k
- +0.7Safety / Integrity: OSSF Scorecard 6.0 against 5.4
- +0.5Transparency: OSSF Scorecard 6.0 against 5.4
- B vs CEvidence coverage: 3 of 5 independent signal types, against 2
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
Choose Sim if maintenance matters most.
- +14.7Maintenance: last push today, against 101d ago
Where they differ
1 dimension identical: Identity 10.8 · Full evidence table
An independent, evidence-based trust comparison of Flowise and Sim, 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 | FlowiseFlowiseAI/Flowise | Simsimstudioai/sim |
|---|---|---|
| HVTrust score | 61.4 | 64.9 |
| Evidence grade | C | C |
| Coverage grade | B | C |
| Overall rank | #668 | #537 |
| Rank in Workflow Platforms | #15 | #10 |
| GitHub stars | 55.6k | 30.2k |
| Last updated | 101d ago | today |
| Build provenance | No | No |
| OSSF Scorecard | 6.0 / 10 | 5.4 / 10 |
| License | NOASSERTION | Apache-2.0 |
| Downloads | 7.4M/wk | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.5 | 11.8 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 13.6 | 13.1 |
| Maintenance / 20 | 5.3 | 20.0 |
| Adoption / 20 | 20.0 | 10.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 6 — Anthropic, Google Gemini, OpenAI, … | 7 — Anthropic, Browserbase, E2B, … |
| Requires API keys | No | No |
| Plugin surface | — | plugins |
| 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.4 →