mem0ai/mem0

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.

Scan timing: clone 7.75s · analysis 12.64s · 30.7 MB · GitHub API rate-limit (preflight)

https://github.com/mem0ai/mem0 · scanned 2026-05-31 01:24 UTC (2 weeks, 1 day ago) · 10 languages

946 raw signals (277 security + 669 graph) 11/13 scanners ran 94th percentile · Typescript · large (100-500K LoC) System graph score 48 (higher by 40)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 1 day ago · v2 · last Δ -0.3 (diff) · 365 actionable findings from 2 signal sources. 202 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 · 254 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`	100.0	0.20	20.00
`documentation_score`	93.0	0.15	13.95
`practices_score`	84.0	0.15	12.60
`code_quality`	68.0	0.10	6.80
Overall		1.00	87.3

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 13 High 53 Medium 26 Low 189 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 111 System graph 254 Crowd 0 Layer: Software 75 Quality 111 Security 51 Cicd 17 Frontend 44 Network 1 Hardware 7 Api 59

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `get_fact_retrieval_messages_legacy` in mem0/memory…

View all legacy markers findings →

Commented-out code 12 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 openclaw/index.ts:418
info Commented-code block (5 lines) in mem0/vector_stores/qdrant.py:315
info Commented-code block (5 lines) in mem0/vector_stores/s3_vectors.py:125
info Commented-code block (5 lines) in mem0/vector_stores/milvus.py:195
info Commented-code block (5 lines) in mem0/memory/telemetry.py:139
info Commented-code block (6 lines) in mem0/llms/aws_bedrock.py:585
info Commented-code block (5 lines) in cli/node/src/commands/init.ts:369
info Commented-code block (5 lines) in cli/python/src/mem0_cli/config.py:182
info Commented-code block (9 lines) in mem0-plugin/scripts/parse_export_file.py:48
info Commented-code block (6 lines) in mem0-ts/src/oss/src/config/manager.ts:60
info Commented-code block (5 lines) in mem0-ts/src/oss/src/vector_stores/langchain.t…
info Commented-code block (5 lines) in mem0-ts/src/oss/src/memory/index.ts:1047

View all commented-out code findings →

Config drift 19 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: vercel-ai-sdk/jest.config.js
low File has no detected symbols: vercel-ai-sdk/tsup.config.ts
low File has no detected symbols: vercel-ai-sdk/config/test-config.ts
low File has no detected symbols: openmemory/api/app/config.py
low File has no detected symbols: openmemory/ui/tailwind.config.ts
low Stray `console.log` in TS/JS — cli/node/src/commands/config.ts:42
low Very large file: mem0/configs/prompts.py (1062 lines)
info Commented-code block (5 lines) in cli/python/src/mem0_cli/config.py:182
info Commented-code block (6 lines) in mem0-ts/src/oss/src/config/manager.ts:60
high FastAPI PUT `update_configuration` without auth dependency — openmemory/api/app… openmemory/api/app/routers/config.py:141
high FastAPI PATCH `patch_configuration` without auth dependency — openmemory/api/ap… openmemory/api/app/routers/config.py:159
high FastAPI POST `reset_configuration` without auth dependency — openmemory/api/app… openmemory/api/app/routers/config.py:180

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/ca6b0b99-4c4e-4439-b664-2839dc2344fa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ca6b0b99-4c4e-4439-b664-2839dc2344fa/

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.