Read 2026-10-04
ktorio/ktor: technical due diligence, read from its repository
What Borehole read in ktorio/ktor's code and history at d08fd03: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
AGENTS.md:5: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongktor-client/ktor-client-curl/desktop/interop/include/curl/curl.h is 3,344 lines, 49× this codebase's median file
adequateThe median source file here is 68 lines. 6 files exceed 1,000 lines, the largest being 3,344. 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.
ktor-client/ktor-client-curl/desktop/interop/include/curl/curl.h:1 — 3,344 lines (49× median) |
ktor-shared/ktor-openapi-schema/common/src/io/ktor/openapi/Operation.kt:1 — 1,653 lines (24× median) |
ktor-client/ktor-client-core/common/src/io/ktor/client/HttpClient.kt:1 — 1,495 lines (21× median) |
ktor-server/ktor-server-core/jvm/src/io/ktor/server/http/content/StaticContent.kt:1 — 1,477 lines (21× median) |
ktor-client/ktor-client-core/common/src/io/ktor/client/plugins/sse/builders.kt:1 — 1,266 lines (18× median) |
Engineering Process & SDLC Maturity
adequate137 tests are switched off
adequate137 skip markers across 58 of 919 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 3.6.0, is not on the branch this survey read; the newest release on it is 3.5.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 3.6.0 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate7 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/automations.yml:81 — action pinned by tag |
.github/workflows/devcontainer.yml:46 — action pinned by tag |
37 locked dependencies have published vulnerabilities, 49 high or critical
adequate37 of 778 locked dependencies match 86 published advisories in OSV, 49 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.
gradle/libs.versions.toml — com.fasterxml.jackson.core:jackson-databind 2.22.2: GHSA-cxp5-3px4-pw24 (high), fixed in 2.22.3 |
gradle/libs.versions.toml — tools.jackson.core:jackson-databind 3.2.2: GHSA-cxp5-3px4-pw24 (high), fixed in 3.2.3 |
ktor-client/ktor-client-webrtc/ktor-client-webrtc-rs/Cargo.lock — rustls-webpki 0.103.4: GHSA-82j2-j2ch-gfr8 (high), fixed in 0.103.13 |
3 compiled libraries committed to the tree: OpenSSL, libcurl, nghttp2
adequateThe product commits built copies of OpenSSL, libcurl, nghttp2. They ship with it as vendored components, but no lockfile names their versions, so their published vulnerabilities were not checked. Ask which version each binary is, how it is rebuilt, and who watches its advisories.
ktor-client/ktor-client-curl/desktop/interop/lib/linuxArm64/libcrypto.a — committed binary |
ktor-client/ktor-client-curl/desktop/interop/lib/linuxArm64/libcurl.a — committed binary |
ktor-client/ktor-client-curl/desktop/interop/lib/linuxArm64/libnghttp2.a — committed binary |
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 ktorio/ktor: 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.