ruvnet/ruflo

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

117 of your 274 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 29.14s · analysis 26.81s · 64.8 MB · GitHub API rate-limit (preflight)

https://github.com/ruvnet/ruflo · scanned 2026-06-05 09:55 UTC (5 days, 16 hours ago) · 10 languages

1579 raw signals (239 security + 1340 graph) 11/13 scanners ran 51st percentile · Typescript · huge (>500K LoC) System graph score 45 (higher by 40)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 16 hours ago · v2 · 613 actionable findings from 2 signal sources. 296 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 530 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	98.0	0.20	19.60
`documentation_score`	77.0	0.15	11.55
`practices_score`	86.0	0.15	12.90
`code_quality`	70.0	0.10	7.00
Overall		1.00	85.0

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 10 High 51 Medium 68 Low 333 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 530 Crowd 0 Layer: Quality 241 Security 35 Cicd 24 Software 55 Frontend 210 Network 2 Hardware 18 Api 28

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low File has no detected symbols: ruflo/src/ruvocal/src/lib/utils/tree/convertLegac…
low Old/deprecated-named symbol `migrateFromLegacy` in v3/@claude-flow/cli/__tests_…
low Old/deprecated-named symbol `fstate_legacy` in v3/@claude-flow/cli/__tests__/q-…
low Old/deprecated-named symbol `wasLegacy` in v3/@claude-flow/cli/src/mcp-tools/ag…
low Old/deprecated-named symbol `checkAndMigrateLegacy` in v3/@claude-flow/cli/src/…

View all legacy markers findings →

Commented-out code 105 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in ruflo/src/ruvocal/mcp-bridge/index.js:16
info Commented-code block (7 lines) in ruflo/src/ruvocal/src/lib/wasm/index.ts:1158
info Commented-code block (5 lines) in ruflo/src/ruvocal/src/lib/wasm/wasm.worker.ts…
info Commented-code block (12 lines) in ruflo/src/ruvocal/src/lib/server/mcp/clientP…
info Commented-code block (7 lines) in ruflo/src/ruvocal/src/routes/conversation/[id…
info Commented-code block (5 lines) in ruflo/src/mcp-bridge/index.js:16
info Commented-code block (8 lines) in v3/vitest.config.ts:44
info Commented-code block (7 lines) in v3/__tests__/honesty/tool-honesty.test.ts:267
info Commented-code block (7 lines) in v3/@claude-flow/security/src/password-hasher.…
info Commented-code block (5 lines) in v3/@claude-flow/swarm/__tests__/byzantine-tra…
info Commented-code block (5 lines) in v3/@claude-flow/swarm/__tests__/consensus-fai…
info Commented-code block (5 lines) in v3/@claude-flow/swarm/__tests__/consensus-tra…

View all commented-out code findings →

Config drift 12 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

low File has no detected symbols: ruflo/src/ruvocal/postcss.config.js
low File has no detected symbols: ruflo/src/ruvocal/src/lib/types/ConfigKey.ts
low Stray `console.log` in TS/JS — ruflo/src/ruvocal/scripts/config.ts:12
low Stray `console.log` in TS/JS — ruflo/src/scripts/generate-config.js:132
info TODO/FIXME marker in shipping code — v3/vitest.config.ts:45
low Stray `console.log` in TS/JS — v3/goal_ui/supabase/functions/optimize-research-…
low Stray `console.log` in TS/JS — v3/plugins/gastown-bridge/tsup.config.ts:95
info Commented-code block (8 lines) in v3/vitest.config.ts:44
info Commented-code block (5 lines) in v3/@claude-flow/cli/vitest.config.ts:12
info Commented-code block (6 lines) in v3/@claude-flow/cli/src/mcp-tools/config-tool…
medium `fetch()` without try/.catch or AbortSignal — v3/goal_ui/supabase/functions/opt…
high Dangling fetch: POST https://ai.gateway.lovable.dev/v1/chat/completions (v3/goa…

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/b30981bf-1d40-4147-9134-b47754ec3cbb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b30981bf-1d40-4147-9134-b47754ec3cbb/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.