Read 2026-10-04
mrkai77/loop: technical due diligence, read from its repository
What Borehole read in mrkai77/loop's code and history at 61e9b09: 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: Apache-2.0 → MIT (2023-06-15) → GPL-3.0 (2024-04-18).github/pull_request_template.md:32: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate6 test files against 180 source files (3.3%). 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.
| 6 test files / 180 source files |
Product & Engineering Maturity
adequate2% of bug fixes add or change a test
adequateOf 63 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 63 |
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 388 tracked files; 0 present |
The build runs third-party code it does not pin
adequate3 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/crowdin-download.yml:17 — action pinned by tag |
.github/workflows/dev-build.yml:190 — action pinned by tag |
Relicensed: Apache-2.0 → MIT (2023-06-15) → GPL-3.0 (2024-04-18)
adequateThe root licence changed 2 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 mrkai77/loop: 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.