Borehole · Project · free tier
quickwit-oss/quickwit
Free reading: not for reliance
4871a55 · 3,887 commits · 1,360 files
Read 2026-10-22

quickwit-oss/quickwit: technical due diligence, read from its repository

What Borehole read in quickwit-oss/quickwit's code and history at 4871a55: 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 Maturityadequate
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • LICENSE: Relicensed: AGPL-3.0 → Apache-2.0 (2025-01-23)
  • AI_POLICY.md:1: states a policy on AI-generated contributions
  • README.md:3: names OpenSSF

Architecture & Codebase — including AI provenance

strong
01.6

quickwit/quickwit-search/src/root.rs is 5,826 lines, 34× this codebase's median file

adequate

The median source file here is 170 lines. 22 files exceed 1,700 lines, the largest being 5,826. 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
quickwit/quickwit-search/src/root.rs:1 — 5,826 lines (34× median)
quickwit/quickwit-control-plane/src/ingest/ingest_controller.rs:1 — 4,202 lines (24× median)
quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:1 — 3,645 lines (21× median)
quickwit/quickwit-search/src/leaf.rs:1 — 3,284 lines (19× median)
quickwit/quickwit-control-plane/src/control_plane.rs:1 — 2,895 lines (17× median)

Engineering Process & SDLC Maturity

adequate
02.24

5% of recent commits change more than 2,000 lines

adequate

30 of 552 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.

Evidence
30 commits over 2,000 lines

Product & Engineering Maturity

adequate
04.19

14% of bug fixes add or change a test

adequate

Of 131 fixes in the last 24 months, 18 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
18 of 131
04.62

Releases are cut from another branch than the one surveyed

adequate

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

Evidence
tag v0.9.3

Security & Reliability Posture

adequate
05.6

2 Dockerfiles run the application as root

adequate

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

Evidence
Dockerfile — runs as root
distribution/docker/ubuntu/Dockerfile — runs as root
05.27

The build runs third-party code it does not pin

adequate

4 steps pipe a download straight into a shell. 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.

Evidence
.github/workflows/publish_docker_images.yml:47 — download piped into a shell
05.22

3 deserialisers that can run code

adequate

3 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

Evidence
quickwit/rest-api-tests/run_tests.py:33 — code-executing deserialiser
quickwit/rest-api-tests/run_tests.py:66 — code-executing deserialiser
quickwit/rest-api-tests/run_tests.py:286 — code-executing deserialiser
05.26

33 locked dependencies have published vulnerabilities, 3 high or critical in what ships

adequate

33 of 1,926 locked dependencies match 72 published advisories in OSV, 26 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
quickwit/rest-api-tests/Pipfile.lock — certifi 2026.2.25: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19
quickwit/quickwit-ui/yarn.lock — dompurify 3.4.14: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17
quickwit/rest-api-tests/Pipfile.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0
05.60

Relicensed: AGPL-3.0 → Apache-2.0 (2025-01-23)

adequate

The root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
LICENSE — AGPL-3.0 from 2021-04-13
LICENSE — Apache-2.0 from 2025-01-23
05.65

2 advisories against this project in the last 24 months, 2 high or critical

adequate

The newest was published on 2026-10-16. 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 2 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 0.9.0. Answer lives in: the release you run, set against each fixed version.

Evidence
2026-10-16: GHSA-g85h-2988-4cv8 (critical), fixed in 0.9.2: Unauthenticated remote command execution via Kafka source client_params in Linux release binaries
2026-09-23: GHSA-55pj-w5q5-r3m6 (high), fixed in 0.9.1: Unauthenticated denial of service via unbounded trace search limits

Observability & Operations

adequate
06.8

One request cannot be followed through the logs

adequate

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

Evidence
no request id, correlation id or tracing found
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 quickwit-oss/quickwit: 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.