Read 2026-10-04
team-spotube/spotube: technical due diligence, read from its repository
What Borehole read in team-spotube/spotube's code and history at 69a310c: 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 |
Architecture & Codebase — including AI provenance
stronglib/models/metadata/metadata.freezed.dart is 6,775 lines, 96× this codebase's median file
adequateThe median source file here is 70 lines. 3 files exceed 1,000 lines, the largest being 6,775. 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.
lib/models/metadata/metadata.freezed.dart:1 — 6,775 lines (96× median) |
lib/models/database/database.g.dart:1 — 6,317 lines (90× median) |
lib/models/database/database.steps.dart:1 — 2,829 lines (40× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate3 test files against 438 source files (0.7%). 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.
| 3 test files / 438 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 1,001 tracked files |
Product & Engineering Maturity
adequate2% of bug fixes add or change a test
adequateOf 172 fixes in the last 24 months, 3 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.
| 3 of 172 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate11 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/potential-duplicates.yml:11 — action pinned by tag |
.github/workflows/pr-lint.yml:16 — action pinned by tag |
22 locked dependencies have published vulnerabilities, 31 high or critical in what ships
adequate22 of 570 locked dependencies match 93 published advisories in OSV, 42 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/pnpm-lock.yaml — astro 5.12.8: GHSA-26w7-cxv4-gfx2 (critical), fixed in 7.2.8 |
website/pnpm-lock.yaml — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; reached only by the build |
website/pnpm-lock.yaml — defu 6.1.4: GHSA-737v-mqg7-c878 (high), fixed in 6.1.5 |
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
android/app/src/main/AndroidManifest.xml:26 — cleartext allowed app-wide |
ios/Runner/Info.plist:31 — cleartext allowed app-wide |
macos/Runner/Info.plist:46 — cleartext allowed app-wide |
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 team-spotube/spotube: 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.