Read 2026-11-03
trykimu/videoeditor: technical due diligence, read from its repository
What Borehole read in trykimu/videoeditor's code and history at 6a30d43: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE-AGPL3.md:1: The licence is AGPL-3.0 with additional terms
Architecture & Codebase — including AI provenance
strongapp/routes/landing.tsx is 1,766 lines, 25× this codebase's median file
adequateThe median source file here is 68 lines. 5 files exceed 1,000 lines, the largest being 1,766. 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.
app/routes/landing.tsx:1 — 1,766 lines (25× median) |
app/hooks/useTimeline.ts:1 — 1,749 lines (25× median) |
app/videorender/videorender.ts:1 — 1,595 lines (23× median) |
app/components/chat/ChatBox.tsx:1 — 1,580 lines (23× median) |
app/routes/home.tsx:1 — 1,286 lines (18× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 139 source files (0.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 0 test files / 139 source files |
Nothing in the history is tagged as a release
adequateAcross 3.9 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| 0 tags across 491 commits and 1429 days |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
backend/ai/routes.py:95 — SQL built from a string |
26 locked dependencies have published vulnerabilities, 20 high or critical in what ships
adequate26 of 970 locked dependencies match 77 published advisories in OSV, 37 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.
backend/uv.lock — anyio 4.12.1: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
backend/uv.lock — certifi 2026.2.25: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
pnpm-lock.yaml — better-auth 1.7.4: GHSA-965c-763c-88jm (critical), fixed in 1.7.7 |
The licence is AGPL-3.0 with additional terms
adequateLICENSE-AGPL3.md grants AGPL-3.0 with additional terms: open source; offering it over a network counts as distributing it, so a hosted product's changes must be published. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE-AGPL3.md:1 — 651 lines, AGPL-3.0 AND LicenseRef-Terms-Additional |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 161 files for 10 structured logging libraries; 0 matched |
One 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 |
An error reporter is installed but never initialised
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on trykimu/videoeditor: 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.