Executive summary
apollographql/apollo-kotlin falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 66 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems.
Production Readiness, at 53, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 11 points. Automating the release would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 74.
Five known security holes in the packages the code depends on can be used by attackers. Two passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command.
The product code is 61,493 lines, about €120,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 53 to 70, the lowest score rated Strong, the score would rise from 66 to about 74.
New since the last survey: 10 findings
- Secrets (history) · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Deployment & Rollback · No deployment automation
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €39,000 to €200,000, for 648 to 2,057 hours of work, about 0.8 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.9 at a score of 66. 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: 61,493 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 api.Executable | 2 ast | 3 compiler.operationoutput | 4 gradle.internal | 5 api.ExecutionContext | 6 api.Operation | 7 api.json | 8 ast.introspection | 9 compiler.ir | 10 network.ws.WsProtocol | 11 api.http | 12 compiler.codegen | 13 api.ApolloRequest | 14 compiler.codegen.java | 15 compiler.codegen.kotlin | 16 exception | 17 api | 18 compiler.internal | 19 cache.normalized.api.internal | 20 compiler | 21 execution.internal | 22 internal.incremental | 23 network.websocket.internal | 24 cache.normalized.api | 25 execution | 26 network.http | 27 network.http.HttpNetworkTransport | 28 network | 29 interceptor | 30 network.websocket | 31 network.ws | 32 testing | 33 ApolloClient | 34 cache.http.internal | 35 com.apollographql.apollo | 36 cache.http | 37 cache.normalized | 38 debugserver.internal.graphql | 39 tooling | 40 cache.normalized.internal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 api.Executable | ||||||||||||||||||||||||||||||||||||||||
| 2 ast | ||||||||||||||||||||||||||||||||||||||||
| 3 compiler.operationoutput | ||||||||||||||||||||||||||||||||||||||||
| 4 gradle.internal | ||||||||||||||||||||||||||||||||||||||||
| 5 api.ExecutionContext | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 api.Operation | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 api.json | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 ast.introspection | 27 | |||||||||||||||||||||||||||||||||||||||
| 9 compiler.ir | 47 | 6 | ||||||||||||||||||||||||||||||||||||||
| 10 network.ws.WsProtocol | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 api.http | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 12 compiler.codegen | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 13 api.ApolloRequest | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 14 compiler.codegen.java | 1 | 6 | 9 | 20 | ||||||||||||||||||||||||||||||||||||
| 15 compiler.codegen.kotlin | 1 | 5 | 9 | 20 | ||||||||||||||||||||||||||||||||||||
| 16 exception | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 api | 3 | 8 | 1 | 30 | 7 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 18 compiler.internal | 23 | 2 | 5 | 1 | 1 | 1 | 14 | |||||||||||||||||||||||||||||||||
| 19 cache.normalized.api.internal | 2 | 5 | 14 | |||||||||||||||||||||||||||||||||||||
| 20 compiler | 16 | 5 | 4 | 6 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 21 execution.internal | 32 | 5 | 20 | |||||||||||||||||||||||||||||||||||||
| 22 internal.incremental | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 network.websocket.internal | 2 | 4 | 2 | 8 | ||||||||||||||||||||||||||||||||||||
| 24 cache.normalized.api | 8 | 9 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 execution | 24 | 2 | 13 | 3 | ||||||||||||||||||||||||||||||||||||
| 26 network.http | 4 | 36 | 1 | 5 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 27 network.http.HttpNetworkTransport | 7 | 7 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 network | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 interceptor | 1 | 15 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 network.websocket | 10 | 4 | 14 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 31 network.ws | 6 | 4 | 1 | 7 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 testing | 1 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 ApolloClient | 1 | 2 | 6 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 cache.http.internal | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 35 com.apollographql.apollo | 8 | 4 | 1 | 13 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 36 cache.http | 2 | 4 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 cache.normalized | 26 | 1 | 2 | 15 | 12 | 14 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 debugserver.internal.graphql | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 tooling | 4 | 1 | 4 | 2 | 5 | 3 | ||||||||||||||||||||||||||||||||||
| 40 cache.normalized.internal | 1 | 8 | 1 | 7 | 4 | 3 |
5→17 api.ExecutionContext uses api part of a loop✕
- Connections
- 2 pairs of types, where a type in api.ExecutionContext uses a type in api.
- The types involved
com.apollographql.apollo.api.ExecutionContext.Companion→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.api.ExecutionContext.Element→com.apollographql.apollo.api.ExecutionContext
- Direction
- api.ExecutionContext uses api, so a change to api can break api.ExecutionContext, while a change to api.ExecutionContext can't break api.
- 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→1 api.Operation uses api.Executable✕
- Connections
- 1 pair of types, where a type in api.Operation uses a type in api.Executable.
- The types involved
com.apollographql.apollo.api.Operation.Data→com.apollographql.apollo.api.Executable.Data
- Direction
- api.Operation uses api.Executable, so a change to api.Executable can break api.Operation, while a change to api.Operation can't break api.Executable.
- Position
- Below the diagonal: api.Operation uses a module listed above it, which is the healthy direction.
7→17 api.json uses api part of a loop✕
- Connections
- 3 pairs of types, where a type in api.json uses a type in api.
- The types involved
com.apollographql.apollo.api.json.BufferedSinkJsonWriter→com.apollographql.apollo.api.Uploadcom.apollographql.apollo.api.json.JsonWriter→com.apollographql.apollo.api.Uploadcom.apollographql.apollo.api.json.MapJsonWriter→com.apollographql.apollo.api.Upload
- Direction
- api.json uses api, so a change to api can break api.json, while a change to api.json can't break api.
- 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→2 ast.introspection uses ast✕
- Connections
- 27 pairs of types, where a type in ast.introspection uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLCapabilitycom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLDirectivecom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLDirectiveDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLEnumTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLEnumValueDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLFieldDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLInputObjectTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLInputValueDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLInterfaceTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLNamedTypecom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLObjectTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLScalarTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLSchemaDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLServiceDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLUnionTypeDefinitioncom.apollographql.apollo.ast.introspection.GQLDocumentBuilder→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.ast.introspection.IntrospectionSchemaBuilder→com.apollographql.apollo.ast.GQLDirectiveDefinitioncom.apollographql.apollo.ast.introspection.IntrospectionSchemaBuilder→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.ast.introspection.IntrospectionSchemaBuilder→com.apollographql.apollo.ast.GQLSchemaDefinitioncom.apollographql.apollo.ast.introspection.IntrospectionSchemaBuilder→com.apollographql.apollo.ast.GQLTypeDefinitioncom.apollographql.apollo.ast.introspection.Introspection_readerKt→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.ast.introspection.Introspection_readerKt→com.apollographql.apollo.ast.GQLServiceDefinitioncom.apollographql.apollo.ast.introspection.Introspection_writerKt→com.apollographql.apollo.ast.GQLOperationTypeDefinition
- Direction
- ast.introspection uses ast, so a change to ast can break ast.introspection, while a change to ast.introspection can't break ast.
- Position
- Below the diagonal: ast.introspection uses a module listed above it, which is the healthy direction.
9→2 compiler.ir uses ast✕
- Connections
- 47 pairs of types, where a type in compiler.ir uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.compiler.ir.BucketsKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.FieldMerger→com.apollographql.apollo.ast.CatchTocom.apollographql.apollo.compiler.ir.FieldMergerKt→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ir.FieldMergerKt→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.ir.FieldNodeBuilder→com.apollographql.apollo.ast.CatchTocom.apollographql.apollo.compiler.ir.FieldNodeBuilder→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ir.FieldNodeBuilder→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.ir.FieldNodeBuilder→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.FieldWithParent→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.compiler.ir.IrDataBuildersKt→com.apollographql.apollo.ast.GQLTypeDefinitioncom.apollographql.apollo.compiler.ir.IrDataBuildersKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.IrFieldInfo→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.compiler.ir.IrOperations→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.CatchTocom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.GQLOperationDefinitioncom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.InferredVariablecom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.ast.VariableUsagecom.apollographql.apollo.compiler.ir.IrSchemaBuilder→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.IrSchemaKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.IrTypeKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ir.MergedField→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.ir.ModelGroupBuilder→com.apollographql.apollo.ast.CatchTo
- Direction
- compiler.ir uses ast, so a change to ast can break compiler.ir, while a change to compiler.ir can't break ast.
- Position
- Below the diagonal: compiler.ir uses a module listed above it, which is the healthy direction.
9→20 compiler.ir uses compiler part of a loop✕
- Connections
- 6 pairs of types, where a type in compiler.ir uses a type in compiler.
- The types involved
com.apollographql.apollo.compiler.ir.IrDataBuildersKt→com.apollographql.apollo.compiler.CodegenSchemacom.apollographql.apollo.compiler.ir.IrDataBuildersKt→com.apollographql.apollo.compiler.UsedCoordinatescom.apollographql.apollo.compiler.ir.IrOperations→com.apollographql.apollo.compiler.UsedCoordinatescom.apollographql.apollo.compiler.ir.IrOperationsBuilder→com.apollographql.apollo.compiler.UsedCoordinatescom.apollographql.apollo.compiler.ir.IrSchemaBuilder→com.apollographql.apollo.compiler.UsedCoordinatescom.apollographql.apollo.compiler.ir.IrSchemaKt→com.apollographql.apollo.compiler.UsedCoordinates
- Direction
- compiler.ir uses compiler, so a change to compiler can break compiler.ir, while a change to compiler.ir can't break compiler.
- 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→31 network.ws.WsProtocol uses network.ws part of a loop✕
- Connections
- 2 pairs of types, where a type in network.ws.WsProtocol uses a type in network.ws.
- The types involved
com.apollographql.apollo.network.ws.WsProtocol.Factory→com.apollographql.apollo.network.ws.WebSocketConnectioncom.apollographql.apollo.network.ws.WsProtocol.Factory→com.apollographql.apollo.network.ws.WsProtocol
- Direction
- network.ws.WsProtocol uses network.ws, so a change to network.ws can break network.ws.WsProtocol, while a change to network.ws.WsProtocol can't break network.ws.
- 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→5 api.http uses api.ExecutionContext✕
- Connections
- 2 pairs of types, where a type in api.http uses a type in api.ExecutionContext.
- The types involved
com.apollographql.apollo.api.http.CacheUrlOverride→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.api.http.CacheUrlOverride→com.apollographql.apollo.api.ExecutionContext.Key
- Direction
- api.http uses api.ExecutionContext, so a change to api.ExecutionContext can break api.http, while a change to api.http can't break api.ExecutionContext.
- Position
- Below the diagonal: api.http uses a module listed above it, which is the healthy direction.
11→17 api.http uses api part of a loop✕
- Connections
- 7 pairs of types, where a type in api.http uses a type in api.
- The types involved
com.apollographql.apollo.api.http.DefaultHttpRequestComposer→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.api.http.DefaultWebSocketPayloadComposer→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.api.http.HttpRequest→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.api.http.HttpRequestComposer→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.api.http.HttpResponse→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.api.http.UploadsHttpBody→com.apollographql.apollo.api.Uploadcom.apollographql.apollo.api.http.WebSocketPayloadComposer→com.apollographql.apollo.api.ApolloRequest
- Direction
- api.http uses api, so a change to api can break api.http, while a change to api.http can't break api.
- 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→2 compiler.codegen uses ast✕
- Connections
- 1 pair of types, where a type in compiler.codegen uses a type in ast.
- The types involved
com.apollographql.apollo.compiler.codegen.FieldPolicyArgsKt→com.apollographql.apollo.ast.Schema
- Direction
- compiler.codegen uses ast, so a change to ast can break compiler.codegen, while a change to compiler.codegen can't break ast.
- Position
- Below the diagonal: compiler.codegen uses a module listed above it, which is the healthy direction.
12→9 compiler.codegen uses compiler.ir✕
- Connections
- 3 pairs of types, where a type in compiler.codegen uses a type in compiler.ir.
- The types involved
com.apollographql.apollo.compiler.codegen.FlattenKt→com.apollographql.apollo.compiler.ir.IrModelGroupcom.apollographql.apollo.compiler.codegen.LayoutImplKt→com.apollographql.apollo.compiler.ir.IrFieldInfocom.apollographql.apollo.compiler.codegen.LayoutImplKt→com.apollographql.apollo.compiler.ir.IrOperationDefinition
- Direction
- compiler.codegen uses compiler.ir, so a change to compiler.ir can break compiler.codegen, while a change to compiler.codegen can't break compiler.ir.
- Position
- Below the diagonal: compiler.codegen uses a module listed above it, which is the healthy direction.
12→20 compiler.codegen uses compiler part of a loop✕
- Connections
- 4 pairs of types, where a type in compiler.codegen uses a type in compiler.
- The types involved
com.apollographql.apollo.compiler.codegen.LayoutImpl→com.apollographql.apollo.compiler.CodegenSchemacom.apollographql.apollo.compiler.codegen.LayoutImpl→com.apollographql.apollo.compiler.PackageNameFactorycom.apollographql.apollo.compiler.codegen.LayoutImplKt→com.apollographql.apollo.compiler.CodegenSchemacom.apollographql.apollo.compiler.codegen.SourceOutput→com.apollographql.apollo.compiler.CodegenMetadata
- Direction
- compiler.codegen uses compiler, so a change to compiler can break compiler.codegen, while a change to compiler.codegen can't break compiler.
- 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→11 api.ApolloRequest uses api.http✕
- Connections
- 2 pairs of types, where a type in api.ApolloRequest uses a type in api.http.
- The types involved
com.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.http.HttpMethod
- Direction
- api.ApolloRequest uses api.http, so a change to api.http can break api.ApolloRequest, while a change to api.ApolloRequest can't break api.http.
- Position
- Below the diagonal: api.ApolloRequest uses a module listed above it, which is the healthy direction.
13→17 api.ApolloRequest uses api part of a loop✕
- Connections
- 5 pairs of types, where a type in api.ApolloRequest uses a type in api.
- The types involved
com.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.MutableExecutionOptionscom.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.api.ApolloRequest.Builder→com.apollographql.apollo.api.Operation
- Direction
- api.ApolloRequest uses api, so a change to api can break api.ApolloRequest, while a change to api.ApolloRequest can't break api.
- 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→3 compiler.codegen.java uses compiler.operationoutput✕
- Connections
- 1 pair of types, where a type in compiler.codegen.java uses a type in compiler.operationoutput.
- The types involved
com.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.operationoutput.OperationDescriptor
- Direction
- compiler.codegen.java uses compiler.operationoutput, so a change to compiler.operationoutput can break compiler.codegen.java, while a change to compiler.codegen.java can't break compiler.operationoutput.
- Position
- Below the diagonal: compiler.codegen.java uses a module listed above it, which is the healthy direction.
14→9 compiler.codegen.java uses compiler.ir✕
- Connections
- 6 pairs of types, where a type in compiler.codegen.java uses a type in compiler.ir.
- The types involved
com.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.ir.IrDataBuilderscom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.ir.IrSchemacom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.ir.IrScalarTypecom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.ir.IrTypecom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.ir.IrType2
- Direction
- compiler.codegen.java uses compiler.ir, so a change to compiler.ir can break compiler.codegen.java, while a change to compiler.codegen.java can't break compiler.ir.
- Position
- Below the diagonal: compiler.codegen.java uses a module listed above it, which is the healthy direction.
14→12 compiler.codegen.java uses compiler.codegen✕
- Connections
- 9 pairs of types, where a type in compiler.codegen.java uses a type in compiler.codegen.
- The types involved
com.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.codegen.OperationsLayoutcom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.codegen.SchemaLayoutcom.apollographql.apollo.compiler.codegen.java.JavaContext→com.apollographql.apollo.compiler.codegen.CommonLayoutcom.apollographql.apollo.compiler.codegen.java.JavaDataBuilderContext→com.apollographql.apollo.compiler.codegen.SchemaLayoutcom.apollographql.apollo.compiler.codegen.java.JavaOperationsContext→com.apollographql.apollo.compiler.codegen.OperationsLayoutcom.apollographql.apollo.compiler.codegen.java.JavaOutputKt→com.apollographql.apollo.compiler.codegen.SourceOutputcom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.codegen.ResolverKeycom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.codegen.ResolverKeyKindcom.apollographql.apollo.compiler.codegen.java.JavaSchemaContext→com.apollographql.apollo.compiler.codegen.SchemaLayout
- Direction
- compiler.codegen.java uses compiler.codegen, so a change to compiler.codegen can break compiler.codegen.java, while a change to compiler.codegen.java can't break compiler.codegen.
- Position
- Below the diagonal: compiler.codegen.java uses a module listed above it, which is the healthy direction.
14→20 compiler.codegen.java uses compiler part of a loop✕
- Connections
- 20 pairs of types, where a type in compiler.codegen.java uses a type in compiler.
- The types involved
com.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.CodegenOptionscom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.JavaOperationsCodegenOptionscom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.JavaSchemaCodegenOptionscom.apollographql.apollo.compiler.codegen.java.JavaCodegen→com.apollographql.apollo.compiler.Transformcom.apollographql.apollo.compiler.codegen.java.JavaCodegenKt→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.java.JavaCodegenKt→com.apollographql.apollo.compiler.JavaNullablecom.apollographql.apollo.compiler.codegen.java.JavaCodegenKt→com.apollographql.apollo.compiler.Transformcom.apollographql.apollo.compiler.codegen.java.JavaContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.java.JavaContext→com.apollographql.apollo.compiler.JavaNullablecom.apollographql.apollo.compiler.codegen.java.JavaDataBuilderContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.java.JavaDataBuilderContext→com.apollographql.apollo.compiler.JavaNullablecom.apollographql.apollo.compiler.codegen.java.JavaOperationsContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.java.JavaOperationsContext→com.apollographql.apollo.compiler.JavaNullablecom.apollographql.apollo.compiler.codegen.java.JavaOutput→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.JavaNullablecom.apollographql.apollo.compiler.codegen.java.JavaResolver→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.java.JavaSchemaContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.java.JavaSchemaContext→com.apollographql.apollo.compiler.JavaNullable
- Direction
- compiler.codegen.java uses compiler, so a change to compiler can break compiler.codegen.java, while a change to compiler.codegen.java can't break compiler.
- 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→3 compiler.codegen.kotlin uses compiler.operationoutput✕
- Connections
- 1 pair of types, where a type in compiler.codegen.kotlin uses a type in compiler.operationoutput.
- The types involved
com.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.operationoutput.OperationDescriptor
- Direction
- compiler.codegen.kotlin uses compiler.operationoutput, so a change to compiler.operationoutput can break compiler.codegen.kotlin, while a change to compiler.codegen.kotlin can't break compiler.operationoutput.
- Position
- Below the diagonal: compiler.codegen.kotlin uses a module listed above it, which is the healthy direction.
15→9 compiler.codegen.kotlin uses compiler.ir✕
- Connections
- 5 pairs of types, where a type in compiler.codegen.kotlin uses a type in compiler.ir.
- The types involved
com.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.ir.IrDataBuilderscom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.ir.IrSchemacom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.ir.IrTypecom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.ir.IrType2
- Direction
- compiler.codegen.kotlin uses compiler.ir, so a change to compiler.ir can break compiler.codegen.kotlin, while a change to compiler.codegen.kotlin can't break compiler.ir.
- Position
- Below the diagonal: compiler.codegen.kotlin uses a module listed above it, which is the healthy direction.
15→12 compiler.codegen.kotlin uses compiler.codegen✕
- Connections
- 9 pairs of types, where a type in compiler.codegen.kotlin uses a type in compiler.codegen.
- The types involved
com.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.codegen.OperationsLayoutcom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.codegen.SchemaLayoutcom.apollographql.apollo.compiler.codegen.kotlin.KotlinContext→com.apollographql.apollo.compiler.codegen.CommonLayoutcom.apollographql.apollo.compiler.codegen.kotlin.KotlinDataBuilderContext→com.apollographql.apollo.compiler.codegen.SchemaLayoutcom.apollographql.apollo.compiler.codegen.kotlin.KotlinOperationsContext→com.apollographql.apollo.compiler.codegen.OperationsLayoutcom.apollographql.apollo.compiler.codegen.kotlin.KotlinOutputKt→com.apollographql.apollo.compiler.codegen.SourceOutputcom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.codegen.ResolverKeycom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.codegen.ResolverKeyKindcom.apollographql.apollo.compiler.codegen.kotlin.KotlinSchemaContext→com.apollographql.apollo.compiler.codegen.SchemaLayout
- Direction
- compiler.codegen.kotlin uses compiler.codegen, so a change to compiler.codegen can break compiler.codegen.kotlin, while a change to compiler.codegen.kotlin can't break compiler.codegen.
- Position
- Below the diagonal: compiler.codegen.kotlin uses a module listed above it, which is the healthy direction.
15→20 compiler.codegen.kotlin uses compiler part of a loop✕
- Connections
- 20 pairs of types, where a type in compiler.codegen.kotlin uses a type in compiler.
- The types involved
com.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.CodegenOptionscom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.KotlinOperationsCodegenOptionscom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.KotlinSchemaCodegenOptionscom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegen→com.apollographql.apollo.compiler.Transformcom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegenKt→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegenKt→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinCodegenKt→com.apollographql.apollo.compiler.Transformcom.apollographql.apollo.compiler.codegen.kotlin.KotlinContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.kotlin.KotlinContext→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinDataBuilderContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.kotlin.KotlinDataBuilderContext→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinOperationsContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.kotlin.KotlinOperationsContext→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinOutput→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.CodegenMetadatacom.apollographql.apollo.compiler.codegen.kotlin.KotlinResolver→com.apollographql.apollo.compiler.TargetLanguagecom.apollographql.apollo.compiler.codegen.kotlin.KotlinSchemaContext→com.apollographql.apollo.compiler.GeneratedMethodcom.apollographql.apollo.compiler.codegen.kotlin.KotlinSchemaContext→com.apollographql.apollo.compiler.TargetLanguage
- Direction
- compiler.codegen.kotlin uses compiler, so a change to compiler can break compiler.codegen.kotlin, while a change to compiler.codegen.kotlin can't break compiler.
- 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→11 exception uses api.http✕
- Connections
- 1 pair of types, where a type in exception uses a type in api.http.
- The types involved
com.apollographql.apollo.exception.ApolloHttpException→com.apollographql.apollo.api.http.HttpHeader
- Direction
- exception uses api.http, so a change to api.http can break exception, while a change to exception can't break api.http.
- Position
- Below the diagonal: exception uses a module listed above it, which is the healthy direction.
16→17 exception uses api part of a loop✕
- Connections
- 2 pairs of types, where a type in exception uses a type in api.
- The types involved
com.apollographql.apollo.exception.ApolloGraphQLException→com.apollographql.apollo.api.Errorcom.apollographql.apollo.exception.RouterError→com.apollographql.apollo.api.Error
- Direction
- exception uses api, so a change to api can break exception, while a change to exception can't break api.
- 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→1 api uses api.Executable✕
- Connections
- 3 pairs of types, where a type in api uses a type in api.Executable.
- The types involved
com.apollographql.apollo.api.CompiledField→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.api.CompiledGraphQLKt→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.api.ExecutablesKt→com.apollographql.apollo.api.Executable.Variables
- Direction
- api uses api.Executable, so a change to api.Executable can break api, while a change to api can't break api.Executable.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→5 api uses api.ExecutionContext✕
- Connections
- 8 pairs of types, where a type in api uses a type in api.ExecutionContext.
- The types involved
com.apollographql.apollo.api.CombinedExecutionContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.api.CombinedExecutionContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.api.CustomScalarAdapters→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.api.CustomScalarAdapters→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.api.EmptyExecutionContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.api.EmptyExecutionContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.api.ExecutionContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.api.ExecutionContext→com.apollographql.apollo.api.ExecutionContext.Key
- Direction
- api uses api.ExecutionContext, so a change to api.ExecutionContext can break api, while a change to api can't break api.ExecutionContext.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→6 api uses api.Operation✕
- Connections
- 1 pair of types, where a type in api uses a type in api.Operation.
- The types involved
com.apollographql.apollo.api.-DataKt→com.apollographql.apollo.api.Operation.Data
- Direction
- api uses api.Operation, so a change to api.Operation can break api, while a change to api can't break api.Operation.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→7 api uses api.json✕
- Connections
- 30 pairs of types, where a type in api uses a type in api.json. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.api.-DataKt→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.Adapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.Adapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.ApolloOptionalAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.ApolloOptionalAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.AssertionsKt→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.CatchToNullAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.CatchToNullAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.CatchToResultAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.CatchToResultAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.ErrorAwareAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.ErrorAwareAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.Executable→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.ExecutablesKt→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.ExecutablesKt→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.ListAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.ListAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.NullableAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.NullableAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.ObjectAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.ObjectAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.OperationsKt→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.OperationsKt→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.api.OptionalAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.api.OptionalAdapter→com.apollographql.apollo.api.json.JsonWriter
- Direction
- api uses api.json, so a change to api.json can break api, while a change to api can't break api.json.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→11 api uses api.http✕
- Connections
- 7 pairs of types, where a type in api uses a type in api.http.
- The types involved
com.apollographql.apollo.api.ApolloRequest→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.api.ApolloRequest→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.api.ExecutionOptions→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.api.ExecutionOptions→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.api.MutableExecutionOptions→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.api.MutableExecutionOptions→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.api.RequestParametersKt→com.apollographql.apollo.api.http.HttpBody
- Direction
- api uses api.http, so a change to api.http can break api, while a change to api can't break api.http.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→13 api uses api.ApolloRequest✕
- Connections
- 1 pair of types, where a type in api uses a type in api.ApolloRequest.
- The types involved
com.apollographql.apollo.api.ApolloRequest→com.apollographql.apollo.api.ApolloRequest.Builder
- Direction
- api uses api.ApolloRequest, so a change to api.ApolloRequest can break api, while a change to api can't break api.ApolloRequest.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
17→16 api uses exception✕
- Connections
- 2 pairs of types, where a type in api uses a type in exception.
- The types involved
com.apollographql.apollo.api.ApolloResponse→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.api.OperationsKt→com.apollographql.apollo.exception.ApolloException
- Direction
- api uses exception, so a change to exception can break api, while a change to api can't break exception.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
18→2 compiler.internal uses ast✕
- Connections
- 23 pairs of types, where a type in compiler.internal uses a type in ast.
- The types involved
com.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.GQLOperationDefinitioncom.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.internal.CheckApolloInlineFragmentsHaveTypeConditionKt→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.compiler.internal.CheckApolloInlineFragmentsHaveTypeConditionKt→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.internal.CheckApolloReservedEnumValueNamesKt→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.internal.CheckApolloReservedEnumValueNamesKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.internal.CheckApolloTargetNameClashesKt→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.internal.CheckApolloTargetNameClashesKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.internal.CheckCapitalizedFieldsKt→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.compiler.internal.CheckCapitalizedFieldsKt→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.internal.CheckCapitalizedFieldsKt→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.internal.CheckConditionalFragmentKt→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.compiler.internal.CheckConditionalFragmentKt→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.compiler.internal.CheckConditionalFragmentKt→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.ast.ForeignSchemacom.apollographql.apollo.compiler.internal.GQLFragmentDefinitionSerializer→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.internal.GQLTypeSerializer→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.compiler.internal.SchemaSerializer→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.internal.ValidationScope→com.apollographql.apollo.ast.Issue
- Direction
- compiler.internal uses ast, so a change to ast can break compiler.internal, while a change to compiler.internal can't break ast.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→3 compiler.internal uses compiler.operationoutput✕
- Connections
- 2 pairs of types, where a type in compiler.internal uses a type in compiler.operationoutput.
- The types involved
com.apollographql.apollo.compiler.internal.LegacyOperationIdsGenerator→com.apollographql.apollo.compiler.operationoutput.OperationDescriptorcom.apollographql.apollo.compiler.internal.LegacyOperationIdsGenerator→com.apollographql.apollo.compiler.operationoutput.OperationId
- Direction
- compiler.internal uses compiler.operationoutput, so a change to compiler.operationoutput can break compiler.internal, while a change to compiler.internal can't break compiler.operationoutput.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→9 compiler.internal uses compiler.ir✕
- Connections
- 5 pairs of types, where a type in compiler.internal uses a type in compiler.ir.
- The types involved
com.apollographql.apollo.compiler.internal.BooleanExpressionSerializer→com.apollographql.apollo.compiler.ir.BTermcom.apollographql.apollo.compiler.internal.BooleanExpressionSerializer→com.apollographql.apollo.compiler.ir.BooleanExpressioncom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.internal.SerializationKt→com.apollographql.apollo.compiler.ir.BTermcom.apollographql.apollo.compiler.internal.SerializationKt→com.apollographql.apollo.compiler.ir.BooleanExpression
- Direction
- compiler.internal uses compiler.ir, so a change to compiler.ir can break compiler.internal, while a change to compiler.internal can't break compiler.ir.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→12 compiler.internal uses compiler.codegen✕
- Connections
- 1 pair of types, where a type in compiler.internal uses a type in compiler.codegen.
- The types involved
com.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.codegen.SchemaAndOperationsLayout
- Direction
- compiler.internal uses compiler.codegen, so a change to compiler.codegen can break compiler.internal, while a change to compiler.internal can't break compiler.codegen.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→14 compiler.internal uses compiler.codegen.java✕
- Connections
- 1 pair of types, where a type in compiler.internal uses a type in compiler.codegen.java.
- The types involved
com.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.codegen.java.JavaOutput
- Direction
- compiler.internal uses compiler.codegen.java, so a change to compiler.codegen.java can break compiler.internal, while a change to compiler.internal can't break compiler.codegen.java.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→15 compiler.internal uses compiler.codegen.kotlin✕
- Connections
- 1 pair of types, where a type in compiler.internal uses a type in compiler.codegen.kotlin.
- The types involved
com.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.codegen.kotlin.KotlinOutput
- Direction
- compiler.internal uses compiler.codegen.kotlin, so a change to compiler.codegen.kotlin can break compiler.internal, while a change to compiler.internal can't break compiler.codegen.kotlin.
- Position
- Below the diagonal: compiler.internal uses a module listed above it, which is the healthy direction.
18→20 compiler.internal uses compiler part of a loop✕
- Connections
- 14 pairs of types, where a type in compiler.internal uses a type in compiler.
- The types involved
com.apollographql.apollo.compiler.internal.ApolloExecutableDocumentTransform→com.apollographql.apollo.compiler.ExecutableDocumentTransformcom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.ApolloCompilerPlugincom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.ApolloCompilerRegistrycom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.CodegenSchemacom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.ExecutableDocumentTransformcom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.LayoutFactorycom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.OperationIdsGeneratorcom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.Ordercom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.SchemaCodeGeneratorcom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.SchemaDocumentTransformcom.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry→com.apollographql.apollo.compiler.Transformcom.apollographql.apollo.compiler.internal.LegacyOperationIdsGenerator→com.apollographql.apollo.compiler.ApolloCompilerPlugincom.apollographql.apollo.compiler.internal.LegacyOperationIdsGenerator→com.apollographql.apollo.compiler.OperationIdsGeneratorcom.apollographql.apollo.compiler.internal.Registration→com.apollographql.apollo.compiler.Order
- Direction
- compiler.internal uses compiler, so a change to compiler can break compiler.internal, while a change to compiler.internal can't break compiler.
- 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 cache.normalized.api.internal uses api.Executable✕
- Connections
- 2 pairs of types, where a type in cache.normalized.api.internal uses a type in api.Executable.
- The types involved
com.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.api.Executable.Variables
- Direction
- cache.normalized.api.internal uses api.Executable, so a change to api.Executable can break cache.normalized.api.internal, while a change to cache.normalized.api.internal can't break api.Executable.
- Position
- Below the diagonal: cache.normalized.api.internal uses a module listed above it, which is the healthy direction.
19→17 cache.normalized.api.internal uses api✕
- Connections
- 5 pairs of types, where a type in cache.normalized.api.internal uses a type in api.
- The types involved
com.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.api.CompiledSelectioncom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.api.CompiledSelectioncom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.api.CompiledType
- Direction
- cache.normalized.api.internal uses api, so a change to api can break cache.normalized.api.internal, while a change to cache.normalized.api.internal can't break api.
- Position
- Below the diagonal: cache.normalized.api.internal uses a module listed above it, which is the healthy direction.
19→24 cache.normalized.api.internal uses cache.normalized.api part of a loop✕
- Connections
- 14 pairs of types, where a type in cache.normalized.api.internal uses a type in cache.normalized.api.
- The types involved
com.apollographql.apollo.cache.normalized.api.internal.BlobRecordSerializer→com.apollographql.apollo.cache.normalized.api.Recordcom.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.cache.normalized.api.CacheDatacom.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.cache.normalized.api.CacheResolvercom.apollographql.apollo.cache.normalized.api.internal.CacheBatchReader→com.apollographql.apollo.cache.normalized.api.ReadOnlyNormalizedCachecom.apollographql.apollo.cache.normalized.api.internal.JsonRecordSerializer→com.apollographql.apollo.cache.normalized.api.Recordcom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.cache.normalized.api.CacheKeycom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorcom.apollographql.apollo.cache.normalized.api.internal.Normalizer→com.apollographql.apollo.cache.normalized.api.Recordcom.apollographql.apollo.cache.normalized.api.internal.OptimisticCache→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.api.internal.OptimisticCache→com.apollographql.apollo.cache.normalized.api.CacheKeycom.apollographql.apollo.cache.normalized.api.internal.OptimisticCache→com.apollographql.apollo.cache.normalized.api.NormalizedCachecom.apollographql.apollo.cache.normalized.api.internal.OptimisticCache→com.apollographql.apollo.cache.normalized.api.Recordcom.apollographql.apollo.cache.normalized.api.internal.RecordWeigher→com.apollographql.apollo.cache.normalized.api.Record
- Direction
- cache.normalized.api.internal uses cache.normalized.api, so a change to cache.normalized.api can break cache.normalized.api.internal, while a change to cache.normalized.api.internal can't break cache.normalized.api.
- 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→2 compiler uses ast✕
- Connections
- 16 pairs of types, where a type in compiler uses a type in ast.
- The types involved
com.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.ast.ForeignSchemacom.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.ast.ParserOptionscom.apollographql.apollo.compiler.ApolloCompilerRegistry→com.apollographql.apollo.ast.ForeignSchemacom.apollographql.apollo.compiler.CodegenSchema→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.DocumentTransform→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.DocumentTransform→com.apollographql.apollo.ast.GQLOperationDefinitioncom.apollographql.apollo.compiler.DocumentTransform→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.ExecutableDocumentTransform→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.compiler.ExecutableDocumentTransform→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.compiler.ExecutableDocumentTransform→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.compiler.IssueGroup→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.compiler.SchemaCodeGenerator→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.compiler.SchemaDocumentTransform→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.compiler.SchemaListener→com.apollographql.apollo.ast.Schema
- Direction
- compiler uses ast, so a change to ast can break compiler, while a change to compiler can't break ast.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→3 compiler uses compiler.operationoutput✕
- Connections
- 5 pairs of types, where a type in compiler uses a type in compiler.operationoutput.
- The types involved
com.apollographql.apollo.compiler.ApolloCompilerPlugin→com.apollographql.apollo.compiler.operationoutput.OperationDescriptorcom.apollographql.apollo.compiler.ApolloCompilerPlugin→com.apollographql.apollo.compiler.operationoutput.OperationIdcom.apollographql.apollo.compiler.JsonKt→com.apollographql.apollo.compiler.operationoutput.OperationDescriptorcom.apollographql.apollo.compiler.OperationIdsGenerator→com.apollographql.apollo.compiler.operationoutput.OperationDescriptorcom.apollographql.apollo.compiler.OperationIdsGenerator→com.apollographql.apollo.compiler.operationoutput.OperationId
- Direction
- compiler uses compiler.operationoutput, so a change to compiler.operationoutput can break compiler, while a change to compiler can't break compiler.operationoutput.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→9 compiler uses compiler.ir✕
- Connections
- 4 pairs of types, where a type in compiler uses a type in compiler.ir.
- The types involved
com.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.ApolloCompilerRegistry→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.JsonKt→com.apollographql.apollo.compiler.ir.IrOperationscom.apollographql.apollo.compiler.JsonKt→com.apollographql.apollo.compiler.ir.IrSchema
- Direction
- compiler uses compiler.ir, so a change to compiler.ir can break compiler, while a change to compiler can't break compiler.ir.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→12 compiler uses compiler.codegen✕
- Connections
- 6 pairs of types, where a type in compiler uses a type in compiler.codegen.
- The types involved
com.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.codegen.SchemaAndOperationsLayoutcom.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.codegen.SchemaLayoutcom.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.codegen.SourceOutputcom.apollographql.apollo.compiler.CodegenMetadata→com.apollographql.apollo.compiler.codegen.ResolverEntrycom.apollographql.apollo.compiler.CodegenMetadataKt→com.apollographql.apollo.compiler.codegen.ResolverClassNamecom.apollographql.apollo.compiler.LayoutFactory→com.apollographql.apollo.compiler.codegen.SchemaAndOperationsLayout
- Direction
- compiler uses compiler.codegen, so a change to compiler.codegen can break compiler, while a change to compiler can't break compiler.codegen.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→14 compiler uses compiler.codegen.java✕
- Connections
- 2 pairs of types, where a type in compiler uses a type in compiler.codegen.java.
- The types involved
com.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.codegen.java.JavaOutputcom.apollographql.apollo.compiler.ApolloCompilerRegistry→com.apollographql.apollo.compiler.codegen.java.JavaOutput
- Direction
- compiler uses compiler.codegen.java, so a change to compiler.codegen.java can break compiler, while a change to compiler can't break compiler.codegen.java.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→15 compiler uses compiler.codegen.kotlin✕
- Connections
- 2 pairs of types, where a type in compiler uses a type in compiler.codegen.kotlin.
- The types involved
com.apollographql.apollo.compiler.ApolloCompiler→com.apollographql.apollo.compiler.codegen.kotlin.KotlinOutputcom.apollographql.apollo.compiler.ApolloCompilerRegistry→com.apollographql.apollo.compiler.codegen.kotlin.KotlinOutput
- Direction
- compiler uses compiler.codegen.kotlin, so a change to compiler.codegen.kotlin can break compiler, while a change to compiler can't break compiler.codegen.kotlin.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
20→18 compiler uses compiler.internal✕
- Connections
- 1 pair of types, where a type in compiler uses a type in compiler.internal.
- The types involved
com.apollographql.apollo.compiler.EntrypointsKt→com.apollographql.apollo.compiler.internal.DefaultApolloCompilerRegistry
- Direction
- compiler uses compiler.internal, so a change to compiler.internal can break compiler, while a change to compiler can't break compiler.internal.
- Position
- Below the diagonal: compiler uses a module listed above it, which is the healthy direction.
21→2 execution.internal uses ast✕
- Connections
- 32 pairs of types, where a type in execution.internal uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLArgumentcom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLEnumTypeDefinitioncom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLInputObjectTypeDefinitioncom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLInputValueDefinitioncom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.GQLVariableDefinitioncom.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.ast.GQLEnumTypeDefinitioncom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.ast.GQLInputObjectTypeDefinitioncom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.ast.GQLVariableDefinitioncom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.internal.CollectedError→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.internal.CollectedField→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.internal.CollectedResult→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.internal.IntrospectionKt→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.execution.internal.IntrospectionKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.internal.IntrospectionType→com.apollographql.apollo.ast.GQLTypecom.apollographql.apollo.execution.internal.IntrospectionType→com.apollographql.apollo.ast.GQLTypeDefinitioncom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.ast.GQLObjectTypeDefinitioncom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.ast.GQLSelection
- Direction
- execution.internal uses ast, so a change to ast can break execution.internal, while a change to execution.internal can't break ast.
- Position
- Below the diagonal: execution.internal uses a module listed above it, which is the healthy direction.
21→17 execution.internal uses api✕
- Connections
- 5 pairs of types, where a type in execution.internal uses a type in api.
- The types involved
com.apollographql.apollo.execution.internal.ErrorsKt→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.api.OnError
- Direction
- execution.internal uses api, so a change to api can break execution.internal, while a change to execution.internal can't break api.
- Position
- Below the diagonal: execution.internal uses a module listed above it, which is the healthy direction.
21→25 execution.internal uses execution part of a loop✕
- Connections
- 20 pairs of types, where a type in execution.internal uses a type in execution.
- The types involved
com.apollographql.apollo.execution.internal.CoerceArgumentValuesKt→com.apollographql.apollo.execution.Coercingcom.apollographql.apollo.execution.internal.CoerceVariablesValuesKt→com.apollographql.apollo.execution.Coercingcom.apollographql.apollo.execution.internal.ErrorsKt→com.apollographql.apollo.execution.GraphQLResponsecom.apollographql.apollo.execution.internal.ErrorsKt→com.apollographql.apollo.execution.SubscriptionResponsecom.apollographql.apollo.execution.internal.IntrospectionKt→com.apollographql.apollo.execution.Resolvercom.apollographql.apollo.execution.internal.IntrospectionKt→com.apollographql.apollo.execution.StringCoercingcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.Coercingcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.GraphQLResponsecom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.Instrumentationcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.OperationCallbackcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.ResolveInfocom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.Resolvercom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.SubscriptionErrorcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.SubscriptionEventcom.apollographql.apollo.execution.internal.OperationContext→com.apollographql.apollo.execution.TypeResolvercom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.execution.Coercingcom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.execution.GraphQLRequestcom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.execution.PersistedDocumentcom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.execution.PersistedDocumentCachecom.apollographql.apollo.execution.internal.PrepareKt→com.apollographql.apollo.execution.PreparedRequest
- Direction
- execution.internal uses execution, so a change to execution can break execution.internal, while a change to execution.internal can't break execution.
- 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→17 internal.incremental uses api✕
- Connections
- 3 pairs of types, where a type in internal.incremental uses a type in api.
- The types involved
com.apollographql.apollo.internal.incremental.IncrementalResultsMerger→com.apollographql.apollo.api.DeferredFragmentIdentifiercom.apollographql.apollo.internal.incremental.V0_1IncrementalResultsMerger→com.apollographql.apollo.api.DeferredFragmentIdentifiercom.apollographql.apollo.internal.incremental.V0_2IncrementalResultsMerger→com.apollographql.apollo.api.DeferredFragmentIdentifier
- Direction
- internal.incremental uses api, so a change to api can break internal.incremental, while a change to internal.incremental can't break api.
- Position
- Below the diagonal: internal.incremental uses a module listed above it, which is the healthy direction.
23→11 network.websocket.internal uses api.http✕
- Connections
- 2 pairs of types, where a type in network.websocket.internal uses a type in api.http.
- The types involved
com.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.internal.WebSocketPool→com.apollographql.apollo.api.http.HttpHeader
- Direction
- network.websocket.internal uses api.http, so a change to api.http can break network.websocket.internal, while a change to network.websocket.internal can't break api.http.
- Position
- Below the diagonal: network.websocket.internal uses a module listed above it, which is the healthy direction.
23→16 network.websocket.internal uses exception✕
- Connections
- 4 pairs of types, where a type in network.websocket.internal uses a type in exception.
- The types involved
com.apollographql.apollo.network.websocket.internal.BufferedWebSocketListener→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.internal.OperationListener→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.internal.WebSocketPool→com.apollographql.apollo.exception.ApolloException
- Direction
- network.websocket.internal uses exception, so a change to exception can break network.websocket.internal, while a change to network.websocket.internal can't break exception.
- Position
- Below the diagonal: network.websocket.internal uses a module listed above it, which is the healthy direction.
23→17 network.websocket.internal uses api✕
- Connections
- 2 pairs of types, where a type in network.websocket.internal uses a type in api.
- The types involved
com.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.internal.WebSocketPool→com.apollographql.apollo.api.ApolloRequest
- Direction
- network.websocket.internal uses api, so a change to api can break network.websocket.internal, while a change to network.websocket.internal can't break api.
- Position
- Below the diagonal: network.websocket.internal uses a module listed above it, which is the healthy direction.
23→30 network.websocket.internal uses network.websocket part of a loop✕
- Connections
- 8 pairs of types, where a type in network.websocket.internal uses a type in network.websocket.
- The types involved
com.apollographql.apollo.network.websocket.internal.BufferedWebSocketListener→com.apollographql.apollo.network.websocket.WebSocketListenercom.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.network.websocket.WebSocketcom.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.network.websocket.WebSocketEnginecom.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.network.websocket.WebSocketListenercom.apollographql.apollo.network.websocket.internal.SubscribableWebSocket→com.apollographql.apollo.network.websocket.WsProtocolcom.apollographql.apollo.network.websocket.internal.SubscribableWebSocketKt→com.apollographql.apollo.network.websocket.ClientMessagecom.apollographql.apollo.network.websocket.internal.WebSocketPool→com.apollographql.apollo.network.websocket.WebSocketEnginecom.apollographql.apollo.network.websocket.internal.WebSocketPool→com.apollographql.apollo.network.websocket.WsProtocol
- Direction
- network.websocket.internal uses network.websocket, so a change to network.websocket can break network.websocket.internal, while a change to network.websocket.internal can't break network.websocket.
- 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 cache.normalized.api uses api.Executable✕
- Connections
- 8 pairs of types, where a type in cache.normalized.api uses a type in api.Executable.
- The types involved
com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorContext→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.CacheKeyResolver→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.CacheResolver→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.DefaultCacheResolver→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.ExpireDateCacheResolver→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.FieldPolicyCacheResolver→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.OperationCacheExtensionsKt→com.apollographql.apollo.api.Executable.Variablescom.apollographql.apollo.cache.normalized.api.ReceiveDateCacheResolver→com.apollographql.apollo.api.Executable.Variables
- Direction
- cache.normalized.api uses api.Executable, so a change to api.Executable can break cache.normalized.api, while a change to cache.normalized.api can't break api.Executable.
- Position
- Below the diagonal: cache.normalized.api uses a module listed above it, which is the healthy direction.
24→17 cache.normalized.api uses api✕
- Connections
- 9 pairs of types, where a type in cache.normalized.api uses a type in api.
- The types involved
com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorContext→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.CacheKeyResolver→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.CacheResolver→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.DefaultCacheResolver→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.ExpireDateCacheResolver→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.FieldPolicyCacheResolver→com.apollographql.apollo.api.CompiledFieldcom.apollographql.apollo.cache.normalized.api.OperationCacheExtensionsKt→com.apollographql.apollo.api.Adaptercom.apollographql.apollo.cache.normalized.api.OperationCacheExtensionsKt→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.cache.normalized.api.ReceiveDateCacheResolver→com.apollographql.apollo.api.CompiledField
- Direction
- cache.normalized.api uses api, so a change to api can break cache.normalized.api, while a change to cache.normalized.api can't break api.
- Position
- Below the diagonal: cache.normalized.api uses a module listed above it, which is the healthy direction.
24→19 cache.normalized.api uses cache.normalized.api.internal✕
- Connections
- 2 pairs of types, where a type in cache.normalized.api uses a type in cache.normalized.api.internal.
- The types involved
com.apollographql.apollo.cache.normalized.api.MemoryCache→com.apollographql.apollo.cache.normalized.api.internal.CacheLockcom.apollographql.apollo.cache.normalized.api.MemoryCache→com.apollographql.apollo.cache.normalized.api.internal.LruCache
- Direction
- cache.normalized.api uses cache.normalized.api.internal, so a change to cache.normalized.api.internal can break cache.normalized.api, while a change to cache.normalized.api can't break cache.normalized.api.internal.
- Position
- Below the diagonal: cache.normalized.api uses a module listed above it, which is the healthy direction.
25→2 execution uses ast✕
- Connections
- 24 pairs of types, where a type in execution uses a type in ast.
- The types involved
com.apollographql.apollo.execution.BooleanCoercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.Coercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.CoercingKt→com.apollographql.apollo.ast.GQLTypeDefinitioncom.apollographql.apollo.execution.CoercingKt→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.ErrorPersistedDocument→com.apollographql.apollo.ast.Issuecom.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.ast.ParserOptionscom.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.ExecutableSchemaKt→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.execution.ExecutableSchemaKt→com.apollographql.apollo.ast.GQLDocumentcom.apollographql.apollo.execution.ExecutableSchemaKt→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.FloatCoercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.IntCoercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.JsonCoercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.OperationInfo→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.execution.OperationInfo→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.execution.OperationInfo→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.PreparedRequest→com.apollographql.apollo.ast.GQLFragmentDefinitioncom.apollographql.apollo.execution.PreparedRequest→com.apollographql.apollo.ast.GQLSelectioncom.apollographql.apollo.execution.ResolveInfo→com.apollographql.apollo.ast.GQLFieldcom.apollographql.apollo.execution.ResolveInfo→com.apollographql.apollo.ast.GQLFieldDefinitioncom.apollographql.apollo.execution.ResolveInfo→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.ResolveTypeInfo→com.apollographql.apollo.ast.Schemacom.apollographql.apollo.execution.StringCoercing→com.apollographql.apollo.ast.GQLValuecom.apollographql.apollo.execution.ValidPersistedDocument→com.apollographql.apollo.ast.GQLDocument
- Direction
- execution uses ast, so a change to ast can break execution, while a change to execution can't break ast.
- Position
- Below the diagonal: execution uses a module listed above it, which is the healthy direction.
25→7 execution uses api.json✕
- Connections
- 2 pairs of types, where a type in execution uses a type in api.json.
- The types involved
com.apollographql.apollo.execution.GraphQLResponse→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.execution.GraphQLResponseKt→com.apollographql.apollo.api.json.JsonWriter
- Direction
- execution uses api.json, so a change to api.json can break execution, while a change to execution can't break api.json.
- Position
- Below the diagonal: execution uses a module listed above it, which is the healthy direction.
25→17 execution uses api✕
- Connections
- 13 pairs of types, where a type in execution uses a type in api.
- The types involved
com.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.execution.ExecutableSchemaKt→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.execution.GraphQLRequest→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.execution.GraphQLResponse→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.GraphQLResponseKt→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.OperationInfo→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.execution.PreparedRequest→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.execution.ResolveInfo→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.execution.ResolveInfo→com.apollographql.apollo.api.Optionalcom.apollographql.apollo.execution.SubscriptionError→com.apollographql.apollo.api.Errorcom.apollographql.apollo.execution.ValuesKt→com.apollographql.apollo.api.Error
- Direction
- execution uses api, so a change to api can break execution, while a change to execution can't break api.
- Position
- Below the diagonal: execution uses a module listed above it, which is the healthy direction.
25→21 execution uses execution.internal✕
- Connections
- 3 pairs of types, where a type in execution uses a type in execution.internal.
- The types involved
com.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.execution.internal.Eithercom.apollographql.apollo.execution.ExecutableSchema→com.apollographql.apollo.execution.internal.OperationContextcom.apollographql.apollo.execution.InMemoryPersistedDocumentCache→com.apollographql.apollo.execution.internal.LruCache
- Direction
- execution uses execution.internal, so a change to execution.internal can break execution, while a change to execution can't break execution.internal.
- Position
- Below the diagonal: execution uses a module listed above it, which is the healthy direction.
26→5 network.http uses api.ExecutionContext✕
- Connections
- 4 pairs of types, where a type in network.http uses a type in api.ExecutionContext.
- The types involved
com.apollographql.apollo.network.http.HttpInfo→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.network.http.HttpInfo→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.network.http.IsFromHttpCache→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.network.http.IsFromHttpCache→com.apollographql.apollo.api.ExecutionContext.Key
- Direction
- network.http uses api.ExecutionContext, so a change to api.ExecutionContext can break network.http, while a change to network.http can't break api.ExecutionContext.
- Position
- Below the diagonal: network.http uses a module listed above it, which is the healthy direction.
26→11 network.http uses api.http✕
- Connections
- 36 pairs of types, where a type in network.http uses a type in api.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.network.http.ApolloClientAwarenessInterceptor→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.ApolloClientAwarenessInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.ApolloClientAwarenessInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.AppleHttpEngine→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.AppleHttpEngine→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.BatchingHttpInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.BatchingHttpInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.DefaultHttpInterceptorChain→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.DefaultHttpInterceptorChain→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HeadersInterceptor→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.HeadersInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HeadersInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpCall→com.apollographql.apollo.api.http.HttpBodycom.apollographql.apollo.network.http.HttpCall→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.HttpCall→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.network.http.HttpCall→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpEngine→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpEngine→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpInfo→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.HttpInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpInterceptorChain→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpInterceptorChain→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.http.HttpRequestComposer
- Direction
- network.http uses api.http, so a change to api.http can break network.http, while a change to network.http can't break api.http.
- Position
- Below the diagonal: network.http uses a module listed above it, which is the healthy direction.
26→16 network.http uses exception✕
- Connections
- 1 pair of types, where a type in network.http uses a type in exception.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.exception.ApolloException
- Direction
- network.http uses exception, so a change to exception can break network.http, while a change to network.http can't break exception.
- Position
- Below the diagonal: network.http uses a module listed above it, which is the healthy direction.
26→17 network.http uses api✕
- Connections
- 5 pairs of types, where a type in network.http uses a type in api.
- The types involved
com.apollographql.apollo.network.http.HttpCall→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.api.Operation
- Direction
- network.http uses api, so a change to api can break network.http, while a change to network.http can't break api.
- Position
- Below the diagonal: network.http uses a module listed above it, which is the healthy direction.
26→22 network.http uses internal.incremental✕
- Connections
- 1 pair of types, where a type in network.http uses a type in internal.incremental.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.internal.incremental.IncrementalDeliveryProtocolImpl
- Direction
- network.http uses internal.incremental, so a change to internal.incremental can break network.http, while a change to network.http can't break internal.incremental.
- Position
- Below the diagonal: network.http uses a module listed above it, which is the healthy direction.
26→27 network.http uses network.http.HttpNetworkTransport part of a loop✕
- Connections
- 2 pairs of types, where a type in network.http uses a type in network.http.HttpNetworkTransport.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.network.http.HttpNetworkTransport.Buildercom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.network.http.HttpNetworkTransport.EngineInterceptor
- Direction
- network.http uses network.http.HttpNetworkTransport, so a change to network.http.HttpNetworkTransport can break network.http, while a change to network.http can't break network.http.HttpNetworkTransport.
- 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→28 network.http uses network part of a loop✕
- Connections
- 2 pairs of types, where a type in network.http uses a type in network.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.network.IncrementalDeliveryProtocolcom.apollographql.apollo.network.http.HttpNetworkTransport→com.apollographql.apollo.network.NetworkTransport
- Direction
- network.http uses network, so a change to network can break network.http, while a change to network.http can't break network.
- 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→11 network.http.HttpNetworkTransport uses api.http✕
- Connections
- 7 pairs of types, where a type in network.http.HttpNetworkTransport uses a type in api.http.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.api.http.HttpRequestComposercom.apollographql.apollo.network.http.HttpNetworkTransport.EngineInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpNetworkTransport.EngineInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.network.http.HttpNetworkTransport.TransportHeadersInterceptor→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.http.HttpNetworkTransport.TransportHeadersInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.network.http.HttpNetworkTransport.TransportHeadersInterceptor→com.apollographql.apollo.api.http.HttpResponse
- Direction
- network.http.HttpNetworkTransport uses api.http, so a change to api.http can break network.http.HttpNetworkTransport, while a change to network.http.HttpNetworkTransport can't break api.http.
- Position
- Below the diagonal: network.http.HttpNetworkTransport uses a module listed above it, which is the healthy direction.
27→26 network.http.HttpNetworkTransport uses network.http✕
- Connections
- 7 pairs of types, where a type in network.http.HttpNetworkTransport uses a type in network.http.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.network.http.HttpEnginecom.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.network.http.HttpInterceptorcom.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.network.http.HttpNetworkTransportcom.apollographql.apollo.network.http.HttpNetworkTransport.EngineInterceptor→com.apollographql.apollo.network.http.HttpInterceptorcom.apollographql.apollo.network.http.HttpNetworkTransport.EngineInterceptor→com.apollographql.apollo.network.http.HttpInterceptorChaincom.apollographql.apollo.network.http.HttpNetworkTransport.TransportHeadersInterceptor→com.apollographql.apollo.network.http.HttpInterceptorcom.apollographql.apollo.network.http.HttpNetworkTransport.TransportHeadersInterceptor→com.apollographql.apollo.network.http.HttpInterceptorChain
- Direction
- network.http.HttpNetworkTransport uses network.http, so a change to network.http can break network.http.HttpNetworkTransport, while a change to network.http.HttpNetworkTransport can't break network.http.
- Position
- Below the diagonal: network.http.HttpNetworkTransport uses a module listed above it, which is the healthy direction.
27→28 network.http.HttpNetworkTransport uses network part of a loop✕
- Connections
- 1 pair of types, where a type in network.http.HttpNetworkTransport uses a type in network.
- The types involved
com.apollographql.apollo.network.http.HttpNetworkTransport.Builder→com.apollographql.apollo.network.IncrementalDeliveryProtocol
- Direction
- network.http.HttpNetworkTransport uses network, so a change to network can break network.http.HttpNetworkTransport, while a change to network.http.HttpNetworkTransport can't break network.
- 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→17 network uses api✕
- Connections
- 2 pairs of types, where a type in network uses a type in api.
- The types involved
com.apollographql.apollo.network.NetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.NetworkTransport→com.apollographql.apollo.api.ApolloResponse
- Direction
- network uses api, so a change to api can break network, while a change to network can't break api.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
28→27 network uses network.http.HttpNetworkTransport✕
- Connections
- 1 pair of types, where a type in network uses a type in network.http.HttpNetworkTransport.
- The types involved
com.apollographql.apollo.network.OkHttpExtensionsKt→com.apollographql.apollo.network.http.HttpNetworkTransport.Builder
- Direction
- network uses network.http.HttpNetworkTransport, so a change to network.http.HttpNetworkTransport can break network, while a change to network can't break network.http.HttpNetworkTransport.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
28→33 network uses ApolloClient part of a loop✕
- Connections
- 1 pair of types, where a type in network uses a type in ApolloClient.
- The types involved
com.apollographql.apollo.network.OkHttpExtensionsKt→com.apollographql.apollo.ApolloClient.Builder
- Direction
- network uses ApolloClient, so a change to ApolloClient can break network, while a change to network can't break ApolloClient.
- 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→11 interceptor uses api.http✕
- Connections
- 1 pair of types, where a type in interceptor uses a type in api.http.
- The types involved
com.apollographql.apollo.interceptor.AutoPersistedQueryInterceptor→com.apollographql.apollo.api.http.HttpMethod
- Direction
- interceptor uses api.http, so a change to api.http can break interceptor, while a change to interceptor can't break api.http.
- Position
- Below the diagonal: interceptor uses a module listed above it, which is the healthy direction.
29→17 interceptor uses api✕
- Connections
- 15 pairs of types, where a type in interceptor uses a type in api.
- The types involved
com.apollographql.apollo.interceptor.ApolloInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.ApolloInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.ApolloInterceptorChain→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.ApolloInterceptorChain→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.AutoPersistedQueryInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.AutoPersistedQueryInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.AutoPersistedQueryInterceptor→com.apollographql.apollo.api.Errorcom.apollographql.apollo.interceptor.DefaultInterceptorChain→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.DefaultInterceptorChain→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.DefaultRetryOnErrorInterceptorImpl→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.DefaultRetryOnErrorInterceptorImpl→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.NetworkInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.NetworkInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.interceptor.RetryContext→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.interceptor.RetryContext→com.apollographql.apollo.api.ApolloResponse
- Direction
- interceptor uses api, so a change to api can break interceptor, while a change to interceptor can't break api.
- Position
- Below the diagonal: interceptor uses a module listed above it, which is the healthy direction.
29→28 interceptor uses network✕
- Connections
- 4 pairs of types, where a type in interceptor uses a type in network.
- The types involved
com.apollographql.apollo.interceptor.DefaultRetryOnErrorInterceptorImpl→com.apollographql.apollo.network.NetworkMonitorcom.apollographql.apollo.interceptor.NetworkInterceptor→com.apollographql.apollo.network.NetworkTransportcom.apollographql.apollo.interceptor.RetryContext→com.apollographql.apollo.network.NetworkMonitorcom.apollographql.apollo.interceptor.RetryOnErrorInterceptorKt→com.apollographql.apollo.network.NetworkMonitor
- Direction
- interceptor uses network, so a change to network can break interceptor, while a change to interceptor can't break network.
- Position
- Below the diagonal: interceptor uses a module listed above it, which is the healthy direction.
30→11 network.websocket uses api.http✕
- Connections
- 10 pairs of types, where a type in network.websocket uses a type in api.http.
- The types involved
com.apollographql.apollo.network.websocket.AppleWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.JsWebSocket→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.JsWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.JvmWebSocket→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.JvmWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.LinuxWebSocket→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.LinuxWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.WasmJsWebSocket→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.WasmJsWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.websocket.WebSocketEngine→com.apollographql.apollo.api.http.HttpHeader
- Direction
- network.websocket uses api.http, so a change to api.http can break network.websocket, while a change to network.websocket can't break api.http.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
30→16 network.websocket uses exception✕
- Connections
- 4 pairs of types, where a type in network.websocket uses a type in exception.
- The types involved
com.apollographql.apollo.network.websocket.DefaultOperationListener→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.WebSocketListener→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.WebSocketNetworkTransport→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.network.websocket.WebSocketNetworkTransportKt→com.apollographql.apollo.exception.ApolloException
- Direction
- network.websocket uses exception, so a change to exception can break network.websocket, while a change to network.websocket can't break exception.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
30→17 network.websocket uses api✕
- Connections
- 14 pairs of types, where a type in network.websocket uses a type in api.
- The types involved
com.apollographql.apollo.network.websocket.AppSyncWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.DefaultOperationListener→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.DefaultOperationListener→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.websocket.DefaultSubscriptionParser→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.DefaultSubscriptionParser→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.websocket.DefaultSubscriptionParser→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.network.websocket.DefaultSubscriptionParserFactory→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.GraphQLWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.SubscriptionParser→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.websocket.SubscriptionParserFactory→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.SubscriptionWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.WebSocketNetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.websocket.WebSocketNetworkTransport→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.websocket.WsProtocol→com.apollographql.apollo.api.ApolloRequest
- Direction
- network.websocket uses api, so a change to api can break network.websocket, while a change to network.websocket can't break api.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
30→22 network.websocket uses internal.incremental✕
- Connections
- 3 pairs of types, where a type in network.websocket uses a type in internal.incremental.
- The types involved
com.apollographql.apollo.network.websocket.DefaultSubscriptionParser→com.apollographql.apollo.internal.incremental.IncrementalDeliveryProtocolImplcom.apollographql.apollo.network.websocket.DefaultSubscriptionParser→com.apollographql.apollo.internal.incremental.IncrementalResultsMergercom.apollographql.apollo.network.websocket.DefaultSubscriptionParserFactory→com.apollographql.apollo.internal.incremental.IncrementalDeliveryProtocolImpl
- Direction
- network.websocket uses internal.incremental, so a change to internal.incremental can break network.websocket, while a change to network.websocket can't break internal.incremental.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
30→23 network.websocket uses network.websocket.internal✕
- Connections
- 2 pairs of types, where a type in network.websocket uses a type in network.websocket.internal.
- The types involved
com.apollographql.apollo.network.websocket.DefaultOperationListener→com.apollographql.apollo.network.websocket.internal.OperationListenercom.apollographql.apollo.network.websocket.WebSocketNetworkTransport→com.apollographql.apollo.network.websocket.internal.WebSocketPool
- Direction
- network.websocket uses network.websocket.internal, so a change to network.websocket.internal can break network.websocket, while a change to network.websocket can't break network.websocket.internal.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
30→28 network.websocket uses network✕
- Connections
- 1 pair of types, where a type in network.websocket uses a type in network.
- The types involved
com.apollographql.apollo.network.websocket.WebSocketNetworkTransport→com.apollographql.apollo.network.NetworkTransport
- Direction
- network.websocket uses network, so a change to network can break network.websocket, while a change to network.websocket can't break network.
- Position
- Below the diagonal: network.websocket uses a module listed above it, which is the healthy direction.
31→10 network.ws uses network.ws.WsProtocol✕
- Connections
- 6 pairs of types, where a type in network.ws uses a type in network.ws.WsProtocol.
- The types involved
com.apollographql.apollo.network.ws.AppSyncWsProtocol→com.apollographql.apollo.network.ws.WsProtocol.Listenercom.apollographql.apollo.network.ws.GraphQLWsProtocol→com.apollographql.apollo.network.ws.WsProtocol.Listenercom.apollographql.apollo.network.ws.SubscriptionWsProtocol→com.apollographql.apollo.network.ws.WsProtocol.Listenercom.apollographql.apollo.network.ws.SubscriptionWsProtocolAdapter→com.apollographql.apollo.network.ws.WsProtocol.Listenercom.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.network.ws.WsProtocol.Factorycom.apollographql.apollo.network.ws.WsProtocol→com.apollographql.apollo.network.ws.WsProtocol.Listener
- Direction
- network.ws uses network.ws.WsProtocol, so a change to network.ws.WsProtocol can break network.ws, while a change to network.ws can't break network.ws.WsProtocol.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
31→11 network.ws uses api.http✕
- Connections
- 4 pairs of types, where a type in network.ws uses a type in api.http.
- The types involved
com.apollographql.apollo.network.ws.DefaultWebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.ws.GraphQLWsProtocol→com.apollographql.apollo.api.http.WebSocketPayloadComposercom.apollographql.apollo.network.ws.WebSocketEngine→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.api.http.HttpHeader
- Direction
- network.ws uses api.http, so a change to api.http can break network.ws, while a change to network.ws can't break api.http.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
31→16 network.ws uses exception✕
- Connections
- 1 pair of types, where a type in network.ws uses a type in exception.
- The types involved
com.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.exception.ApolloException
- Direction
- network.ws uses exception, so a change to exception can break network.ws, while a change to network.ws can't break exception.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
31→17 network.ws uses api✕
- Connections
- 7 pairs of types, where a type in network.ws uses a type in api.
- The types involved
com.apollographql.apollo.network.ws.AppSyncWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.ws.GraphQLWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.ws.SubscriptionWsProtocol→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.ws.SubscriptionWsProtocolAdapter→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.network.ws.WsProtocol→com.apollographql.apollo.api.ApolloRequest
- Direction
- network.ws uses api, so a change to api can break network.ws, while a change to network.ws can't break api.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
31→22 network.ws uses internal.incremental✕
- Connections
- 1 pair of types, where a type in network.ws uses a type in internal.incremental.
- The types involved
com.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.internal.incremental.IncrementalDeliveryProtocolImpl
- Direction
- network.ws uses internal.incremental, so a change to internal.incremental can break network.ws, while a change to network.ws can't break internal.incremental.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
31→28 network.ws uses network✕
- Connections
- 1 pair of types, where a type in network.ws uses a type in network.
- The types involved
com.apollographql.apollo.network.ws.WebSocketNetworkTransport→com.apollographql.apollo.network.NetworkTransport
- Direction
- network.ws uses network, so a change to network can break network.ws, while a change to network.ws can't break network.
- Position
- Below the diagonal: network.ws uses a module listed above it, which is the healthy direction.
32→6 testing uses api.Operation✕
- Connections
- 1 pair of types, where a type in testing uses a type in api.Operation.
- The types involved
com.apollographql.apollo.testing.MapTestNetworkTransport→com.apollographql.apollo.api.Operation.Data
- Direction
- testing uses api.Operation, so a change to api.Operation can break testing, while a change to testing can't break api.Operation.
- Position
- Below the diagonal: testing uses a module listed above it, which is the healthy direction.
32→7 testing uses api.json✕
- Connections
- 1 pair of types, where a type in testing uses a type in api.json.
- The types involved
com.apollographql.apollo.testing.FilesystemCommonKt→com.apollographql.apollo.api.json.JsonReader
- Direction
- testing uses api.json, so a change to api.json can break testing, while a change to testing can't break api.json.
- Position
- Below the diagonal: testing uses a module listed above it, which is the healthy direction.
32→17 testing uses api✕
- Connections
- 8 pairs of types, where a type in testing uses a type in api.
- The types involved
com.apollographql.apollo.testing.MapTestNetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.testing.MapTestNetworkTransport→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.testing.MapTestNetworkTransport→com.apollographql.apollo.api.Operationcom.apollographql.apollo.testing.QueueTestNetworkTransport→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.testing.QueueTestNetworkTransport→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.testing.TestNetworkTransportKt→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.testing.TestNetworkTransportKt→com.apollographql.apollo.api.Errorcom.apollographql.apollo.testing.TestNetworkTransportKt→com.apollographql.apollo.api.Operation
- Direction
- testing uses api, so a change to api can break testing, while a change to testing can't break api.
- Position
- Below the diagonal: testing uses a module listed above it, which is the healthy direction.
32→28 testing uses network✕
- Connections
- 2 pairs of types, where a type in testing uses a type in network.
- The types involved
com.apollographql.apollo.testing.MapTestNetworkTransport→com.apollographql.apollo.network.NetworkTransportcom.apollographql.apollo.testing.QueueTestNetworkTransport→com.apollographql.apollo.network.NetworkTransport
- Direction
- testing uses network, so a change to network can break testing, while a change to testing can't break network.
- Position
- Below the diagonal: testing uses a module listed above it, which is the healthy direction.
33→10 ApolloClient uses network.ws.WsProtocol✕
- Connections
- 1 pair of types, where a type in ApolloClient uses a type in network.ws.WsProtocol.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.network.ws.WsProtocol.Factory
- Direction
- ApolloClient uses network.ws.WsProtocol, so a change to network.ws.WsProtocol can break ApolloClient, while a change to ApolloClient can't break network.ws.WsProtocol.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→11 ApolloClient uses api.http✕
- Connections
- 2 pairs of types, where a type in ApolloClient uses a type in api.http.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.http.HttpMethod
- Direction
- ApolloClient uses api.http, so a change to api.http can break ApolloClient, while a change to ApolloClient can't break api.http.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→17 ApolloClient uses api✕
- Connections
- 6 pairs of types, where a type in ApolloClient uses a type in api.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.Adaptercom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.CustomScalarTypecom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.api.MutableExecutionOptions
- Direction
- ApolloClient uses api, so a change to api can break ApolloClient, while a change to ApolloClient can't break api.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→26 ApolloClient uses network.http✕
- Connections
- 2 pairs of types, where a type in ApolloClient uses a type in network.http.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.network.http.HttpEnginecom.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.network.http.HttpInterceptor
- Direction
- ApolloClient uses network.http, so a change to network.http can break ApolloClient, while a change to ApolloClient can't break network.http.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→28 ApolloClient uses network✕
- Connections
- 1 pair of types, where a type in ApolloClient uses a type in network.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.network.NetworkTransport
- Direction
- ApolloClient uses network, so a change to network can break ApolloClient, while a change to ApolloClient can't break network.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→29 ApolloClient uses interceptor✕
- Connections
- 1 pair of types, where a type in ApolloClient uses a type in interceptor.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.interceptor.ApolloInterceptor
- Direction
- ApolloClient uses interceptor, so a change to interceptor can break ApolloClient, while a change to ApolloClient can't break interceptor.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→31 ApolloClient uses network.ws✕
- Connections
- 1 pair of types, where a type in ApolloClient uses a type in network.ws.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.network.ws.WebSocketEngine
- Direction
- ApolloClient uses network.ws, so a change to network.ws can break ApolloClient, while a change to ApolloClient can't break network.ws.
- Position
- Below the diagonal: ApolloClient uses a module listed above it, which is the healthy direction.
33→35 ApolloClient uses com.apollographql.apollo part of a loop✕
- Connections
- 1 pair of types, where a type in ApolloClient uses a type in com.apollographql.apollo.
- The types involved
com.apollographql.apollo.ApolloClient.Builder→com.apollographql.apollo.ApolloClient
- Direction
- ApolloClient uses com.apollographql.apollo, so a change to com.apollographql.apollo can break ApolloClient, while a change to ApolloClient can't break com.apollographql.apollo.
- 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.
34→11 cache.http.internal uses api.http✕
- Connections
- 2 pairs of types, where a type in cache.http.internal uses a type in api.http.
- The types involved
com.apollographql.apollo.cache.http.internal.CacheHeadersHttpInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.cache.http.internal.CacheHeadersHttpInterceptor→com.apollographql.apollo.api.http.HttpResponse
- Direction
- cache.http.internal uses api.http, so a change to api.http can break cache.http.internal, while a change to cache.http.internal can't break api.http.
- Position
- Below the diagonal: cache.http.internal uses a module listed above it, which is the healthy direction.
34→17 cache.http.internal uses api✕
- Connections
- 2 pairs of types, where a type in cache.http.internal uses a type in api.
- The types involved
com.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.api.ApolloResponse
- Direction
- cache.http.internal uses api, so a change to api can break cache.http.internal, while a change to cache.http.internal can't break api.
- Position
- Below the diagonal: cache.http.internal uses a module listed above it, which is the healthy direction.
34→26 cache.http.internal uses network.http✕
- Connections
- 2 pairs of types, where a type in cache.http.internal uses a type in network.http.
- The types involved
com.apollographql.apollo.cache.http.internal.CacheHeadersHttpInterceptor→com.apollographql.apollo.network.http.HttpInterceptorcom.apollographql.apollo.cache.http.internal.CacheHeadersHttpInterceptor→com.apollographql.apollo.network.http.HttpInterceptorChain
- Direction
- cache.http.internal uses network.http, so a change to network.http can break cache.http.internal, while a change to cache.http.internal can't break network.http.
- Position
- Below the diagonal: cache.http.internal uses a module listed above it, which is the healthy direction.
34→29 cache.http.internal uses interceptor✕
- Connections
- 2 pairs of types, where a type in cache.http.internal uses a type in interceptor.
- The types involved
com.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChain
- Direction
- cache.http.internal uses interceptor, so a change to interceptor can break cache.http.internal, while a change to cache.http.internal can't break interceptor.
- Position
- Below the diagonal: cache.http.internal uses a module listed above it, which is the healthy direction.
34→36 cache.http.internal uses cache.http part of a loop✕
- Connections
- 2 pairs of types, where a type in cache.http.internal uses a type in cache.http.
- The types involved
com.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.cache.http.CachingHttpInterceptorcom.apollographql.apollo.cache.http.internal.HttpCacheApolloInterceptor→com.apollographql.apollo.cache.http.HttpFetchPolicy
- Direction
- cache.http.internal uses cache.http, so a change to cache.http can break cache.http.internal, while a change to cache.http.internal can't break cache.http.
- 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.
35→5 com.apollographql.apollo uses api.ExecutionContext✕
- Connections
- 8 pairs of types, where a type in com.apollographql.apollo uses a type in api.ExecutionContext.
- The types involved
com.apollographql.apollo.AutoPersistedQueryInfo→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.AutoPersistedQueryInfo→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.CacheDumpProviderContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.CacheDumpProviderContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.ConcurrencyInfo→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.ConcurrencyInfo→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.ConflateResponsesContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.ConflateResponsesContext→com.apollographql.apollo.api.ExecutionContext.Key
- Direction
- com.apollographql.apollo uses api.ExecutionContext, so a change to api.ExecutionContext can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break api.ExecutionContext.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→11 com.apollographql.apollo uses api.http✕
- Connections
- 4 pairs of types, where a type in com.apollographql.apollo uses a type in api.http.
- The types involved
com.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.http.HttpHeadercom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.http.HttpMethod
- Direction
- com.apollographql.apollo uses api.http, so a change to api.http can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break api.http.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→13 com.apollographql.apollo uses api.ApolloRequest✕
- Connections
- 1 pair of types, where a type in com.apollographql.apollo uses a type in api.ApolloRequest.
- The types involved
com.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.ApolloRequest.Builder
- Direction
- com.apollographql.apollo uses api.ApolloRequest, so a change to api.ApolloRequest can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break api.ApolloRequest.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→17 com.apollographql.apollo uses api✕
- Connections
- 13 pairs of types, where a type in com.apollographql.apollo uses a type in api.
- The types involved
com.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.MutableExecutionOptionscom.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.OnErrorcom.apollographql.apollo.ApolloCall→com.apollographql.apollo.api.Operationcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.ExecutionContextcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.ExecutionOptionscom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.Mutationcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.Querycom.apollographql.apollo.ApolloClient→com.apollographql.apollo.api.Subscription
- Direction
- com.apollographql.apollo uses api, so a change to api can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break api.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→28 com.apollographql.apollo uses network✕
- Connections
- 1 pair of types, where a type in com.apollographql.apollo uses a type in network.
- The types involved
com.apollographql.apollo.ApolloClient→com.apollographql.apollo.network.NetworkTransport
- Direction
- com.apollographql.apollo uses network, so a change to network can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break network.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→29 com.apollographql.apollo uses interceptor✕
- Connections
- 2 pairs of types, where a type in com.apollographql.apollo uses a type in interceptor.
- The types involved
com.apollographql.apollo.ApolloClient→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.ApolloClient→com.apollographql.apollo.interceptor.NetworkInterceptor
- Direction
- com.apollographql.apollo uses interceptor, so a change to interceptor can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break interceptor.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
35→33 com.apollographql.apollo uses ApolloClient✕
- Connections
- 1 pair of types, where a type in com.apollographql.apollo uses a type in ApolloClient.
- The types involved
com.apollographql.apollo.ApolloClient→com.apollographql.apollo.ApolloClient.Builder
- Direction
- com.apollographql.apollo uses ApolloClient, so a change to ApolloClient can break com.apollographql.apollo, while a change to com.apollographql.apollo can't break ApolloClient.
- Position
- Below the diagonal: com.apollographql.apollo uses a module listed above it, which is the healthy direction.
36→5 cache.http uses api.ExecutionContext✕
- Connections
- 2 pairs of types, where a type in cache.http uses a type in api.ExecutionContext.
- The types involved
com.apollographql.apollo.cache.http.HttpFetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.http.HttpFetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Key
- Direction
- cache.http uses api.ExecutionContext, so a change to api.ExecutionContext can break cache.http, while a change to cache.http can't break api.ExecutionContext.
- Position
- Below the diagonal: cache.http uses a module listed above it, which is the healthy direction.
36→11 cache.http uses api.http✕
- Connections
- 4 pairs of types, where a type in cache.http uses a type in api.http.
- The types involved
com.apollographql.apollo.cache.http.ApolloHttpCache→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.cache.http.CachingHttpInterceptor→com.apollographql.apollo.api.http.HttpRequestcom.apollographql.apollo.cache.http.CachingHttpInterceptor→com.apollographql.apollo.api.http.HttpResponsecom.apollographql.apollo.cache.http.DiskLruHttpCache→com.apollographql.apollo.api.http.HttpResponse
- Direction
- cache.http uses api.http, so a change to api.http can break cache.http, while a change to cache.http can't break api.http.
- Position
- Below the diagonal: cache.http uses a module listed above it, which is the healthy direction.
36→26 cache.http uses network.http✕
- Connections
- 2 pairs of types, where a type in cache.http uses a type in network.http.
- The types involved
com.apollographql.apollo.cache.http.CachingHttpInterceptor→com.apollographql.apollo.network.http.HttpInterceptorcom.apollographql.apollo.cache.http.CachingHttpInterceptor→com.apollographql.apollo.network.http.HttpInterceptorChain
- Direction
- cache.http uses network.http, so a change to network.http can break cache.http, while a change to cache.http can't break network.http.
- Position
- Below the diagonal: cache.http uses a module listed above it, which is the healthy direction.
36→33 cache.http uses ApolloClient✕
- Connections
- 1 pair of types, where a type in cache.http uses a type in ApolloClient.
- The types involved
com.apollographql.apollo.cache.http.HttpCacheExtensionsKt→com.apollographql.apollo.ApolloClient.Builder
- Direction
- cache.http uses ApolloClient, so a change to ApolloClient can break cache.http, while a change to cache.http can't break ApolloClient.
- Position
- Below the diagonal: cache.http uses a module listed above it, which is the healthy direction.
36→34 cache.http uses cache.http.internal✕
- Connections
- 1 pair of types, where a type in cache.http uses a type in cache.http.internal.
- The types involved
com.apollographql.apollo.cache.http.DiskLruHttpCache→com.apollographql.apollo.cache.http.internal.DiskLruCache
- Direction
- cache.http uses cache.http.internal, so a change to cache.http.internal can break cache.http, while a change to cache.http can't break cache.http.internal.
- Position
- Below the diagonal: cache.http uses a module listed above it, which is the healthy direction.
37→5 cache.normalized uses api.ExecutionContext✕
- Connections
- 26 pairs of types, where a type in cache.normalized uses a type in api.ExecutionContext. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.apollographql.apollo.cache.normalized.CacheHeadersContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.CacheHeadersContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.CacheInfo→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.CacheInfo→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.DoNotStoreContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.DoNotStoreContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.FetchFromCacheContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.FetchFromCacheContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.FetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.FetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.MemoryCacheOnlyContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.MemoryCacheOnlyContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.OptimisticUpdatesContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.OptimisticUpdatesContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.RefetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.RefetchPolicyContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.StoreExpirationDateContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.StoreExpirationDateContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.StorePartialResponsesContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.StorePartialResponsesContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.StoreReceiveDateContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.StoreReceiveDateContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.WatchContext→com.apollographql.apollo.api.ExecutionContext.Elementcom.apollographql.apollo.cache.normalized.WatchContext→com.apollographql.apollo.api.ExecutionContext.Keycom.apollographql.apollo.cache.normalized.WriteToCacheAsynchronouslyContext→com.apollographql.apollo.api.ExecutionContext.Element
- Direction
- cache.normalized uses api.ExecutionContext, so a change to api.ExecutionContext can break cache.normalized, while a change to cache.normalized can't break api.ExecutionContext.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→13 cache.normalized uses api.ApolloRequest✕
- Connections
- 1 pair of types, where a type in cache.normalized uses a type in api.ApolloRequest.
- The types involved
com.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.api.ApolloRequest.Builder
- Direction
- cache.normalized uses api.ApolloRequest, so a change to api.ApolloRequest can break cache.normalized, while a change to cache.normalized can't break api.ApolloRequest.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→16 cache.normalized uses exception✕
- Connections
- 2 pairs of types, where a type in cache.normalized uses a type in exception.
- The types involved
com.apollographql.apollo.cache.normalized.CacheInfo→com.apollographql.apollo.exception.ApolloExceptioncom.apollographql.apollo.cache.normalized.CacheInfo→com.apollographql.apollo.exception.CacheMissException
- Direction
- cache.normalized uses exception, so a change to exception can break cache.normalized, while a change to cache.normalized can't break exception.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→17 cache.normalized uses api✕
- Connections
- 15 pairs of types, where a type in cache.normalized uses a type in api.
- The types involved
com.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.api.Fragmentcom.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.api.Operationcom.apollographql.apollo.cache.normalized.CacheInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.CacheInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.CacheMissLoggingInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.CacheMissLoggingInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.api.MutableExecutionOptionscom.apollographql.apollo.cache.normalized.DefaultInterceptorChain→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.DefaultInterceptorChain→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.FetchPolicyRouterInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.FetchPolicyRouterInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.StoreExpirationInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.StoreExpirationInterceptor→com.apollographql.apollo.api.ApolloResponse
- Direction
- cache.normalized uses api, so a change to api can break cache.normalized, while a change to cache.normalized can't break api.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→24 cache.normalized uses cache.normalized.api✕
- Connections
- 12 pairs of types, where a type in cache.normalized uses a type in cache.normalized.api.
- The types involved
com.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.cache.normalized.api.CacheKeycom.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.cache.normalized.api.NormalizedCachecom.apollographql.apollo.cache.normalized.ApolloStore→com.apollographql.apollo.cache.normalized.api.Recordcom.apollographql.apollo.cache.normalized.ApolloStoreKt→com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorcom.apollographql.apollo.cache.normalized.ApolloStoreKt→com.apollographql.apollo.cache.normalized.api.CacheResolvercom.apollographql.apollo.cache.normalized.ApolloStoreKt→com.apollographql.apollo.cache.normalized.api.NormalizedCacheFactorycom.apollographql.apollo.cache.normalized.CacheHeadersContext→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorcom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.cache.normalized.api.CacheResolvercom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.cache.normalized.api.NormalizedCacheFactory
- Direction
- cache.normalized uses cache.normalized.api, so a change to cache.normalized.api can break cache.normalized, while a change to cache.normalized can't break cache.normalized.api.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→29 cache.normalized uses interceptor✕
- Connections
- 14 pairs of types, where a type in cache.normalized uses a type in interceptor.
- The types involved
com.apollographql.apollo.cache.normalized.CacheInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.CacheInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChaincom.apollographql.apollo.cache.normalized.CacheMissLoggingInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.CacheMissLoggingInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChaincom.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.DefaultInterceptorChain→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.DefaultInterceptorChain→com.apollographql.apollo.interceptor.ApolloInterceptorChaincom.apollographql.apollo.cache.normalized.FetchPolicyContext→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.FetchPolicyInterceptorsKt→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.FetchPolicyRouterInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.FetchPolicyRouterInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChaincom.apollographql.apollo.cache.normalized.RefetchPolicyContext→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.StoreExpirationInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.StoreExpirationInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChain
- Direction
- cache.normalized uses interceptor, so a change to interceptor can break cache.normalized, while a change to cache.normalized can't break interceptor.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→33 cache.normalized uses ApolloClient✕
- Connections
- 1 pair of types, where a type in cache.normalized uses a type in ApolloClient.
- The types involved
com.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.ApolloClient.Builder
- Direction
- cache.normalized uses ApolloClient, so a change to ApolloClient can break cache.normalized, while a change to cache.normalized can't break ApolloClient.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
37→35 cache.normalized uses com.apollographql.apollo✕
- Connections
- 1 pair of types, where a type in cache.normalized uses a type in com.apollographql.apollo.
- The types involved
com.apollographql.apollo.cache.normalized.ClientCacheExtensionsKt→com.apollographql.apollo.ApolloCall
- Direction
- cache.normalized uses com.apollographql.apollo, so a change to com.apollographql.apollo can break cache.normalized, while a change to cache.normalized can't break com.apollographql.apollo.
- Position
- Below the diagonal: cache.normalized uses a module listed above it, which is the healthy direction.
38→2 debugserver.internal.graphql uses ast✕
- Connections
- 1 pair of types, where a type in debugserver.internal.graphql uses a type in ast.
- The types involved
com.apollographql.apollo.debugserver.internal.graphql.FieldsCoercing→com.apollographql.apollo.ast.GQLValue
- Direction
- debugserver.internal.graphql uses ast, so a change to ast can break debugserver.internal.graphql, while a change to debugserver.internal.graphql can't break ast.
- Position
- Below the diagonal: debugserver.internal.graphql uses a module listed above it, which is the healthy direction.
38→25 debugserver.internal.graphql uses execution✕
- Connections
- 2 pairs of types, where a type in debugserver.internal.graphql uses a type in execution.
- The types involved
com.apollographql.apollo.debugserver.internal.graphql.FieldsCoercing→com.apollographql.apollo.execution.Coercingcom.apollographql.apollo.debugserver.internal.graphql.GraphQL→com.apollographql.apollo.execution.ExecutableSchema
- Direction
- debugserver.internal.graphql uses execution, so a change to execution can break debugserver.internal.graphql, while a change to debugserver.internal.graphql can't break execution.
- Position
- Below the diagonal: debugserver.internal.graphql uses a module listed above it, which is the healthy direction.
38→35 debugserver.internal.graphql uses com.apollographql.apollo✕
- Connections
- 3 pairs of types, where a type in debugserver.internal.graphql uses a type in com.apollographql.apollo.
- The types involved
com.apollographql.apollo.debugserver.internal.graphql.GraphQL→com.apollographql.apollo.ApolloClientcom.apollographql.apollo.debugserver.internal.graphql.GraphQLApolloClient→com.apollographql.apollo.ApolloClientcom.apollographql.apollo.debugserver.internal.graphql.Query→com.apollographql.apollo.ApolloClient
- Direction
- debugserver.internal.graphql uses com.apollographql.apollo, so a change to com.apollographql.apollo can break debugserver.internal.graphql, while a change to debugserver.internal.graphql can't break com.apollographql.apollo.
- Position
- Below the diagonal: debugserver.internal.graphql uses a module listed above it, which is the healthy direction.
39→2 tooling uses ast✕
- Connections
- 4 pairs of types, where a type in tooling uses a type in ast.
- The types involved
com.apollographql.apollo.tooling.RegisterOperationsKt→com.apollographql.apollo.ast.GQLNodecom.apollographql.apollo.tooling.RegisterOperationsKt→com.apollographql.apollo.ast.SDLWritercom.apollographql.apollo.tooling.SchemaHelper→com.apollographql.apollo.ast.GQLDefinitioncom.apollographql.apollo.tooling.SchemaHelper→com.apollographql.apollo.ast.GQLField
- Direction
- tooling uses ast, so a change to ast can break tooling, while a change to tooling can't break ast.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
39→3 tooling uses compiler.operationoutput✕
- Connections
- 1 pair of types, where a type in tooling uses a type in compiler.operationoutput.
- The types involved
com.apollographql.apollo.tooling.RegisterOperations→com.apollographql.apollo.compiler.operationoutput.OperationDescriptor
- Direction
- tooling uses compiler.operationoutput, so a change to compiler.operationoutput can break tooling, while a change to tooling can't break compiler.operationoutput.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
39→7 tooling uses api.json✕
- Connections
- 4 pairs of types, where a type in tooling uses a type in api.json.
- The types involved
com.apollographql.apollo.tooling.TimestampAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.tooling.TimestampAdapter→com.apollographql.apollo.api.json.JsonWritercom.apollographql.apollo.tooling.VoidAdapter→com.apollographql.apollo.api.json.JsonReadercom.apollographql.apollo.tooling.VoidAdapter→com.apollographql.apollo.api.json.JsonWriter
- Direction
- tooling uses api.json, so a change to api.json can break tooling, while a change to tooling can't break api.json.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
39→11 tooling uses api.http✕
- Connections
- 2 pairs of types, where a type in tooling uses a type in api.http.
- The types involved
com.apollographql.apollo.tooling.SchemaDownloaderKt→com.apollographql.apollo.api.http.HttpMethodcom.apollographql.apollo.tooling.SchemaHelper→com.apollographql.apollo.api.http.HttpMethod
- Direction
- tooling uses api.http, so a change to api.http can break tooling, while a change to tooling can't break api.http.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
39→17 tooling uses api✕
- Connections
- 5 pairs of types, where a type in tooling uses a type in api.
- The types involved
com.apollographql.apollo.tooling.SchemaDownloaderKt→com.apollographql.apollo.api.Errorcom.apollographql.apollo.tooling.TimestampAdapter→com.apollographql.apollo.api.Adaptercom.apollographql.apollo.tooling.TimestampAdapter→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.tooling.VoidAdapter→com.apollographql.apollo.api.Adaptercom.apollographql.apollo.tooling.VoidAdapter→com.apollographql.apollo.api.CustomScalarAdapters
- Direction
- tooling uses api, so a change to api can break tooling, while a change to tooling can't break api.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
39→35 tooling uses com.apollographql.apollo✕
- Connections
- 3 pairs of types, where a type in tooling uses a type in com.apollographql.apollo.
- The types involved
com.apollographql.apollo.tooling.GraphosKt→com.apollographql.apollo.ApolloClientcom.apollographql.apollo.tooling.InternalPlatformApiKt→com.apollographql.apollo.ApolloClientcom.apollographql.apollo.tooling.SchemaUploader→com.apollographql.apollo.ApolloClient
- Direction
- tooling uses com.apollographql.apollo, so a change to com.apollographql.apollo can break tooling, while a change to tooling can't break com.apollographql.apollo.
- Position
- Below the diagonal: tooling uses a module listed above it, which is the healthy direction.
40→16 cache.normalized.internal uses exception✕
- Connections
- 1 pair of types, where a type in cache.normalized.internal uses a type in exception.
- The types involved
com.apollographql.apollo.cache.normalized.internal.WatcherInterceptorKt→com.apollographql.apollo.exception.DefaultApolloException
- Direction
- cache.normalized.internal uses exception, so a change to exception can break cache.normalized.internal, while a change to cache.normalized.internal can't break exception.
- Position
- Below the diagonal: cache.normalized.internal uses a module listed above it, which is the healthy direction.
40→17 cache.normalized.internal uses api✕
- Connections
- 8 pairs of types, where a type in cache.normalized.internal uses a type in api.
- The types involved
com.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.api.ApolloResponsecom.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.api.CustomScalarAdapterscom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.api.Fragmentcom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.api.Operationcom.apollographql.apollo.cache.normalized.internal.WatcherInterceptor→com.apollographql.apollo.api.ApolloRequestcom.apollographql.apollo.cache.normalized.internal.WatcherInterceptor→com.apollographql.apollo.api.ApolloResponse
- Direction
- cache.normalized.internal uses api, so a change to api can break cache.normalized.internal, while a change to cache.normalized.internal can't break api.
- Position
- Below the diagonal: cache.normalized.internal uses a module listed above it, which is the healthy direction.
40→19 cache.normalized.internal uses cache.normalized.api.internal✕
- Connections
- 1 pair of types, where a type in cache.normalized.internal uses a type in cache.normalized.api.internal.
- The types involved
com.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.internal.OptimisticCache
- Direction
- cache.normalized.internal uses cache.normalized.api.internal, so a change to cache.normalized.api.internal can break cache.normalized.internal, while a change to cache.normalized.internal can't break cache.normalized.api.internal.
- Position
- Below the diagonal: cache.normalized.internal uses a module listed above it, which is the healthy direction.
40→24 cache.normalized.internal uses cache.normalized.api✕
- Connections
- 7 pairs of types, where a type in cache.normalized.internal uses a type in cache.normalized.api.
- The types involved
com.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.CacheHeaderscom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.CacheKeycom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.CacheKeyGeneratorcom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.CacheResolvercom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.NormalizedCachecom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.NormalizedCacheFactorycom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.api.Record
- Direction
- cache.normalized.internal uses cache.normalized.api, so a change to cache.normalized.api can break cache.normalized.internal, while a change to cache.normalized.internal can't break cache.normalized.api.
- Position
- Below the diagonal: cache.normalized.internal uses a module listed above it, which is the healthy direction.
40→29 cache.normalized.internal uses interceptor✕
- Connections
- 4 pairs of types, where a type in cache.normalized.internal uses a type in interceptor.
- The types involved
com.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChaincom.apollographql.apollo.cache.normalized.internal.WatcherInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorcom.apollographql.apollo.cache.normalized.internal.WatcherInterceptor→com.apollographql.apollo.interceptor.ApolloInterceptorChain
- Direction
- cache.normalized.internal uses interceptor, so a change to interceptor can break cache.normalized.internal, while a change to cache.normalized.internal can't break interceptor.
- Position
- Below the diagonal: cache.normalized.internal uses a module listed above it, which is the healthy direction.
40→37 cache.normalized.internal uses cache.normalized✕
- Connections
- 3 pairs of types, where a type in cache.normalized.internal uses a type in cache.normalized.
- The types involved
com.apollographql.apollo.cache.normalized.internal.ApolloCacheInterceptor→com.apollographql.apollo.cache.normalized.ApolloStorecom.apollographql.apollo.cache.normalized.internal.DefaultApolloStore→com.apollographql.apollo.cache.normalized.ApolloStorecom.apollographql.apollo.cache.normalized.internal.WatcherInterceptor→com.apollographql.apollo.cache.normalized.ApolloStore
- Direction
- cache.normalized.internal uses cache.normalized, so a change to cache.normalized can break cache.normalized.internal, while a change to cache.normalized.internal can't break cache.normalized.
- Position
- Below the diagonal: cache.normalized.internal 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 | 18 | High / Critical |
| A05:2025 — Injection | 5 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Immediately resolve the leaked secret in the REDACTED and the three environment secret findings in the GitHub workflows to secure the codebase. Establish automated, reversible deployment pipelines to ensure releases are repeatable, while configuring HTTP timeouts and resilience patterns to protect against dependency failures. Finally, extend structured logging across all runnable modules to ensure full observability and diagnosability in production.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +10.6 pts | Low | Secret Scanning |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +6.5 pts | Medium | Deployment & Rollback |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +5.2 pts | Medium | Outbound HTTP resilience |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.4 pts | Low | Static Analysis (SAST) |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.8 pts | Medium | Observability |
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). | +0.9 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +0.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt | 5.5 | Mixed | Cyclomatic Complexity: DefaultApolloExtension.telemetryUsedOptions (cyclomatic 21) |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExtensionsMerger.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/OperationContext.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/coerceArgumentValues.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrOperationsBuilder.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/fields_merging.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt | 6.0 | Mixed | Explicit Debt: XxxComment |
| libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExecutableValidationScope.kt | 6.7 | Mixed | Explicit Debt: XxxComment |
| libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/http/BatchingHttpInterceptor.kt | 6.7 | 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
Watchdog 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. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 63 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, 261 of 273 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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, .java) 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog 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, .java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. 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 — Watchdog 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because storage.googleapis.com — the registry that answers it — was asked and did not reply (the build stopped because storage.googleapis.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add storage.googleapis.com to the allowlist and re-run — not to build anything.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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.
- D20 ADR Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. The ADR lexicon (adr-lexicon-1) covers de, en, it, nl. A record identified as another language, or whose language could not be identified (fewer than 25 words of prose, or no clear winner), is never read with English rules: its missing-section, status, consequence-cost and same-question rules abstain, and only the structural rules (title, single option, dangling link, enforcement field) run.
- D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming 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. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (libraries/apollo-gradle-plugin/testProjects/multi-modules-transitive/root/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — Watchdog 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.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `libraries/apollo-annotations/src/appleMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/jsMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/jvmMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/linuxMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/wasmJsMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.wasmJs.kt`, … (+20 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.
- AX1 Captive dependencies — not measured this run — Watchdog 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog 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. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C2 Access Controls — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- 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
26 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Lexer.nextToken at 40. A further 3 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 BufferedSourceJsonReader.peek at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/CustomScalarAdapters.kt (CustomScalarAdapters.responseAdapterFor at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 26 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Lexer.nextToken (cyclomatic 40), Lexer.readNumber (cyclomatic 34), SchemaValidationScopeKt.validateSchema (cyclomatic 34). — 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 26 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
39 method(s) exceeded the cognitive complexity threshold of 15; the worst was Lexer.readNumber at 73.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Lexer.readNumber (cognitive 73). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
21 god class(es) detected.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with gql.kt, Parser.kt, SchemaValidationScope.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with DefaultApolloExtension.kt, introspection.kt, SchemaValidationScope.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with Parser.kt, ApolloClient.kt, DefaultService.kt. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
70 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MapJsonReader.kt (2), LruCache.kt (2), FragmentDataAdapterBuilder.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with JavaCodegen.kt, AppSyncWsProtocol.kt, gql.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with MapJsonReader.kt (2), bestGuess.kt, serialization.kt. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
155 production modules (Gradle), 0 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; 1 module(s) off the main sequence, with abstractness counted on 31 of the 155 (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 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 153 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DefaultApolloCompilerRegistry.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Resolve the 12 Classify ADR enforcement finding(s) in Architectural Integrity — start with ApolloResult.md, Codegen.md, Compiler.md. — One of this dimension's main actionable groups (12 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
52 test methods: 52 unit, 0 integration, 0 BDD, 0 e2e.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 60 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 168 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. 8 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 28 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
26 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt. Counted over 252 of the 726 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
42 deducted task-comment markers across 61493 LoC (0.1/KLoC) → score 9.9. 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 29 TodoComment finding(s) in Explicit Debt — start with SelectionSetsBuilder.kt (2), Value.kt (2), LexerTest.kt (2). — One of this dimension's main actionable groups (29 warning-level).
- Resolve the 13 XxxComment finding(s) in Explicit Debt — start with IrSchema.kt (5), json.kt (3), FragmentTest.kt. — One of this dimension's main actionable groups (13 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 111 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 10 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question). How well each record argues its case is not measured.
D26 · Project Cohesion
4 of 20 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).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 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 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. semgrep hit a parse error in 4 file(s) — `gradlew` (line 74, line 178), `libraries/apollo-gradle-plugin/testProjects/java-only/src/main/java/com/example/Adapters.java` (line 1), `libraries/apollo-gradle-plugin/testProjects/multi-modules-publishing-consumer/gradlew` (line 74, line 181), `libraries/apollo-gradle-plugin/testProjects/multi-modules-publishing-producer/gradlew` (line 74, line 181) — 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- 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
6 finding(s): 0 critical, 5 high, 0 medium, 1 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
8 of 252 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedWithInterfacesModelGroupBuilder.kt. Counted over 252 of the 726 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: DefaultApolloExtension.kt↔ModelNames.kt 90%; SchemaDownloader.kt↔SchemaHelper.kt 62%; gqldocument.kt↔SchemaValidationScope.kt 52%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with DefaultApolloExtension.kt, SchemaDownloader.kt, gqldocument.kt. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-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 8 platform declaration(s) and 89 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
M1 · Documentation (README)
What to do
- 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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 63 of 88 project(s) that lack one — worth up to 1.4 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 12) — reach 20 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `build-logic`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `HttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — libraries/apollo-runtime/src/linuxMain/kotlin/com/apollographql/apollo/network/websocket/WebSocketEngine.linux.kt:33
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF1 · Benchmark discipline
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 14 use(s) across 69,339 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `toAny` is public and takes its `JsonElement` receiver from its caller, and it calls itself at line 65 with a piece of its receiver (and at line 66) — the function is not `tailrec`, so every call is a real frame — and nowhere in `toAny` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `toAny` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/serialization.kt:65
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
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
- `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. (×2) — libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/WsProtocol.kt:108, libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/DiskLruHttpCache.kt:134
- `catch (ignore: 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. — libraries/apollo-normalized-cache-api/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/api/internal/OptimisticCache.kt:23
- 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) — libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/internal/DiskLruCache.kt:718, libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/JsonReaders.kt:103, libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/JsonReaders.kt:107, …
- `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. — libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt:69
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 85% | Strong | Strongest area. |
| Maturity | 79% | Strong | Solid. |
| Readiness | 53% | Adequate — gated by P4, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Strong | Solid. |
| Performance | 83% | Strong | Solid. |
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 — 55 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — 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
- 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. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — no public interfaces
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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 — ~35796 lines of test source are present (.kt, .java) 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 — Dependency currency not established — storage.googleapis.com did not answer
- 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 — Naming consistency is measured on C# only; Java, JavaScript, Kotlin, Swift not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic 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 — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 25 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- 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): 91 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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 111 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 1); M4 checks only links and versions.
- 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'.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 225 finding(s)
- TodoComment tests/sample-server/src/main/kotlin/com/apollographql/apollo/sample/server/graphql/SubscriptionRoot.kt:78
- TodoComment tests/jsexport/src/jsTest/kotlin/JsExportTest.js.kt:29
- TodoComment tests/defer/src/commonTest/kotlin/test/DeferV0_1NormalizedCacheTest.kt:469
- TodoComment tests/defer/src/commonTest/kotlin/test/DeferV0_1Test.kt:258
- TodoComment tests/defer/src/commonTest/kotlin/test/DeferV0_2NormalizedCacheTest.kt:567
- TodoComment tests/defer/src/commonTest/kotlin/test/DeferV0_2Test.kt:190
- TodoComment tests/defer/src/commonTest/kotlin/test/DeferWithRouterTest.kt:313
- TodoComment libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/http/BatchingHttpInterceptor.kt:201
- TodoComment libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/http/HttpInterceptor.kt:29
- TodoComment libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/OperationContext.kt:257
- TodoComment libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/coerceArgumentValues.kt:184
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt:214
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrOperationsBuilder.kt:522
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedWithInterfacesModelGroupBuilder.kt:320
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/SelectionSetsBuilder.kt:115
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/SelectionSetsBuilder.kt:136
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/helpers/Value.kt:18
- TodoComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/helpers/Value.kt:27
- TodoComment libraries/apollo-ast/src/commonTest/kotlin/com/apollographql/apollo/graphql/ast/test/LexerTest.kt:238
- TodoComment libraries/apollo-ast/src/commonTest/kotlin/com/apollographql/apollo/graphql/ast/test/LexerTest.kt:455
- TodoComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/Issue.kt:6
- TodoComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/exception.kt:10
- TodoComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt:1624
- TodoComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExtensionsMerger.kt:533
- TodoComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:333
- XxxComment tests/data-builders-kotlin/src/test/kotlin/test/FragmentTest.kt:56
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/json.kt:32
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/json.kt:37
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/json.kt:91
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:175
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:191
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:293
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:306
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:325
- XxxComment libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/EnumAsSealedInterfaceBuilder.kt:60
- XxxComment libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExecutableValidationScope.kt:659
- XxxComment libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/Adapters.kt:461
- XxxComment libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/http/internal/UrlEncode.kt:70
- Duplicated block (8 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:109
- Duplicated block (8 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:412
- Duplicated block (8 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/operations/FragmentDataAdapterBuilder.kt:43
- Duplicated block (8 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/builders/FragmentExtensionBuilder.kt:26
- Duplicated block (8 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedModelGroupBuilder.kt:414
- Duplicated block (8 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:52
- Duplicated block (8 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:83
- Duplicated block (8 lines × 2) libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:641
- FileTooLong: ast/gql.kt libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt
- FileTooLong: internal/Parser.kt libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Parser.kt
- FileTooLong: internal/SchemaValidationScope.kt libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt
- FileTooLong: internal/DefaultApolloExtension.kt libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt
- FileTooLong: json/BufferedSourceJsonReader.kt libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt
- FileTooLong: internal/DiskLruCache.kt libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/internal/DiskLruCache.kt
- FileTooLong: internal/definitions.kt libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/definitions.kt
- Duplicated block (10 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/JavaCodegen.kt:179
- Duplicated block (10 lines × 2) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/AppSyncWsProtocol.kt:91
- Duplicated block (10 lines × 2) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt:2481
- Duplicated block (10 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/Flatten.kt:5
- Duplicated block (10 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/InterfaceBuilder.kt:38
- Duplicated block (10 lines × 2) libraries/apollo-normalized-cache/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/ClientCacheExtensions.kt:131
- Duplicated block (10 lines × 2) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/websocket/GraphQLWsProtocol.kt:24
- Duplicated block (7 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:64
- Duplicated block (7 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/bestGuess.kt:12
- Duplicated block (7 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/serialization.kt:56
- Duplicated block (7 lines × 2) libraries/apollo-api-java/src/main/kotlin/com/apollographql/apollo/api/java/adapter/GuavaOptionalAdapter.kt:30
- Duplicated block (7 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:168
- Duplicated block (7 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/builders/FragmentExtensionBuilder.kt:50
- Duplicated block (7 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/EnumAsApolloEnumBuilder.kt:88
- MethodTooLong: DefaultApolloExtension.registerService libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:407
- MethodTooLong: IntrospectionKt.introspectionResolvers libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/introspection.kt:42
- MethodTooLong: SchemaValidationScopeKt.validateSchema libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:62
- MethodTooLong: OperationBasedModelGroupBuilder.buildField libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedModelGroupBuilder.kt:124
- MethodTooLong: Lexer.readNumber libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:429
- MethodTooLong: OperationBasedWithInterfacesModelGroupBuilder.buildNode libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedWithInterfacesModelGroupBuilder.kt:125
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Parser.kt:335
- Duplicated block (9 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/TypesBuilder.kt:58
- Duplicated block (9 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/util/TypesBuilder.kt:56
- Duplicated block (9 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:132
- Duplicated block (9 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:206
- Duplicated block (9 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/InputObjectAdapterBuilder.kt:35
- Duplicated block (21 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:227
- Duplicated block (21 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:250
- Duplicated block (21 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:273
- Duplicated block (21 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:361
- Duplicated block (21 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/buckets.kt:36
- TooManyMethods: Parser libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Parser.kt:6
- TooManyMethods: Builder libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/ApolloClient.kt:355
- TooManyMethods: DefaultService libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultService.kt:21
- TooManyMethods: BufferedSourceJsonReader libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:35
- ClassTooLong: Parser libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Parser.kt:6
- ClassTooLong: DefaultApolloExtension libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:57
- ClassTooLong: BufferedSourceJsonReader libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:35
- ClassTooLong: DiskLruCache libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/internal/DiskLruCache.kt:87
- Duplicated block (13 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/AdapterCommon.kt:216
- Duplicated block (13 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedModelGroupBuilder.kt:349
- Duplicated block (13 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedModelGroupBuilder.kt:400
- Duplicated block (13 lines × 2) libraries/apollo-testing-support/src/commonMain/kotlin/com/apollographql/apollo/testing/TestNetworkTransport.kt:38
- Swallowed exception (caught, then discarded) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/WsProtocol.kt:108
- Swallowed exception (caught, then discarded) libraries/apollo-normalized-cache-api/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/api/internal/OptimisticCache.kt:23
- Swallowed exception (caught, then discarded) libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/DiskLruHttpCache.kt:134
- Swallowed exception (caught, then discarded) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt:69
- Swallowed exception (empty catch) libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/internal/DiskLruCache.kt:718
- Swallowed exception (empty catch) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/JsonReaders.kt:103
- Swallowed exception (empty catch) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/JsonReaders.kt:107
- Swallowed exception (empty catch) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/JsonReaders.kt:111
- Change coupling: DefaultApolloExtension.kt ↔ ModelNames.kt libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:1
- Change coupling: SchemaDownloader.kt ↔ SchemaHelper.kt libraries/apollo-tooling/src/main/kotlin/com/apollographql/apollo/tooling/SchemaDownloader.kt:1
- Change coupling: gqldocument.kt ↔ SchemaValidationScope.kt libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gqldocument.kt:1
- Duplicated block (19 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:296
- Duplicated block (19 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:93
- Duplicated block (19 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:134
- Duplicated block (18 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/JavaCodegen.kt:259
- Duplicated block (18 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/EnumAsApolloEnumBuilder.kt:206
- Duplicated block (18 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:114
- Duplicated block (15 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/EnumAsClassBuilder.kt:56
- Duplicated block (15 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedModelGroupBuilder.kt:287
- Duplicated block (15 lines × 2) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/GraphQLWsProtocol.kt:54
- Duplicated block (12 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/EnumAsEnumBuilder.kt:137
- Duplicated block (12 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/EnumAsApolloEnumBuilder.kt:152
- Duplicated block (12 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/helpers/Collections.kt:16
- Duplicated block (6 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:515
- Duplicated block (6 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/ScalarBuilder.kt:38
- Duplicated block (6 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/InterfaceBuilder.kt:56
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/JavaCodegen.kt:232
- Duplicated block (17 lines × 2) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:383
- Duplicated block (14 lines × 2) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt:741
- Duplicated block (14 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/builders/FragmentExtensionBuilder.kt:35
- Duplicated block (9 lines × 3) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/model/CompilationUnitModel.kt:41
- Duplicated block (9 lines × 3) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/InterfaceBuilder.kt:46
- Duplicated block (11 lines × 2) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/LruCache.kt:34
- Duplicated block (11 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/AdapterCommon.kt:86
- Duplicated block (5 lines × 2) libraries/apollo-runtime/src/jvmCommonMain/kotlin/com/apollographql/apollo/network/OkHttpExtensions.kt:74
- Duplicated block (5 lines × 2) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:187
- Lexer.nextToken (cyclomatic 40) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:55
- Lexer.readNumber (cyclomatic 34) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:429
- SchemaValidationScopeKt.validateSchema (cyclomatic 34) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:62
- BufferedSourceJsonReader.peekNumber (cyclomatic 31) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:307
- IntrospectionKt.introspectionResolvers (cyclomatic 30) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/introspection.kt:42
- BufferedSourceJsonReader.doPeek (cyclomatic 29) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:145
- ValidationCommonKt.validateDirectives (cyclomatic 26) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ValidationCommon.kt:124
- ExtensionsMergerKt.areEqual (cyclomatic 25) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExtensionsMerger.kt:479
- KotlinResolver.adapterInitializer (cyclomatic 22) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/KotlinResolver.kt:189
- ScalarBuilder.prepare (cyclomatic 22) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/ScalarBuilder.kt:34
- DefaultApolloExtension.telemetryUsedOptions (cyclomatic 21) libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:147
- ApolloExecutableDocumentTransform.addRequiredFields (cyclomatic 21) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/ApolloExecutableDocumentTransform.kt:125
- BufferedSourceJsonReader.readEscapeCharacter (cyclomatic 21) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:824
- KmpKt.defaultTargets (cyclomatic 21) build-logic/src/main/kotlin/kmp.kt:36
- DefaultApolloExtension.registerService (cyclomatic 20) libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:407
- ScalarBuilder.prepare (cyclomatic 20) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/ScalarBuilder.kt:35
- Parser.parseDefinition (cyclomatic 20) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Parser.kt:829
- IrDataBuildersKt.buildIrDataBuilders (cyclomatic 19) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrDataBuilders.kt:105
- MultipartReader.nextPart (cyclomatic 17) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/internal/MultipartReader.kt:88
- WebSocketNetworkTransport.supervise (cyclomatic 17) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/WebSocketNetworkTransport.kt:130
- OperationContext.completeValueOrThrow (cyclomatic 17) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/OperationContext.kt:378
- CoerceArgumentValuesKt.coerceInputLiteralToInternal (cyclomatic 17) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/coerceArgumentValues.kt:122
- ApolloCompiler.buildCodegenSchema (cyclomatic 16) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt:99
- IrOperationsBuilder.mergeWith (cyclomatic 16) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrOperationsBuilder.kt:331
- ExecutableValidationScope.areValuesEqual (cyclomatic 16) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExecutableValidationScope.kt:604
- Fields_mergingKt.requireSameOutputTypeShape (cyclomatic 16) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/fields_merging.kt:300
- Lexer.readNumber (cognitive 73) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:429
- SchemaValidationScopeKt.validateSchema (cognitive 55) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:62
- ExtensionsMergerKt.areEqual (cognitive 51) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/ExtensionsMerger.kt:479
- BufferedSourceJsonReader.peekNumber (cognitive 48) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:307
- WebSocketNetworkTransport.supervise (cognitive 44) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/ws/WebSocketNetworkTransport.kt:130
- Lexer.nextToken (cognitive 39) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:55
- DefaultApolloExtension.registerService (cognitive 31) libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:407
- Fields_mergingKt.collectFields (cognitive 31) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/fields_merging.kt:101
- BufferedSourceJsonReader.selectName (cognitive 31) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:708
- IrDataBuildersKt.buildIrDataBuilders (cognitive 30) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrDataBuilders.kt:105
- Fields_mergingKt.requireSameOutputTypeShape (cognitive 30) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/fields_merging.kt:300
- BufferedSourceJsonReader.doPeek (cognitive 30) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/BufferedSourceJsonReader.kt:145
- HttpNetworkTransport.multipleResponses (cognitive 26) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/http/HttpNetworkTransport.kt:195
- CoerceArgumentValuesKt.coerceInputLiteralToInternal (cognitive 26) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/coerceArgumentValues.kt:122
- MultipartReader.nextPart (cognitive 25) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/internal/MultipartReader.kt:88
- DiskLruCache.completeEdit (cognitive 24) libraries/apollo-http-cache/src/main/kotlin/com/apollographql/apollo/cache/http/internal/DiskLruCache.kt:470
- OptionsKt.validate (cognitive 24) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/Options.kt:635
- AdapterCommonKt.readFromResponseCodeBlock (cognitive 24) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/helpers/AdapterCommon.kt:37
- ApolloExecutableDocumentTransform.addRequiredFields (cognitive 23) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/ApolloExecutableDocumentTransform.kt:125
- IntrospectionKt.introspectionResolvers (cognitive 22) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/introspection.kt:42
- IrOperationsBuilder.merge (cognitive 21) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrOperationsBuilder.kt:466
- DefaultApolloExtension.telemetryUsedOptions (cognitive 20) libraries/apollo-gradle-plugin/src/main/kotlin/com/apollographql/apollo/gradle/internal/DefaultApolloExtension.kt:147
- ApolloCompiler.buildCodegenSchema (cognitive 20) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ApolloCompiler.kt:99
- Lexer.readBlockString (cognitive 20) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/Lexer.kt:340
- SchemaValidationScopeKt.reverseGraph (cognitive 20) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:810
- CoerceArgumentValuesKt.coerceArgumentValues (cognitive 19) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/coerceArgumentValues.kt:60
- FakeResolverKt.buildFieldOfNonNullType (cognitive 19) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/fakeResolver.kt:171
- DefaultHttpRequestComposer.compose (cognitive 19) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/http/DefaultHttpRequestComposer.kt:50
- OperationContext.completeValueOrThrow (cognitive 18) libraries/apollo-execution/src/commonMain/kotlin/com/apollographql/apollo/execution/internal/OperationContext.kt:378
- AdapterCommonKt.readFromResponseCodeBlock (cognitive 18) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/AdapterCommon.kt:61
- IrOperationsBuilder.mergeWith (cognitive 18) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrOperationsBuilder.kt:331
- GQLDocumentBuilder.toGQLDirectiveDefinition (cognitive 18) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/introspection/introspection_reader.kt:533
- SchemaDownloader.download (cognitive 17) libraries/apollo-tooling/src/main/kotlin/com/apollographql/apollo/tooling/SchemaDownloader.kt:53
- BatchingHttpInterceptor.executePendingRequests (cognitive 17) libraries/apollo-runtime/src/commonMain/kotlin/com/apollographql/apollo/network/http/BatchingHttpInterceptor.kt:124
- ScalarBuilder.prepare (cognitive 17) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/schema/ScalarBuilder.kt:34
- SchemaValidationScopeKt.getLinkedSchemas (cognitive 17) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/internal/SchemaValidationScope.kt:402
- NormalizedCache.prettifyDump (cognitive 16) libraries/apollo-normalized-cache-api/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/api/NormalizedCache.kt:85
- KotlinResolver.adapterInitializer (cognitive 16) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/KotlinResolver.kt:189
- CompiledGraphQLKt.resolveVariables (cognitive 16) libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/CompiledGraphQL.kt:518
- REDACTED
- Near-duplicate member pair (42 shared lines) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/AdapterCommon.kt:65
- Members sharing a duplicated core (4 members, 50+ identical tokens) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt:614
- Duplicated block (20 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/schema/EnumAsClassBuilder.kt:80
- Duplicated block (18–19 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/AdapterCommon.kt:114
- Duplicated block (15–16 lines × 4) libraries/apollo-ast/src/commonMain/kotlin/com/apollographql/apollo/ast/gql.kt:618
- Duplicated block (15–16 lines × 2) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/IrSchema.kt:302
- Duplicated block (10–11 lines × 2) libraries/apollo-normalized-cache-sqlite/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/sql/SqlNormalizedCache.kt:163
- Duplicated block (9–10 lines × 2) libraries/apollo-tooling/src/main/kotlin/com/apollographql/apollo/tooling/SchemaUploader.kt:63
- Duplicated block (6 lines × 4) libraries/apollo-api/src/appleMain/kotlin/com/apollographql/apollo/api/toJson.kt:15
- Duplicated block (7 lines × 4) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/helpers/InputAdapter.kt:72
- Off the main sequence: multi-modules-custom-scalar:root
- Low cohesion: DefaultApolloCompilerRegistry (LCOM4 8) libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/DefaultApolloCompilerRegistry.kt:66
- No deployment automation
- Outbound HTTP without resilience libraries/apollo-runtime/src/linuxMain/kotlin/com/apollographql/apollo/network/websocket/WebSocketEngine.linux.kt:33
- Recursive walk over a caller-supplied document has no depth cap libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/internal/serialization.kt:65
Minor — 35 finding(s)
- Classify ADR enforcement: Modeling GraphQL results in Kotlin design-docs/ApolloResult.md
- Classify ADR enforcement: Codegen Models design-docs/Codegen.md
- Classify ADR enforcement: Compiler design-docs/Compiler.md
- Classify ADR enforcement: `@defer`: draft API design-docs/Defer draft API.md
- Classify ADR enforcement: `@defer`: merging implementation design-docs/Defer merging implementation.md
- Classify ADR enforcement: Glossary design-docs/Glossary.md
- Classify ADR enforcement: Json design-docs/Json.md
- Classify ADR enforcement: Normalized cache overview design-docs/Normalized cache overview.md
- Classify ADR enforcement: Operation execution design-docs/Operation execution.md
- Classify ADR enforcement: Thoughts on Android threading and concurrency design-docs/Threading.md
- Classify ADR enforcement: Historical algorithms design-docs/Typename.md
- Classify ADR enforcement: Field type = Inline fragment type design-docs/operationBasedWithInterfaces.md
- Orphaned file libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/OperationBasedWithInterfacesModelGroupBuilder.kt:1
- Orphaned file libraries/apollo-api/src/jsMain/kotlin/com/apollographql/apollo/api/json/DynamicJsJsonReader.kt:1
- Orphaned file libraries/apollo-runtime/src/wasmJsMain/kotlin/com/apollographql/apollo/network/websocket/WebSocketEngine.wasmJs.kt:1
- Orphaned file libraries/apollo-runtime/src/jsMain/kotlin/com/apollographql/apollo/network/ws/JsWebSocketEngine.kt:1
- Orphaned file libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/ExecutionContext.kt:1
- Orphaned file libraries/apollo-runtime/src/linuxMain/kotlin/com/apollographql/apollo/network/http/DefaultHttpEngine.kt:1
- Orphaned file libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/ir/buckets.kt:1
- Orphaned file libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/internal/JsonScope.kt:1
- Duplicated predicate libraries/apollo-api/src/commonMain/kotlin/com/apollographql/apollo/api/json/MapJsonReader.kt:362
- Duplicated predicate libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/JavaCodegen.kt:248
- Duplicated predicate libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/java/JavaCodegen.kt:188
- Duplicated predicate libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo/compiler/codegen/kotlin/operations/FragmentBuilder.kt:100
- Duplicated predicate libraries/apollo-normalized-cache-api/src/commonMain/kotlin/com/apollographql/apollo/cache/normalized/api/CacheKeyResolver.kt:59
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Logging is not universal
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-34775e04addb4c999c05e85485f1ad79/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-34775e04addb4c999c05e85485f1ad79/tree.json --exit-code 0 --source . | 0 | 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/watchdog-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 libraries/apollo-compiler/src/test/graphql/com/example/__schema/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/__schema/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/antlr_tokens/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/antlr_tokens/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/arguments_hardcoded/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/arguments_hardcoded/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/big_query/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/capitalized_fields/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/capitalized_fields/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/case_sensitive_enum/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/case_sensitive_enum/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/companion/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/companion/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/custom_scalar_type/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/custom_scalar_type/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/data_builders/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/data_builders/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/decapitalized_fields/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/decapitalized_fields/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/deprecated_merged_field/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/deprecated_merged_field/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/deprecation/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/deprecation/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/empty/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/empty/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/enum_field/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/enum_field/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/enums_as_sealed/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/enums_as_sealed/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/escape_equals_hashcode/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/escape_equals_hashcode/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/escaped_kdocs/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/escaped_kdocs/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/field_with_include_directive/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/field_with_include_directive/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fieldset_with_multiple_super/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fieldset_with_multiple_super/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_spread_with_include_directive/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_spread_with_include_directive/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_spread_with_nested_fields/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_spread_with_nested_fields/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_used_twice/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_used_twice/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_with_inline_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_with_inline_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_with_multiple_fieldsets/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragment_with_multiple_fieldsets/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_same_type_condition/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_same_type_condition/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_with_defer_and_include_directives/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_with_defer_and_include_directives/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_with_type_condition/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/fragments_with_type_condition/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_details/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_details/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_details_semantic_naming/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_details_semantic_naming/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_name/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_name/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_name_query_long_name/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_name_query_long_name/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_with_review/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/hero_with_review/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_for_non_optional_field/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_for_non_optional_field/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_inside_inline_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_inside_inline_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_intersection/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_intersection/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_merge_fields/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_merge_fields/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_simple/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_simple/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_type_coercion/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_type_coercion/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_with_include_directive/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragment_with_include_directive/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragments_with_friends/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/inline_fragments_with_friends/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_oneof/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_oneof/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_type/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_type/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_variable_and_argument/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_variable_and_argument/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_variable_and_argument_with_generated_methods/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/input_object_variable_and_argument_with_generated_methods/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/interface_always_nested/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/interface_always_nested/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/interface_on_interface/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/interface_on_interface/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/introspection_query/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/introspection_query/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java8annotation/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java8annotation/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_android_annotations/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_android_annotations/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_apollo_optionals/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_apollo_optionals/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_guava_optionals/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_guava_optionals/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_hashcode/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_hashcode/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_java_optionals/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_java_optionals/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_jetbrains_annotations/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_jetbrains_annotations/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_jsr305_annotations/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_jsr305_annotations/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_primitive_types/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/java_primitive_types/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/list_field_clash/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/list_field_clash/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/merged_include/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/merged_include/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/monomorphic/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/monomorphic/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/multiple_fragments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/multiple_fragments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/mutation_create_review/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/mutation_create_review/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/mutation_create_review_semantic_naming/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/mutation_create_review_semantic_naming/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_delegate/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_delegate/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_inside_inline_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_inside_inline_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_with_variables/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_with_variables/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_without_implementation/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/named_fragment_without_implementation/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_conditional_inline/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_conditional_inline/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_field_with_multiple_fieldsets/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_field_with_multiple_fieldsets/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_named_fragments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/nested_named_fragments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/not_all_combinations_are_needed/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/not_all_combinations_are_needed/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/object/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/object/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/operation_id_generator/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/operation_id_generator/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/operationbased2_ex7/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/operationbased2_ex7/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/operationbased2_ex8/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/operationbased2_ex8/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/optional/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/optional/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/path_vs_flat_accessors/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/path_vs_flat_accessors/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/recursive_selection/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/recursive_selection/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/reserved_keywords/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/reserved_keywords/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_fragment_with_nested_fragments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_fragment_with_nested_fragments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_inline_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/root_query_inline_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_fragment_with_inline_fragments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_fragment_with_inline_fragments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_inline_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_inline_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_union/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/simple_union/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/starships/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/starships/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/subscriptions/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/subscriptions/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/suppressed_warnings/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/suppressed_warnings/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/target_name/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/target_name/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/test_inline/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/test_inline/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/two_heroes_unique/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/two_heroes_unique/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/two_heroes_with_friends/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/two_heroes_with_friends/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/typename_always_first/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/typename_always_first/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/typepolicy/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/typepolicy/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/union_fragment/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/union_fragment/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/union_inline_fragments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/union_inline_fragments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/unique_type_name/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/unique_type_name/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/used_arguments/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/used_arguments/kotlin --exclude libraries/apollo-compiler/src/test/graphql/com/example/variable_default_value/java --exclude libraries/apollo-compiler/src/test/graphql/com/example/variable_default_value/kotlin . | 5 | 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/** . --skip-db-update | 6 | 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 25 file(s) — `libraries/apollo-annotations/src/appleMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/jsMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/jvmMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/linuxMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.kt`, `libraries/apollo-annotations/src/wasmJsMain/kotlin/com/apollographql/apollo/annotations/ApolloAdaptableWith.wasmJs.kt`, … (+20 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/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |