Borehole · Project · free tier
quarylabs/quary
Free reading: not for reliance
1119101 · 495 commits · 691 files
Read 2026-11-03

quarylabs/quary: technical due diligence, read from its repository

What Borehole read in quarylabs/quary's code and history at 1119101: 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 provenanceadequate
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

adequate
01.6

rust/core/src/project.rs is 3,782 lines, 54× this codebase's median file

adequate

The median source file here is 69 lines. 8 files exceed 1,000 lines, the largest being 3,782. 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
rust/core/src/project.rs:1 — 3,782 lines (54× median)
rust/wasm-binding/src/rpc_proto_defined_functions.rs:1 — 2,479 lines (35× median)
rust/quary-databases/src/databases_postgres.rs:1 — 1,818 lines (26× median)
rust/core/src/project_to_sql.rs:1 — 1,732 lines (25× median)
rust/quary-databases/src/databases_duckdb.rs:1 — 1,312 lines (19× median)
01.7

6% of code blocks appear verbatim in more than one file

adequate

1,789 distinct 8-line blocks appear in two or more files. Copy-paste is the cheapest thing a generator does and among the more expensive things to inherit: a fix has to be applied everywhere the block landed, and nothing in the repository records where that is. Tests, fixtures and documentation examples are excluded — those repeat by design — so this is duplication in code that ships. Blocks are matched after normalising whitespace and only across different files.

Evidence
identical 8-line block in 7 files: js/packages/quary-extension/src/web/servicesDatabaseBigQueryNode.ts, js/packages/quary-extension/src/web/servicesDatabaseClickhouseNode.ts, js/packages/quary-extension/src/web/servicesDatabaseDremioNode.ts
identical 8-line block in 7 files: js/packages/quary-extension/src/web/servicesDatabaseBigQueryNode.ts, js/packages/quary-extension/src/web/servicesDatabaseClickhouseNode.ts, js/packages/quary-extension/src/web/servicesDatabaseDremioNode.ts
identical 8-line block in 7 files: js/packages/quary-extension/src/web/servicesDatabaseBigQueryNode.ts, js/packages/quary-extension/src/web/servicesDatabaseClickhouseNode.ts, js/packages/quary-extension/src/web/servicesDatabaseDremioNode.ts
identical 8-line block in 7 files: js/packages/quary-extension/src/web/servicesDatabaseBigQueryNode.ts, js/packages/quary-extension/src/web/servicesDatabaseClickhouseNode.ts, js/packages/quary-extension/src/web/servicesDatabaseDremioNode.ts
identical 8-line block in 7 files: js/packages/quary-extension/src/web/servicesDatabaseBigQueryNode.ts, js/packages/quary-extension/src/web/servicesDatabaseClickhouseNode.ts, js/packages/quary-extension/src/web/servicesDatabaseDremioNode.ts
01.25

1 base image floats: no version, or `latest`

adequate

1 of 2 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.

Evidence
.hacking/docker/Dockerfile:20 — base image without a version

Engineering Process & SDLC Maturity

strong
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 691 tracked files

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.6

1 Dockerfile runs 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
.hacking/docker/Dockerfile — runs as root

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on quarylabs/quary: 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.