Read 2026-10-23
canner/wrenai: technical due diligence, read from its repository
What Borehole read in canner/wrenai's code and history at 86fcca2: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: Apache-2.0 → AGPL-3.0 (2024-05-21)
Architecture & Codebase — including AI provenance
strongcore/wren-core/core/src/mdl/mod.rs is 5,955 lines, 53× this codebase's median file
adequateThe median source file here is 112 lines. 15 files exceed 1,120 lines, the largest being 5,955. 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.
core/wren-core/core/src/mdl/mod.rs:1 — 5,955 lines (53× median) |
core/wren/src/wren/context.py:1 — 2,214 lines (19× median) |
core/wren-core/core/src/mdl/function/dialect/bigquery/scalar.rs:1 — 1,944 lines (17× median) |
core/wren/src/wren/context_cli.py:1 — 1,828 lines (16× median) |
core/wren/src/wren/cloud.py:1 — 1,806 lines (16× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.50 to 1.15 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.50, second half 1.15 (split 2024-07-31) |
Fixes are 56% of recent work, up from 31%
adequateIn the last two quarters 56% of commits were fixes, against 31% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 62%, 49%, 26%, 39%, 40%, 27%, 28%, 25% |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 0.29.2, is not on the branch this survey read; the newest release on it is 0.29.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.29.2 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate9 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; 2 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.
.github/workflows/core-py-ci.yml:29 — action pinned by tag |
.github/workflows/publish-wren-core-py.yml:84 — action pinned by tag |
skills/install.sh:12 — download piped into a shell |
10 locked dependencies have published vulnerabilities, 1 high or critical
adequate10 of 601 locked dependencies match 19 published advisories in OSV, 1 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. None of the high or critical ones is in what the product ships: they are optional extras of a package, installed only on request. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
core/wren/uv.lock — fsspec 2026.1.0: GHSA-27vj-qcqg-25rc (high), fixed in 2026.6.0; an optional extra |
core/wren/uv.lock — mcp 1.28.1: GHSA-84m7-p3x7-pcfv (moderate), fixed in 1.30.0; an optional extra |
core/wren/uv.lock — oauthlib 3.3.1: GHSA-hj66-6f7g-4r5v (moderate), fixed in 4.0.0; an optional extra |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 51 lines, unrecognised |
Relicensed: Apache-2.0 → AGPL-3.0 (2024-05-21)
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
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on canner/wrenai: 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.