Borehole · Project · free tier
sodadata/soda-core
Free reading: not for reliance
b1cb7f2 · 327 commits · 506 files
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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • LICENSE:1: The licence is Elastic-2.0: source available, not open source
  • CONTRIBUTING.md:5: states a policy on AI-generated contributions

Architecture & Codebase — including AI provenance

strong
01.6

soda-core/src/soda_core/common/soda_cloud.py is 2,730 lines, 22× this codebase's median file

adequate

The 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.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.13

3 outbound calls can wait forever

adequate

3 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.

Evidence
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
05.26

12 locked dependencies have published vulnerabilities, 7 high or critical in what ships

adequate

12 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.

Evidence
uv.lock — certifi 2026.1.4: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18
uv.lock — oauthlib 3.3.1: GHSA-3jp2-3mrg-2vxc (high), fixed in 4.0.0
uv.lock — pyasn1 0.6.4: GHSA-2qm8-x737-gmw5 (high), fixed in 0.6.5
05.66

The licence is Elastic-2.0: source available, not open source

adequate

LICENSE 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.

Evidence
LICENSE:1 — 91 lines, Elastic-2.0

Observability & Operations

adequate
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
searched 498 files for 10 structured logging libraries; 0 matched
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised
06.18

1 of 2 deployed images carry no version, or `latest`

adequate

1 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.

Evidence
soda-trino/local_instance/docker-compose.yml:12 — image without a version

Fit with the Acquirer

not assessable

Not 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.