Read 2026-11-03
ovh/utask: technical due diligence, read from its repository
What Borehole read in ovh/utask's code and history at 8164f79: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 584,653 lines — 62% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2019-11-05T13:27:57+00:00; +584,653 across 1818 files; subject: 'Initial commit :rocket:' |
engine/engine.go is 1,151 lines, 19× this codebase's median file
adequateThe median source file here is 58 lines. 1 file exceed 1,000 lines, the largest being 1,151. 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.
engine/engine.go:1 — 1,151 lines (19× median) |
77 errors caught and discarded in product code
adequate77 places catch an error and do nothing with it, across 4 files (1.8 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
ui/dashboard/projects/utask-lib/src/lib/@components/error-message/error-message.component.ts:37 — error caught and discarded |
ui/dashboard/projects/utask-lib/src/lib/@components/error-message/error-message.component.ts:39 — error caught and discarded |
ui/swagger-ui/swagger-ui-bundle.js:1 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.28 to 1.08 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.28, second half 1.08 (split 2023-03-18) |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo 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.
Dockerfile — runs as root |
22 locked dependencies have published vulnerabilities, 40 high or critical in what ships
adequate22 of 286 locked dependencies match 83 published advisories in OSV, 43 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.
go.mod — golang.org/x/crypto v0.41.0: GHSA-89gr-r52h-f8rx (critical), fixed in 0.52.0 |
ui/dashboard/package-lock.json — @angular/common 20.3.16: GHSA-39pv-4j6c-2g6v (high), fixed in 20.3.25 |
ui/dashboard/package-lock.json — @angular/compiler 20.3.16: GHSA-g93w-mfhg-p222 (high), fixed in 20.3.18 |
10 places insert HTML from a variable without sanitising it
adequate10 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.
ui/swagger-ui/swagger-ui-bundle.js:51 — HTML from a variable |
ui/swagger-ui/swagger-ui-bundle.js:51 — HTML from a variable |
ui/swagger-ui/swagger-ui-bundle.js:51 — HTML from a variable |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
ui/dashboard/angular.json:68 — source maps in a production build |
vscode/web/angular.json:78 — source maps in a production build |
Observability & Operations
strongAn 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 ovh/utask: 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.