Read 2026-10-04
teamnewpipe/newpipe: technical due diligence, read from its repository
What Borehole read in teamnewpipe/newpipe's code and history at 7e5df38: 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 | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/CONTRIBUTING.md:6: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate46% of commit subjects are exact repeats of another subject, and subject length varies by only 46.8 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 280× 'Translated using Weblate (Russian)' |
| 271× 'Translated using Weblate (French)' |
| 255× 'Translated using Weblate (German)' |
app/src/main/java/org/schabi/newpipe/fragments/detail/VideoDetailFragment.java is 2,528 lines, 34× this codebase's median file
adequateThe median source file here is 74 lines. 8 files exceed 1,000 lines, the largest being 2,528. 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.
app/src/main/java/org/schabi/newpipe/fragments/detail/VideoDetailFragment.java:1 — 2,528 lines (34× median) |
app/src/main/java/org/schabi/newpipe/player/Player.java:1 — 2,489 lines (33× median) |
app/src/main/java/org/schabi/newpipe/player/ui/VideoPlayerUi.java:1 — 1,643 lines (22× median) |
app/src/main/java/org/schabi/newpipe/fragments/list/search/SearchFragment.java:1 — 1,191 lines (16× median) |
app/src/main/java/org/schabi/newpipe/download/DownloadDialog.java:1 — 1,128 lines (15× median) |
A move from Java to Kotlin began 81 months ago and is 43% done
adequate216 product files are in the new language and 282 are still in the old one, 81 months after the first new file appeared. The new language's share of the lines rose from 0% to 22%, and moved 8 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.
| 282 old, 216 new |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate42 test files against 550 source files (7.6%). 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.
| 42 test files / 550 source files |
Product & Engineering Maturity
adequate7% of bug fixes add or change a test
adequateOf 135 fixes in the last 24 months, 10 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.
| 10 of 135 |
Security & Reliability Posture
adequate1 credential-shaped string committed to the tree
adequateMatches for Google API key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. Only Google API keys matched. Those are often public by design, in a browser app's Firebase or Maps configuration; the question is whether each is restricted to the app's domains and APIs.
| Google API key pattern matched |
None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 4,432 tracked files; 0 present |
The build runs third-party code it does not pin
adequate5 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. 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.
.github/workflows/backport-pr.yml:43 — action pinned by tag |
.github/workflows/ci.yml:41 — action pinned by tag |
3 deserialisers that can run code
adequate3 places read data with a deserialiser that executes what it reads (Java object streams). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
app/src/main/java/org/schabi/newpipe/util/SerializedCache.java:106 — code-executing deserialiser |
app/src/main/java/org/schabi/newpipe/util/StateSaver.java:132 — code-executing deserialiser |
app/src/main/java/us/shandian/giga/util/Utility.java:85 — code-executing deserialiser |
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 teamnewpipe/newpipe: 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.