Read 2026-11-07
kareadita/kavita: technical due diligence, read from its repository
What Borehole read in kareadita/kavita's code and history at d549d5b: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.github/AI_POLICY.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate49% of commit subjects are exact repeats of another subject, and subject length varies by only 23.9 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.
| 1055× 'Bump versions by dotnet-bump-version.' |
| 145× 'Update OpenAPI documentation' |
| 38× 'Translated using Weblate (Chinese (Simplified))' |
Kavita.Services/Plus/ExternalMetadataService.cs is 3,123 lines, 84× this codebase's median file
adequateThe median source file here is 37 lines. 25 files exceed 1,000 lines, the largest being 3,123. 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.
Kavita.Services/Plus/ExternalMetadataService.cs:1 — 3,123 lines (84× median) |
UI/Web/src/app/book-reader/_components/book-reader/book-reader.component.ts:1 — 2,697 lines (72× median) |
Kavita.Services/Plus/ScrobblingService.cs:1 — 2,135 lines (57× median) |
UI/Web/src/app/manga-reader/_components/manga-reader/manga-reader.component.ts:1 — 2,077 lines (56× median) |
Kavita.Services/BookService.cs:1 — 2,034 lines (54× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate161 test files against 2,456 source files (6.6%). 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.
| 161 test files / 2,456 source files |
16% of recent commits change more than 2,000 lines
adequate74 of 462 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.
| 74 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| JWT, where fakes are usual |
1 credential-shaped string added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| JWT, where fakes are usual |
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 |
13 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-10-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 1 record names Kavita with nothing tying it to this repository (CVE-2014-7776).
| 2026-10-22: CVE-2022-51024 (high): Kavita 0.5.2 before 0.5.4.1 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files by supplying '../' sequences i |
| 2026-10-13: CVE-2026-110223 (low): Kavita 0.9.0 through 0.9.1.4 contains a server-side request forgery vulnerability that allows authenticated users to bypass the SSRF blocklist through DNS rebin |
| 2026-09-05: GHSA-gjx7-m655-3grw (moderate), fixed in 0.9.1: Annotation read endpoints filter only by self-selected social preferences and skip the library-access and age-restriction checks |
| 2026-09-05: GHSA-jhw9-5hj3-mvp4 (low), fixed in 0.9.1: IDOR in dashboard/side-nav stream update lets any user toggle another user's widget visibility (CWE-639) |
| 2026-09-05: GHSA-fpjf-pxrq-4xv7 (moderate), fixed in 0.9.1: IDOR in DELETE /api/filter allows any user to delete another user's Smart Filter (CWE-639) |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on kareadita/kavita: 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.