Read 2026-10-04
ultralytics/ultralytics: technical due diligence, read from its repository
What Borehole read in ultralytics/ultralytics's code and history at 0ea465b: 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 | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2023-04-14)AGENTS.md:23: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongultralytics/models/sam/predict.py is 3,988 lines, 24× this codebase's median file
adequateThe median source file here is 160 lines. 8 files exceed 1,600 lines, the largest being 3,988. 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.
ultralytics/models/sam/predict.py:1 — 3,988 lines (24× median) |
ultralytics/data/augment.py:1 — 3,240 lines (20× median) |
ultralytics/nn/tasks.py:1 — 2,333 lines (14× median) |
ultralytics/nn/modules/block.py:1 — 2,081 lines (13× median) |
ultralytics/utils/metrics.py:1 — 2,070 lines (12× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate11 test files against 241 source files (4.6%). 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.
| 11 test files / 241 source files |
Product & Engineering Maturity
adequate14% of bug fixes add or change a test
adequateOf 942 fixes in the last 24 months, 131 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.
| 131 of 942 |
Security & Reliability Posture
adequate9 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
examples/YOLOv8-Action-Recognition/requirements.txt:3 — any version |
examples/YOLOv8-Action-Recognition/requirements.txt:4 — any version |
examples/YOLOv8-ONNXRuntime/requirements.txt:1 — any version |
examples/YOLOv8-ONNXRuntime/requirements.txt:2 — any version |
examples/YOLOv8-ONNXRuntime/requirements.txt:3 — any version |
1 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.
docker/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate12 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:68 — action pinned by tag |
.github/workflows/ci.yml:72 — action pinned by tag |
ultralytics/data/scripts/get_imagenet.sh:45 — download piped into a shell |
5 shell commands built from strings
adequate5 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
ultralytics/nn/modules/__init__.py:17 — command run through a shell |
ultralytics/utils/checks.py:1180 — command run through a shell |
ultralytics/utils/export/tensorflow.py:258 — command run through a shell |
Relicensed: GPL-3.0 → AGPL-3.0 (2023-04-14)
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
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,014 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on ultralytics/ultralytics: 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.