Borehole · Project · free tier
thanos-io/thanos
Free reading: not for reliance
729fda3 · 5,130 commits · 1,261 files
Read 2026-10-28

thanos-io/thanos: technical due diligence, read from its repository

What Borehole read in thanos-io/thanos's code and history at 729fda3: 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 Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsstrong
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • CONTRIBUTING.md:24: names CNCF
  • CONTRIBUTING.md:69: states a policy on AI-generated contributions

Architecture & Codebase — including AI provenance

strong
01.6

pkg/store/bucket.go is 4,050 lines, 30× this codebase's median file

adequate

The median source file here is 131 lines. 9 files exceed 1,310 lines, the largest being 4,050. 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.

Evidence
pkg/store/bucket.go:1 — 4,050 lines (30× median)
pkg/ui/react-app/src/thanos/pages/blocks/__testdata__/testdata.ts:1 — 2,223 lines (16× median)
pkg/receive/handler.go:1 — 2,039 lines (15× median)
pkg/receive/writecapnp/write_request.capnp.go:1 — 1,877 lines (14× median)
pkg/api/query/v1.go:1 — 1,805 lines (13× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.3

102 direct dependencies in a single manifest

adequate

go.mod declares 102 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.

Evidence
go.mod — 102 declared
pkg/ui/react-app/package.json — 45 declared
.bingo/go.mod — 0 declared
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v0.42.5, is not on the branch this survey read; the newest release on it is v0.42.4. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v0.42.5

Security & Reliability Posture

adequate
05.26

78 locked dependencies have published vulnerabilities, 21 high or critical in what ships

adequate

78 of 1,602 locked dependencies match 150 published advisories in OSV, 75 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.

Evidence
pkg/ui/react-app/pnpm-lock.yaml — @babel/traverse 7.17.3: GHSA-67hx-6x53-jw92 (critical), fixed in 7.23.2
pkg/ui/react-app/pnpm-lock.yaml — form-data 3.0.1: GHSA-fjxv-7rqg-78g4 (critical), fixed in 3.0.4
pkg/ui/react-app/pnpm-lock.yaml — ejs 3.1.6: GHSA-phwq-j96m-2c2q (critical), fixed in 3.1.7; a development dependency

Observability & Operations

strong
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

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on thanos-io/thanos: 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.