Read 2026-11-07
mltframework/shotcut: technical due diligence, read from its repository
What Borehole read in mltframework/shotcut's code and history at 34dde4f: 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
strongsrc/qml/export-chapters/export-chapters.js is 7,634 lines, 83× this codebase's median file
adequateThe median source file here is 91 lines. 31 files exceed 1,000 lines, the largest being 7,634. 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.
src/qml/export-chapters/export-chapters.js:1 — 7,634 lines (83× median) |
src/mainwindow.cpp:1 — 7,069 lines (77× median) |
src/qml/export-edl/export-edl.js:1 — 7,055 lines (77× median) |
src/docks/timelinedock.cpp:1 — 5,379 lines (59× median) |
src/models/multitrackmodel.cpp:1 — 4,850 lines (53× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate5 test files against 878 source files (0.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.
| 5 test files / 878 source files |
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 465 fixes in the last 24 months, 1 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.
| 1 of 465 |
Security & Reliability Posture
adequateNone 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 3,160 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/build-linux.yml:54 — action pinned by tag |
.github/workflows/build-linux.yml:137 — action pinned by tag |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-28. 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. The record is incomplete: NVD: 1 record names shotcut with nothing tying it to this repository (CVE-2025-65834).
| 2026-09-28: GHSA-r3f6-m5ww-9r4p (high): Shotcut: the update check falls back to plain HTTP and the response's url reaches ShellExecute |
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 mltframework/shotcut: 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.