Read 2026-11-03
getsops/sops: technical due diligence, read from its repository
What Borehole read in getsops/sops's code and history at cbb1216: 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:41: names CNCF
Architecture & Codebase — including AI provenance
strongcmd/sops/main.go is 2,629 lines, 18× this codebase's median file
adequateThe median source file here is 145 lines. 1 file exceed 1,450 lines, the largest being 2,629. 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.
cmd/sops/main.go:1 — 2,629 lines (18× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
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.
.release/Dockerfile — runs as root |
1 locked dependency has published vulnerabilities
adequate1 of 147 locked dependencies match 2 published advisories in OSV. 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.
go.mod — golang.org/x/crypto v0.55.0: GO-2026-6354 (unrated), fixed in 0.56.0 |
4 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-14. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-08-14: GHSA-pvcx-747w-54qw (low), fixed in 3.13.2: Switching user in `sops exec-file` and `sops exec-env` sets user's UID as GID (Unix only) |
| 2026-08-14: GHSA-hqjv-fvgv-rh27 (moderate), fixed in 3.13.0: Memory exhaustion when decrypting untrusted INI or DotEnv files |
| 2026-08-14: GHSA-jgf3-f6rg-8x3h (high): HC Vault / OpenBao token exfiltration when decrypting untrusted SOPS-encrypted files |
| 2026-08-14: GHSA-x4cm-pcq4-39j4 (moderate), fixed in 3.13.0: Path traversal in `sops exec-file --filename` leaks decrypted plaintext outside temporary directory |
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 getsops/sops: 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.