Read 2026-10-23
apache/shardingsphere: technical due diligence, read from its repository
What Borehole read in apache/shardingsphere's code and history at f4acdb6: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
.github/PULL_REQUEST_TEMPLATE.md:16: states a policy on AI-generated contributionsREADME.md:17: names OpenSSFREADME.md:319: names CNCF
Architecture & Codebase — including AI provenance
adequateparser/sql/engine/dialect/oracle/src/main/antlr4/imports/oracle/OracleKeyword.g4 is 8,086 lines, 149× this codebase's median file
adequateThe median source file here is 54 lines. 39 files exceed 1,000 lines, the largest being 8,086. 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.
parser/sql/engine/dialect/oracle/src/main/antlr4/imports/oracle/OracleKeyword.g4:1 — 8,086 lines (149× median) |
parser/sql/engine/dialect/oracle/src/main/antlr4/imports/oracle/DDLStatement.g4:1 — 4,451 lines (82× median) |
parser/sql/engine/dialect/hive/src/main/antlr4/imports/hive/HiveKeyword.g4:1 — 3,636 lines (67× median) |
parser/sql/engine/dialect/doris/src/main/antlr4/imports/doris/DorisKeyword.g4:1 — 3,547 lines (65× median) |
parser/sql/engine/dialect/mysql/src/main/antlr4/imports/mysql/MySQLKeyword.g4:1 — 3,242 lines (60× median) |
1 base image floats: no version, or `latest`
adequate1 of 4 `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.
distribution/proxy/Dockerfile:18 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 5.5.3, is not on the branch this survey read; the newest release on it is 3.1.0. 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 (5 Feb 2016 to 23 Oct 2026) only; older history was not read.
| tag 5.5.3 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 17,839 tracked files; 0 present |
3 Dockerfiles run 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/agent/Dockerfile — runs as root |
distribution/mcp/Dockerfile — runs as root |
distribution/proxy/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/release-mcp.yml:116 — action pinned by tag |
.github/workflows/release-mcp.yml:121 — action pinned by tag |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-02-06. 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 3.1.0. Answer lives in: the release you run, set against each fixed version.
| 2025-02-06: CVE-2022-31764 (high): The Lite UI of Apache ShardingSphere ElasticJob-UI allows an attacker to perform RCE by constructing a special JDBC URL of H2 database. This issue affects Apach |
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 13,535 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 apache/shardingsphere: 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.