Read 2026-11-03
kanriapp/kanri: technical due diligence, read from its repository
What Borehole read in kanriapp/kanri's code and history at 48f19e3: 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 → GPL-3.0 (2024-03-25)CONTRIBUTING.md:19: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpages/licenses/rust.vue is 13,192 lines, 149× this codebase's median file
adequateThe median source file here is 88 lines. 3 files exceed 1,000 lines, the largest being 13,192. 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.
pages/licenses/rust.vue:1 — 13,192 lines (149× median) |
pages/licenses/index.vue:1 — 2,879 lines (32× median) |
pages/licenses/dev_js.vue:1 — 1,810 lines (20× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate4 test files against 76 source files (5.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.
| 4 test files / 76 source files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.43 to 0.77 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.43, second half 0.77 (split 2024-08-03) |
0% of bug fixes add or change a test
adequateOf 97 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 97 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/devskim.yml:28 — action pinned by tag |
.github/workflows/provenance_check.yml:25 — action pinned by tag |
62 locked dependencies have published vulnerabilities, 17 high or critical in what ships
adequate62 of 1,840 locked dependencies match 137 published advisories in OSV, 63 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
pnpm-lock.yaml — @nuxt/devtools 3.2.4: GHSA-279x-mwfv-vcqv (critical), fixed in 3.3.1; a development dependency |
pnpm-lock.yaml — @simple-git/argv-parser 1.1.1: GHSA-v5rq-49vh-5v5c (critical), fixed in 2.0.1; a development dependency |
pnpm-lock.yaml — seroval 1.5.4: GHSA-p6vx-979v-rg4c (critical), fixed in 1.6.2; a development dependency |
Relicensed: Apache-2.0 → GPL-3.0 (2024-03-25)
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 5 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 kanriapp/kanri: 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.