Read 2026-11-03
sodadata/soda-core: technical due diligence, read from its repository
What Borehole read in sodadata/soda-core's code and history at b1cb7f2: 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
LICENSE:1: The licence is Elastic-2.0: source available, not open sourceCONTRIBUTING.md:5: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsoda-core/src/soda_core/common/soda_cloud.py is 2,730 lines, 22× this codebase's median file
adequateThe median source file here is 122 lines. 5 files exceed 1,220 lines, the largest being 2,730. 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.
soda-core/src/soda_core/common/soda_cloud.py:1 — 2,730 lines (22× median) |
soda-core/src/soda_core/common/sql_dialect.py:1 — 2,582 lines (21× median) |
soda-core/src/soda_core/contracts/impl/contract_verification_impl.py:1 — 2,031 lines (16× median) |
soda-core/src/soda_core/check_collections/base.py:1 — 1,762 lines (14× median) |
soda-core/src/soda_core/common/sql_ast.py:1 — 1,356 lines (11× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate3 outbound calls can wait forever
adequate3 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
soda-core/src/soda_core/common/soda_cloud.py:1749 — outbound call without a timeout |
soda-core/src/soda_core/common/soda_cloud.py:1784 — outbound call without a timeout |
soda-trino/src/soda_trino/common/data_sources/trino_data_source_connection.py:158 — outbound call without a timeout |
12 locked dependencies have published vulnerabilities, 7 high or critical in what ships
adequate12 of 111 locked dependencies match 40 published advisories in OSV, 20 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.
The licence is Elastic-2.0: source available, not open source
adequateLICENSE grants Elastic-2.0: source available, not open source; offering it as a managed service is not allowed. 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 — 91 lines, Elastic-2.0 |
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 498 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 2 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.
soda-trino/local_instance/docker-compose.yml:12 — 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 sodadata/soda-core: 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.