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

Scan timing: clone 1.73s · analysis 53.79s · 6.6 MB · GitHub API rate-limit (preflight)

usememos/memos

https://github.com/usememos/memos · scanned 2026-06-05 09:42 UTC (5 days, 17 hours ago) · 10 languages

499 raw signals (193 security + 306 graph) 4th percentile · Typescript · large (100-500K LoC) System graph score 77 (lower by 21)

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

Complete repo analysis

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

JSON
Combined
61.9
/100
Security checks
47
105 findings
System graph
77
100.0% cov · 98 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 0.0 0.25 0.00
testing_score 71.0 0.20 14.20
documentation_score 76.0 0.15 11.40
practices_score 80.0 0.15 12.00
code_quality 51.4 0.10 5.14
Overall 1.00 55.5
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 50 Medium 21 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 105 System graph 98 Crowd 0 Layer: Security 21 Software 107 Cicd 9 Quality 37 Frontend 25 Hardware 4

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 2 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/`.
2 matching findings on this repo
  • info Commented-code block (5 lines) in web/src/auth-state.ts:64
  • info Commented-code block (5 lines) in web/src/components/MemoEditor/index.tsx:86
View all commented-out code 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/3629e548-a242-47a9-bc2f-d17e4090d0d5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3629e548-a242-47a9-bc2f-d17e4090d0d5/

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.