Skills/npm/ruflo

ruflo@3.79.0

VERIFIED· not started

Publisher claims: "Ruflo - Enterprise AI agent orchestration platform. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher ruvnet · publishing for 527 daysInstalls 347KLast detonated 2 h ago
$claude mcp add ruflo -- npx -y ruflo
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y ruflo

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 3.78.1

vet-skills diff ruflo 3.78.1 3.79.0

In the sandbox, this version reached for nothing 3.78.1 did not. Compared from the two recorded runs, not from source.

3.79.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only. Only one of the two runs produced a tool list; tools are not compared.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 61 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
60sprocessdependency install exceeded 60s
60sclaimednot started: dependency install timed out; the server itself was not observed
60sprocessscript backend runs setup only
60sprocessno install scripts to re-run

Static findings

LOW
Unpinned dependencybin/ruflo.js:35 · Unpinned dependency'Stop running Ruflo MCP servers and their hosts, then reinstall with npm install -g ruflo@latest.'Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

No other findings across 782 lines in 4 files.

Cost to the agent

Instructions loaded
≈79 tok
1 file · 4 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.

ruflo@3.79.0 safety verdict: Verified (not started) — KillerSkills