Read 2026-10-04
jellyfin/jellyfin: technical due diligence, read from its repository
What Borehole read in jellyfin/jellyfin's code and history at 390296c: 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
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongMediaBrowser.Controller/MediaEncoding/EncodingHelper.cs is 8,043 lines, 148× this codebase's median file
adequateThe median source file here is 54 lines. 31 files exceed 1,000 lines, the largest being 8,043. 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.
MediaBrowser.Controller/MediaEncoding/EncodingHelper.cs:1 — 8,043 lines (148× median) |
Emby.Server.Implementations/Library/LibraryManager.cs:1 — 4,177 lines (77× median) |
MediaBrowser.Controller/Entities/BaseItem.cs:1 — 3,091 lines (57× median) |
MediaBrowser.Model/Dlna/StreamBuilder.cs:1 — 2,494 lines (46× median) |
Emby.Server.Implementations/Session/SessionManager.cs:1 — 2,270 lines (42× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong18 files still carry code deprecated more than two years ago
adequate18 files were marked deprecated over two years ago and still are, the oldest since May 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
MediaBrowser.Model/Activity/ActivityLogEntry.cs — deprecated since May 2020 |
Jellyfin.Api/Controllers/LiveTvController.cs — deprecated since Jun 2020 |
Jellyfin.Api/Controllers/MusicGenresController.cs — deprecated since Nov 2020 |
Jellyfin.Api/Controllers/InstantMixController.cs — deprecated since Mar 2021 |
MediaBrowser.Controller/Session/AuthenticationRequest.cs — deprecated since Apr 2021 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v12.1, is not on the branch this survey read; the newest release on it is v10.6.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v12.1 |
Security & Reliability Posture
adequate18 advisories against this project in the last 24 months, 8 high or critical
adequateThe newest was published on 2026-09-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 5 records name jellyfin with nothing tying them to this repository (CVE-2025-24960, CVE-2025-64178, CVE-2026-10107, …).
| 2026-09-22: GHSA-cf3c-8m59-2vhx (high), fixed in 12.0: Memory exhaustion and SSRF via external references in user-supplied SVG images |
| 2026-09-22: GHSA-6828-c7cx-hvqm (critical), fixed in 12.0: Path traversal in the virtual-folder management endpoints allows deletion and relocation of arbitrary directories |
| 2026-09-22: GHSA-4vx8-xhc9-qg6x (moderate): Broken access control in session remote-control API |
| 2026-09-22: GHSA-9x85-gx46-6522 (moderate), fixed in 12.0: Potential IDOR in playlist management |
| 2026-09-22: GHSA-hw73-62vp-9gxf (moderate), fixed in 12.0: Potential path transversal exposure in HlsSegmentController.cs |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 jellyfin/jellyfin: 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.