Read 2026-10-23
bluenviron/mediamtx: technical due diligence, read from its repository
What Borehole read in bluenviron/mediamtx's code and history at 437cc96: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/pull_request_template.md:2: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
stronginternal/core/core.go is 1,433 lines, 15× this codebase's median file
adequateThe median source file here is 90 lines. 7 files exceed 1,000 lines, the largest being 1,433. 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.
internal/core/core.go:1 — 1,433 lines (15× median) |
internal/conf/conf.go:1 — 1,330 lines (14× median) |
internal/servers/moq/reader.js:1 — 1,264 lines (14× median) |
internal/core/path.go:1 — 1,253 lines (13× median) |
internal/metrics/metrics.go:1 — 1,197 lines (13× 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.
internal/teste2e/images/ffmpeg/Dockerfile — runs as root |
internal/teste2e/images/gstreamer/Dockerfile — runs as root |
3 outbound calls can wait forever
adequate3 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
internal/servers/hls/hlsjsdownloader/main.go:31 — outbound call without a timeout |
internal/staticsources/rpicamera/mtxrpicamdownloader/main.go:98 — outbound call without a timeout |
internal/upgrade/upgrade.go:83 — outbound call without a timeout |
12 advisories against this project in the last 24 months, 8 high or critical
adequateThe newest was published on 2026-10-08. 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-10-08: GHSA-w334-5mp5-h897 (critical), fixed in >= 1.21.1: Cross-site request forgery on the Control API allows remote command execution through a browser form POST |
| 2026-10-08: GHSA-7498-vjgw-9cr2 (high), fixed in >= 1.21.0: Zero-length HEVC parameter sets in an RTMP publisher's configuration cause an index-out-of-range panic that crashes MediaMTX |
| 2026-10-08: GHSA-5jgv-c722-r5cg (high), fixed in >= 1.21.0: Zero-length H264 SPS/PPS in an RTMP AVC configuration causes an unrecovered panic that terminates MediaMTX |
| 2026-09-20: GHSA-438c-q3c2-xj75 (high), fixed in >= 1.21.0: MoQ subgroup reordering permits excessive memory retention from out-of-order group IDs |
| 2026-09-12: GHSA-p8h6-6w9q-q7f3 (high), fixed in >= 1.20.1: Unauthenticated denial of service via unbounded track count in MoQ catalog PUBLISH |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 609 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 609 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 609 files for 10 structured logging libraries; 0 matched |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on bluenviron/mediamtx: 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.