Read 2026-10-04
square/okhttp: technical due diligence, read from its repository
What Borehole read in square/okhttp's code and history at 40a3b87: 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
CONTRIBUTING.md:27: states a policy on AI-generated contributions.gitmodules:1: 1 submodule(s) this survey does not read: okhttp-hpacktests/src/test/resources/hpack-test-case
Architecture & Codebase — including AI provenance
strongokhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt is 1,817 lines, 19× this codebase's median file
adequateThe median source file here is 93 lines. 5 files exceed 1,000 lines, the largest being 1,817. 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.
okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:1 — 1,817 lines (19× median) |
okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt:1 — 1,398 lines (15× median) |
mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:1 — 1,300 lines (13× median) |
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt:1 — 1,122 lines (12× median) |
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt:1 — 1,047 lines (11× median) |
Engineering Process & SDLC Maturity
adequate67 tests are switched off
adequate67 skip markers across 23 of 275 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
Pinned dependencies have not moved in 38 months
adequateThe lockfile last changed 1152 days before the newest commit, and 1,033 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
| kotlin-js-store/yarn.lock last changed 2023-07-22 |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings 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. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| Google API key, where fakes are usual |
| private key block, where fakes are usual |
28 locked dependencies have published vulnerabilities, 41 high or critical
adequate28 of 367 locked dependencies match 75 published advisories in OSV, 41 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.
kotlin-js-store/yarn.lock — body-parser 1.20.0: GHSA-qwcr-r2fm-qrc7 (high), fixed in 1.20.3 |
kotlin-js-store/yarn.lock — brace-expansion 1.1.11: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16 |
kotlin-js-store/yarn.lock — brace-expansion 2.0.1: GHSA-3jxr-9vmj-r5cp (high), fixed in 2.1.2 |
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 square/okhttp: 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.