Is Claude Flow safe and trustworthy?

tashan scores Claude Flow on public evidence — tashan score 77.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Claude Flow?

In Claude Code: run `claude mcp add claude-flow-cli -- npx -y @claude-flow/cli`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Claude Flow

npm

Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: AI & Agents — see all ranked ›

Work: Agent development · Retrieval systems

Who it is for: AI engineer

Install (Claude Code):

claude mcp add claude-flow-cli -- npx -y @claude-flow/cli

Not graded: shares its documentation with 2 other capabilities. A grade read off another project’s document would borrow its credit, or its blame.

tashan score: 77.0
Adoption: 36k/wk
Upkeep: 73.0
Freshness: 99.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 3.41.2 — this package, not its dependency tree

5 vulnerable dependenciesinstalls@opentelemetry/[email protected], @opentelemetry/[email protected], [email protected] — GHSA-8988-4f7v-96qf, GHSA-45rx-2jwx-cxfr · found by resolving all 592 packages this installs and querying OSV at the version each resolves to, not by name

Runs a script at install timecodenode ./scripts/postinstall.cjs

Reads and writes filesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-23 @claude-flow/cli published 3.38.11, was 3.38.12 A new release is available.
2026-08-24 @claude-flow/cli published 3.38.19, was 3.38.11 A new release is available.
2026-08-25 @claude-flow/cli published 3.38.20, was 3.38.19 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Claude Flow in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-claude-flow-cli.svg)](https://tashan.sh/capability/pkg-claude-flow-cli.html)

npm ↗ · source ↗ · pkg:@claude-flow/cli

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?