Read 2026-10-23
opensearch-project/opensearch: technical due diligence, read from its repository
What Borehole read in opensearch-project/opensearch's code and history at 0ab7848: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:8: names OpenSSF
Architecture & Codebase — including AI provenance
strongplugins/ingestion-hive/src/main/java/org/opensearch/plugin/hive/metastore/ThriftHiveMetastore.java is 8,687 lines, 84× this codebase's median file
adequateThe median source file here is 103 lines. 101 files exceed 1,030 lines, the largest being 8,687. 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.
plugins/ingestion-hive/src/main/java/org/opensearch/plugin/hive/metastore/ThriftHiveMetastore.java:1 — 8,687 lines (84× median) |
server/src/main/java/org/opensearch/index/shard/IndexShard.java:1 — 7,092 lines (68× median) |
server/src/main/java/org/opensearch/search/aggregations/metrics/AbstractHyperLogLog.java:1 — 5,975 lines (58× median) |
modules/lang-painless/src/main/java/org/opensearch/painless/antlr/PainlessParser.java:1 — 5,831 lines (56× median) |
server/src/main/java/org/opensearch/repositories/blobstore/BlobStoreRepository.java:1 — 4,971 lines (48× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate151 of 2119 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.
| 151 commits over 2,000 lines |
Product & Engineering Maturity
strong87 files still carry code deprecated more than two years ago
adequate87 files were marked deprecated over two years ago and still are, the oldest since Mar 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
server/src/main/java/org/opensearch/common/settings/Setting.java — deprecated since Mar 2021 |
server/src/main/java/org/opensearch/index/IndexModule.java — deprecated since Aug 2021 |
server/src/main/java/org/opensearch/index/engine/Engine.java — deprecated since Sep 2021 |
server/src/main/java/org/opensearch/index/IndexSettings.java — deprecated since Sep 2021 |
server/src/main/java/org/opensearch/common/joda/Joda.java — deprecated since Oct 2021 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 3.9.0, is not on the branch this survey read; the newest pre-release on it is 3.0.0-alpha1. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (20 Nov 2014 to 23 Oct 2026) only; older history was not read.
| tag 3.9.0 |
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.
distribution/docker/src/docker/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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/gradle-check.yml:35 — action pinned by tag |
.github/workflows/gradle-check.yml:48 — action pinned by tag |
3 shell commands built from strings
adequate3 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
dev-tools/prepare_release_update_documentation.py:37 — command run through a shell |
dev-tools/prepare_release_update_documentation.py:42 — command run through a shell |
dev-tools/prepare_release_update_documentation.py:47 — command run through a shell |
11 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 11 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 12 records name OpenSearch with nothing tying them to this repository (CVE-2025-23671, CVE-2026-107335, CVE-2026-111906, …).
| 2026-10-22: GHSA-68xw-fqpj-h922 (moderate), fixed in 2.19.7: DoS in zstd decompression |
| 2026-09-08: CVE-2026-84942 (moderate): Improper input validation in the Vega expression function implementation in OpenSearch Dashboards allows a remote authenticated actor with dashboard write permi |
| 2026-08-21: CVE-2026-77811 (moderate): Improper input validation in the dashboards-observability plugin in OpenSearch Dashboards allows a remote authenticated user with write permissions to OpenSearc |
| 2026-08-20: CVE-2026-18420 (high): Improper input validation in the Time Series Visual Builder (TSVB) plugin in OpenSearch Dashboards allows an authenticated remote user to execute arbitrary code |
| 2026-08-13: CVE-2026-18428 (high): A SQL query validation bypass in the Flint extension query handler in the OpenSearch SQL plugin allows a remote authenticated actor with async query access to e |
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 11,168 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 opensearch-project/opensearch: 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.