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.
Sign up free Scan another repo
59 of your 108 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 28.04s · analysis 11.19s · 39.9 MB · GitHub API rate-limit (preflight)

AppFlowy-IO/AppFlowy

https://github.com/AppFlowy-IO/AppFlowy · scanned 2026-06-05 08:18 UTC (5 days, 20 hours ago) · 10 languages

223 raw signals (101 security + 122 graph) 11/13 scanners ran System graph score 76 (lower by 7)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
72.9
/100
Security checks
70
33 findings
System graph
76
88.9% cov · 14 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 39.0 0.20 7.80
documentation_score 70.0 0.15 10.50
practices_score 78.0 0.15 11.70
code_quality 80.0 0.10 8.00
Overall 1.00 69.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 0 High 11 Medium 5 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 33 System graph 14 Crowd 0 Layer: Cicd 13 Software 5 Security 5 Quality 18 Api 1 Hardware 4 Frontend 1

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.

Config drift 1 finding
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.
1 matching finding on this repo
  • low File has no detected symbols: commitlint.config.js
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/4b6bbd79-6a10-4b1c-852c-53d1dc74ab1e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4b6bbd79-6a10-4b1c-852c-53d1dc74ab1e/

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.