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.
90 of your 230 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 21.12s · analysis 21.17s · 43.8 MB · GitHub API rate-limit (preflight)

FlowiseAI/Flowise

https://github.com/FlowiseAI/Flowise · scanned 2026-06-05 11:20 UTC (5 days, 13 hours ago) · 10 languages

790 raw signals (202 security + 588 graph) 11/13 scanners ran 68th percentile · Typescript · large (100-500K LoC) System graph score 52 (higher by 27)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
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 47.0 0.20 9.40
documentation_score 83.0 0.15 12.45
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 78.8
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

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.

Commented-out code 28 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 packages/agentflow/src/__test_utils__/jest-en…
  • info Commented-code block (7 lines) in packages/agentflow/src/infrastructure/api/loa…
  • info Commented-code block (5 lines) in packages/ui/src/serviceWorker.js:4
  • info Commented-code block (5 lines) in packages/ui/src/ui-component/dialog/InviteUse…
  • info Commented-code block (7 lines) in packages/ui/src/ui-component/input/Suggestion…
  • info Commented-code block (5 lines) in packages/ui/src/ui-component/input/suggestion…
  • info Commented-code block (5 lines) in packages/ui/src/routes/MainRoutes.jsx:284
  • info Commented-code block (8 lines) in packages/ui/src/menu-items/dashboard.js:271
  • info Commented-code block (6 lines) in packages/ui/src/views/docstore/DocStoreAPIDia…
  • info Commented-code block (5 lines) in packages/ui/src/views/tools/CustomMcpServerDi…
  • info Commented-code block (6 lines) in packages/observe/examples/vite.config.ts:9
  • info Commented-code block (5 lines) in packages/observe/src/__test_utils__/jest-envi…
View all commented-out code findings →
Config drift 11 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.
11 matching findings on this repo
  • low File has no detected symbols: packages/agentflow/vite.config.ts
  • low File has no detected symbols: packages/agentflow/jest.config.js
  • low File has no detected symbols: packages/agentflow/examples/vite.config.ts
  • low File has no detected symbols: packages/agentflow/examples/src/config.ts
  • info TODO/FIXME marker in shipping code — packages/server/src/AppConfig.ts:3
  • info TODO/FIXME marker in shipping code — packages/server/src/utils/getUploadsConfig…
  • low Very large file: packages/ui/src/views/auth/ssoConfig.jsx (1033 lines)
  • low Very large file: packages/ui/src/views/assistants/custom/CustomAssistantConfigu…
  • low Very large file: packages/ui/src/views/docstore/VectorStoreConfigure.jsx (1001 …
  • info Commented-code block (6 lines) in packages/observe/examples/vite.config.ts:9
  • info Commented-code block (6 lines) in packages/components/jest.config.js:14
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/d33148df-aaa2-49a7-9b50-965011560982/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d33148df-aaa2-49a7-9b50-965011560982/

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.