Read 2026-11-03
the-momentum/open-wearables: technical due diligence, read from its repository
What Borehole read in the-momentum/open-wearables's code and history at 6ba9e2e: 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
CONTRIBUTING.md:44: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongbackend/app/services/providers/garmin/data_247.py is 2,229 lines, 35× this codebase's median file
adequateThe median source file here is 62 lines. 7 files exceed 1,000 lines, the largest being 2,229. 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.
backend/app/services/providers/garmin/data_247.py:1 — 2,229 lines (35× median) |
backend/app/repositories/data_point_series_repository.py:1 — 1,587 lines (25× median) |
backend/app/repositories/event_record_repository.py:1 — 1,501 lines (24× median) |
backend/app/services/providers/oura/data_247.py:1 — 1,411 lines (22× median) |
backend/app/services/event_record_service.py:1 — 1,309 lines (21× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate52 of 936 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 52 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 Dockerfiles run 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.
backend/Dockerfile — runs as root |
frontend/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 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; 8 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/ci.yml:28 — action pinned by tag |
.github/workflows/ci.yml:256 — action pinned by tag |
.github/workflows/ci.yml:51 — download piped into a shell |
4 SQL statements built from strings
adequate4 places in product code build SQL by formatting or joining strings rather than passing parameters. 4 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
backend/app/repositories/data_type_coverage_repository.py:88 — SQL built from a string |
backend/app/repositories/data_type_coverage_repository.py:89 — SQL built from a string |
backend/app/repositories/data_type_coverage_repository.py:170 — SQL built from a string |
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 1,443 files for 10 structured logging libraries; 0 matched |
Sends usage data to telemetry.openwearables.io by default
adequatebackend/app/config.py sends to telemetry.openwearables.io, and backend/app/config.py leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
backend/app/config.py:354 — reports to telemetry.openwearables.io |
backend/app/config.py:353 — the reporting setting is on by default |
1 of 5 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.yml:119 — 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 the-momentum/open-wearables: 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.