Read 2026-10-22
milvus-io/milvus: technical due diligence, read from its repository
What Borehole read in milvus-io/milvus's code and history at f0f7677: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
stronginternal/core/src/segcore/ChunkedSegmentSealedImpl.cpp is 11,480 lines, 63× this codebase's median file
adequateThe median source file here is 180 lines. 83 files exceed 1,800 lines, the largest being 11,480. 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.
internal/core/src/segcore/ChunkedSegmentSealedImpl.cpp:1 — 11,480 lines (63× median) |
pkg/util/paramtable/component_param.go:1 — 10,213 lines (56× median) |
internal/proxy/impl.go:1 — 7,685 lines (42× median) |
internal/core/build-support/cpplint.py:1 — 6,902 lines (38× median) |
internal/core/unittest/test_sealed.cpp:1 — 6,539 lines (36× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate349 of 4362 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 349 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v3.0.3, is not on the branch this survey read; the newest release on it is v2.6.3. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.0.3 |
Security & Reliability Posture
adequate26 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
cmd/tools/binlogv2/requirements.txt:1 — >=1.28.0 |
cmd/tools/binlogv2/requirements.txt:2 — >=0.9.0 |
cmd/tools/binlogv2/requirements.txt:3 — >=2.0.0 |
cmd/tools/binlogv2/requirements.txt:4 — >=2.3.7 |
cmd/tools/binlogv2/requirements.txt:5 — >=7.2.0 |
1 environment file is committed
adequate.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env — committed environment file |
The build runs third-party code it does not pin
adequate18 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/all-contributors.yaml:32 — action pinned by tag |
.github/workflows/bump-version-only-for-standalone-embed-milvus.yaml:33 — action pinned by tag |
24 locked dependencies have published vulnerabilities, 4 high or critical
adequate24 of 822 locked dependencies match 44 published advisories in OSV, 4 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
internal/core/thirdparty/tantivy/tantivy-binding/Cargo.lock — oneshot 0.1.11: GHSA-rvr2-r3pv-5m4p (high), fixed in 0.1.12 |
internal/core/thirdparty/tantivy/tantivy-binding/Cargo.lock — quinn-proto 0.11.13: GHSA-4w2j-m93h-cj5j (high), fixed in 0.11.15 |
internal/core/thirdparty/tantivy/tantivy-binding/Cargo.lock — rustls-webpki 0.103.6: GHSA-82j2-j2ch-gfr8 (high), fixed in 0.103.13 |
6 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-09-27. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. GHSA-jh4h-22hq-x74p (moderate), GHSA-mhjq-8c7m-3f7p (critical) are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-09-27: GHSA-jh4h-22hq-x74p (moderate), fixed in 2.6.25: Import bypasses collection-level RBAC and reads Milvus internal storage |
| 2026-08-05: CVE-2026-69111 (high): Milvus through 2.6.22 and 3.0.0 contains an unauthenticated denial of service vulnerability that allows remote attackers to terminate service components by send |
| 2026-06-04: GHSA-jh6h-v6mp-h22v (low), fixed in 0.10.3-0.20260602041816-3d932f1c3e06: milvus: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgery |
| 2026-02-11: GHSA-7ppg-37fh-vcr6 (critical), fixed in 2.6.10: Milvus: Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromise |
| 2026-01-05: CVE-2025-15453 (low): A security vulnerability has been detected in milvus up to 2.6.7. This vulnerability affects the function expr.Exec of the file pkg/util/expr/expr.go of the com |
Observability & Operations
strongNo 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 |
4 of 10 deployed images carry no version, or `latest`
adequate4 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.
deployments/docker/standalone/docker-compose.yml:67 — image without a version |
docker-compose.yml:136 — image without a version |
docker-compose.yml:140 — 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 milvus-io/milvus: 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.