Read 2026-10-23
turbot/steampipe: technical due diligence, read from its repository
What Borehole read in turbot/steampipe's code and history at 103201b: 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 | adequate |
| Product & Engineering Maturity | adequate |
| 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
LICENSE: Relicensed: MPL-2.0 → AGPL-3.0 (2021-05-20).gitmodules:1: 3 submodule(s) this survey does not read: tests/acceptance/lib/bats-core, tests/acceptance/lib/bats-assert, tests/acceptance/lib/bats-support
Architecture & Codebase — including AI provenance
adequateNo finding.
Engineering Process & SDLC Maturity
adequateNo finding.
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.54 to 7.31 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.54, second half 7.31 (split 2023-11-28) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.4.8, is not on the branch this survey read; the newest release on it is v2.4.7. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.4.8 |
Security & Reliability Posture
adequate9 SQL statements built from strings
adequate9 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
pkg/db/db_client/db_client_search_path.go:122 — SQL built from a string |
pkg/db/db_common/cache_control.go:36 — SQL built from a string |
pkg/db/db_common/cache_control.go:48 — SQL built from a string |
4 locked dependencies have published vulnerabilities, 3 high or critical
adequate4 of 215 locked dependencies match 8 published advisories in OSV, 3 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.
go.mod — github.com/containerd/containerd v1.7.35: GO-2026-5064 (high) |
go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.35.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
go.mod — go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.35.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
Relicensed: MPL-2.0 → AGPL-3.0 (2021-05-20)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
3 of 3 deployed images carry no version, or `latest`
adequate3 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.
pkg/otel/docker-compose.yaml:5 — image without a version |
pkg/otel/docker-compose.yaml:13 — image without a version |
pkg/otel/docker-compose.yaml:27 — 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 turbot/steampipe: 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.