Read 2026-10-04
borgbackup/borg: technical due diligence, read from its repository
What Borehole read in borgbackup/borg's code and history at a586f69: 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
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:25: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/borg/archive.py is 3,184 lines, 22× this codebase's median file
adequateThe median source file here is 143 lines. 5 files exceed 1,430 lines, the largest being 3,184. 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.
src/borg/archive.py:1 — 3,184 lines (22× median) |
src/borg/repository.py:1 — 2,681 lines (18× median) |
src/borg/helpers/parseformat.py:1 — 1,712 lines (11× median) |
src/borg/legacy/repository.py:1 — 1,681 lines (11× median) |
src/borg/crypto/key.py:1 — 1,545 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 1.4.5, is not on the branch this survey read; the newest release on it is 1.2.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.4.5 |
Security & Reliability Posture
adequateManifest says BSD-3-Clause, licence file says BSD-2-Clause
adequatepyproject.toml declares BSD-3-Clause. LICENSE contains the text of BSD-2-Clause. Package managers and downstream users read the first; auditors and acquirers read the second. One of them is wrong, and until it is settled the terms this code is offered under are genuinely ambiguous.
pyproject.toml:30 — declares BSD-3-Clause |
LICENSE — text of BSD-2-Clause |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-08-26. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.2.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 4 records name borg with nothing tying them to this repository (CVE-2023-26265, CVE-2026-6885, CVE-2026-6886, …).
| 2026-08-26: GHSA-gfp8-w835-v44j (low), fixed in 1.4.5: borg extract might modify or disclose out-of-tree files when extracting maliciously crafted archives |
Observability & Operations
not assessableNot rated: only 5 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 borgbackup/borg: 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.