Read 2026-10-04
obsproject/obs-studio: technical due diligence, read from its repository
What Borehole read in obsproject/obs-studio's code and history at e9f043d: 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 | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
COPYING: Relicensed: GPL-3.0 → GPL-2.0 (2013-12-03)CONTRIBUTING.md:126: states a policy on AI-generated contributions.gitmodules:1: 3 submodule(s) this survey does not read: deps/libdshowcapture/src, plugins/obs-browser, plugins/obs-websocket
Architecture & Codebase — including AI provenance
strongdeps/glad/include/glad/glad.h is 13,234 lines, 124× this codebase's median file
adequateThe median source file here is 106 lines. 86 files exceed 1,060 lines, the largest being 13,234. 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.
deps/glad/include/glad/glad.h:1 — 13,234 lines (124× median) |
plugins/obs-filters/rnnoise/src/rnn_data.c:1 — 11,052 lines (104× median) |
deps/glad/src/glad.c:1 — 7,350 lines (69× median) |
frontend/settings/OBSBasicSettings.cpp:1 — 6,087 lines (57× median) |
libobs/obs-source.c:1 — 6,071 lines (57× median) |
A move from Objective-C to Swift began 40 months ago and is 50% done
adequate39 product files are in the new language and 39 are still in the old one, 40 months after the first new file appeared. The new language's share of the lines rose from 6% to 42%, and moved 1 percentage points in the last year. Two languages for one job doubles what an engineer has to know, and the unmoved half is usually what nobody wants to touch. Ask whether finishing it is planned, and what it costs.
| 39 old, 39 new |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate159 test files against 1,809 source files (8.8%). 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.
| 159 test files / 1,809 source files |
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 229 fixes in the last 24 months, 0 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.
| 0 of 229 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 32.2.2, is not on the branch this survey read; the newest release on it is 32.2.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 32.2.2 |
Security & Reliability Posture
strong1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
deps/blake2 — 5 tracked files, no licence file |
Relicensed: GPL-3.0 → GPL-2.0 (2013-12-03)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-01-20. 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 32.2.1. Answer lives in: the release you run, set against each fixed version.
| 2025-01-20: CVE-2024-13524 (low): A vulnerability has been found in obsproject OBS Studio up to 30.0.2 on Windows and classified as problematic. Affected by this vulnerability is an unknown func |
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 obsproject/obs-studio: 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.