Read 2026-11-03
slothflowlabs/duckle: technical due diligence, read from its repository
What Borehole read in slothflowlabs/duckle's code and history at 772c19d: 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 | strong |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongcrates/duckdb-engine/src/plan/builders.rs is 11,654 lines, 56× this codebase's median file
adequateThe median source file here is 208 lines. 17 files exceed 2,080 lines, the largest being 11,654. 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.
crates/duckdb-engine/src/plan/builders.rs:1 — 11,654 lines (56× median) |
frontend/src/workflow-ui/fields/manifest-synth.ts:1 — 10,158 lines (48× median) |
crates/duckdb-engine/src/lib.rs:1 — 10,034 lines (48× median) |
crates/duckle-runner/src/serve.rs:1 — 9,154 lines (44× median) |
crates/duckdb-engine/src/plan/mod.rs:1 — 7,546 lines (36× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 158 of 1,779 commits (8.9%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 158 of 1,779 commits in the last 24 months carry review evidence; 8.9% across all 1,779 |
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 693 fixes in the last 24 months, 125 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.
| 125 of 693 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate11 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes 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.
.github/workflows/ci.yml:105 — action pinned by tag |
.github/workflows/ci.yml:108 — action pinned by tag |
.gitlab-ci.yml:138 — download piped into a shell |
20 locked dependencies have published vulnerabilities, 2 high or critical
adequate20 of 1,636 locked dependencies match 32 published advisories in OSV, 2 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.
Cargo.lock — zip 9.0.1: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
Cargo.lock — russh 0.64.1: GHSA-vp5q-ff62-jwqv (high), fixed in 0.65 |
Cargo.lock — glib 0.18.5: GHSA-wrw7-89jp-8q8g (moderate), fixed in 0.20.0 |
16 places insert HTML from a variable without sanitising it
adequate16 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
crates/duckle-runner/src/panel.html:453 — HTML from a variable |
crates/duckle-runner/src/panel.html:506 — HTML from a variable |
crates/duckle-runner/src/panel.html:575 — HTML from a variable |
7 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-09-23. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-09-23: GHSA-6xvv-58mg-4gxx (moderate), fixed in 0.7.4: Serve console pipeline id breaks out of an inline onclick handler because HTML-entity escaping is decoded first |
| 2026-09-09: GHSA-6756-rxf2-f9xr (moderate), fixed in 0.7.3: Run parameters are substituted into pipeline SQL unescaped, letting an Operator inject DuckDB SQL and read server files |
| 2026-09-09: GHSA-x7pg-4h32-8r25 (critical), fixed in 0.7.3: Official Duckle container: unauthenticated admin claim for 15 minutes after every start, then container RCE via code.shell |
| 2026-09-09: GHSA-c3jh-48x5-mhpw (moderate), fixed in 0.7.3: Duckle serve console: GET /api skips the rebinding guard and Local mode grants Admin |
| 2026-09-09: GHSA-58g9-237h-ch2g (high), fixed in 0.7.3: Duckle self-extracting artifacts trust a predictable /tmp cache directory — a local user can plant code the victim executes |
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 |
1 of 1 deployed images carry no version, or `latest`
adequate1 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.
docker-compose.coolify.yml:26 — 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 slothflowlabs/duckle: 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.