Read 2026-11-03
codenotary/immudb: technical due diligence, read from its repository
What Borehole read in codenotary/immudb's code and history at bfdce03: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE:1: The licence is BUSL-1.1: source available, not open sourceLICENSE: Relicensed: Apache-2.0 → BUSL-1.1 (2023-12-20)
Architecture & Codebase — including AI provenance
strongembedded/sql/stmt.go is 8,882 lines, 91× this codebase's median file
adequateThe median source file here is 97 lines. 17 files exceed 1,000 lines, the largest being 8,882. 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.
embedded/sql/stmt.go:1 — 8,882 lines (91× median) |
pkg/api/schema/schema.pb.gw.go:1 — 4,386 lines (45× median) |
embedded/store/immustore.go:1 — 3,764 lines (38× median) |
embedded/sql/sql_parser.go:1 — 3,085 lines (31× median) |
embedded/tbtree/tbtree.go:1 — 2,906 lines (29× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongGo 1.25 is past end of life
adequateThe code is pinned to Go 1.25 (end of life 2026-08-11). None of these receives security fixes any more; the first stopped on 2026-08-11. 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.
Dockerfile — Go 1.25, end of life 2026-08-11 |
11 files still carry code deprecated more than two years ago
adequate11 files were marked deprecated over two years ago and still are, the oldest since Jul 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
pkg/client/client.go — deprecated since Jul 2020 |
pkg/api/schema/schema.pb.go — deprecated since Dec 2020 |
pkg/server/options.go — deprecated since Dec 2021 |
pkg/api/schema/schema_grpc.pb.go — deprecated since Jul 2022 |
pkg/client/options.go — deprecated since Sep 2022 |
Releases are cut from another branch than the one surveyed
adequateThe newest pre-release, v2.0.0-RC1, is not on the branch this survey read; the newest release on it is v1.11.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.0.0-RC1 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| private key block, where fakes are usual |
The build runs third-party code it does not pin
adequate6 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/performance.yml:120 — action pinned by tag |
.github/workflows/performance.yml:148 — action pinned by tag |
The licence is BUSL-1.1: source available, not open source
adequateLICENSE grants BUSL-1.1: source available, not open source; production use restricted until the change date. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 89 lines, BUSL-1.1 |
Relicensed: Apache-2.0 → BUSL-1.1 (2023-12-20)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
adequateNo 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 |
Readiness and liveness probes are identical in 1 of 1 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
helm/templates/statefulset.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on codenotary/immudb: 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.