Is Flowise safe to use?

Flowise has an HVTrust score of 71.9/100 (Grade B), ranked #117 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Flowise?

Flowise scores 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 55.4k GitHub stars and is categorized under Workflow Platforms.

Flowise

FlowiseAI/Flowise

Build AI Agents, Visually

Workflow Platforms TypeScript Grade B Needs review NOASSERTION

71.9/100

Rank #117 of 1308

Compare Flowise

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-13 · 12d ago

Recent change

Rank

Is Flowise safe? Flowise scores 71.9/100 (Grade B), ranked #117 of 1308 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.0/10; 100% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#4 Dify — 78.8 (B) → #5 Flyte — 72.2 (B) → #7 Airbyte — 66.2 (B) → #8 Nocobase — 66.1 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 10 spots (#115 → #125)

2026-08-14

Rank Moved

Rank dropped 16 spots (#91 → #107)

2026-08-13

Warning Issued

Warning: eligibility issues detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/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.

Review Flags

[5.1] repository is archived

Compare with Trigger.dev Get email alerts for Flowise View Workflow Platforms Report missing data

86.3

Activity sub-score · out of 100

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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

55.4k

Forks

24.9k

Last Push

2026-08-13

12 days ago

Commits (4 wk)

Downloads (7d)

6,484,312

npm+docker

HN mentions (30d)

—

Open Issues

700

Rank Change

▲8

was #125

Analysis

HVTrust Dimensions vs Workflow Platforms

71.9 / 100 · 100.0% confidence

Flowise Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.5 / 25

2.3 above avg 10.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

1.2 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

15.8 / 20

2.5 below avg 18.3

AdoptionLog-scaled stars · package downloads

20.0 / 20

7.4 above avg 12.6

Activity Inputs

86.3 / 100

StarsRepository reach

28.5 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

14.3 / 25

CommunityFork signal

20 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 25, 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 0

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Flowise safe?

Flowise has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.0/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?

Maintained. Last push was 12 days ago.

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 Langflow →

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

2026-08-24

Rank Moved

Rank dropped 10 spots (#115 → #125)

2026-08-14

Rank Moved

Rank dropped 16 spots (#91 → #107)

2026-08-13

Warning Issued

Warning: eligibility issues detected

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)

GitHub → npm: flowise

Embed Badge Badge guide for maintainers →

For maintainers

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