Botpress vs Flowise
Botpress leads on trust: 86.6/100 (Grade A) against 61.4/100 (Grade C), a 25.2-point gap. Botpress leads on supply-chain integrity and maintenance, and rests on broader evidence; Flowise leads on adoption.
The open-source hub to build & deploy GPT/LLM Agents ⚡️
Choose Botpress if supply-chain integrity and maintenance matter most.
- +12.9Maintenance: last push 1d ago, against 101d ago
- +7.3Safety / Integrity: package provenance attested, against none
- +7.2Identity / Provenance: package provenance attested, against none
- A vs BEvidence coverage: 4 of 5 independent signal types, against 3
Build AI Agents, Visually
Choose Flowise if adoption matters most.
- +4.6Adoption: 7.4M weekly downloads against 11.2k
Where they differ
An independent, evidence-based trust comparison of Botpress 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.
Full evidence
| Signal | Botpressbotpress/botpress | FlowiseFlowiseAI/Flowise |
|---|---|---|
| HVTrust score | 86.6 | 61.4 |
| Evidence grade | A | C |
| Coverage grade | A | B |
| Overall rank | #83 | #668 |
| Rank in Workflow Platforms | #3 | #15 |
| GitHub stars | 15.0k | 55.6k |
| Last updated | 1d ago | 101d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 5.9 / 10 | 6.0 / 10 |
| License | MIT | NOASSERTION |
| Downloads | 11k/wk | 7.4M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 19.8 | 12.5 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 13.5 | 13.6 |
| Maintenance / 20 | 18.2 | 5.3 |
| Adoption / 20 | 15.4 | 20.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | — | Implemented |
| External providers | — | 6 — Anthropic, Google Gemini, OpenAI, … |
| Requires API keys | Yes | No |
| Plugin surface | plugins | — |
| Provenance drift | Match | 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 →