Is Langflow safe to use?

Langflow has an HVTrust score of 79.4/100 (Grade B), ranked #71 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Langflow?

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

Langflow

langflow-ai/langflow

Langflow is a powerful tool for building and deploying AI-powered agents and workflows.

Workflow Platforms Python Grade B Listed MIT

79.4/100

Rank #71 of 1283

Compare Langflow

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 A · 4/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

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

Ranked neighbours in Workflow Platforms

#2 n8n — 89.6 (A) → #3 Botpress — 87.8 (A) → #5 Dify — 79.1 (B) → #6 Flowise — 75.2 (B) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-07-23

Activity Score Changed

Activity score up 5pts (93 → 98)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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 Langflow View Workflow Platforms Report missing data

98.6

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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

153.1k

Forks

9.8k

Last Push

2026-08-11

today

Commits (4 wk)

219

Downloads (7d)

20,979

pypi

HN mentions (30d)

Open Issues

217

Rank Change

was #71

Analysis

HVTrust Dimensions vs Workflow Platforms

79.4 / 100 · 100.0% confidence

Langflow Workflow Platforms average (24 agents)

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

11.8 / 25

1.4 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

13.2 / 17

0.8 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

1.8 above avg 18.2

AdoptionLog-scaled stars · package downloads

18.2 / 20

5.3 above avg 12.9

Activity Inputs

98.6 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

18.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

98%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 9

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 7

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Langflow safe?

Public supply-chain signals for Langflow are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Langflow carries less obvious unverified-evidence risk than projects with thin signals.

Does Langflow publish package provenance?

No published build provenance is currently detected for Langflow. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Langflow have an OpenSSF Scorecard?

Langflow has an OpenSSF Scorecard score of 5.5/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 Langflow actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Langflow use?

Langflow ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Langflow's commits signed?

98% of the last 100 commits to Langflow 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 Langflow head-to-head

Langflow vs Trigger.dev → Langflow vs n8n → Langflow 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

Langflow appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Postgres

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Langflow's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-06-15

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-06-13

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-06-11

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-06-10

Provider Added

Runtime surface grew — new detected provider dependency: Redis

Maintain Langflow?

For maintainers

HVTrust scores Langflow 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-07-23

Activity Score Changed

Activity score up 5pts (93 → 98)

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-06-15

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-06-15

Rank Moved

Rank dropped 10 spots (#55 → #65)

2026-06-13

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-06-11

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-06-11

Rank Moved

Rank dropped 10 spots (#55 → #65)

2026-06-10

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-06-10

Rank Moved

Rank rose 10 spots (#65 → #55)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (58.3 → 68.3)

2026-05-27

Scorecard Added

OSSF Scorecard: 5.3/10

2026-05-27

Grade Changed

Trust grade D → B

2026-05-27

Rank Moved

Rank rose 11 spots (#18 → #7)

2026-05-27

HVTrust Changed

HVTrust up 36.7pts (28.0 → 64.7)

2026-05-27

Activity Score Changed

Activity score up 25pts (73 → 98)

2026-05-26

Activity Score Changed

Activity score down 21pts (94 → 73)

2026-05-25

Newly Listed

First tracked at rank #9

GitHub → PyPI: langflow

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/langflow.svg)](https://hvtracker.net/agents/langflow)
            
HTML:
            <a href="https://hvtracker.net/agents/langflow"><img src="https://hvtracker.net/badge/langflow.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

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