updated 2026-08-11 19:32 UTC

Flowise

FlowiseAI/Flowise

Build AI Agents, Visually

Workflow Platforms TypeScript Grade B Listed NOASSERTION
75.2/100
Rank #90 of 1283
Compare Flowise

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-10 · 1d ago
Recent change
No recent signal change

Is Flowise safe? Flowise scores 75.2/100 (Grade B), ranked #90 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.8/10; 100% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#4 Langflow — 79.4 (B) → #5 Dify — 79.1 (B) → #7 Flyte — 72.3 (B) → #8 Airbyte — 67.1 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-13
Rank Moved
Rank dropped 11 spots (#64 → #75)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with Trigger.dev Get email alerts for Flowise View Workflow Platforms Report missing data
90.4
Activity sub-score · out of 100
#6
In Workflow Platforms

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-11 19:32 UTC · Repo last pushed yesterday

Activity & Reach

Stars
55.3k
Forks
24.9k
Last Push
2026-08-10
yesterday
Commits (4 wk)
22
Downloads (7d)
6,484,312
npm+docker
HN mentions (30d)
—
Open Issues
700
Rank Change
=
was #90

Analysis

HVTrust Dimensions vs Workflow Platforms

75.2 / 100 · 100.0% confidence

Flowise Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.5 / 25
3.1 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
1.9 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
0.8 below avg 18.2
AdoptionLog-scaled stars · package downloads
20.0 / 20
7.1 above avg 12.9

Activity Inputs

90.4 / 100
StarsRepository reach
28.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
17.0 / 25
CommunityFork signal
20 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.8 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 10
Security-Policy 9
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Flowise safe?

Public supply-chain signals for Flowise are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Flowise carries less obvious unverified-evidence risk than projects with thin signals.
Does Flowise publish package provenance?
No published build provenance is currently detected for Flowise. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Flowise have an OpenSSF Scorecard?
Flowise has an OpenSSF Scorecard score of 6.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Flowise actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Flowise use?
Flowise ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Flowise's commits signed?
100% of the last 100 commits to Flowise are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Flowise head-to-head

Flowise vs Trigger.dev → Flowise vs n8n → Flowise vs Botpress →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Flowise appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Flowise?

For maintainers

HVTrust scores Flowise from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5HVTrust 3Listed 1Grade 1Scorecard 1Score 1
2026-07-13
Rank Moved
Rank dropped 11 spots (#64 → #75)
2026-06-15
Rank Moved
Rank rose 13 spots (#67 → #54)
2026-06-14
Rank Moved
Rank dropped 12 spots (#55 → #67)
2026-06-02
Rank Moved
Rank rose 13 spots (#48 → #35)
2026-06-02
HVTrust Changed
HVTrust up 4.2pts (71.7 → 75.9)
2026-05-29
HVTrust Changed
HVTrust up 10.1pts (60.6 → 70.7)
2026-05-28
Activity Score Changed
Activity score up 20pts (73 → 93)
2026-05-27
Scorecard Added
OSSF Scorecard: 6.6/10
2026-05-27
Grade Changed
Trust grade D → C
2026-05-27
HVTrust Changed
HVTrust up 17.4pts (45.2 → 62.6)
2026-05-25
Rank Moved
Rank dropped 12 spots (#11 → #23)
2026-05-24
Newly Listed
First tracked at rank #11
GitHub → npm: flowise

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 75.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/flowise.svg)](https://hvtracker.net/agents/flowise)
HTML:
<a href="https://hvtracker.net/agents/flowise"><img src="https://hvtracker.net/badge/flowise.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON