Read 2026-10-04
flameshot-org/flameshot: technical due diligence, read from its repository
What Borehole read in flameshot-org/flameshot's code and history at 2d47806: 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/widgets/capture/capturewidget.cpp is 2,099 lines, 39× this codebase's median file
adequateThe median source file here is 53 lines. 2 files exceed 1,000 lines, the largest being 2,099. 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/widgets/capture/capturewidget.cpp:1 — 2,099 lines (39× median) |
src/config/generalconf.cpp:1 — 1,009 lines (19× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate2 test files against 162 source files (1.2%). 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.
| 2 test files / 162 source files |
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 85 fixes in the last 24 months, 0 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.
| 0 of 85 |
Security & Reliability Posture
adequateThe 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/Linux-pack.yml:91 — action pinned by tag |
.github/workflows/Linux-pack.yml:536 — action pinned by tag |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-12. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2026-09-12: GHSA-6qcf-hw42-mx5x (high): OS Command Injection in flameshot-cli.exe (Windows CLI wrapper) via unescaped argument forwarding to cmd.exe |
| 2026-06-25: GHSA-fqqf-4rj8-c392 (low), fixed in v14.0: TOCTOU symlink attack via predictable /tmp path in Flameshot "Open With" |
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 flameshot-org/flameshot: 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.