Ruflo

🌊 The original agent meta-harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build co

Multi-Agent Systems TypeScript Grade C Listed MIT
64.2/100
Rank #247 of 1283
Compare Ruflo

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-11 · 1d ago
Recent change
Rank +1

Is Ruflo safe? Ruflo scores 64.2/100 (Grade C), ranked #247 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 19% 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 Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 16 spots (#221 → #237)
2026-08-08
Rank Moved
Rank dropped 42 spots (#177 → #219)
2026-07-30
Rank Moved
Rank rose 18 spots (#208 → #190)
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
97.2
Activity sub-score · out of 100
#7

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

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
67.7k
Forks
8.1k
Last Push
2026-08-11
yesterday
Commits (4 wk)
176
Downloads (7d)
HN mentions (30d)
Open Issues
561
Rank Change
▼4
was #243

Analysis

HVTrust Dimensions vs Multi-Agent Systems

64.2 / 100 · 100.0% confidence

Ruflo Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.8 / 25
1.6 above avg 6.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
2.2 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.9 above avg 13.0
AdoptionLog-scaled stars · package downloads
11.6 / 20
1.6 above avg 10.0

Activity Inputs

97.2 / 100
StarsRepository reach
29.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.2 / 20

Supply Chain Trust

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

Is Ruflo safe?

Ruflo 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 Ruflo publish package provenance?
No published build provenance is currently detected for Ruflo. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ruflo have an OpenSSF Scorecard?
Ruflo 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 Ruflo actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ruflo use?
Ruflo ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ruflo's commits signed?
19% of the last 100 commits to Ruflo 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 Ruflo head-to-head

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
Ruflo appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • filesystem
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Ruflo?

For maintainers

HVTrust scores Ruflo 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.

Reputation Timeline

Signal history
Rank 6Listed 1
2026-08-10
Rank Moved
Rank dropped 16 spots (#221 → #237)
2026-08-08
Rank Moved
Rank dropped 42 spots (#177 → #219)
2026-07-30
Rank Moved
Rank rose 18 spots (#208 → #190)
2026-07-29
Rank Moved
Rank dropped 13 spots (#195 → #208)
2026-07-14
Rank Moved
Rank dropped 12 spots (#169 → #181)
2026-07-13
Rank Moved
Rank dropped 22 spots (#147 → #169)
2026-06-24
Newly Listed
First tracked at rank #147

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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