Read 2026-10-04
astral-sh/uv: technical due diligence, read from its repository
What Borehole read in astral-sh/uv's code and history at bac35f5: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:31: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongcrates/uv-lock/src/lock/mod.rs is 11,107 lines, 66× this codebase's median file
adequateThe median source file here is 167 lines. 37 files exceed 1,670 lines, the largest being 11,107. 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.
crates/uv-lock/src/lock/mod.rs:1 — 11,107 lines (66× median) |
crates/uv-cli/src/lib.rs:1 — 7,984 lines (47× median) |
crates/uv/src/settings.rs:1 — 5,512 lines (33× median) |
crates/uv-python/src/discovery.rs:1 — 4,851 lines (29× median) |
crates/uv-pep440/src/version.rs:1 — 4,805 lines (28× median) |
Engineering Process & SDLC Maturity
strongNo finding.
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.
Dockerfile — runs as root |
crates/uv-trampoline/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 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/test-system.yml:681 — download piped into a shell |
12 locked dependencies have published vulnerabilities, 8 high or critical
adequate12 of 841 locked dependencies match 23 published advisories in OSV, 8 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 development dependencies. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
uv.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2; a development dependency |
uv.lock — gitpython 3.1.58: GHSA-284h-m62q-gf8w (critical), fixed in 3.1.59; a development dependency |
uv.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0; a development dependency |
Observability & Operations
not assessableNot rated: only 4 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 astral-sh/uv: 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.