Executive summary
lysine-dev/okhttp falls short of our standard for production because three passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 59 out of 100 and is rated Adequate, and 26 of its 30 critical findings are security problems.
Production Readiness, at 46, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 12 points. Recording design decisions comes next, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 67.
Twenty-one known security holes in the packages the code depends on can be used by attackers. Three passwords or keys in the code and one in the code's history are open to anyone who can read the repository, and one pipeline step installs packages that can change without warning. Updating the vulnerable packages, replacing each exposed password or key and pinning what the pipeline installs would close these risks. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 54,727 lines, about €140,000 to rebuild.
If Production Readiness rose from 46 to 70, the lowest score rated Strong, the score would rise from 59 to about 67.
New since the last survey: 33 findings
- Code Duplication · Edited copy of a member (25 corresponding lines) mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt
- Code Duplication · Edited copy of a member (27 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/RealDnsCache.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt
- Code Duplication · Edited copy of a member (25 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt
- Code Duplication · Edited copy of a member (25 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) mockwebserver-junit5/src/main/kotlin/mockwebserver3/junit5/internal/StartStopExtension.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) okhttp-tls/src/main/kotlin/okhttp3/tls/Certificates.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) okhttp-testing-support/src/main/kotlin/okhttp3/sockets/FakeSocket.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/IdnaMappingTable.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/platform/Platform.kt
- Code Duplication · Duplicated block (18 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt
- Code Duplication · Duplicated block (13 lines × 2) mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt
- Code Duplication · Duplicated block (12 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/ConscryptSocketAdapter.kt
- Code Duplication · Duplicated block (9–10 lines × 2) mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt
- Code Duplication · Duplicated block (13 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt
- Code Duplication · Duplicated block (7 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/Android10Platform.kt
- Code Duplication · Duplicated block (11 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/Android10SocketAdapter.kt
- Code Duplication · Duplicated block (9 lines × 2) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketExtensions.kt
- Code Duplication · Edited copy of a member (42 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/Progress.java
- Code Duplication · Edited copy of a member (16 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/CustomTrust.java
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/PostForm.java
- Code Duplication · Edited copy of a member (13 corresponding lines) samples/slack/src/main/java/okhttp3/slack/SlackApi.java
- Code Duplication · Edited copy of a member (14 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/PostFile.java
- Code Duplication · Edited copy of a member (12 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/CertificatePinning.java
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/Authenticate.java
- Code Duplication · Edited copy of a member (17 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/kt/ParseResponseWithMoshi.kt
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/kt/PostFile.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) samples/guide/src/main/java/okhttp3/guide/PostExample.java
- Code Duplication · Edited copy of a member (9 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/ConfigureTimeouts.java
- License Compliance · Banned license: org.graalvm.nativeimage:svm
Fixed since the last survey: 14 findings
- Code Duplication · Duplicated block (19 lines × 2) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt
- Code Duplication · Duplicated block (18 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt
- Code Duplication · Duplicated block (12 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/ConscryptSocketAdapter.kt
- Code Duplication · Duplicated block (9–10 lines × 2) mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt
- Code Duplication · Duplicated block (13 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt
- Code Duplication · Duplicated block (7 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/Android10Platform.kt
- Code Duplication · Duplicated block (11 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/Android10SocketAdapter.kt
- Code Duplication · Duplicated block (9 lines × 2) samples/guide/src/main/java/okhttp3/recipes/CacheResponse.java
- REDACTED Scanning · Leaked secret: REDACTED REDACTED
- REDACTED Scanning · Leaked secret: slack-token samples/slack/src/main/java/okhttp3/slack/SlackClient.java
- REDACTED Scanning · Leaked secret: gcp-api-key samples/guide/src/main/java/okhttp3/recipes/RequestBodyCompression.java
- REDACTED Scanning · Leaked secret: high-entropy-secret samples/guide/src/main/java/okhttp3/recipes/RequestBodyCompression.java
- Secrets (history) · REDACTED: generic-api-key samples/guide/src/main/java/com/squareup/okhttp/recipes/RequestBodyCompression.java
- Secrets (history) · REDACTED: generic-api-key samples/guide/src/main/java/okhttp3/recipes/RequestBodyCompression.java
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €46,000 to €230,000, for 760 to 2,412 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 54,727 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 okhttp3.internal.concurrent | 2 okhttp3.logging.HttpLoggingInterceptor | 3 okhttp3.tls | 4 okhttp3.tls.internal.der | 5 okhttp3.Call | 6 okhttp3.Dns | 7 okhttp3.EventListener | 8 okhttp3.Headers | 9 okhttp3.Interceptor | 10 okhttp3.internal.dns.DnsQuery | 11 okhttp3.internal.http.ExchangeCodec | 12 okhttp3.internal.http2.Http2Connection | 13 okhttp3.internal.platform.android.DeferredSocketAdapter | 14 okhttp3.internal.tls | 15 okhttp3.sockets.FakeSslSocket | 16 okhttp3.FakeDns | 17 okhttp3.Response | 18 okhttp3.internal.cache | 19 okhttp3.internal.dns | 20 okhttp3.internal.platform.android | 21 okhttp3.sockets.FakeSocket.State | 22 okhttp3.internal.http | 23 okhttp3.internal.platform | 24 okhttp3.internal.http2 | 25 okhttp3.sockets | 26 okhttp3.internal | 27 okhttp3.Request | 28 okhttp3.internal.connection | 29 okhttp3.OkHttpClient | 30 okhttp3 | 31 mockwebserver3.MockResponse | 32 mockwebserver3.internal | 33 okhttp3.android | 34 okhttp3.dnsoverhttps | 35 okhttp3.internal.http1 | 36 okhttp3.internal.ws | 37 okhttp3.sse | 38 mockwebserver3 | 39 mockwebserver3.MockWebServer | 40 okhttp3.mockwebserver |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 okhttp3.internal.concurrent | ||||||||||||||||||||||||||||||||||||||||
| 2 okhttp3.logging.HttpLoggingInterceptor | ||||||||||||||||||||||||||||||||||||||||
| 3 okhttp3.tls | ||||||||||||||||||||||||||||||||||||||||
| 4 okhttp3.tls.internal.der | ||||||||||||||||||||||||||||||||||||||||
| 5 okhttp3.Call | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 okhttp3.Dns | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 okhttp3.EventListener | 12 | |||||||||||||||||||||||||||||||||||||||
| 8 okhttp3.Headers | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 okhttp3.Interceptor | 13 | |||||||||||||||||||||||||||||||||||||||
| 10 okhttp3.internal.dns.DnsQuery | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 okhttp3.internal.http.ExchangeCodec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 okhttp3.internal.http2.Http2Connection | 1 | 11 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 okhttp3.internal.platform.android.DeferredSocketAdapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 okhttp3.internal.tls | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 okhttp3.sockets.FakeSslSocket | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 okhttp3.FakeDns | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 17 okhttp3.Response | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 18 okhttp3.internal.cache | 3 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 19 okhttp3.internal.dns | 4 | 9 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 20 okhttp3.internal.platform.android | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 21 okhttp3.sockets.FakeSocket.State | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 22 okhttp3.internal.http | 4 | 1 | 1 | 1 | 4 | 37 | ||||||||||||||||||||||||||||||||||
| 23 okhttp3.internal.platform | 6 | 2 | 9 | |||||||||||||||||||||||||||||||||||||
| 24 okhttp3.internal.http2 | 5 | 1 | 3 | 1 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 25 okhttp3.sockets | 3 | 1 | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 26 okhttp3.internal | 1 | 1 | 2 | 1 | 4 | 1 | 21 | |||||||||||||||||||||||||||||||||
| 27 okhttp3.Request | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 28 okhttp3.internal.connection | 8 | 1 | 2 | 1 | 1 | 4 | 3 | 1 | 40 | |||||||||||||||||||||||||||||||
| 29 okhttp3.OkHttpClient | 1 | 1 | 1 | 1 | 1 | 15 | ||||||||||||||||||||||||||||||||||
| 30 okhttp3 | 6 | 1 | 1 | 4 | 3 | 1 | 4 | 2 | 1 | 1 | 3 | 4 | 1 | 1 | 1 | 1 | 1 | 10 | 2 | 2 | ||||||||||||||||||||
| 31 mockwebserver3.MockResponse | 1 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 32 mockwebserver3.internal | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 okhttp3.android | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 okhttp3.dnsoverhttps | 1 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 35 okhttp3.internal.http1 | 1 | 1 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 36 okhttp3.internal.ws | 4 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 37 okhttp3.sse | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 38 mockwebserver3 | 1 | 3 | 9 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 39 mockwebserver3.MockWebServer | 1 | 2 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 40 okhttp3.mockwebserver | 1 | 1 | 9 | 5 |
5→30 okhttp3.Call uses okhttp3 part of a loop✕
- Connections
- 2 pairs of types, where a type in okhttp3.Call uses a type in okhttp3.
- The types involved
okhttp3.Call.Factory→okhttp3.Callokhttp3.Call.Factory→okhttp3.Request
- Direction
- okhttp3.Call uses okhttp3, so a change to okhttp3 can break okhttp3.Call, while a change to okhttp3.Call can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→30 okhttp3.Dns uses okhttp3 part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.Dns uses a type in okhttp3.
- The types involved
okhttp3.Dns.Companion→okhttp3.Dns
- Direction
- okhttp3.Dns uses okhttp3, so a change to okhttp3 can break okhttp3.Dns, while a change to okhttp3.Dns can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→30 okhttp3.EventListener uses okhttp3 part of a loop✕
- Connections
- 12 pairs of types, where a type in okhttp3.EventListener uses a type in okhttp3.
- The types involved
okhttp3.EventListener.AggregateEventListener→okhttp3.Callokhttp3.EventListener.AggregateEventListener→okhttp3.Connectionokhttp3.EventListener.AggregateEventListener→okhttp3.Dispatcherokhttp3.EventListener.AggregateEventListener→okhttp3.EventListenerokhttp3.EventListener.AggregateEventListener→okhttp3.Handshakeokhttp3.EventListener.AggregateEventListener→okhttp3.HttpUrlokhttp3.EventListener.AggregateEventListener→okhttp3.Protocolokhttp3.EventListener.AggregateEventListener→okhttp3.Requestokhttp3.EventListener.AggregateEventListener→okhttp3.Responseokhttp3.EventListener.Companion→okhttp3.EventListenerokhttp3.EventListener.Factory→okhttp3.Callokhttp3.EventListener.Factory→okhttp3.EventListener
- Direction
- okhttp3.EventListener uses okhttp3, so a change to okhttp3 can break okhttp3.EventListener, while a change to okhttp3.EventListener can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 okhttp3.Headers uses okhttp3 part of a loop✕
- Connections
- 2 pairs of types, where a type in okhttp3.Headers uses a type in okhttp3.
- The types involved
okhttp3.Headers.Builder→okhttp3.Headersokhttp3.Headers.Companion→okhttp3.Headers
- Direction
- okhttp3.Headers uses okhttp3, so a change to okhttp3 can break okhttp3.Headers, while a change to okhttp3.Headers can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→30 okhttp3.Interceptor uses okhttp3 part of a loop✕
- Connections
- 13 pairs of types, where a type in okhttp3.Interceptor uses a type in okhttp3.
- The types involved
okhttp3.Interceptor.Chain→okhttp3.Authenticatorokhttp3.Interceptor.Chain→okhttp3.Cacheokhttp3.Interceptor.Chain→okhttp3.Callokhttp3.Interceptor.Chain→okhttp3.CertificatePinnerokhttp3.Interceptor.Chain→okhttp3.Connectionokhttp3.Interceptor.Chain→okhttp3.ConnectionPoolokhttp3.Interceptor.Chain→okhttp3.CookieJarokhttp3.Interceptor.Chain→okhttp3.Dnsokhttp3.Interceptor.Chain→okhttp3.EventListenerokhttp3.Interceptor.Chain→okhttp3.Requestokhttp3.Interceptor.Chain→okhttp3.Responseokhttp3.Interceptor.Companion→okhttp3.Interceptorokhttp3.Interceptor.Companion→okhttp3.Response
- Direction
- okhttp3.Interceptor uses okhttp3, so a change to okhttp3 can break okhttp3.Interceptor, while a change to okhttp3.Interceptor can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→19 okhttp3.internal.dns.DnsQuery uses okhttp3.internal.dns part of a loop✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.dns.DnsQuery uses a type in okhttp3.internal.dns.
- The types involved
okhttp3.internal.dns.DnsQuery.Callback→okhttp3.internal.dns.DnsMessageokhttp3.internal.dns.DnsQuery.Factory→okhttp3.internal.dns.DnsQueryokhttp3.internal.dns.DnsQuery.Factory→okhttp3.internal.dns.Question
- Direction
- okhttp3.internal.dns.DnsQuery uses okhttp3.internal.dns, so a change to okhttp3.internal.dns can break okhttp3.internal.dns.DnsQuery, while a change to okhttp3.internal.dns.DnsQuery can't break okhttp3.internal.dns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→28 okhttp3.internal.http.ExchangeCodec uses okhttp3.internal.connection part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http.ExchangeCodec uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.http.ExchangeCodec.Carrier→okhttp3.internal.connection.RealCall
- Direction
- okhttp3.internal.http.ExchangeCodec uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.http.ExchangeCodec, while a change to okhttp3.internal.http.ExchangeCodec can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→30 okhttp3.internal.http.ExchangeCodec uses okhttp3 part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http.ExchangeCodec uses a type in okhttp3.
- The types involved
okhttp3.internal.http.ExchangeCodec.Carrier→okhttp3.Route
- Direction
- okhttp3.internal.http.ExchangeCodec uses okhttp3, so a change to okhttp3 can break okhttp3.internal.http.ExchangeCodec, while a change to okhttp3.internal.http.ExchangeCodec can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 okhttp3.internal.http2.Http2Connection uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http2.Http2Connection uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.http2.Http2Connection.Builder→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal.http2.Http2Connection uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.http2.Http2Connection, while a change to okhttp3.internal.http2.Http2Connection can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.http2.Http2Connection uses a module listed above it, which is the healthy direction.
12→24 okhttp3.internal.http2.Http2Connection uses okhttp3.internal.http2 part of a loop✕
- Connections
- 11 pairs of types, where a type in okhttp3.internal.http2.Http2Connection uses a type in okhttp3.internal.http2.
- The types involved
okhttp3.internal.http2.Http2Connection.Builder→okhttp3.internal.http2.FlowControlListenerokhttp3.internal.http2.Http2Connection.Builder→okhttp3.internal.http2.Http2Connectionokhttp3.internal.http2.Http2Connection.Builder→okhttp3.internal.http2.PushObserverokhttp3.internal.http2.Http2Connection.Companion→okhttp3.internal.http2.Settingsokhttp3.internal.http2.Http2Connection.Listener→okhttp3.internal.http2.Http2Connectionokhttp3.internal.http2.Http2Connection.Listener→okhttp3.internal.http2.Http2Streamokhttp3.internal.http2.Http2Connection.Listener→okhttp3.internal.http2.Settingsokhttp3.internal.http2.Http2Connection.ReaderRunnable→okhttp3.internal.http2.ErrorCodeokhttp3.internal.http2.Http2Connection.ReaderRunnable→okhttp3.internal.http2.Headerokhttp3.internal.http2.Http2Connection.ReaderRunnable→okhttp3.internal.http2.Http2Readerokhttp3.internal.http2.Http2Connection.ReaderRunnable→okhttp3.internal.http2.Settings
- Direction
- okhttp3.internal.http2.Http2Connection uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break okhttp3.internal.http2.Http2Connection, while a change to okhttp3.internal.http2.Http2Connection can't break okhttp3.internal.http2.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→28 okhttp3.internal.http2.Http2Connection uses okhttp3.internal.connection part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http2.Http2Connection uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.http2.Http2Connection.Builder→okhttp3.internal.connection.BufferedSocket
- Direction
- okhttp3.internal.http2.Http2Connection uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.http2.Http2Connection, while a change to okhttp3.internal.http2.Http2Connection can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→20 okhttp3.internal.platform.android.DeferredSocketAdapter uses okhttp3.internal.platform.android part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.platform.android.DeferredSocketAdapter uses a type in okhttp3.internal.platform.android.
- The types involved
okhttp3.internal.platform.android.DeferredSocketAdapter.Factory→okhttp3.internal.platform.android.SocketAdapter
- Direction
- okhttp3.internal.platform.android.DeferredSocketAdapter uses okhttp3.internal.platform.android, so a change to okhttp3.internal.platform.android can break okhttp3.internal.platform.android.DeferredSocketAdapter, while a change to okhttp3.internal.platform.android.DeferredSocketAdapter can't break okhttp3.internal.platform.android.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→30 okhttp3.internal.tls uses okhttp3 part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.tls uses a type in okhttp3.
- The types involved
okhttp3.internal.tls.CertificateBlocklist→okhttp3.Handshake
- Direction
- okhttp3.internal.tls uses okhttp3, so a change to okhttp3 can break okhttp3.internal.tls, while a change to okhttp3.internal.tls can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→30 okhttp3.sockets.FakeSslSocket uses okhttp3 part of a loop✕
- Connections
- 2 pairs of types, where a type in okhttp3.sockets.FakeSslSocket uses a type in okhttp3.
- The types involved
okhttp3.sockets.FakeSslSocket.FakeSslSession→okhttp3.Handshakeokhttp3.sockets.FakeSslSocket.FakeSslSession→okhttp3.Protocol
- Direction
- okhttp3.sockets.FakeSslSocket uses okhttp3, so a change to okhttp3 can break okhttp3.sockets.FakeSslSocket, while a change to okhttp3.sockets.FakeSslSocket can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 okhttp3.FakeDns uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.FakeDns uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.FakeDns.FakeDnsCall→okhttp3.internal.concurrent.TaskQueue
- Direction
- okhttp3.FakeDns uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.FakeDns, while a change to okhttp3.FakeDns can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.FakeDns uses a module listed above it, which is the healthy direction.
16→6 okhttp3.FakeDns uses okhttp3.Dns✕
- Connections
- 3 pairs of types, where a type in okhttp3.FakeDns uses a type in okhttp3.Dns.
- The types involved
okhttp3.FakeDns.FakeDnsCall→okhttp3.Dns.Callokhttp3.FakeDns.FakeDnsCall→okhttp3.Dns.Callbackokhttp3.FakeDns.FakeDnsCall→okhttp3.Dns.Request
- Direction
- okhttp3.FakeDns uses okhttp3.Dns, so a change to okhttp3.Dns can break okhttp3.FakeDns, while a change to okhttp3.FakeDns can't break okhttp3.Dns.
- Position
- Below the diagonal: okhttp3.FakeDns uses a module listed above it, which is the healthy direction.
17→8 okhttp3.Response uses okhttp3.Headers✕
- Connections
- 1 pair of types, where a type in okhttp3.Response uses a type in okhttp3.Headers.
- The types involved
okhttp3.Response.Builder→okhttp3.Headers.Builder
- Direction
- okhttp3.Response uses okhttp3.Headers, so a change to okhttp3.Headers can break okhttp3.Response, while a change to okhttp3.Response can't break okhttp3.Headers.
- Position
- Below the diagonal: okhttp3.Response uses a module listed above it, which is the healthy direction.
17→28 okhttp3.Response uses okhttp3.internal.connection part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.Response uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.Response.Builder→okhttp3.internal.connection.Exchange
- Direction
- okhttp3.Response uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.Response, while a change to okhttp3.Response can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→30 okhttp3.Response uses okhttp3 part of a loop✕
- Connections
- 7 pairs of types, where a type in okhttp3.Response uses a type in okhttp3.
- The types involved
okhttp3.Response.Builder→okhttp3.Handshakeokhttp3.Response.Builder→okhttp3.Headersokhttp3.Response.Builder→okhttp3.Protocolokhttp3.Response.Builder→okhttp3.Requestokhttp3.Response.Builder→okhttp3.Responseokhttp3.Response.Builder→okhttp3.ResponseBodyokhttp3.Response.Builder→okhttp3.TrailersSource
- Direction
- okhttp3.Response uses okhttp3, so a change to okhttp3 can break okhttp3.Response, while a change to okhttp3.Response can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 okhttp3.internal.cache uses okhttp3.internal.concurrent✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.cache uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.cache.DiskLruCache→okhttp3.internal.concurrent.Lockableokhttp3.internal.cache.DiskLruCache→okhttp3.internal.concurrent.TaskQueueokhttp3.internal.cache.DiskLruCache→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal.cache uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.cache, while a change to okhttp3.internal.cache can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.cache uses a module listed above it, which is the healthy direction.
18→9 okhttp3.internal.cache uses okhttp3.Interceptor✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.cache uses a type in okhttp3.Interceptor.
- The types involved
okhttp3.internal.cache.CacheInterceptor→okhttp3.Interceptor.Chain
- Direction
- okhttp3.internal.cache uses okhttp3.Interceptor, so a change to okhttp3.Interceptor can break okhttp3.internal.cache, while a change to okhttp3.internal.cache can't break okhttp3.Interceptor.
- Position
- Below the diagonal: okhttp3.internal.cache uses a module listed above it, which is the healthy direction.
18→30 okhttp3.internal.cache uses okhttp3 part of a loop✕
- Connections
- 5 pairs of types, where a type in okhttp3.internal.cache uses a type in okhttp3.
- The types involved
okhttp3.internal.cache.CacheInterceptor→okhttp3.Interceptorokhttp3.internal.cache.CacheInterceptor→okhttp3.Responseokhttp3.internal.cache.CacheInterceptorKt→okhttp3.Requestokhttp3.internal.cache.CacheStrategy→okhttp3.Requestokhttp3.internal.cache.CacheStrategy→okhttp3.Response
- Direction
- okhttp3.internal.cache uses okhttp3, so a change to okhttp3 can break okhttp3.internal.cache, while a change to okhttp3.internal.cache can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 okhttp3.internal.dns uses okhttp3.internal.concurrent✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal.dns uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.dns.LookupDnsCall→okhttp3.internal.concurrent.Taskokhttp3.internal.dns.LookupDnsCall→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.dns.RealDnsCache→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.dns.StateMachineDnsCall→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal.dns uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.dns, while a change to okhttp3.internal.dns can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.dns uses a module listed above it, which is the healthy direction.
19→6 okhttp3.internal.dns uses okhttp3.Dns✕
- Connections
- 9 pairs of types, where a type in okhttp3.internal.dns uses a type in okhttp3.Dns.
- The types involved
okhttp3.internal.dns.-ExecuteDnsKt→okhttp3.Dns.Recordokhttp3.internal.dns.-StateMachineDnsCallKt→okhttp3.Dns.Callokhttp3.internal.dns.LookupDnsCall→okhttp3.Dns.Callokhttp3.internal.dns.LookupDnsCall→okhttp3.Dns.Callbackokhttp3.internal.dns.LookupDnsCall→okhttp3.Dns.Requestokhttp3.internal.dns.StateMachineDnsCall→okhttp3.Dns.Callokhttp3.internal.dns.StateMachineDnsCall→okhttp3.Dns.Callbackokhttp3.internal.dns.StateMachineDnsCall→okhttp3.Dns.Recordokhttp3.internal.dns.StateMachineDnsCall→okhttp3.Dns.Request
- Direction
- okhttp3.internal.dns uses okhttp3.Dns, so a change to okhttp3.Dns can break okhttp3.internal.dns, while a change to okhttp3.internal.dns can't break okhttp3.Dns.
- Position
- Below the diagonal: okhttp3.internal.dns uses a module listed above it, which is the healthy direction.
19→10 okhttp3.internal.dns uses okhttp3.internal.dns.DnsQuery✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.dns uses a type in okhttp3.internal.dns.DnsQuery.
- The types involved
okhttp3.internal.dns.DnsQuery→okhttp3.internal.dns.DnsQuery.Callbackokhttp3.internal.dns.RealDnsCache→okhttp3.internal.dns.DnsQuery.Factoryokhttp3.internal.dns.StateMachineDnsCall→okhttp3.internal.dns.DnsQuery.Factory
- Direction
- okhttp3.internal.dns uses okhttp3.internal.dns.DnsQuery, so a change to okhttp3.internal.dns.DnsQuery can break okhttp3.internal.dns, while a change to okhttp3.internal.dns can't break okhttp3.internal.dns.DnsQuery.
- Position
- Below the diagonal: okhttp3.internal.dns uses a module listed above it, which is the healthy direction.
19→30 okhttp3.internal.dns uses okhttp3 part of a loop✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.dns uses a type in okhttp3.
- The types involved
okhttp3.internal.dns.DnsTestingKt→okhttp3.Dnsokhttp3.internal.dns.InetAddressDns→okhttp3.Dnsokhttp3.internal.dns.LookupDnsCall→okhttp3.Dns
- Direction
- okhttp3.internal.dns uses okhttp3, so a change to okhttp3 can break okhttp3.internal.dns, while a change to okhttp3.internal.dns can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→13 okhttp3.internal.platform.android uses okhttp3.internal.platform.android.DeferredSocketAdapter✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.platform.android uses a type in okhttp3.internal.platform.android.DeferredSocketAdapter.
- The types involved
okhttp3.internal.platform.android.DeferredSocketAdapter→okhttp3.internal.platform.android.DeferredSocketAdapter.Factory
- Direction
- okhttp3.internal.platform.android uses okhttp3.internal.platform.android.DeferredSocketAdapter, so a change to okhttp3.internal.platform.android.DeferredSocketAdapter can break okhttp3.internal.platform.android, while a change to okhttp3.internal.platform.android can't break okhttp3.internal.platform.android.DeferredSocketAdapter.
- Position
- Below the diagonal: okhttp3.internal.platform.android uses a module listed above it, which is the healthy direction.
20→14 okhttp3.internal.platform.android uses okhttp3.internal.tls✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.platform.android uses a type in okhttp3.internal.tls.
- The types involved
okhttp3.internal.platform.android.AndroidCertificateChainCleaner→okhttp3.internal.tls.CertificateChainCleaner
- Direction
- okhttp3.internal.platform.android uses okhttp3.internal.tls, so a change to okhttp3.internal.tls can break okhttp3.internal.platform.android, while a change to okhttp3.internal.platform.android can't break okhttp3.internal.tls.
- Position
- Below the diagonal: okhttp3.internal.platform.android uses a module listed above it, which is the healthy direction.
20→30 okhttp3.internal.platform.android uses okhttp3 part of a loop✕
- Connections
- 7 pairs of types, where a type in okhttp3.internal.platform.android uses a type in okhttp3.
- The types involved
okhttp3.internal.platform.android.Android10SocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.Android17SocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.AndroidSocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.BouncyCastleSocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.ConscryptSocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.DeferredSocketAdapter→okhttp3.Protocolokhttp3.internal.platform.android.SocketAdapter→okhttp3.Protocol
- Direction
- okhttp3.internal.platform.android uses okhttp3, so a change to okhttp3 can break okhttp3.internal.platform.android, while a change to okhttp3.internal.platform.android can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→15 okhttp3.sockets.FakeSocket.State uses okhttp3.sockets.FakeSslSocket✕
- Connections
- 2 pairs of types, where a type in okhttp3.sockets.FakeSocket.State uses a type in okhttp3.sockets.FakeSslSocket.
- The types involved
okhttp3.sockets.FakeSocket.State.Closed→okhttp3.sockets.FakeSslSocket.HandshakeStateokhttp3.sockets.FakeSocket.State.Connected→okhttp3.sockets.FakeSslSocket.HandshakeState
- Direction
- okhttp3.sockets.FakeSocket.State uses okhttp3.sockets.FakeSslSocket, so a change to okhttp3.sockets.FakeSslSocket can break okhttp3.sockets.FakeSocket.State, while a change to okhttp3.sockets.FakeSocket.State can't break okhttp3.sockets.FakeSslSocket.
- Position
- Below the diagonal: okhttp3.sockets.FakeSocket.State uses a module listed above it, which is the healthy direction.
21→25 okhttp3.sockets.FakeSocket.State uses okhttp3.sockets part of a loop✕
- Connections
- 4 pairs of types, where a type in okhttp3.sockets.FakeSocket.State uses a type in okhttp3.sockets.
- The types involved
okhttp3.sockets.FakeSocket.State.Connected→okhttp3.sockets.FakeConnectionokhttp3.sockets.FakeSocket.State.Connected→okhttp3.sockets.SocketSinkokhttp3.sockets.FakeSocket.State.Connected→okhttp3.sockets.SocketSourceokhttp3.sockets.FakeSocket.State.Connecting→okhttp3.sockets.ConnectAttempt
- Direction
- okhttp3.sockets.FakeSocket.State uses okhttp3.sockets, so a change to okhttp3.sockets can break okhttp3.sockets.FakeSocket.State, while a change to okhttp3.sockets.FakeSocket.State can't break okhttp3.sockets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→9 okhttp3.internal.http uses okhttp3.Interceptor✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal.http uses a type in okhttp3.Interceptor.
- The types involved
okhttp3.internal.http.BridgeInterceptor→okhttp3.Interceptor.Chainokhttp3.internal.http.CallServerInterceptor→okhttp3.Interceptor.Chainokhttp3.internal.http.RealInterceptorChain→okhttp3.Interceptor.Chainokhttp3.internal.http.RetryAndFollowUpInterceptor→okhttp3.Interceptor.Chain
- Direction
- okhttp3.internal.http uses okhttp3.Interceptor, so a change to okhttp3.Interceptor can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.Interceptor.
- Position
- Below the diagonal: okhttp3.internal.http uses a module listed above it, which is the healthy direction.
22→11 okhttp3.internal.http uses okhttp3.internal.http.ExchangeCodec✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http uses a type in okhttp3.internal.http.ExchangeCodec.
- The types involved
okhttp3.internal.http.ExchangeCodec→okhttp3.internal.http.ExchangeCodec.Carrier
- Direction
- okhttp3.internal.http uses okhttp3.internal.http.ExchangeCodec, so a change to okhttp3.internal.http.ExchangeCodec can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.internal.http.ExchangeCodec.
- Position
- Below the diagonal: okhttp3.internal.http uses a module listed above it, which is the healthy direction.
22→14 okhttp3.internal.http uses okhttp3.internal.tls✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http uses a type in okhttp3.internal.tls.
- The types involved
okhttp3.internal.http.RealInterceptorChain→okhttp3.internal.tls.CertificateChainCleaner
- Direction
- okhttp3.internal.http uses okhttp3.internal.tls, so a change to okhttp3.internal.tls can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.internal.tls.
- Position
- Below the diagonal: okhttp3.internal.http uses a module listed above it, which is the healthy direction.
22→17 okhttp3.internal.http uses okhttp3.Response✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http uses a type in okhttp3.Response.
- The types involved
okhttp3.internal.http.ExchangeCodec→okhttp3.Response.Builder
- Direction
- okhttp3.internal.http uses okhttp3.Response, so a change to okhttp3.Response can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.Response.
- Position
- Below the diagonal: okhttp3.internal.http uses a module listed above it, which is the healthy direction.
22→28 okhttp3.internal.http uses okhttp3.internal.connection part of a loop✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal.http uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.http.RealInterceptorChain→okhttp3.internal.connection.Exchangeokhttp3.internal.http.RealInterceptorChain→okhttp3.internal.connection.RealCallokhttp3.internal.http.RetryAndFollowUpInterceptor→okhttp3.internal.connection.Exchangeokhttp3.internal.http.RetryAndFollowUpInterceptor→okhttp3.internal.connection.RealCall
- Direction
- okhttp3.internal.http uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→30 okhttp3.internal.http uses okhttp3 part of a loop✕
- Connections
- 37 pairs of types, where a type in okhttp3.internal.http uses a type in okhttp3. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
okhttp3.internal.http.BridgeInterceptor→okhttp3.Cookieokhttp3.internal.http.BridgeInterceptor→okhttp3.Interceptorokhttp3.internal.http.BridgeInterceptor→okhttp3.Responseokhttp3.internal.http.CallServerInterceptor→okhttp3.Interceptorokhttp3.internal.http.CallServerInterceptor→okhttp3.Responseokhttp3.internal.http.ExchangeCodec→okhttp3.Headersokhttp3.internal.http.ExchangeCodec→okhttp3.Requestokhttp3.internal.http.ExchangeCodec→okhttp3.Responseokhttp3.internal.http.GzipRequestBody→okhttp3.MediaTypeokhttp3.internal.http.GzipRequestBody→okhttp3.RequestBodyokhttp3.internal.http.HttpHeadersKt→okhttp3.Challengeokhttp3.internal.http.HttpHeadersKt→okhttp3.Headersokhttp3.internal.http.HttpHeadersKt→okhttp3.HttpUrlokhttp3.internal.http.HttpHeadersKt→okhttp3.Responseokhttp3.internal.http.RealInterceptorChain→okhttp3.Addressokhttp3.internal.http.RealInterceptorChain→okhttp3.Authenticatorokhttp3.internal.http.RealInterceptorChain→okhttp3.Cacheokhttp3.internal.http.RealInterceptorChain→okhttp3.Callokhttp3.internal.http.RealInterceptorChain→okhttp3.CertificatePinnerokhttp3.internal.http.RealInterceptorChain→okhttp3.Connectionokhttp3.internal.http.RealInterceptorChain→okhttp3.ConnectionPoolokhttp3.internal.http.RealInterceptorChain→okhttp3.CookieJarokhttp3.internal.http.RealInterceptorChain→okhttp3.Dnsokhttp3.internal.http.RealInterceptorChain→okhttp3.EventListenerokhttp3.internal.http.RealInterceptorChain→okhttp3.HttpUrl
- Direction
- okhttp3.internal.http uses okhttp3, so a change to okhttp3 can break okhttp3.internal.http, while a change to okhttp3.internal.http can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→14 okhttp3.internal.platform uses okhttp3.internal.tls✕
- Connections
- 6 pairs of types, where a type in okhttp3.internal.platform uses a type in okhttp3.internal.tls.
- The types involved
okhttp3.internal.platform.Android10Platform→okhttp3.internal.tls.CertificateChainCleanerokhttp3.internal.platform.Android10Platform→okhttp3.internal.tls.TrustRootIndexokhttp3.internal.platform.AndroidPlatform→okhttp3.internal.tls.CertificateChainCleanerokhttp3.internal.platform.AndroidPlatform→okhttp3.internal.tls.TrustRootIndexokhttp3.internal.platform.Platform→okhttp3.internal.tls.CertificateChainCleanerokhttp3.internal.platform.Platform→okhttp3.internal.tls.TrustRootIndex
- Direction
- okhttp3.internal.platform uses okhttp3.internal.tls, so a change to okhttp3.internal.tls can break okhttp3.internal.platform, while a change to okhttp3.internal.platform can't break okhttp3.internal.tls.
- Position
- Below the diagonal: okhttp3.internal.platform uses a module listed above it, which is the healthy direction.
23→20 okhttp3.internal.platform uses okhttp3.internal.platform.android✕
- Connections
- 2 pairs of types, where a type in okhttp3.internal.platform uses a type in okhttp3.internal.platform.android.
- The types involved
okhttp3.internal.platform.Android10Platform→okhttp3.internal.platform.android.SocketAdapterokhttp3.internal.platform.AndroidPlatform→okhttp3.internal.platform.android.SocketAdapter
- Direction
- okhttp3.internal.platform uses okhttp3.internal.platform.android, so a change to okhttp3.internal.platform.android can break okhttp3.internal.platform, while a change to okhttp3.internal.platform can't break okhttp3.internal.platform.android.
- Position
- Below the diagonal: okhttp3.internal.platform uses a module listed above it, which is the healthy direction.
23→30 okhttp3.internal.platform uses okhttp3 part of a loop✕
- Connections
- 9 pairs of types, where a type in okhttp3.internal.platform uses a type in okhttp3.
- The types involved
okhttp3.internal.platform.Android10Platform→okhttp3.Protocolokhttp3.internal.platform.AndroidPlatform→okhttp3.Protocolokhttp3.internal.platform.BouncyCastlePlatform→okhttp3.Protocolokhttp3.internal.platform.ConscryptPlatform→okhttp3.Protocolokhttp3.internal.platform.Jdk8WithJettyBootPlatform→okhttp3.Protocolokhttp3.internal.platform.Jdk9Platform→okhttp3.Protocolokhttp3.internal.platform.OpenJSSEPlatform→okhttp3.Protocolokhttp3.internal.platform.Platform→okhttp3.Dnsokhttp3.internal.platform.Platform→okhttp3.Protocol
- Direction
- okhttp3.internal.platform uses okhttp3, so a change to okhttp3 can break okhttp3.internal.platform, while a change to okhttp3.internal.platform can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 okhttp3.internal.http2 uses okhttp3.internal.concurrent✕
- Connections
- 5 pairs of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.http2.Http2Connection→okhttp3.internal.concurrent.Lockableokhttp3.internal.http2.Http2Connection→okhttp3.internal.concurrent.TaskQueueokhttp3.internal.http2.Http2Connection→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.http2.Http2Stream→okhttp3.internal.concurrent.Lockableokhttp3.internal.http2.Http2Writer→okhttp3.internal.concurrent.Lockable
- Direction
- okhttp3.internal.http2 uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.http2 uses a module listed above it, which is the healthy direction.
24→11 okhttp3.internal.http2 uses okhttp3.internal.http.ExchangeCodec✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.internal.http.ExchangeCodec.
- The types involved
okhttp3.internal.http2.Http2ExchangeCodec→okhttp3.internal.http.ExchangeCodec.Carrier
- Direction
- okhttp3.internal.http2 uses okhttp3.internal.http.ExchangeCodec, so a change to okhttp3.internal.http.ExchangeCodec can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.internal.http.ExchangeCodec.
- Position
- Below the diagonal: okhttp3.internal.http2 uses a module listed above it, which is the healthy direction.
24→12 okhttp3.internal.http2 uses okhttp3.internal.http2.Http2Connection✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.internal.http2.Http2Connection.
- The types involved
okhttp3.internal.http2.Http2Connection→okhttp3.internal.http2.Http2Connection.Builderokhttp3.internal.http2.Http2Connection→okhttp3.internal.http2.Http2Connection.Listenerokhttp3.internal.http2.Http2Connection→okhttp3.internal.http2.Http2Connection.ReaderRunnable
- Direction
- okhttp3.internal.http2 uses okhttp3.internal.http2.Http2Connection, so a change to okhttp3.internal.http2.Http2Connection can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.internal.http2.Http2Connection.
- Position
- Below the diagonal: okhttp3.internal.http2 uses a module listed above it, which is the healthy direction.
24→17 okhttp3.internal.http2 uses okhttp3.Response✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.Response.
- The types involved
okhttp3.internal.http2.Http2ExchangeCodec→okhttp3.Response.Builder
- Direction
- okhttp3.internal.http2 uses okhttp3.Response, so a change to okhttp3.Response can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.Response.
- Position
- Below the diagonal: okhttp3.internal.http2 uses a module listed above it, which is the healthy direction.
24→22 okhttp3.internal.http2 uses okhttp3.internal.http✕
- Connections
- 2 pairs of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.internal.http.
- The types involved
okhttp3.internal.http2.Http2ExchangeCodec→okhttp3.internal.http.ExchangeCodecokhttp3.internal.http2.Http2ExchangeCodec→okhttp3.internal.http.RealInterceptorChain
- Direction
- okhttp3.internal.http2 uses okhttp3.internal.http, so a change to okhttp3.internal.http can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.internal.http.
- Position
- Below the diagonal: okhttp3.internal.http2 uses a module listed above it, which is the healthy direction.
24→28 okhttp3.internal.http2 uses okhttp3.internal.connection part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.http2.Http2Connection→okhttp3.internal.connection.BufferedSocket
- Direction
- okhttp3.internal.http2 uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→30 okhttp3.internal.http2 uses okhttp3 part of a loop✕
- Connections
- 6 pairs of types, where a type in okhttp3.internal.http2 uses a type in okhttp3.
- The types involved
okhttp3.internal.http2.Http2ExchangeCodec→okhttp3.Headersokhttp3.internal.http2.Http2ExchangeCodec→okhttp3.OkHttpClientokhttp3.internal.http2.Http2ExchangeCodec→okhttp3.Protocolokhttp3.internal.http2.Http2ExchangeCodec→okhttp3.Requestokhttp3.internal.http2.Http2ExchangeCodec→okhttp3.Responseokhttp3.internal.http2.Http2Stream→okhttp3.Headers
- Direction
- okhttp3.internal.http2 uses okhttp3, so a change to okhttp3 can break okhttp3.internal.http2, while a change to okhttp3.internal.http2 can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 okhttp3.sockets uses okhttp3.internal.concurrent✕
- Connections
- 3 pairs of types, where a type in okhttp3.sockets uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.sockets.BoundServer→okhttp3.internal.concurrent.Lockableokhttp3.sockets.ConnectAttempt→okhttp3.internal.concurrent.Lockableokhttp3.sockets.FakeConnection→okhttp3.internal.concurrent.Lockable
- Direction
- okhttp3.sockets uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.sockets uses a module listed above it, which is the healthy direction.
25→3 okhttp3.sockets uses okhttp3.tls✕
- Connections
- 1 pair of types, where a type in okhttp3.sockets uses a type in okhttp3.tls.
- The types involved
okhttp3.sockets.FakeTls→okhttp3.tls.HandshakeCertificates
- Direction
- okhttp3.sockets uses okhttp3.tls, so a change to okhttp3.tls can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.tls.
- Position
- Below the diagonal: okhttp3.sockets uses a module listed above it, which is the healthy direction.
25→15 okhttp3.sockets uses okhttp3.sockets.FakeSslSocket✕
- Connections
- 1 pair of types, where a type in okhttp3.sockets uses a type in okhttp3.sockets.FakeSslSocket.
- The types involved
okhttp3.sockets.FakeSslSocket→okhttp3.sockets.FakeSslSocket.HandshakeState
- Direction
- okhttp3.sockets uses okhttp3.sockets.FakeSslSocket, so a change to okhttp3.sockets.FakeSslSocket can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.sockets.FakeSslSocket.
- Position
- Below the diagonal: okhttp3.sockets uses a module listed above it, which is the healthy direction.
25→21 okhttp3.sockets uses okhttp3.sockets.FakeSocket.State✕
- Connections
- 1 pair of types, where a type in okhttp3.sockets uses a type in okhttp3.sockets.FakeSocket.State.
- The types involved
okhttp3.sockets.FakeSslSocket→okhttp3.sockets.FakeSocket.State.Connected
- Direction
- okhttp3.sockets uses okhttp3.sockets.FakeSocket.State, so a change to okhttp3.sockets.FakeSocket.State can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.sockets.FakeSocket.State.
- Position
- Below the diagonal: okhttp3.sockets uses a module listed above it, which is the healthy direction.
25→23 okhttp3.sockets uses okhttp3.internal.platform✕
- Connections
- 1 pair of types, where a type in okhttp3.sockets uses a type in okhttp3.internal.platform.
- The types involved
okhttp3.sockets.FakeNetworkPlatform→okhttp3.internal.platform.Platform
- Direction
- okhttp3.sockets uses okhttp3.internal.platform, so a change to okhttp3.internal.platform can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.internal.platform.
- Position
- Below the diagonal: okhttp3.sockets uses a module listed above it, which is the healthy direction.
25→30 okhttp3.sockets uses okhttp3 part of a loop✕
- Connections
- 5 pairs of types, where a type in okhttp3.sockets uses a type in okhttp3.
- The types involved
okhttp3.sockets.FakeNetworkPlatform→okhttp3.Protocolokhttp3.sockets.FakeSslSocket→okhttp3.CipherSuiteokhttp3.sockets.FakeSslSocket→okhttp3.TlsVersionokhttp3.sockets.FakeTls→okhttp3.CipherSuiteokhttp3.sockets.FakeTls→okhttp3.TlsVersion
- Direction
- okhttp3.sockets uses okhttp3, so a change to okhttp3 can break okhttp3.sockets, while a change to okhttp3.sockets can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→1 okhttp3.internal uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.internal uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.InternalKt→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal uses a module listed above it, which is the healthy direction.
26→7 okhttp3.internal uses okhttp3.EventListener✕
- Connections
- 1 pair of types, where a type in okhttp3.internal uses a type in okhttp3.EventListener.
- The types involved
okhttp3.internal.-UtilJvmKt→okhttp3.EventListener.Factory
- Direction
- okhttp3.internal uses okhttp3.EventListener, so a change to okhttp3.EventListener can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.EventListener.
- Position
- Below the diagonal: okhttp3.internal uses a module listed above it, which is the healthy direction.
26→8 okhttp3.internal uses okhttp3.Headers✕
- Connections
- 2 pairs of types, where a type in okhttp3.internal uses a type in okhttp3.Headers.
- The types involved
okhttp3.internal.-HeadersCommonKt→okhttp3.Headers.Builderokhttp3.internal.InternalKt→okhttp3.Headers.Builder
- Direction
- okhttp3.internal uses okhttp3.Headers, so a change to okhttp3.Headers can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.Headers.
- Position
- Below the diagonal: okhttp3.internal uses a module listed above it, which is the healthy direction.
26→24 okhttp3.internal uses okhttp3.internal.http2✕
- Connections
- 1 pair of types, where a type in okhttp3.internal uses a type in okhttp3.internal.http2.
- The types involved
okhttp3.internal.-UtilJvmKt→okhttp3.internal.http2.Header
- Direction
- okhttp3.internal uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.internal.http2.
- Position
- Below the diagonal: okhttp3.internal uses a module listed above it, which is the healthy direction.
26→28 okhttp3.internal uses okhttp3.internal.connection part of a loop✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.InternalKt→okhttp3.internal.connection.ConnectionListenerokhttp3.internal.InternalKt→okhttp3.internal.connection.RealConnectionokhttp3.internal.NativeImageTestsAccessorsKt→okhttp3.internal.connection.Exchangeokhttp3.internal.NativeImageTestsAccessorsKt→okhttp3.internal.connection.RealConnection
- Direction
- okhttp3.internal uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.internal.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→29 okhttp3.internal uses okhttp3.OkHttpClient part of a loop✕
- Connections
- 1 pair of types, where a type in okhttp3.internal uses a type in okhttp3.OkHttpClient.
- The types involved
okhttp3.internal.InternalKt→okhttp3.OkHttpClient.Builder
- Direction
- okhttp3.internal uses okhttp3.OkHttpClient, so a change to okhttp3.OkHttpClient can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.OkHttpClient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→30 okhttp3.internal uses okhttp3 part of a loop✕
- Connections
- 21 pairs of types, where a type in okhttp3.internal uses a type in okhttp3.
- The types involved
okhttp3.internal.-CacheControlCommonKt→okhttp3.CacheControlokhttp3.internal.-CacheControlCommonKt→okhttp3.Headersokhttp3.internal.-HeadersCommonKt→okhttp3.Headersokhttp3.internal.-UtilJvmKt→okhttp3.Headersokhttp3.internal.-UtilJvmKt→okhttp3.HttpUrlokhttp3.internal.InternalKt→okhttp3.Cacheokhttp3.internal.InternalKt→okhttp3.ConnectionPoolokhttp3.internal.InternalKt→okhttp3.ConnectionSpecokhttp3.internal.InternalKt→okhttp3.Cookieokhttp3.internal.InternalKt→okhttp3.HttpUrlokhttp3.internal.InternalKt→okhttp3.MediaTypeokhttp3.internal.InternalKt→okhttp3.Requestokhttp3.internal.InternalKt→okhttp3.Responseokhttp3.internal.NativeImageTestsAccessorsKt→okhttp3.Cacheokhttp3.internal.RecordingOkAuthenticator→okhttp3.Authenticatorokhttp3.internal.RecordingOkAuthenticator→okhttp3.Requestokhttp3.internal.RecordingOkAuthenticator→okhttp3.Responseokhttp3.internal.RecordingOkAuthenticator→okhttp3.Routeokhttp3.internal.UnreadableResponseBody→okhttp3.MediaTypeokhttp3.internal.UnreadableResponseBody→okhttp3.ResponseBodyokhttp3.internal.UnreadableResponseBodyKt→okhttp3.Response
- Direction
- okhttp3.internal uses okhttp3, so a change to okhttp3 can break okhttp3.internal, while a change to okhttp3.internal can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→8 okhttp3.Request uses okhttp3.Headers✕
- Connections
- 1 pair of types, where a type in okhttp3.Request uses a type in okhttp3.Headers.
- The types involved
okhttp3.Request.Builder→okhttp3.Headers.Builder
- Direction
- okhttp3.Request uses okhttp3.Headers, so a change to okhttp3.Headers can break okhttp3.Request, while a change to okhttp3.Request can't break okhttp3.Headers.
- Position
- Below the diagonal: okhttp3.Request uses a module listed above it, which is the healthy direction.
27→26 okhttp3.Request uses okhttp3.internal✕
- Connections
- 1 pair of types, where a type in okhttp3.Request uses a type in okhttp3.internal.
- The types involved
okhttp3.Request.Builder→okhttp3.internal.Tags
- Direction
- okhttp3.Request uses okhttp3.internal, so a change to okhttp3.internal can break okhttp3.Request, while a change to okhttp3.Request can't break okhttp3.internal.
- Position
- Below the diagonal: okhttp3.Request uses a module listed above it, which is the healthy direction.
27→30 okhttp3.Request uses okhttp3 part of a loop✕
- Connections
- 5 pairs of types, where a type in okhttp3.Request uses a type in okhttp3.
- The types involved
okhttp3.Request.Builder→okhttp3.CacheControlokhttp3.Request.Builder→okhttp3.Headersokhttp3.Request.Builder→okhttp3.HttpUrlokhttp3.Request.Builder→okhttp3.Requestokhttp3.Request.Builder→okhttp3.RequestBody
- Direction
- okhttp3.Request uses okhttp3, so a change to okhttp3 can break okhttp3.Request, while a change to okhttp3.Request can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→1 okhttp3.internal.connection uses okhttp3.internal.concurrent✕
- Connections
- 8 pairs of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.connection.ConnectPlan→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.connection.FastFallbackExchangeFinder→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.connection.RealCall→okhttp3.internal.concurrent.Lockableokhttp3.internal.connection.RealConnection→okhttp3.internal.concurrent.Lockableokhttp3.internal.connection.RealConnection→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.connection.RealConnectionPool→okhttp3.internal.concurrent.TaskQueueokhttp3.internal.connection.RealConnectionPool→okhttp3.internal.concurrent.TaskRunnerokhttp3.internal.connection.RealRoutePlanner→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal.connection uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→9 okhttp3.internal.connection uses okhttp3.Interceptor✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.connection uses a type in okhttp3.Interceptor.
- The types involved
okhttp3.internal.connection.ConnectInterceptor→okhttp3.Interceptor.Chain
- Direction
- okhttp3.internal.connection uses okhttp3.Interceptor, so a change to okhttp3.Interceptor can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.Interceptor.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→11 okhttp3.internal.connection uses okhttp3.internal.http.ExchangeCodec✕
- Connections
- 2 pairs of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.http.ExchangeCodec.
- The types involved
okhttp3.internal.connection.ConnectPlan→okhttp3.internal.http.ExchangeCodec.Carrierokhttp3.internal.connection.RealConnection→okhttp3.internal.http.ExchangeCodec.Carrier
- Direction
- okhttp3.internal.connection uses okhttp3.internal.http.ExchangeCodec, so a change to okhttp3.internal.http.ExchangeCodec can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.http.ExchangeCodec.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→12 okhttp3.internal.connection uses okhttp3.internal.http2.Http2Connection✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.http2.Http2Connection.
- The types involved
okhttp3.internal.connection.RealConnection→okhttp3.internal.http2.Http2Connection.Listener
- Direction
- okhttp3.internal.connection uses okhttp3.internal.http2.Http2Connection, so a change to okhttp3.internal.http2.Http2Connection can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.http2.Http2Connection.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→17 okhttp3.internal.connection uses okhttp3.Response✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.connection uses a type in okhttp3.Response.
- The types involved
okhttp3.internal.connection.Exchange→okhttp3.Response.Builder
- Direction
- okhttp3.internal.connection uses okhttp3.Response, so a change to okhttp3.Response can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.Response.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→22 okhttp3.internal.connection uses okhttp3.internal.http✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.http.
- The types involved
okhttp3.internal.connection.Exchange→okhttp3.internal.http.ExchangeCodecokhttp3.internal.connection.RealCall→okhttp3.internal.http.RealInterceptorChainokhttp3.internal.connection.RealConnection→okhttp3.internal.http.ExchangeCodecokhttp3.internal.connection.RealConnection→okhttp3.internal.http.RealInterceptorChain
- Direction
- okhttp3.internal.connection uses okhttp3.internal.http, so a change to okhttp3.internal.http can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.http.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→24 okhttp3.internal.connection uses okhttp3.internal.http2✕
- Connections
- 3 pairs of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.http2.
- The types involved
okhttp3.internal.connection.RealConnection→okhttp3.internal.http2.Http2Connectionokhttp3.internal.connection.RealConnection→okhttp3.internal.http2.Http2Streamokhttp3.internal.connection.RealConnection→okhttp3.internal.http2.Settings
- Direction
- okhttp3.internal.connection uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.http2.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→26 okhttp3.internal.connection uses okhttp3.internal✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.connection uses a type in okhttp3.internal.
- The types involved
okhttp3.internal.connection.RealCall→okhttp3.internal.Tags
- Direction
- okhttp3.internal.connection uses okhttp3.internal, so a change to okhttp3.internal can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.internal.
- Position
- Below the diagonal: okhttp3.internal.connection uses a module listed above it, which is the healthy direction.
28→30 okhttp3.internal.connection uses okhttp3 part of a loop✕
- Connections
- 40 pairs of types, where a type in okhttp3.internal.connection uses a type in okhttp3. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
okhttp3.internal.connection.ConnectInterceptor→okhttp3.Interceptorokhttp3.internal.connection.ConnectInterceptor→okhttp3.Responseokhttp3.internal.connection.ConnectPlan→okhttp3.ConnectionSpecokhttp3.internal.connection.ConnectPlan→okhttp3.Handshakeokhttp3.internal.connection.ConnectPlan→okhttp3.Protocolokhttp3.internal.connection.ConnectPlan→okhttp3.Requestokhttp3.internal.connection.ConnectPlan→okhttp3.Routeokhttp3.internal.connection.ConnectionListener→okhttp3.Callokhttp3.internal.connection.ConnectionListener→okhttp3.Connectionokhttp3.internal.connection.ConnectionListener→okhttp3.Routeokhttp3.internal.connection.Exchange→okhttp3.Headersokhttp3.internal.connection.Exchange→okhttp3.Requestokhttp3.internal.connection.Exchange→okhttp3.Responseokhttp3.internal.connection.Exchange→okhttp3.ResponseBodyokhttp3.internal.connection.InetAddressOrderKt→okhttp3.Routeokhttp3.internal.connection.RealCall→okhttp3.Callokhttp3.internal.connection.RealCall→okhttp3.Callbackokhttp3.internal.connection.RealCall→okhttp3.EventListenerokhttp3.internal.connection.RealCall→okhttp3.OkHttpClientokhttp3.internal.connection.RealCall→okhttp3.Requestokhttp3.internal.connection.RealCall→okhttp3.Responseokhttp3.internal.connection.RealConnection→okhttp3.Addressokhttp3.internal.connection.RealConnection→okhttp3.Connectionokhttp3.internal.connection.RealConnection→okhttp3.Handshakeokhttp3.internal.connection.RealConnection→okhttp3.HttpUrl
- Direction
- okhttp3.internal.connection uses okhttp3, so a change to okhttp3 can break okhttp3.internal.connection, while a change to okhttp3.internal.connection can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 okhttp3.OkHttpClient uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.OkHttpClient uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.OkHttpClient uses a module listed above it, which is the healthy direction.
29→7 okhttp3.OkHttpClient uses okhttp3.EventListener✕
- Connections
- 1 pair of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.EventListener.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.EventListener.Factory
- Direction
- okhttp3.OkHttpClient uses okhttp3.EventListener, so a change to okhttp3.EventListener can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.EventListener.
- Position
- Below the diagonal: okhttp3.OkHttpClient uses a module listed above it, which is the healthy direction.
29→9 okhttp3.OkHttpClient uses okhttp3.Interceptor✕
- Connections
- 1 pair of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.Interceptor.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.Interceptor.Chain
- Direction
- okhttp3.OkHttpClient uses okhttp3.Interceptor, so a change to okhttp3.Interceptor can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.Interceptor.
- Position
- Below the diagonal: okhttp3.OkHttpClient uses a module listed above it, which is the healthy direction.
29→14 okhttp3.OkHttpClient uses okhttp3.internal.tls✕
- Connections
- 1 pair of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.internal.tls.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.internal.tls.CertificateChainCleaner
- Direction
- okhttp3.OkHttpClient uses okhttp3.internal.tls, so a change to okhttp3.internal.tls can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.internal.tls.
- Position
- Below the diagonal: okhttp3.OkHttpClient uses a module listed above it, which is the healthy direction.
29→28 okhttp3.OkHttpClient uses okhttp3.internal.connection✕
- Connections
- 1 pair of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.internal.connection.RouteDatabase
- Direction
- okhttp3.OkHttpClient uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.internal.connection.
- Position
- Below the diagonal: okhttp3.OkHttpClient uses a module listed above it, which is the healthy direction.
29→30 okhttp3.OkHttpClient uses okhttp3 part of a loop✕
- Connections
- 15 pairs of types, where a type in okhttp3.OkHttpClient uses a type in okhttp3.
- The types involved
okhttp3.OkHttpClient.Builder→okhttp3.Authenticatorokhttp3.OkHttpClient.Builder→okhttp3.Cacheokhttp3.OkHttpClient.Builder→okhttp3.CertificatePinnerokhttp3.OkHttpClient.Builder→okhttp3.ConnectionPoolokhttp3.OkHttpClient.Builder→okhttp3.ConnectionSpecokhttp3.OkHttpClient.Builder→okhttp3.CookieJarokhttp3.OkHttpClient.Builder→okhttp3.Dispatcherokhttp3.OkHttpClient.Builder→okhttp3.Dnsokhttp3.OkHttpClient.Builder→okhttp3.EventListenerokhttp3.OkHttpClient.Builder→okhttp3.Interceptorokhttp3.OkHttpClient.Builder→okhttp3.OkHttpClientokhttp3.OkHttpClient.Builder→okhttp3.Protocolokhttp3.OkHttpClient.Builder→okhttp3.Responseokhttp3.OkHttpClient.Companion→okhttp3.ConnectionSpecokhttp3.OkHttpClient.Companion→okhttp3.Protocol
- Direction
- okhttp3.OkHttpClient uses okhttp3, so a change to okhttp3 can break okhttp3.OkHttpClient, while a change to okhttp3.OkHttpClient can't break okhttp3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 okhttp3 uses okhttp3.internal.concurrent✕
- Connections
- 6 pairs of types, where a type in okhttp3 uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.Cache→okhttp3.internal.concurrent.TaskRunnerokhttp3.ConnectionPool→okhttp3.internal.concurrent.TaskRunnerokhttp3.FakeDns→okhttp3.internal.concurrent.TaskRunnerokhttp3.OkHttpClient→okhttp3.internal.concurrent.TaskRunnerokhttp3.TestValueFactory→okhttp3.internal.concurrent.TaskFakerokhttp3.TestValueFactory→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3 uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→3 okhttp3 uses okhttp3.tls✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.tls.
- The types involved
okhttp3.TestValueFactory→okhttp3.tls.HandshakeCertificates
- Direction
- okhttp3 uses okhttp3.tls, so a change to okhttp3.tls can break okhttp3, while a change to okhttp3 can't break okhttp3.tls.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→5 okhttp3 uses okhttp3.Call✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.Call.
- The types involved
okhttp3.OkHttpClient→okhttp3.Call.Factory
- Direction
- okhttp3 uses okhttp3.Call, so a change to okhttp3.Call can break okhttp3, while a change to okhttp3 can't break okhttp3.Call.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→6 okhttp3 uses okhttp3.Dns✕
- Connections
- 4 pairs of types, where a type in okhttp3 uses a type in okhttp3.Dns.
- The types involved
okhttp3.Dns→okhttp3.Dns.Callokhttp3.Dns→okhttp3.Dns.Requestokhttp3.FakeDns→okhttp3.Dns.Callokhttp3.FakeDns→okhttp3.Dns.Request
- Direction
- okhttp3 uses okhttp3.Dns, so a change to okhttp3.Dns can break okhttp3, while a change to okhttp3 can't break okhttp3.Dns.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→7 okhttp3 uses okhttp3.EventListener✕
- Connections
- 3 pairs of types, where a type in okhttp3 uses a type in okhttp3.EventListener.
- The types involved
okhttp3.ClientRuleEventListener→okhttp3.EventListener.Factoryokhttp3.OkHttpClient→okhttp3.EventListener.Factoryokhttp3.OkHttpClientTestRule→okhttp3.EventListener.Factory
- Direction
- okhttp3 uses okhttp3.EventListener, so a change to okhttp3.EventListener can break okhttp3, while a change to okhttp3 can't break okhttp3.EventListener.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→8 okhttp3 uses okhttp3.Headers✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.Headers.
- The types involved
okhttp3.Headers→okhttp3.Headers.Builder
- Direction
- okhttp3 uses okhttp3.Headers, so a change to okhttp3.Headers can break okhttp3, while a change to okhttp3 can't break okhttp3.Headers.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→9 okhttp3 uses okhttp3.Interceptor✕
- Connections
- 4 pairs of types, where a type in okhttp3 uses a type in okhttp3.Interceptor.
- The types involved
okhttp3.CompressionInterceptor→okhttp3.Interceptor.Chainokhttp3.Interceptor→okhttp3.Interceptor.Chainokhttp3.UppercaseRequestInterceptor→okhttp3.Interceptor.Chainokhttp3.UppercaseResponseInterceptor→okhttp3.Interceptor.Chain
- Direction
- okhttp3 uses okhttp3.Interceptor, so a change to okhttp3.Interceptor can break okhttp3, while a change to okhttp3 can't break okhttp3.Interceptor.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→14 okhttp3 uses okhttp3.internal.tls✕
- Connections
- 2 pairs of types, where a type in okhttp3 uses a type in okhttp3.internal.tls.
- The types involved
okhttp3.CertificatePinner→okhttp3.internal.tls.CertificateChainCleanerokhttp3.OkHttpClient→okhttp3.internal.tls.CertificateChainCleaner
- Direction
- okhttp3 uses okhttp3.internal.tls, so a change to okhttp3.internal.tls can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.tls.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→16 okhttp3 uses okhttp3.FakeDns✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.FakeDns.
- The types involved
okhttp3.FakeDns→okhttp3.FakeDns.Request
- Direction
- okhttp3 uses okhttp3.FakeDns, so a change to okhttp3.FakeDns can break okhttp3, while a change to okhttp3 can't break okhttp3.FakeDns.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→17 okhttp3 uses okhttp3.Response✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.Response.
- The types involved
okhttp3.Response→okhttp3.Response.Builder
- Direction
- okhttp3 uses okhttp3.Response, so a change to okhttp3.Response can break okhttp3, while a change to okhttp3 can't break okhttp3.Response.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→18 okhttp3 uses okhttp3.internal.cache✕
- Connections
- 3 pairs of types, where a type in okhttp3 uses a type in okhttp3.internal.cache.
- The types involved
okhttp3.Cache→okhttp3.internal.cache.CacheRequestokhttp3.Cache→okhttp3.internal.cache.CacheStrategyokhttp3.Cache→okhttp3.internal.cache.DiskLruCache
- Direction
- okhttp3 uses okhttp3.internal.cache, so a change to okhttp3.internal.cache can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.cache.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→19 okhttp3 uses okhttp3.internal.dns✕
- Connections
- 4 pairs of types, where a type in okhttp3 uses a type in okhttp3.internal.dns.
- The types involved
okhttp3.DnsCache→okhttp3.internal.dns.RealDnsCacheokhttp3.FakeDns→okhttp3.internal.dns.DnsMessageokhttp3.FakeDns→okhttp3.internal.dns.Questionokhttp3.FakeDns→okhttp3.internal.dns.ResourceRecord
- Direction
- okhttp3 uses okhttp3.internal.dns, so a change to okhttp3.internal.dns can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.dns.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→22 okhttp3 uses okhttp3.internal.http✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.internal.http.
- The types involved
okhttp3.TestValueFactory→okhttp3.internal.http.RealInterceptorChain
- Direction
- okhttp3 uses okhttp3.internal.http, so a change to okhttp3.internal.http can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.http.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→24 okhttp3 uses okhttp3.internal.http2✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.internal.http2.
- The types involved
okhttp3.TestUtil→okhttp3.internal.http2.Header
- Direction
- okhttp3 uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.http2.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→25 okhttp3 uses okhttp3.sockets✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.sockets.
- The types involved
okhttp3.SpecificHostSocketFactory→okhttp3.sockets.DelegatingSocketFactory
- Direction
- okhttp3 uses okhttp3.sockets, so a change to okhttp3.sockets can break okhttp3, while a change to okhttp3 can't break okhttp3.sockets.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→26 okhttp3 uses okhttp3.internal✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.internal.
- The types involved
okhttp3.Request→okhttp3.internal.Tags
- Direction
- okhttp3 uses okhttp3.internal, so a change to okhttp3.internal can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→27 okhttp3 uses okhttp3.Request✕
- Connections
- 1 pair of types, where a type in okhttp3 uses a type in okhttp3.Request.
- The types involved
okhttp3.Request→okhttp3.Request.Builder
- Direction
- okhttp3 uses okhttp3.Request, so a change to okhttp3.Request can break okhttp3, while a change to okhttp3 can't break okhttp3.Request.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→28 okhttp3 uses okhttp3.internal.connection✕
- Connections
- 10 pairs of types, where a type in okhttp3 uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.ConnectionPool→okhttp3.internal.connection.ConnectionListenerokhttp3.ConnectionPool→okhttp3.internal.connection.RealConnectionPoolokhttp3.Dispatcher→okhttp3.internal.connection.RealCallokhttp3.OkHttpClient→okhttp3.internal.connection.RouteDatabaseokhttp3.RecordingConnectionListener→okhttp3.internal.connection.ConnectionListenerokhttp3.Response→okhttp3.internal.connection.Exchangeokhttp3.TestValueFactory→okhttp3.internal.connection.RealCallokhttp3.TestValueFactory→okhttp3.internal.connection.RealConnectionokhttp3.TestValueFactory→okhttp3.internal.connection.RealConnectionPoolokhttp3.TestValueFactory→okhttp3.internal.connection.RealRoutePlanner
- Direction
- okhttp3 uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3, while a change to okhttp3 can't break okhttp3.internal.connection.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→29 okhttp3 uses okhttp3.OkHttpClient✕
- Connections
- 2 pairs of types, where a type in okhttp3 uses a type in okhttp3.OkHttpClient.
- The types involved
okhttp3.OkHttpClient→okhttp3.OkHttpClient.Builderokhttp3.OkHttpClientTestRule→okhttp3.OkHttpClient.Builder
- Direction
- okhttp3 uses okhttp3.OkHttpClient, so a change to okhttp3.OkHttpClient can break okhttp3, while a change to okhttp3 can't break okhttp3.OkHttpClient.
- Position
- Below the diagonal: okhttp3 uses a module listed above it, which is the healthy direction.
30→38 okhttp3 uses mockwebserver3 part of a loop✕
- Connections
- 2 pairs of types, where a type in okhttp3 uses a type in mockwebserver3.
- The types involved
okhttp3.FakeDns→mockwebserver3.Dispatcherokhttp3.FakeDns→mockwebserver3.MockResponse
- Direction
- okhttp3 uses mockwebserver3, so a change to mockwebserver3 can break okhttp3, while a change to okhttp3 can't break mockwebserver3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→8 mockwebserver3.MockResponse uses okhttp3.Headers✕
- Connections
- 1 pair of types, where a type in mockwebserver3.MockResponse uses a type in okhttp3.Headers.
- The types involved
mockwebserver3.MockResponse.Builder→okhttp3.Headers.Builder
- Direction
- mockwebserver3.MockResponse uses okhttp3.Headers, so a change to okhttp3.Headers can break mockwebserver3.MockResponse, while a change to mockwebserver3.MockResponse can't break okhttp3.Headers.
- Position
- Below the diagonal: mockwebserver3.MockResponse uses a module listed above it, which is the healthy direction.
31→24 mockwebserver3.MockResponse uses okhttp3.internal.http2✕
- Connections
- 1 pair of types, where a type in mockwebserver3.MockResponse uses a type in okhttp3.internal.http2.
- The types involved
mockwebserver3.MockResponse.Builder→okhttp3.internal.http2.Settings
- Direction
- mockwebserver3.MockResponse uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break mockwebserver3.MockResponse, while a change to mockwebserver3.MockResponse can't break okhttp3.internal.http2.
- Position
- Below the diagonal: mockwebserver3.MockResponse uses a module listed above it, which is the healthy direction.
31→30 mockwebserver3.MockResponse uses okhttp3✕
- Connections
- 2 pairs of types, where a type in mockwebserver3.MockResponse uses a type in okhttp3.
- The types involved
mockwebserver3.MockResponse.Builder→okhttp3.Headersmockwebserver3.MockResponse.Builder→okhttp3.WebSocketListener
- Direction
- mockwebserver3.MockResponse uses okhttp3, so a change to okhttp3 can break mockwebserver3.MockResponse, while a change to mockwebserver3.MockResponse can't break okhttp3.
- Position
- Below the diagonal: mockwebserver3.MockResponse uses a module listed above it, which is the healthy direction.
31→38 mockwebserver3.MockResponse uses mockwebserver3 part of a loop✕
- Connections
- 5 pairs of types, where a type in mockwebserver3.MockResponse uses a type in mockwebserver3.
- The types involved
mockwebserver3.MockResponse.Builder→mockwebserver3.MockResponsemockwebserver3.MockResponse.Builder→mockwebserver3.MockResponseBodymockwebserver3.MockResponse.Builder→mockwebserver3.PushPromisemockwebserver3.MockResponse.Builder→mockwebserver3.SocketEffectmockwebserver3.MockResponse.Builder→mockwebserver3.SocketHandler
- Direction
- mockwebserver3.MockResponse uses mockwebserver3, so a change to mockwebserver3 can break mockwebserver3.MockResponse, while a change to mockwebserver3.MockResponse can't break mockwebserver3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→28 mockwebserver3.internal uses okhttp3.internal.connection✕
- Connections
- 1 pair of types, where a type in mockwebserver3.internal uses a type in okhttp3.internal.connection.
- The types involved
mockwebserver3.internal.MockWebServerSocket→okhttp3.internal.connection.BufferedSocket
- Direction
- mockwebserver3.internal uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break mockwebserver3.internal, while a change to mockwebserver3.internal can't break okhttp3.internal.connection.
- Position
- Below the diagonal: mockwebserver3.internal uses a module listed above it, which is the healthy direction.
32→30 mockwebserver3.internal uses okhttp3✕
- Connections
- 3 pairs of types, where a type in mockwebserver3.internal uses a type in okhttp3.
- The types involved
mockwebserver3.internal.MockWebServerSocket→okhttp3.Handshakemockwebserver3.internal.RecordedRequestFactoryKt→okhttp3.Headersmockwebserver3.internal.RecordedRequestFactoryKt→okhttp3.HttpUrl
- Direction
- mockwebserver3.internal uses okhttp3, so a change to okhttp3 can break mockwebserver3.internal, while a change to mockwebserver3.internal can't break okhttp3.
- Position
- Below the diagonal: mockwebserver3.internal uses a module listed above it, which is the healthy direction.
32→38 mockwebserver3.internal uses mockwebserver3 part of a loop✕
- Connections
- 3 pairs of types, where a type in mockwebserver3.internal uses a type in mockwebserver3.
- The types involved
mockwebserver3.internal.BufferMockResponseBody→mockwebserver3.MockResponseBodymockwebserver3.internal.BufferMockResponseBodyKt→mockwebserver3.MockResponseBodymockwebserver3.internal.RecordedRequestFactoryKt→mockwebserver3.RecordedRequest
- Direction
- mockwebserver3.internal uses mockwebserver3, so a change to mockwebserver3 can break mockwebserver3.internal, while a change to mockwebserver3.internal can't break mockwebserver3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 okhttp3.android uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.android uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.android.AndroidDns→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.android uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.android, while a change to okhttp3.android can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.android uses a module listed above it, which is the healthy direction.
33→6 okhttp3.android uses okhttp3.Dns✕
- Connections
- 2 pairs of types, where a type in okhttp3.android uses a type in okhttp3.Dns.
- The types involved
okhttp3.android.AndroidDns→okhttp3.Dns.Callokhttp3.android.AndroidDns→okhttp3.Dns.Request
- Direction
- okhttp3.android uses okhttp3.Dns, so a change to okhttp3.Dns can break okhttp3.android, while a change to okhttp3.android can't break okhttp3.Dns.
- Position
- Below the diagonal: okhttp3.android uses a module listed above it, which is the healthy direction.
33→10 okhttp3.android uses okhttp3.internal.dns.DnsQuery✕
- Connections
- 1 pair of types, where a type in okhttp3.android uses a type in okhttp3.internal.dns.DnsQuery.
- The types involved
okhttp3.android.AndroidDns→okhttp3.internal.dns.DnsQuery.Factory
- Direction
- okhttp3.android uses okhttp3.internal.dns.DnsQuery, so a change to okhttp3.internal.dns.DnsQuery can break okhttp3.android, while a change to okhttp3.android can't break okhttp3.internal.dns.DnsQuery.
- Position
- Below the diagonal: okhttp3.android uses a module listed above it, which is the healthy direction.
33→19 okhttp3.android uses okhttp3.internal.dns✕
- Connections
- 1 pair of types, where a type in okhttp3.android uses a type in okhttp3.internal.dns.
- The types involved
okhttp3.android.AndroidDns→okhttp3.internal.dns.StateMachineDnsCall
- Direction
- okhttp3.android uses okhttp3.internal.dns, so a change to okhttp3.internal.dns can break okhttp3.android, while a change to okhttp3.android can't break okhttp3.internal.dns.
- Position
- Below the diagonal: okhttp3.android uses a module listed above it, which is the healthy direction.
33→30 okhttp3.android uses okhttp3✕
- Connections
- 2 pairs of types, where a type in okhttp3.android uses a type in okhttp3.
- The types involved
okhttp3.android.AndroidDns→okhttp3.Dnsokhttp3.android.AndroidDns→okhttp3.DnsCache
- Direction
- okhttp3.android uses okhttp3, so a change to okhttp3 can break okhttp3.android, while a change to okhttp3.android can't break okhttp3.
- Position
- Below the diagonal: okhttp3.android uses a module listed above it, which is the healthy direction.
34→1 okhttp3.dnsoverhttps uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in okhttp3.dnsoverhttps uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.dnsoverhttps.DnsOverHttps→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.dnsoverhttps uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.dnsoverhttps, while a change to okhttp3.dnsoverhttps can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.dnsoverhttps uses a module listed above it, which is the healthy direction.
34→6 okhttp3.dnsoverhttps uses okhttp3.Dns✕
- Connections
- 2 pairs of types, where a type in okhttp3.dnsoverhttps uses a type in okhttp3.Dns.
- The types involved
okhttp3.dnsoverhttps.DnsOverHttps→okhttp3.Dns.Callokhttp3.dnsoverhttps.DnsOverHttps→okhttp3.Dns.Request
- Direction
- okhttp3.dnsoverhttps uses okhttp3.Dns, so a change to okhttp3.Dns can break okhttp3.dnsoverhttps, while a change to okhttp3.dnsoverhttps can't break okhttp3.Dns.
- Position
- Below the diagonal: okhttp3.dnsoverhttps uses a module listed above it, which is the healthy direction.
34→10 okhttp3.dnsoverhttps uses okhttp3.internal.dns.DnsQuery✕
- Connections
- 1 pair of types, where a type in okhttp3.dnsoverhttps uses a type in okhttp3.internal.dns.DnsQuery.
- The types involved
okhttp3.dnsoverhttps.DnsOverHttps→okhttp3.internal.dns.DnsQuery.Factory
- Direction
- okhttp3.dnsoverhttps uses okhttp3.internal.dns.DnsQuery, so a change to okhttp3.internal.dns.DnsQuery can break okhttp3.dnsoverhttps, while a change to okhttp3.dnsoverhttps can't break okhttp3.internal.dns.DnsQuery.
- Position
- Below the diagonal: okhttp3.dnsoverhttps uses a module listed above it, which is the healthy direction.
34→30 okhttp3.dnsoverhttps uses okhttp3✕
- Connections
- 5 pairs of types, where a type in okhttp3.dnsoverhttps uses a type in okhttp3.
- The types involved
okhttp3.dnsoverhttps.BootstrapDns→okhttp3.Dnsokhttp3.dnsoverhttps.DnsOverHttps→okhttp3.Dnsokhttp3.dnsoverhttps.DnsOverHttps→okhttp3.DnsCacheokhttp3.dnsoverhttps.DnsOverHttps→okhttp3.HttpUrlokhttp3.dnsoverhttps.DnsOverHttps→okhttp3.OkHttpClient
- Direction
- okhttp3.dnsoverhttps uses okhttp3, so a change to okhttp3 can break okhttp3.dnsoverhttps, while a change to okhttp3.dnsoverhttps can't break okhttp3.
- Position
- Below the diagonal: okhttp3.dnsoverhttps uses a module listed above it, which is the healthy direction.
35→11 okhttp3.internal.http1 uses okhttp3.internal.http.ExchangeCodec✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http1 uses a type in okhttp3.internal.http.ExchangeCodec.
- The types involved
okhttp3.internal.http1.Http1ExchangeCodec→okhttp3.internal.http.ExchangeCodec.Carrier
- Direction
- okhttp3.internal.http1 uses okhttp3.internal.http.ExchangeCodec, so a change to okhttp3.internal.http.ExchangeCodec can break okhttp3.internal.http1, while a change to okhttp3.internal.http1 can't break okhttp3.internal.http.ExchangeCodec.
- Position
- Below the diagonal: okhttp3.internal.http1 uses a module listed above it, which is the healthy direction.
35→17 okhttp3.internal.http1 uses okhttp3.Response✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http1 uses a type in okhttp3.Response.
- The types involved
okhttp3.internal.http1.Http1ExchangeCodec→okhttp3.Response.Builder
- Direction
- okhttp3.internal.http1 uses okhttp3.Response, so a change to okhttp3.Response can break okhttp3.internal.http1, while a change to okhttp3.internal.http1 can't break okhttp3.Response.
- Position
- Below the diagonal: okhttp3.internal.http1 uses a module listed above it, which is the healthy direction.
35→22 okhttp3.internal.http1 uses okhttp3.internal.http✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http1 uses a type in okhttp3.internal.http.
- The types involved
okhttp3.internal.http1.Http1ExchangeCodec→okhttp3.internal.http.ExchangeCodec
- Direction
- okhttp3.internal.http1 uses okhttp3.internal.http, so a change to okhttp3.internal.http can break okhttp3.internal.http1, while a change to okhttp3.internal.http1 can't break okhttp3.internal.http.
- Position
- Below the diagonal: okhttp3.internal.http1 uses a module listed above it, which is the healthy direction.
35→28 okhttp3.internal.http1 uses okhttp3.internal.connection✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.http1 uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.http1.Http1ExchangeCodec→okhttp3.internal.connection.BufferedSocket
- Direction
- okhttp3.internal.http1 uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.http1, while a change to okhttp3.internal.http1 can't break okhttp3.internal.connection.
- Position
- Below the diagonal: okhttp3.internal.http1 uses a module listed above it, which is the healthy direction.
35→30 okhttp3.internal.http1 uses okhttp3✕
- Connections
- 6 pairs of types, where a type in okhttp3.internal.http1 uses a type in okhttp3.
- The types involved
okhttp3.internal.http1.HeadersReader→okhttp3.Headersokhttp3.internal.http1.Http1ExchangeCodec→okhttp3.Headersokhttp3.internal.http1.Http1ExchangeCodec→okhttp3.HttpUrlokhttp3.internal.http1.Http1ExchangeCodec→okhttp3.OkHttpClientokhttp3.internal.http1.Http1ExchangeCodec→okhttp3.Requestokhttp3.internal.http1.Http1ExchangeCodec→okhttp3.Response
- Direction
- okhttp3.internal.http1 uses okhttp3, so a change to okhttp3 can break okhttp3.internal.http1, while a change to okhttp3.internal.http1 can't break okhttp3.
- Position
- Below the diagonal: okhttp3.internal.http1 uses a module listed above it, which is the healthy direction.
36→1 okhttp3.internal.ws uses okhttp3.internal.concurrent✕
- Connections
- 4 pairs of types, where a type in okhttp3.internal.ws uses a type in okhttp3.internal.concurrent.
- The types involved
okhttp3.internal.ws.RealWebSocket→okhttp3.internal.concurrent.Lockableokhttp3.internal.ws.RealWebSocket→okhttp3.internal.concurrent.Taskokhttp3.internal.ws.RealWebSocket→okhttp3.internal.concurrent.TaskQueueokhttp3.internal.ws.RealWebSocket→okhttp3.internal.concurrent.TaskRunner
- Direction
- okhttp3.internal.ws uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break okhttp3.internal.ws, while a change to okhttp3.internal.ws can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: okhttp3.internal.ws uses a module listed above it, which is the healthy direction.
36→28 okhttp3.internal.ws uses okhttp3.internal.connection✕
- Connections
- 1 pair of types, where a type in okhttp3.internal.ws uses a type in okhttp3.internal.connection.
- The types involved
okhttp3.internal.ws.RealWebSocket→okhttp3.internal.connection.BufferedSocket
- Direction
- okhttp3.internal.ws uses okhttp3.internal.connection, so a change to okhttp3.internal.connection can break okhttp3.internal.ws, while a change to okhttp3.internal.ws can't break okhttp3.internal.connection.
- Position
- Below the diagonal: okhttp3.internal.ws uses a module listed above it, which is the healthy direction.
36→30 okhttp3.internal.ws uses okhttp3✕
- Connections
- 6 pairs of types, where a type in okhttp3.internal.ws uses a type in okhttp3.
- The types involved
okhttp3.internal.ws.RealWebSocket→okhttp3.Callokhttp3.internal.ws.RealWebSocket→okhttp3.OkHttpClientokhttp3.internal.ws.RealWebSocket→okhttp3.Requestokhttp3.internal.ws.RealWebSocket→okhttp3.Responseokhttp3.internal.ws.RealWebSocket→okhttp3.WebSocketokhttp3.internal.ws.RealWebSocket→okhttp3.WebSocketListener
- Direction
- okhttp3.internal.ws uses okhttp3, so a change to okhttp3 can break okhttp3.internal.ws, while a change to okhttp3.internal.ws can't break okhttp3.
- Position
- Below the diagonal: okhttp3.internal.ws uses a module listed above it, which is the healthy direction.
37→5 okhttp3.sse uses okhttp3.Call✕
- Connections
- 1 pair of types, where a type in okhttp3.sse uses a type in okhttp3.Call.
- The types involved
okhttp3.sse.EventSources→okhttp3.Call.Factory
- Direction
- okhttp3.sse uses okhttp3.Call, so a change to okhttp3.Call can break okhttp3.sse, while a change to okhttp3.sse can't break okhttp3.Call.
- Position
- Below the diagonal: okhttp3.sse uses a module listed above it, which is the healthy direction.
37→30 okhttp3.sse uses okhttp3✕
- Connections
- 4 pairs of types, where a type in okhttp3.sse uses a type in okhttp3.
- The types involved
okhttp3.sse.EventSource→okhttp3.Requestokhttp3.sse.EventSourceListener→okhttp3.Responseokhttp3.sse.EventSources→okhttp3.OkHttpClientokhttp3.sse.EventSources→okhttp3.Response
- Direction
- okhttp3.sse uses okhttp3, so a change to okhttp3 can break okhttp3.sse, while a change to okhttp3.sse can't break okhttp3.
- Position
- Below the diagonal: okhttp3.sse uses a module listed above it, which is the healthy direction.
38→1 mockwebserver3 uses okhttp3.internal.concurrent✕
- Connections
- 1 pair of types, where a type in mockwebserver3 uses a type in okhttp3.internal.concurrent.
- The types involved
mockwebserver3.MockWebServer→okhttp3.internal.concurrent.TaskRunner
- Direction
- mockwebserver3 uses okhttp3.internal.concurrent, so a change to okhttp3.internal.concurrent can break mockwebserver3, while a change to mockwebserver3 can't break okhttp3.internal.concurrent.
- Position
- Below the diagonal: mockwebserver3 uses a module listed above it, which is the healthy direction.
38→24 mockwebserver3 uses okhttp3.internal.http2✕
- Connections
- 3 pairs of types, where a type in mockwebserver3 uses a type in okhttp3.internal.http2.
- The types involved
mockwebserver3.MockResponse→okhttp3.internal.http2.Settingsmockwebserver3.MockWebServer→okhttp3.internal.http2.Http2Connectionmockwebserver3.MockWebServer→okhttp3.internal.http2.Http2Stream
- Direction
- mockwebserver3 uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break mockwebserver3, while a change to mockwebserver3 can't break okhttp3.internal.http2.
- Position
- Below the diagonal: mockwebserver3 uses a module listed above it, which is the healthy direction.
38→30 mockwebserver3 uses okhttp3✕
- Connections
- 9 pairs of types, where a type in mockwebserver3 uses a type in okhttp3.
- The types involved
mockwebserver3.MockResponse→okhttp3.Headersmockwebserver3.MockResponse→okhttp3.WebSocketListenermockwebserver3.MockWebServer→okhttp3.Headersmockwebserver3.MockWebServer→okhttp3.HttpUrlmockwebserver3.MockWebServer→okhttp3.Protocolmockwebserver3.PushPromise→okhttp3.Headersmockwebserver3.RecordedRequest→okhttp3.Handshakemockwebserver3.RecordedRequest→okhttp3.Headersmockwebserver3.RecordedRequest→okhttp3.HttpUrl
- Direction
- mockwebserver3 uses okhttp3, so a change to okhttp3 can break mockwebserver3, while a change to mockwebserver3 can't break okhttp3.
- Position
- Below the diagonal: mockwebserver3 uses a module listed above it, which is the healthy direction.
38→31 mockwebserver3 uses mockwebserver3.MockResponse✕
- Connections
- 1 pair of types, where a type in mockwebserver3 uses a type in mockwebserver3.MockResponse.
- The types involved
mockwebserver3.MockResponse→mockwebserver3.MockResponse.Builder
- Direction
- mockwebserver3 uses mockwebserver3.MockResponse, so a change to mockwebserver3.MockResponse can break mockwebserver3, while a change to mockwebserver3 can't break mockwebserver3.MockResponse.
- Position
- Below the diagonal: mockwebserver3 uses a module listed above it, which is the healthy direction.
38→32 mockwebserver3 uses mockwebserver3.internal✕
- Connections
- 2 pairs of types, where a type in mockwebserver3 uses a type in mockwebserver3.internal.
- The types involved
mockwebserver3.MockWebServer→mockwebserver3.internal.MockWebServerSocketmockwebserver3.MockWebServer→mockwebserver3.internal.RequestLine
- Direction
- mockwebserver3 uses mockwebserver3.internal, so a change to mockwebserver3.internal can break mockwebserver3, while a change to mockwebserver3 can't break mockwebserver3.internal.
- Position
- Below the diagonal: mockwebserver3 uses a module listed above it, which is the healthy direction.
39→12 mockwebserver3.MockWebServer uses okhttp3.internal.http2.Http2Connection✕
- Connections
- 1 pair of types, where a type in mockwebserver3.MockWebServer uses a type in okhttp3.internal.http2.Http2Connection.
- The types involved
mockwebserver3.MockWebServer.Http2SocketHandler→okhttp3.internal.http2.Http2Connection.Listener
- Direction
- mockwebserver3.MockWebServer uses okhttp3.internal.http2.Http2Connection, so a change to okhttp3.internal.http2.Http2Connection can break mockwebserver3.MockWebServer, while a change to mockwebserver3.MockWebServer can't break okhttp3.internal.http2.Http2Connection.
- Position
- Below the diagonal: mockwebserver3.MockWebServer uses a module listed above it, which is the healthy direction.
39→24 mockwebserver3.MockWebServer uses okhttp3.internal.http2✕
- Connections
- 2 pairs of types, where a type in mockwebserver3.MockWebServer uses a type in okhttp3.internal.http2.
- The types involved
mockwebserver3.MockWebServer.Http2SocketHandler→okhttp3.internal.http2.Headermockwebserver3.MockWebServer.Http2SocketHandler→okhttp3.internal.http2.Http2Stream
- Direction
- mockwebserver3.MockWebServer uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break mockwebserver3.MockWebServer, while a change to mockwebserver3.MockWebServer can't break okhttp3.internal.http2.
- Position
- Below the diagonal: mockwebserver3.MockWebServer uses a module listed above it, which is the healthy direction.
39→30 mockwebserver3.MockWebServer uses okhttp3✕
- Connections
- 1 pair of types, where a type in mockwebserver3.MockWebServer uses a type in okhttp3.
- The types involved
mockwebserver3.MockWebServer.Http2SocketHandler→okhttp3.Protocol
- Direction
- mockwebserver3.MockWebServer uses okhttp3, so a change to okhttp3 can break mockwebserver3.MockWebServer, while a change to mockwebserver3.MockWebServer can't break okhttp3.
- Position
- Below the diagonal: mockwebserver3.MockWebServer uses a module listed above it, which is the healthy direction.
39→32 mockwebserver3.MockWebServer uses mockwebserver3.internal✕
- Connections
- 2 pairs of types, where a type in mockwebserver3.MockWebServer uses a type in mockwebserver3.internal.
- The types involved
mockwebserver3.MockWebServer.Http2SocketHandler→mockwebserver3.internal.MockWebServerSocketmockwebserver3.MockWebServer.SocketHandler→mockwebserver3.internal.MockWebServerSocket
- Direction
- mockwebserver3.MockWebServer uses mockwebserver3.internal, so a change to mockwebserver3.internal can break mockwebserver3.MockWebServer, while a change to mockwebserver3.MockWebServer can't break mockwebserver3.internal.
- Position
- Below the diagonal: mockwebserver3.MockWebServer uses a module listed above it, which is the healthy direction.
39→38 mockwebserver3.MockWebServer uses mockwebserver3✕
- Connections
- 4 pairs of types, where a type in mockwebserver3.MockWebServer uses a type in mockwebserver3.
- The types involved
mockwebserver3.MockWebServer.Http2SocketHandler→mockwebserver3.MockResponsemockwebserver3.MockWebServer.Http2SocketHandler→mockwebserver3.PushPromisemockwebserver3.MockWebServer.Http2SocketHandler→mockwebserver3.RecordedRequestmockwebserver3.MockWebServer.SocketHandler→mockwebserver3.MockResponse
- Direction
- mockwebserver3.MockWebServer uses mockwebserver3, so a change to mockwebserver3 can break mockwebserver3.MockWebServer, while a change to mockwebserver3.MockWebServer can't break mockwebserver3.
- Position
- Below the diagonal: mockwebserver3.MockWebServer uses a module listed above it, which is the healthy direction.
40→8 okhttp3.mockwebserver uses okhttp3.Headers✕
- Connections
- 1 pair of types, where a type in okhttp3.mockwebserver uses a type in okhttp3.Headers.
- The types involved
okhttp3.mockwebserver.MockResponse→okhttp3.Headers.Builder
- Direction
- okhttp3.mockwebserver uses okhttp3.Headers, so a change to okhttp3.Headers can break okhttp3.mockwebserver, while a change to okhttp3.mockwebserver can't break okhttp3.Headers.
- Position
- Below the diagonal: okhttp3.mockwebserver uses a module listed above it, which is the healthy direction.
40→24 okhttp3.mockwebserver uses okhttp3.internal.http2✕
- Connections
- 1 pair of types, where a type in okhttp3.mockwebserver uses a type in okhttp3.internal.http2.
- The types involved
okhttp3.mockwebserver.MockResponse→okhttp3.internal.http2.Settings
- Direction
- okhttp3.mockwebserver uses okhttp3.internal.http2, so a change to okhttp3.internal.http2 can break okhttp3.mockwebserver, while a change to okhttp3.mockwebserver can't break okhttp3.internal.http2.
- Position
- Below the diagonal: okhttp3.mockwebserver uses a module listed above it, which is the healthy direction.
40→30 okhttp3.mockwebserver uses okhttp3✕
- Connections
- 9 pairs of types, where a type in okhttp3.mockwebserver uses a type in okhttp3.
- The types involved
okhttp3.mockwebserver.MockResponse→okhttp3.Headersokhttp3.mockwebserver.MockResponse→okhttp3.WebSocketListenerokhttp3.mockwebserver.MockWebServer→okhttp3.HttpUrlokhttp3.mockwebserver.MockWebServer→okhttp3.Protocolokhttp3.mockwebserver.PushPromise→okhttp3.Headersokhttp3.mockwebserver.RecordedRequest→okhttp3.Handshakeokhttp3.mockwebserver.RecordedRequest→okhttp3.Headersokhttp3.mockwebserver.RecordedRequest→okhttp3.HttpUrlokhttp3.mockwebserver.RecordedRequest→okhttp3.TlsVersion
- Direction
- okhttp3.mockwebserver uses okhttp3, so a change to okhttp3 can break okhttp3.mockwebserver, while a change to okhttp3.mockwebserver can't break okhttp3.
- Position
- Below the diagonal: okhttp3.mockwebserver uses a module listed above it, which is the healthy direction.
40→38 okhttp3.mockwebserver uses mockwebserver3✕
- Connections
- 5 pairs of types, where a type in okhttp3.mockwebserver uses a type in mockwebserver3.
- The types involved
okhttp3.mockwebserver.DeprecationBridgeKt→mockwebserver3.Dispatcherokhttp3.mockwebserver.DeprecationBridgeKt→mockwebserver3.MockResponseokhttp3.mockwebserver.DeprecationBridgeKt→mockwebserver3.PushPromiseokhttp3.mockwebserver.MockWebServer→mockwebserver3.MockWebServerokhttp3.mockwebserver.QueueDispatcher→mockwebserver3.QueueDispatcher
- Direction
- okhttp3.mockwebserver uses mockwebserver3, so a change to mockwebserver3 can break okhttp3.mockwebserver, while a change to okhttp3.mockwebserver can't break mockwebserver3.
- Position
- Below the diagonal: okhttp3.mockwebserver uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 30 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. | +11.8 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +8.0 pts | Low | ADR Quality |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.3 pts | Low | License Compliance |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.5 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +7.0 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.1 pts | Medium | Deployment & Rollback |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.1 pts | Medium | Observability |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.9 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Reader.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Stream.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt | 6.4 | Mixed | Explicit Debt: TodoComment |
| okhttp-tls/src/main/kotlin/okhttp3/tls/internal/der/DerReader.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/RealWebSocket.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/platform/Platform.kt | 7.0 | Mixed | Code Duplication: Edited copies of one member (4 members, 12+ corresponding lines) |
| mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt | 7.0 | Mixed | Cyclomatic Complexity: MockWebServer.readRequest (cyclomatic 18) |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt | 7.1 | Mixed | Cyclomatic Complexity: Builder.parse (cyclomatic 26) |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt | 7.1 | Mixed | Cyclomatic Complexity: Punycode.decodeLabel (cyclomatic 22) |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt | 7.1 | Mixed | Cyclomatic Complexity: Writer.writeHeaders (cyclomatic 17) |
| okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt | 7.1 | Mixed | God Classes: TooManyMethods: Builder |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| samples/slack/src/main/java/okhttp3/slack/RtmSession.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| okhttp/src/jvmTest/kotlin/okhttp3/JSSETest.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 53 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 254 of 277 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 38 Maven/Gradle manifest(s) were read, stating a version for 81 dependency(ies) and leaving 9 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `build-logic/src/main/kotlin/AlpnVersions.kt`, `build-logic/src/main/kotlin/BndBuildAction.kt`, `build-logic/src/main/kotlin/okhttp.quality-conventions.gradle.kts`, `okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/HttpLoggingInterceptor.kt`, `okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/LoggingEventListener.kt`, … (+24 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (regression-test/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
27 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HttpLoggingInterceptor.intercept at 35. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being CacheStrategy.isCacheable at 17 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with HttpLoggingInterceptor.intercept (cyclomatic 35). — Refactoring it lifts Cyclomatic Complexity from 7.1 to about 7.3/10.
D2 · Cognitive Complexity
50 method(s) exceeded the cognitive complexity threshold of 15; the worst was WebSocketExtensions.parse at 77.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with WebSocketExtensions.parse (cognitive 77), HttpLoggingInterceptor.intercept (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
31 god class(es) detected.
What to do
- Resolve the 16 TooManyMethods finding(s) in God Classes — start with OkHttpClient.kt (2), HttpUrl.kt (2), MockResponse.kt (2). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with MockWebServer.kt, OkHttpClient.kt, DiskLruCache.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with HttpUrl.kt, MockWebServer.kt, OkHttpClient.kt. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. A further 24 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 18 of the 39 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Edited copy of a member (25 corresponding lines) finding(s) in Code Duplication — start with MockResponse.kt, OkHttpClient.kt, Hpack.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with StartStopExtension.kt, IdnaMappingTable.kt, ConnectPlan.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with Certificates.kt, PostFile.java. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
26 production modules (Gradle+Maven), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 7 module(s) off the main sequence, with abstractness counted on 20 of the 26 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
1 of 124 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Platform.kt. — One of this dimension's main actionable groups (1 warning-level).
D13 · REDACTED Scanning
2 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D14 · License Compliance
1 of 69 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 38 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 9 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 11 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: okhttp-dnsoverhttps/src/main/kotlin/okhttp3/dnsoverhttps/internal/-DnsOverHttpsQuery.kt (3 of 4 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with -DnsOverHttpsQuery.kt. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
27 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealConnection.kt. Counted over 181 of the 361 production source files in this repository: 173 are under the ~2,400-byte size floor this dimension measures over, and the remaining 7 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
50 deducted task-comment markers across 54727 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 50 TodoComment finding(s) in Explicit Debt — start with HttpUrlTest.kt (7), Http2Connection.kt (6), -HostnamesCommon.kt (4). — One of this dimension's main actionable groups (50 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 34 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 18 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
66 % of calls cross a namespace and 11 % go through an interface, but 55 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 5 file(s) — `gradlew` (line 74, line 178), `maven-tests/mvnw` (line 86, line 121, line 131, …), `okhttp/src/androidMain/kotlin/okhttp3/internal/platform/Android10Platform.kt` (line 110), `okhttp/src/jvmTest/kotlin/okhttp3/URLConnectionTest.kt` (line 1683, line 1689), `okhttp/src/jvmTest/kotlin/okhttp3/internal/tls/HostnameVerifierTest.kt` (line 878) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
28 finding(s): 0 critical, 21 high, 5 medium, 2 low.
What to do
- Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
8 of 188 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is okhttp/src/commonJvmAndroid/kotlin/okhttp3/CacheControl.kt. Counted over 188 of the 361 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: CallEvent.kt↔ClientRuleEventListener.kt 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with CallEvent.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 11 platform declaration(s) and 82 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
- The projects :mockwebserver3-junit4 → :okhttp → :mockwebserver3-junit4 (one cycle inside a mutually-dependent group of 4 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX8 · Test isolation
- `:okhttp` (production) references the test project `:mockwebserver3-junit4`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 7/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `module-tests`, `okhttp-idna-mapping-table`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/build.yml:7
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — okhttp/src/commonJvmAndroid/kotlin/okhttp3/Challenge.kt:54, okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilCommon.kt:287, okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilJvm.kt:297, …
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/tls/BasicTrustRootIndex.kt:43
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — build-logic/src/main/kotlin/BndBuildAction.kt:184
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Strong | Solid. |
| Architecture | 85% | Strong | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Weak — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 6% of this repository's production lines — kotlin (51,344 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~75812 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 38 Maven/Gradle manifest(s) were read, stating a version for 81 dependency(ies) and leaving 9 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Java, Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 29 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 94 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 34 current-state document(s) make no claim of a kind M4 checks. 13 claim(s) of kinds M4 does not check were not checked (path 1, environment variable 12); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 30 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle
- Production project references a test project: :okhttp → :mockwebserver3-junit4
- Banned license: org.graalvm.nativeimage:svm
- REDACTED
- REDACTED
- Circular dependency
Serious — 218 finding(s)
- TodoComment samples/slack/src/main/java/okhttp3/slack/RtmSession.java:42
- TodoComment samples/slack/src/main/java/okhttp3/slack/RtmSession.java:59
- TodoComment regression-test/src/androidTest/java/okhttp/regression/compare/ApacheHttpClientTest.kt:47
- TodoComment okhttp-tls/src/main/kotlin/okhttp3/tls/internal/der/DerReader.kt:308
- TodoComment okhttp-testing-support/src/main/kotlin/okhttp3/internal/concurrent/TaskFaker.kt:372
- TodoComment okhttp-dnsoverhttps/src/test/java/okhttp3/dnsoverhttps/DnsOverHttpsTest.kt:328
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/CallHandshakeTest.kt:159
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:74
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:426
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:453
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:876
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:895
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:906
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt:2165
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/JSSETest.kt:66
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/JSSETest.kt:67
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/RequestCommonTest.kt:345
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/RouteFailureTest.kt:149
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/RouteFailureTest.kt:230
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/URLConnectionTest.kt:654
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/URLConnectionTest.kt:3636
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/internal/http2/Http2Test.kt:703
- TodoComment okhttp/src/jvmTest/kotlin/okhttp3/internal/http2/HttpOverHttp2Test.kt:166
- TodoComment okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:336
- TodoComment okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:337
- TooManyMethods: FakeSslSocket okhttp-testing-support/src/main/kotlin/okhttp3/sockets/FakeSslSocket.kt:49
- TooManyMethods: DelegatingSSLSocket okhttp-testing-support/src/main/kotlin/okhttp3/sockets/DelegatingSSLSocket.kt:32
- TooManyMethods: PlatformRule okhttp-testing-support/src/main/kotlin/okhttp3/testing/PlatformRule.kt:60
- TooManyMethods: FakeSocket okhttp-testing-support/src/main/kotlin/okhttp3/sockets/FakeSocket.kt:42
- TooManyMethods: Builder okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt:590
- TooManyMethods: Builder okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:935
- TooManyMethods: Builder mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt:128
- TooManyMethods: ClientRuleEventListener okhttp-testing-support/src/main/kotlin/okhttp3/ClientRuleEventListener.kt:24
- TooManyMethods: EventListenerAdapter okhttp-testing-support/src/main/kotlin/okhttp3/EventListenerAdapter.kt:60
- TooManyMethods: EventListener okhttp/src/commonJvmAndroid/kotlin/okhttp3/EventListener.kt:63
- TooManyMethods: AggregateEventListener okhttp/src/commonJvmAndroid/kotlin/okhttp3/EventListener.kt:576
- TooManyMethods: HttpUrl okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:294
- TooManyMethods: MockResponse mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt:26
- TooManyMethods: LoggingEventListener okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/LoggingEventListener.kt:41
- TooManyMethods: OkHttpClient okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt:135
- TooManyMethods: Http2Connection okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt:53
- Off the main sequence: :okhttp-brotli
- Off the main sequence: :okhttp-dnsoverhttps
- Off the main sequence: :okhttp-java-net-cookiejar
- Off the main sequence: :okhttp-tls
- Off the main sequence: :okhttp-idna-mapping-table
- Off the main sequence: :logging-interceptor
- Off the main sequence: :mockwebserver3
- ClassTooLong: MockWebServer mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:97
- ClassTooLong: OkHttpClient okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt:135
- ClassTooLong: DiskLruCache okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt:88
- ClassTooLong: Http2Connection okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt:53
- ClassTooLong: Cache okhttp/src/commonJvmAndroid/kotlin/okhttp3/Cache.kt:147
- ClassTooLong: Cookie okhttp/src/commonJvmAndroid/kotlin/okhttp3/Cookie.kt:44
- FileTooLong: okhttp3/HttpUrl.kt okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt
- FileTooLong: mockwebserver3/MockWebServer.kt mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt
- FileTooLong: okhttp3/OkHttpClient.kt okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt
- FileTooLong: cache/DiskLruCache.kt okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt
- FileTooLong: http2/Http2Connection.kt okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: Reader.<init> okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt:128
- MethodTooLong: Writer.<init> okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt:435
- MethodTooLong: CallServerInterceptor.intercept okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/CallServerInterceptor.kt:32
- MethodTooLong: HttpLoggingInterceptor.intercept okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/HttpLoggingInterceptor.kt:166
- Swallowed exception (empty catch) okhttp/src/commonJvmAndroid/kotlin/okhttp3/Challenge.kt:54
- Swallowed exception (empty catch) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilCommon.kt:287
- Swallowed exception (empty catch) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilJvm.kt:297
- Swallowed exception (empty catch) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilJvm.kt:307
- Edited copy of a member (25 corresponding lines) mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt:98
- Edited copy of a member (25 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt:310
- Edited copy of a member (25 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt:174
- Edited copy of a member (19 corresponding lines) mockwebserver-junit5/src/main/kotlin/mockwebserver3/junit5/internal/StartStopExtension.kt:33
- Edited copy of a member (19 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/IdnaMappingTable.kt:220
- Edited copy of a member (19 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt:114
- Edited copy of a member (14 corresponding lines) okhttp-tls/src/main/kotlin/okhttp3/tls/Certificates.kt:45
- Edited copy of a member (14 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/PostFile.java:32
- Edited copy of a member (15 corresponding lines) mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt:163
- Edited copy of a member (15 corresponding lines) okhttp-testing-support/src/main/kotlin/okhttp3/sockets/FakeSocket.kt:141
- Duplicated block (13 lines × 2) mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt:107
- Duplicated block (13 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt:66
- Edited copies of one member (3 members, 15+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/PostForm.java:28
- Edited copies of one member (3 members, 15+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/kt/PostFile.kt:29
- Edited copy of a member (9 corresponding lines) samples/guide/src/main/java/okhttp3/guide/PostExample.java:30
- Edited copy of a member (9 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/ConfigureTimeouts.java:35
- Duplicated block (8 lines × 2) samples/guide/src/main/java/okhttp3/recipes/PerCallSettings.java:33
- Duplicated block (8 lines × 2) samples/guide/src/main/java/okhttp3/recipes/PostStreaming.java:46
- Swallowed exception (caught, then discarded) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/tls/BasicTrustRootIndex.kt:43
- Swallowed exception (caught, then discarded) build-logic/src/main/kotlin/BndBuildAction.kt:184
- HttpLoggingInterceptor.intercept (cyclomatic 35) okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/HttpLoggingInterceptor.kt:166
- Cookie.parse (cyclomatic 29) okhttp/src/commonJvmAndroid/kotlin/okhttp3/Cookie.kt:450
- CallServerInterceptor.intercept (cyclomatic 29) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/CallServerInterceptor.kt:32
- Builder.parse (cyclomatic 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:1332
- DnsMessageReader.readHttpsResourceRecord (cyclomatic 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/-DnsMessageReader.kt:191
- RetryAndFollowUpInterceptor.followUpRequest (cyclomatic 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt:206
- SimpleIdnaMappingTableKt.readPlainTextIdnaMappingTable (cyclomatic 23) okhttp-idna-mapping-table/src/main/kotlin/okhttp3/internal/idn/SimpleIdnaMappingTable.kt:173
- -CacheControlCommonKt.commonParse (cyclomatic 23) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-CacheControlCommon.kt:110
- Punycode.decodeLabel (cyclomatic 22) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt:180
- -UrlKt.writeCanonicalized (cyclomatic 20) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/url/-Url.kt:38
- WebSocketExtensions.parse (cyclomatic 20) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketExtensions.kt:89
- Dispatcher.promoteAndExecute (cyclomatic 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/Dispatcher.kt:170
- Factory.computeCandidate (cyclomatic 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/CacheStrategy.kt:143
- HttpHeadersKt.readChallengeHeader (cyclomatic 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/HttpHeaders.kt:74
- WebSocketReader.readHeader (cyclomatic 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketReader.kt:120
- MockWebServer.readRequest (cyclomatic 18) mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:686
- CacheInterceptor.intercept (cyclomatic 18) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/CacheInterceptor.kt:45
- BndBuildAction.execute (cyclomatic 17) build-logic/src/main/kotlin/BndBuildAction.kt:83
- -HostnamesCommonKt.decodeIpv6 (cyclomatic 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:83
- StateMachineDnsCall.updateStateAndCallCallbacks (cyclomatic 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/-StateMachineDnsCall.kt:237
- Writer.writeHeaders (cyclomatic 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt:524
- Http2Reader.readSettings (cyclomatic 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Reader.kt:247
- SocketHandler.handle (cyclomatic 16) mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:444
- DiskLruCache.completeEdit (cyclomatic 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt:547
- RealCall.messageDone (cyclomatic 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealCall.kt:336
- Punycode.encodeLabel (cyclomatic 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt:76
- PublicSuffixDatabase.binarySearch (cyclomatic 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/publicsuffix/PublicSuffixDatabase.kt:160
- Repeated repair: okhttp-dnsoverhttps/src/main/kotlin/okhttp3/dnsoverhttps/internal/-DnsOverHttpsQuery.kt okhttp-dnsoverhttps/src/main/kotlin/okhttp3/dnsoverhttps/internal/-DnsOverHttpsQuery.kt:127
- WebSocketExtensions.parse (cognitive 77) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketExtensions.kt:89
- HttpLoggingInterceptor.intercept (cognitive 63) okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/HttpLoggingInterceptor.kt:166
- Builder.parse (cognitive 49) okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:1332
- DnsMessageReader.readHttpsResourceRecord (cognitive 49) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/-DnsMessageReader.kt:191
- HttpHeadersKt.readChallengeHeader (cognitive 44) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/HttpHeaders.kt:74
- CallServerInterceptor.intercept (cognitive 43) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/CallServerInterceptor.kt:32
- PublicSuffixDatabase.binarySearch (cognitive 38) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/publicsuffix/PublicSuffixDatabase.kt:160
- Cookie.parse (cognitive 36) okhttp/src/commonJvmAndroid/kotlin/okhttp3/Cookie.kt:450
- Punycode.encodeLabel (cognitive 36) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt:76
- Punycode.decodeLabel (cognitive 36) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt:180
- -HostnamesCommonKt.decodeIpv6 (cognitive 33) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:83
- Writer.writeHeaders (cognitive 33) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Hpack.kt:524
- FastFallbackExchangeFinder.find (cognitive 31) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/FastFallbackExchangeFinder.kt:53
- -UrlKt.writeCanonicalized (cognitive 31) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/url/-Url.kt:38
- StateMachineDnsCall.updateStateAndCallCallbacks (cognitive 30) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/-StateMachineDnsCall.kt:237
- Dispatcher.promoteAndExecute (cognitive 28) okhttp/src/commonJvmAndroid/kotlin/okhttp3/Dispatcher.kt:170
- -CacheControlCommonKt.commonToString (cognitive 27) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-CacheControlCommon.kt:24
- SequentialExchangeFinder.find (cognitive 27) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/SequentialExchangeFinder.kt:26
- SocketHandler.handle (cognitive 26) mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:444
- CertificatePinner.check (cognitive 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/CertificatePinner.kt:157
- DiskLruCache.completeEdit (cognitive 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/DiskLruCache.kt:547
- WebSocketReader.readHeader (cognitive 26) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketReader.kt:120
- -CacheControlCommonKt.commonParse (cognitive 25) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-CacheControlCommon.kt:110
- CacheInterceptor.intercept (cognitive 25) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/CacheInterceptor.kt:45
- RetryAndFollowUpInterceptor.followUpRequest (cognitive 25) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt:206
- SimpleIdnaMappingTableKt.readPlainTextIdnaMappingTable (cognitive 24) okhttp-idna-mapping-table/src/main/kotlin/okhttp3/internal/idn/SimpleIdnaMappingTable.kt:173
- MockWebServer.readRequest (cognitive 23) mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:686
- -HostnamesCommonKt.decodeIpv4Suffix (cognitive 23) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:155
- TaskRunner.awaitTaskToRun (cognitive 23) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/TaskRunner.kt:170
- FramingSource.read (cognitive 23) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Stream.kt:377
- BndBuildAction.execute (cognitive 22) build-logic/src/main/kotlin/BndBuildAction.kt:83
- CacheQuery.enqueue (cognitive 21) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/RealDnsCache.kt:107
- Http2Reader.readSettings (cognitive 20) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Reader.kt:247
- PublicSuffixDatabase.findMatchingRule (cognitive 20) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/publicsuffix/PublicSuffixDatabase.kt:81
- Http2SocketHandler.readRequest (cognitive 19) mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt:1088
- Factory.computeCandidate (cognitive 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache/CacheStrategy.kt:143
- RealCall.messageDone (cognitive 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealCall.kt:336
- RetryAndFollowUpInterceptor.intercept (cognitive 19) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt:53
- MultipartReader.nextPart (cognitive 18) okhttp/src/commonJvmAndroid/kotlin/okhttp3/MultipartReader.kt:97
- AlpnProvider.invoke (cognitive 18) okhttp/src/jvmMain/kotlin/okhttp3/internal/platform/Jdk8WithJettyBootPlatform.kt:97
- FakeSslSocket.requireHandshake (cognitive 17) okhttp-testing-support/src/main/kotlin/okhttp3/sockets/FakeSslSocket.kt:122
- DerReader.readHeader (cognitive 17) okhttp-tls/src/main/kotlin/okhttp3/tls/internal/der/DerReader.kt:104
- Builder.toString (cognitive 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt:1274
- -HostnamesCommonKt.inet6AddressToAscii (cognitive 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt:197
- RealConnectionPool.closeConnections (cognitive 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealConnectionPool.kt:190
- BasicCertificateChainCleaner.clean (cognitive 17) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/tls/BasicCertificateChainCleaner.kt:47
- MultipartBody.writeOrCountBytes (cognitive 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/MultipartBody.kt:114
- ConnectPlan.connectTlsEtc (cognitive 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt:168
- RealConnection.trackFailure (cognitive 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealConnection.kt:369
- RealWebSocket.writeOneFrame (cognitive 16) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/RealWebSocket.kt:521
- Change coupling: CallEvent.kt ↔ ClientRuleEventListener.kt okhttp-testing-support/src/main/kotlin/okhttp3/CallEvent.kt:1
- Edited copy of a member (27 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/dns/RealDnsCache.kt:203
- Edited copy of a member (21 corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt:51
- Edited copy of a member (18 corresponding lines) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt:136
- Edited copies of one member (4 members, 12+ corresponding lines) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/platform/Platform.kt:98
- Duplicated block (18 lines × 2) okhttp-testing-support/src/main/kotlin/okhttp3/EventRecorder.kt:96
- Duplicated block (12 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/ConscryptSocketAdapter.kt:86
- Duplicated block (9–10 lines × 2) mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/MockResponse.kt:167
- Duplicated block (7 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/Android10Platform.kt:138
- Duplicated block (11 lines × 2) okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/Android10SocketAdapter.kt:44
- Duplicated block (9 lines × 2) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/ws/WebSocketExtensions.kt:135
- Edited copy of a member (42 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/Progress.java:32
- Edited copy of a member (16 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/CustomTrust.java:145
- Edited copy of a member (13 corresponding lines) samples/slack/src/main/java/okhttp3/slack/SlackApi.java:76
- Edited copy of a member (12 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/CertificatePinning.java:33
- Edited copies of one member (3 members, 11+ corresponding lines) samples/guide/src/main/java/okhttp3/recipes/Authenticate.java:44
- Edited copy of a member (17 corresponding lines) samples/guide/src/main/java/okhttp3/recipes/kt/ParseResponseWithMoshi.kt:29
- Duplicated block (19 lines × 2) samples/guide/src/main/java/okhttp3/recipes/Progress.java:41
- Duplicated block (14 lines × 2) samples/guide/src/main/java/okhttp3/recipes/PrintEvents.java:42
- Duplicated block (10 lines × 2) samples/guide/src/main/java/okhttp3/recipes/PostFile.java:35
- Duplicated block (8 lines × 9) samples/guide/src/main/java/okhttp3/recipes/Authenticate.java:47
- Duplicated block (6 lines × 4) samples/guide/src/main/java/okhttp3/recipes/Authenticate.java:45
- Low cohesion: Platform (LCOM4 5) okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/platform/Platform.kt:81
Minor — 29 finding(s)
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/CacheControl.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/WebSocket.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/Authenticator.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/Connection.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Settings.kt:1
- Orphaned file okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/AndroidCertificateChainCleaner.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/TaskLogger.kt:1
- Orphaned file okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/Task.kt:1
- Duplicated predicate okhttp/src/androidMain/kotlin/okhttp3/internal/platform/android/ConscryptSocketAdapter.kt:71
- Duplicated predicate okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-UtilJvm.kt:348
- Duplicated predicate okhttp/src/androidMain/kotlin/okhttp3/internal/platform/Android10Platform.kt:147
- Duplicated predicate okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/platform/Platform.kt:105
- Duplicated predicate okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Reader.kt:117
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found okhttp/build.gradle.kts:46
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST .github/workflows/build.yml:7
- No release approval gate
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-25cbb5d817a74049ad658c9897d47bfc/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-25cbb5d817a74049ad658c9897d47bfc/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude kotlin-js-store . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 28 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 29 file(s) — `build-logic/src/main/kotlin/AlpnVersions.kt`, `build-logic/src/main/kotlin/BndBuildAction.kt`, `build-logic/src/main/kotlin/okhttp.quality-conventions.gradle.kts`, `okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/HttpLoggingInterceptor.kt`, `okhttp-logging-interceptor/src/main/kotlin/okhttp3/logging/LoggingEventListener.kt`, … (+24 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |