Read 2026-10-23
mem0ai/mem0: technical due diligence, read from its repository
What Borehole read in mem0ai/mem0's code and history at 2c81af3: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/PULL_REQUEST_TEMPLATE.md:22: states a policy on AI-generated contributions.gitmodules:1: 1 submodule(s) this survey does not read: evaluation
Architecture & Codebase — including AI provenance
strongmem0/memory/main.py is 3,913 lines, 37× this codebase's median file
adequateThe median source file here is 103 lines. 19 files exceed 1,030 lines, the largest being 3,913. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
mem0/memory/main.py:1 — 3,913 lines (37× median) |
integrations/agent-plugin-core/python/memory_core.py:1 — 2,677 lines (25× median) |
integrations/antigravity-plugin/core/memory_core.py:1 — 2,677 lines (25× median) |
integrations/claude-code-plugin/core/memory_core.py:1 — 2,677 lines (25× median) |
integrations/codex-plugin/core/memory_core.py:1 — 2,677 lines (25× median) |
264 errors caught and discarded in product code
adequate264 places catch an error and do nothing with it, across 53 files (0.9 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
cli/python/src/mem0_cli/app.py:75 — error caught and discarded |
cli/python/src/mem0_cli/commands/agent_mode_cmd.py:100 — error caught and discarded |
cli/python/src/mem0_cli/commands/init_cmd.py:313 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateNode.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
server/dashboard/Dockerfile — Node.js 20, end of life 2026-04-30 |
Fixes are 58% of recent work, up from 33%
adequateIn the last two quarters 58% of commits were fixes, against 33% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 56%, 61%, 60%, 39%, 39%, 26%, 19%, 15% |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
server/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/agent-plugins-typescript-checks.yml:21 — action pinned by tag |
.github/workflows/cd.yml:51 — action pinned by tag |
44 SQL statements built from strings
adequate44 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
mem0/memory/storage.py:87 — SQL built from a string |
integrations/agent-plugin-core/python/memory_core.py:971 — SQL built from a string |
integrations/agent-plugin-core/python/memory_core.py:1220 — SQL built from a string |
46 locked dependencies have published vulnerabilities, 10 high or critical in what ships
adequate46 of 2,216 locked dependencies match 130 published advisories in OSV, 69 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
poetry.lock — anyio 4.9.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
poetry.lock — certifi 2025.1.31: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
server/dashboard/pnpm-lock.yaml — next 15.5.24: GHSA-2464-fhr4-w9xw (critical), fixed in 15.5.28 |
12 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-10-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 4 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2.2.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names mem0 with nothing tying it to this repository (CVE-2026-19111).
| 2026-10-22: CVE-2026-115324 (critical): mem0 0.1.117 before 1.0.8 contains an sql injection vulnerability in mem0/vector_stores/databricks.py that allows attackers to inject SQL by influencing stored |
| 2026-10-20: GHSA-5324-3w58-qpp2 (moderate), fixed in 3.1.6: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope) |
| 2026-07-07: CVE-2026-59706 (critical): mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery via attacker-controlled ollama_ba |
| 2026-07-07: CVE-2026-59705 (critical): mem0's openmemory/api component contains an unauthenticated access vulnerability that allows unauthenticated attackers to read, write, and delete arbitrary user |
| 2026-06-09: CVE-2026-49948 (high): Mem0 versions through 0.2.8, fixed in commit ae7f406, contain a missing authorization vulnerability in the self-hosted server component where the POST /configur |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,370 files for 10 structured logging libraries; 0 matched |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on mem0ai/mem0: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.