Read 2026-11-03
fincept-corporation/finceptterminal: technical due diligence, read from its repository
What Borehole read in fincept-corporation/finceptterminal's code and history at 7716ee8: 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
LICENSE: Relicensed: MIT → AGPL-3.0 (2026-01-05)
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate42% of commit subjects are exact repeats of another subject, and subject length varies by only 26.4 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.
| 20× 'readme update' |
| 18× '📝 Move translated READMEs to docs/translations/' |
| 15× 'setup correction' |
fincept-qt/src/services/workflow/adapters/ServiceBridges.cpp is 2,803 lines, 22× this codebase's median file
adequateThe median source file here is 126 lines. 42 files exceed 1,260 lines, the largest being 2,803. 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.
fincept-qt/src/services/workflow/adapters/ServiceBridges.cpp:1 — 2,803 lines (22× median) |
fincept-qt/src/screens/excel/FormulaEngine.cpp:1 — 2,664 lines (21× median) |
fincept-qt/src/python/PythonSetupManager.cpp:1 — 2,433 lines (19× median) |
fincept-qt/src/screens/quantlib/QuantLibScreen_Data.cpp:1 — 2,150 lines (17× median) |
fincept-qt/src/screens/equity_trading/AccountManagementDialog.cpp:1 — 2,075 lines (16× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate18 test files against 2,031 source files (0.9%). 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.
| 18 test files / 2,031 source files |
24% of recent commits change more than 2,000 lines
adequate193 of 813 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.
| 193 commits over 2,000 lines |
Product & Engineering Maturity
adequate3% of bug fixes add or change a test
adequateOf 174 fixes in the last 24 months, 6 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.
| 6 of 174 |
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,458 tracked files; 0 present |
2 credential-shaped strings exist in the history
adequateMatches for Google API key were committed at some point across 881 commits examined. The files that held them are no longer in the working tree — but removal from a file is not removal from the history, and the history is what transfers with the asset. What matters is whether each was rotated after it was committed. 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.
| 2 cited: Google API key pattern added here |
1 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
adequate4 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-cpp.yml:87 — action pinned by tag |
.github/workflows/build-cpp.yml:172 — action pinned by tag |
2 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
fincept-qt/resources/wallet/vendor/README.md — 1 tracked files, no licence file |
fincept-qt/resources/wallet/vendor/web3.js — 1 tracked files, no licence file |
Relicensed: MIT → AGPL-3.0 (2026-01-05)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
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 fincept-corporation/finceptterminal: 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.