Read 2026-10-23
getzep/graphiti: technical due diligence, read from its repository
What Borehole read in getzep/graphiti's code and history at 3ffc978: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequategraphiti_core/graphiti.py is 2,252 lines, 13× this codebase's median file
adequateThe median source file here is 172 lines. 2 files exceed 1,720 lines, the largest being 2,252. 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.
graphiti_core/graphiti.py:1 — 2,252 lines (13× median) |
graphiti_core/search/search_utils.py:1 — 2,076 lines (12× median) |
81 errors caught and discarded in product code
adequate81 places catch an error and do nothing with it, across 13 files (0.8 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.
graphiti_core/driver/falkordb_driver.py:183 — error caught and discarded |
graphiti_core/driver/neo4j_driver.py:97 — error caught and discarded |
graphiti_core/edges.py:63 — error caught and discarded |
1 base image floats: no version, or `latest`
adequate1 of 2 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
mcp_server/docker/Dockerfile:5 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
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.
mcp_server/docker/Dockerfile — runs as root |
7 locked dependencies have published vulnerabilities, 33 high or critical
adequate7 of 318 locked dependencies match 54 published advisories in OSV, 33 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. None of the high or critical ones is in what the product ships: they are optional extras of a package, installed only on request.
mcp_server/uv.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0; an optional extra |
mcp_server/uv.lock — aiohttp 3.14.3: GHSA-2g87-pp6c-29x5 (high), fixed in 3.14.4; an optional extra |
uv.lock — jupyter-server 2.20.0: GHSA-c3mw-737p-c7g2 (high), fixed in 2.21.0; an optional extra |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-13. 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 1 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 0.31.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names graphiti with nothing tying it to this repository (CVE-2026-33286).
| 2026-09-13: CVE-2026-90601 (moderate): A vulnerability was found in getzep graphiti up to 0.30.2. Affected is an unknown function of the file server/graph_service/main.py of the component REST API. T |
| 2026-03-11: GHSA-gg5m-55jj-8m5g (high), fixed in 0.28.2: Graphiti vulnerable to Cypher Injection via unsanitized node_labels in search filters |
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 414 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 |
1 of 5 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
mcp_server/docker/docker-compose-falkordb.yml:3 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on getzep/graphiti: 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.