Read 2026-11-03
dialmasterorg/youtarr: technical due diligence, read from its repository
What Borehole read in dialmasterorg/youtarr's code and history at 758bc0a: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongserver/routes/channels.js is 1,479 lines, 13× this codebase's median file
adequateThe median source file here is 112 lines. 8 files exceed 1,120 lines, the largest being 1,479. 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.
server/routes/channels.js:1 — 1,479 lines (13× median) |
server/modules/jobModule.js:1 — 1,414 lines (12× median) |
client/src/components/ChannelPage/ChannelVideos.tsx:1 — 1,406 lines (12× median) |
server/modules/downloadModule.js:1 — 1,276 lines (11× median) |
server/routes/videos.js:1 — 1,172 lines (10× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (server/modules/filesystem/__tests__/directoryManager.test.js). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
server/modules/filesystem/__tests__/directoryManager.test.js:85 — test retry |
7% of recent commits change more than 2,000 lines
adequate60 of 853 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 60 commits over 2,000 lines |
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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
Dockerfile:61 — download piped into a shell |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
server/modules/storageUsage.js:21 — SQL built from a string |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
server/modules/videoDownloadPostProcessFiles.js:227 — command run through a shell |
server/modules/videoDownloadPostProcessFiles.js:665 — command run through a shell |
26 locked dependencies have published vulnerabilities, 23 high or critical in what ships
adequate26 of 1,407 locked dependencies match 61 published advisories in OSV, 23 of them rated high or critical. 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.
website/package-lock.json — shell-quote 1.10.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0 |
website/package-lock.json — tinypool 1.1.1: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1 |
website/package-lock.json — body-parser 1.20.8: GHSA-27r3-jxmh-p828 (high), fixed in 1.20.9 |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
client/vite.config.ts:77 — source maps in a production build |
4 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-10-17. 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-17: GHSA-wjc6-2jch-82h6 (moderate), fixed in 1.89.0: Unauthenticated WebSocket stream exposes real-time download and channel activity |
| 2026-10-17: GHSA-jprg-87hp-2phh (high), fixed in 1.89.0: Authenticated command execution in Youtarr via a yt-dlp custom-args denylist bypass using --use-postprocessor Exec. |
| 2026-10-17: GHSA-j7h9-rcv4-v45c (high), fixed in 1.86.0: Authenticated OS command injection (RCE as root) via crafted channel URL: yt-dlp-derived channel_id flows unsanitized into an ffmpeg execSync shell string |
| 2026-10-13: GHSA-cqmg-7g3c-67m4 (moderate), fixed in 1.88.0: Unauthenticated Plex OAuth PIN Redemption Allows Unauthorized Persistent Plex Token Configuration in Youtarr |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,439 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 1,439 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 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 dialmasterorg/youtarr: 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.