Read 2026-10-23
usekaneo/kaneo: technical due diligence, read from its repository
What Borehole read in usekaneo/kaneo's code and history at 6172d75: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
AI_POLICY.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongapps/web/src/components/activity/comment-editor.tsx is 1,846 lines, 32× this codebase's median file
adequateThe median source file here is 57 lines. 9 files exceed 1,000 lines, the largest being 1,846. 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.
apps/web/src/components/activity/comment-editor.tsx:1 — 1,846 lines (32× median) |
apps/web/src/components/task/task-description.tsx:1 — 1,802 lines (31× median) |
apps/api/src/database/schema.ts:1 — 1,497 lines (26× median) |
apps/mobile/src/features/task/sections.tsx:1 — 1,422 lines (24× median) |
apps/web/src/components/shared/modals/create-task-modal.tsx:1 — 1,370 lines (24× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (tests/e2e/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
tests/e2e/playwright.config.ts:15 — test retry |
7% of recent commits change more than 2,000 lines
adequate138 of 2095 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.
| 138 commits over 2,000 lines |
Product & Engineering Maturity
adequate91 direct dependencies in a single manifest
adequateapps/web/package.json declares 91 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
apps/web/package.json — 91 declared |
apps/mobile/package.json — 37 declared |
apps/api/package.json — 32 declared |
apps/site/package.json — 16 declared |
Fixes are 64% of recent work, up from 21%
adequateIn the last two quarters 64% of commits were fixes, against 21% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 65%, 63%, 41%, 9%, 16%, 13%, 30%, 19% |
Security & Reliability Posture
adequate1 environment file is committed
adequateapps/web/.env.production is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
apps/web/.env.production — committed environment file |
The build runs third-party code it does not pin
adequate1 step pipes a download straight into a shell. 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/publish-cli.yml:250 — download piped into a shell |
15 locked dependencies have published vulnerabilities, 7 high or critical in what ships
adequate15 of 2,053 locked dependencies match 37 published advisories in OSV, 11 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.
pnpm-lock.yaml — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10 |
pnpm-lock.yaml — markdown-it 14.1.1: GHSA-gfr2-rv44-r23c (high), fixed in 14.3.3 |
pnpm-lock.yaml — node-forge 1.4.0: GHSA-86w9-cpqp-85rv (high) |
6 places insert HTML from a variable without sanitising it
adequate6 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
apps/site/app/layout.tsx:109 — HTML from a variable |
apps/site/app/layout.tsx:130 — HTML from a variable |
apps/site/components/landing/blog-post-page.tsx:134 — HTML from a variable |
11 advisories against this project in the last 24 months, 9 high or critical
adequateThe newest was published on 2026-10-14. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2.47.0. Answer lives in: the release you run, set against each fixed version.
| 2026-10-14: CVE-2025-71433 (high): Kaneo before 2.1.6 contains a missing authorization vulnerability that allows authenticated users to access other workspaces by supplying project, task, label o |
| 2026-09-22: GHSA-96fw-wgvw-9q34 (high), fixed in 2.26.0: Cross-tenant IDOR: any workspace can read/link/write other tenants' private GitHub repos through the shared GitHub App |
| 2026-09-22: GHSA-w3qx-xr6r-frch (moderate), fixed in 2.26.0: Former workspace member keeps receiving post-removal task metadata through an orphaned notification rule (`apps/api`) |
| 2026-09-22: GHSA-jrwx-vxf6-5v55 (critical), fixed in 2.26.0: Kaneo: unset AUTH_SECRET falls back to Better Auth's public default secret, enabling offline cookie forgery and full auth bypass |
| 2026-09-22: GHSA-wcf5-rr68-wg5c (high), fixed in 2.26.0: Missing project:share Authorization Allows Restricted Users to Publish Private Projects Summary |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 4,339 files for 10 structured logging libraries; 0 matched |
Readiness and liveness probes are identical in 1 of 2 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
charts/kaneo/values.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on usekaneo/kaneo: 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.