Executive summary
Netflix/dgs-framework falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 65 out of 100 and is rated Adequate, and all 23 of its critical findings are security problems in the build pipeline and in its code.
Maturity, at 59, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Making the naming consistent comes next, also worth about 5. Raising Maturity to 70 would lift the score to about 68.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two weaknesses in the code could be used by an attacker, and one pipeline step installs packages that can change without warning. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and pinning what the pipeline installs would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed.
The product code is 17,093 lines, about €42,000 to rebuild.
If Maturity rose from 59 to 70, the lowest score rated Strong, the score would rise from 65 to about 68.
New since the last survey: 21 findings
- Code Duplication · Edited copy of a member (27 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Edited copy of a member (29 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) graphql-dgs/src/main/java/com/netflix/graphql/dgs/internal/DgsDataLoaderInstrumentationDataLoaderCustomizer.java
- Code Duplication · Edited copy of a member (22 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DefaultDgsDataLoaderProvider.kt
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt
- Code Duplication · Duplicated block (25 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt
- Code Duplication · Duplicated block (17 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt
- Code Duplication · Duplicated block (14 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Duplicated block (7–11 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Duplicated block (9–10 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt
- Code Duplication · Duplicated block (8 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomMonoGraphQLClient.kt
- Code Duplication · Duplicated block (9 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt
- Code Duplication · Duplicated block (9 lines × 4) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt
- Code Duplication · Duplicated block (5 lines × 7) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/datafetcher/ConcurrentDataFetcher.java
- Code Duplication · Edited copy of a member (8 corresponding lines) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/types/ActionMovie.java
- Code Duplication · Edited copy of a member (8 corresponding lines) graphql-dgs-spring-boot-micrometer/src/jmh/kotlin/com/netflix/graphql/dgs/metrics/micrometer/DgsGraphQLMetricsInstrumentationBenchmark.kt
Fixed since the last survey: 15 findings
- Cyclomatic Complexity · DgsSchemaProvider.registerDataFetcher (cyclomatic 20) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt
- Cognitive Complexity · DgsSchemaProvider.registerDataFetcher (cognitive 29) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt
- Cognitive Complexity · DgsSchemaProvider.findEntityFetchers (cognitive 16) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt
- God Classes · MethodTooLong: DgsSchemaProvider.registerDataFetcher graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt
- Code Duplication · Duplicated block (25 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt
- Code Duplication · Duplicated block (17 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt
- Code Duplication · Duplicated block (12 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Duplicated block (7–11 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Code Duplication · Duplicated block (9–10 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt
- Code Duplication · Duplicated block (8 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomMonoGraphQLClient.kt
- Code Duplication · Duplicated block (9 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt
- Code Duplication · Duplicated block (9 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt
- Code Duplication · Duplicated block (9 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt
- Code Duplication · Duplicated block (5 lines × 7) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt
- Static Analysis (SAST) · Medium: watchdog-eol-python-runtime-in-workflow REDACTED
Rebuild cost: about €42,000 · Estimate
| Cost to rebuild | €14,000 to €69,000, for 230 to 729 hours of work, about 0.3 person-years for one engineer |
|---|---|
| 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 65. 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 | Small: 17,093 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 dgs.DgsDataLoaderReloadController | 2 dgs.apq.DgsAPQSupportProperties | 3 dgs.autoconfig.DgsConfigurationProperties | 4 dgs.autoconfig.DgsExtendedScalarsAutoConfiguration | 5 dgs.autoconfig.DgsExtendedValidationAutoConfiguration | 6 dgs.client.DgsWebClientGraphQLClient | 7 dgs.json | 8 dgs.metrics.DgsMetrics | 9 dgs.metrics.micrometer.DgsGraphQLMetricsProperties | 10 dgs.metrics.micrometer.utils.QuerySignatureRepository | 11 dgs.reactive | 12 types.subscription | 13 types.subscription.websockets | 14 dgs.apq | 15 dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration | 16 dgs.client | 17 dgs.internal.DgsSchemaProvider.Companion | 18 dgs.internal.method | 19 dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation | 20 dgs.metrics.micrometer.utils | 21 types.subscription.websockets.Message | 22 dgs.apq.DgsAPQSupportAutoConfiguration | 23 dgs.client.ErrorType | 24 dgs.internal | 25 dgs.metrics.micrometer.tagging | 26 dgs.autoconfig | 27 dgs.context | 28 dgs | 29 dgs.context.DgsContext | 30 dgs.reactive.internal | 31 dgs.springgraphql.webmvc | 32 dgs.DgsExecutionResult | 33 dgs.federation | 34 dgs.metrics.micrometer.dataloader | 35 dgs.springgraphql | 36 dgs.springgraphql.webflux | 37 dgs.metrics.micrometer | 38 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration | 39 dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration | 40 dgs.springgraphql.autoconfig |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 dgs.DgsDataLoaderReloadController | ||||||||||||||||||||||||||||||||||||||||
| 2 dgs.apq.DgsAPQSupportProperties | ||||||||||||||||||||||||||||||||||||||||
| 3 dgs.autoconfig.DgsConfigurationProperties | ||||||||||||||||||||||||||||||||||||||||
| 4 dgs.autoconfig.DgsExtendedScalarsAutoConfiguration | ||||||||||||||||||||||||||||||||||||||||
| 5 dgs.autoconfig.DgsExtendedValidationAutoConfiguration | ||||||||||||||||||||||||||||||||||||||||
| 6 dgs.client.DgsWebClientGraphQLClient | ||||||||||||||||||||||||||||||||||||||||
| 7 dgs.json | ||||||||||||||||||||||||||||||||||||||||
| 8 dgs.metrics.DgsMetrics | ||||||||||||||||||||||||||||||||||||||||
| 9 dgs.metrics.micrometer.DgsGraphQLMetricsProperties | ||||||||||||||||||||||||||||||||||||||||
| 10 dgs.metrics.micrometer.utils.QuerySignatureRepository | ||||||||||||||||||||||||||||||||||||||||
| 11 dgs.reactive | ||||||||||||||||||||||||||||||||||||||||
| 12 types.subscription | ||||||||||||||||||||||||||||||||||||||||
| 13 types.subscription.websockets | ||||||||||||||||||||||||||||||||||||||||
| 14 dgs.apq | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 dgs.client | 1 | 8 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 dgs.internal.DgsSchemaProvider.Companion | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 dgs.internal.method | 4 | |||||||||||||||||||||||||||||||||||||||
| 19 dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 dgs.metrics.micrometer.utils | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 types.subscription.websockets.Message | 9 | |||||||||||||||||||||||||||||||||||||||
| 22 dgs.apq.DgsAPQSupportAutoConfiguration | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 dgs.client.ErrorType | 8 | |||||||||||||||||||||||||||||||||||||||
| 24 dgs.internal | 1 | 1 | 3 | 2 | 4 | 24 | ||||||||||||||||||||||||||||||||||
| 25 dgs.metrics.micrometer.tagging | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 dgs.autoconfig | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 dgs.context | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 dgs | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 dgs.context.DgsContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 dgs.reactive.internal | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 dgs.springgraphql.webmvc | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 dgs.DgsExecutionResult | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 dgs.federation | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 dgs.metrics.micrometer.dataloader | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 dgs.springgraphql | 2 | 1 | 7 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 36 dgs.springgraphql.webflux | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 dgs.metrics.micrometer | 5 | 3 | 2 | 2 | 9 | 1 | ||||||||||||||||||||||||||||||||||
| 38 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration | 2 | 1 | 2 | 5 | 1 | 1 | 4 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 39 dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 40 dgs.springgraphql.autoconfig | 1 | 2 | 12 | 2 | 3 | 6 | 2 |
14→2 dgs.apq uses dgs.apq.DgsAPQSupportProperties✕
- Connections
- 1 pair of types, where a type in dgs.apq uses a type in dgs.apq.DgsAPQSupportProperties.
- The types involved
com.netflix.graphql.dgs.apq.DgsAPQSupportProperties→com.netflix.graphql.dgs.apq.DgsAPQSupportProperties.DgsAPQDefaultCaffeineCacheProperties
- Direction
- dgs.apq uses dgs.apq.DgsAPQSupportProperties, so a change to dgs.apq.DgsAPQSupportProperties can break dgs.apq, while a change to dgs.apq can't break dgs.apq.DgsAPQSupportProperties.
- Position
- Below the diagonal: dgs.apq uses a module listed above it, which is the healthy direction.
15→4 dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration uses dgs.autoconfig.DgsExtendedScalarsAutoConfiguration✕
- Connections
- 2 pairs of types, where a type in dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration uses a type in dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.
- The types involved
com.netflix.graphql.dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration.BigDecimalAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.ExtendedScalarRegistrarcom.netflix.graphql.dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration.BigIntegerAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.ExtendedScalarRegistrar
- Direction
- dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration uses dgs.autoconfig.DgsExtendedScalarsAutoConfiguration, so a change to dgs.autoconfig.DgsExtendedScalarsAutoConfiguration can break dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration, while a change to dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration can't break dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.
- Position
- Below the diagonal: dgs.autoconfig.DgsExtendedScalarsAutoConfiguration.NumbersExtendedScalarsAutoConfiguration uses a module listed above it, which is the healthy direction.
16→6 dgs.client uses dgs.client.DgsWebClientGraphQLClient✕
- Connections
- 1 pair of types, where a type in dgs.client uses a type in dgs.client.DgsWebClientGraphQLClient.
- The types involved
com.netflix.graphql.dgs.client.DgsWebClientGraphQLClient→com.netflix.graphql.dgs.client.DgsWebClientGraphQLClient.RequestBodyUriCustomizer
- Direction
- dgs.client uses dgs.client.DgsWebClientGraphQLClient, so a change to dgs.client.DgsWebClientGraphQLClient can break dgs.client, while a change to dgs.client can't break dgs.client.DgsWebClientGraphQLClient.
- Position
- Below the diagonal: dgs.client uses a module listed above it, which is the healthy direction.
16→7 dgs.client uses dgs.json✕
- Connections
- 8 pairs of types, where a type in dgs.client uses a type in dgs.json.
- The types involved
com.netflix.graphql.dgs.client.DefaultDgsGraphQLResponse→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.DgsCustomGraphQLClient→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.DgsCustomMonoGraphQLClient→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.DgsGraphqlSSESubscriptionGraphQLClient→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.DgsRestClientGraphQLClient→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.DgsWebClientGraphQLClient→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.Jackson2DgsJsonMapperAdapter→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.client.Jackson3DgsJsonMapperAdapter→com.netflix.graphql.dgs.json.DgsJsonMapper
- Direction
- dgs.client uses dgs.json, so a change to dgs.json can break dgs.client, while a change to dgs.client can't break dgs.json.
- Position
- Below the diagonal: dgs.client uses a module listed above it, which is the healthy direction.
16→12 dgs.client uses types.subscription✕
- Connections
- 2 pairs of types, where a type in dgs.client uses a type in types.subscription.
- The types involved
com.netflix.graphql.dgs.client.OperationMessageWebSocketClient→com.netflix.graphql.types.subscription.OperationMessagecom.netflix.graphql.dgs.client.WebSocketGraphQLClient→com.netflix.graphql.types.subscription.OperationMessage
- Direction
- dgs.client uses types.subscription, so a change to types.subscription can break dgs.client, while a change to dgs.client can't break types.subscription.
- Position
- Below the diagonal: dgs.client uses a module listed above it, which is the healthy direction.
17→24 dgs.internal.DgsSchemaProvider.Companion uses dgs.internal part of a loop✕
- Connections
- 2 pairs of types, where a type in dgs.internal.DgsSchemaProvider.Companion uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.internal.DgsSchemaProvider.Companion.DataFetcherInfo→com.netflix.graphql.dgs.internal.DataFetcherReferencecom.netflix.graphql.dgs.internal.DgsSchemaProvider.Companion.MutableDataFetcherInfo→com.netflix.graphql.dgs.internal.DataFetcherReference
- Direction
- dgs.internal.DgsSchemaProvider.Companion uses dgs.internal, so a change to dgs.internal can break dgs.internal.DgsSchemaProvider.Companion, while a change to dgs.internal.DgsSchemaProvider.Companion can't break dgs.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→24 dgs.internal.method uses dgs.internal part of a loop✕
- Connections
- 4 pairs of types, where a type in dgs.internal.method uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.internal.method.AbstractInputArgumentResolver→com.netflix.graphql.dgs.internal.InputObjectMappercom.netflix.graphql.dgs.internal.method.FallbackEnvironmentArgumentResolver→com.netflix.graphql.dgs.internal.InputObjectMappercom.netflix.graphql.dgs.internal.method.InputArgumentResolver→com.netflix.graphql.dgs.internal.InputObjectMappercom.netflix.graphql.dgs.internal.method.InputObjectMapperConverter→com.netflix.graphql.dgs.internal.InputObjectMapper
- Direction
- dgs.internal.method uses dgs.internal, so a change to dgs.internal can break dgs.internal.method, while a change to dgs.internal.method can't break dgs.internal.
- 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→10 dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses dgs.metrics.micrometer.utils.QuerySignatureRepository✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses a type in dgs.metrics.micrometer.utils.QuerySignatureRepository.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationState→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository.QuerySignature
- Direction
- dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses dgs.metrics.micrometer.utils.QuerySignatureRepository, so a change to dgs.metrics.micrometer.utils.QuerySignatureRepository can break dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation, while a change to dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation can't break dgs.metrics.micrometer.utils.QuerySignatureRepository.
- Position
- Below the diagonal: dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses a module listed above it, which is the healthy direction.
19→37 dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses dgs.metrics.micrometer part of a loop✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses a type in dgs.metrics.micrometer.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationState→com.netflix.graphql.dgs.metrics.micrometer.LimitedTagMetricResolver
- Direction
- dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation uses dgs.metrics.micrometer, so a change to dgs.metrics.micrometer can break dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation, while a change to dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation can't break dgs.metrics.micrometer.
- 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→10 dgs.metrics.micrometer.utils uses dgs.metrics.micrometer.utils.QuerySignatureRepository✕
- Connections
- 3 pairs of types, where a type in dgs.metrics.micrometer.utils uses a type in dgs.metrics.micrometer.utils.QuerySignatureRepository.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.utils.CacheableQuerySignatureRepository→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository.QuerySignaturecom.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository.QuerySignaturecom.netflix.graphql.dgs.metrics.micrometer.utils.SimpleQuerySignatureRepository→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository.QuerySignature
- Direction
- dgs.metrics.micrometer.utils uses dgs.metrics.micrometer.utils.QuerySignatureRepository, so a change to dgs.metrics.micrometer.utils.QuerySignatureRepository can break dgs.metrics.micrometer.utils, while a change to dgs.metrics.micrometer.utils can't break dgs.metrics.micrometer.utils.QuerySignatureRepository.
- Position
- Below the diagonal: dgs.metrics.micrometer.utils uses a module listed above it, which is the healthy direction.
20→37 dgs.metrics.micrometer.utils uses dgs.metrics.micrometer part of a loop✕
- Connections
- 2 pairs of types, where a type in dgs.metrics.micrometer.utils uses a type in dgs.metrics.micrometer.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.utils.CacheableQuerySignatureRepository→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySuppliercom.netflix.graphql.dgs.metrics.micrometer.utils.SimpleQuerySignatureRepository→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySupplier
- Direction
- dgs.metrics.micrometer.utils uses dgs.metrics.micrometer, so a change to dgs.metrics.micrometer can break dgs.metrics.micrometer.utils, while a change to dgs.metrics.micrometer.utils can't break dgs.metrics.micrometer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→13 types.subscription.websockets.Message uses types.subscription.websockets✕
- Connections
- 9 pairs of types, where a type in types.subscription.websockets.Message uses a type in types.subscription.websockets.
- The types involved
com.netflix.graphql.types.subscription.websockets.Message.CompleteMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.ConnectionAckMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.ConnectionInitMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.ErrorMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.NextMessage→com.netflix.graphql.types.subscription.websockets.ExecutionResultcom.netflix.graphql.types.subscription.websockets.Message.NextMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.PingMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.PongMessage→com.netflix.graphql.types.subscription.websockets.Messagecom.netflix.graphql.types.subscription.websockets.Message.SubscribeMessage→com.netflix.graphql.types.subscription.websockets.Message
- Direction
- types.subscription.websockets.Message uses types.subscription.websockets, so a change to types.subscription.websockets can break types.subscription.websockets.Message, while a change to types.subscription.websockets.Message can't break types.subscription.websockets.
- Position
- Below the diagonal: types.subscription.websockets.Message uses a module listed above it, which is the healthy direction.
22→14 dgs.apq.DgsAPQSupportAutoConfiguration uses dgs.apq✕
- Connections
- 1 pair of types, where a type in dgs.apq.DgsAPQSupportAutoConfiguration uses a type in dgs.apq.
- The types involved
com.netflix.graphql.dgs.apq.DgsAPQSupportAutoConfiguration.APQCaffeineCacheConfiguration→com.netflix.graphql.dgs.apq.DgsAPQSupportProperties
- Direction
- dgs.apq.DgsAPQSupportAutoConfiguration uses dgs.apq, so a change to dgs.apq can break dgs.apq.DgsAPQSupportAutoConfiguration, while a change to dgs.apq.DgsAPQSupportAutoConfiguration can't break dgs.apq.
- Position
- Below the diagonal: dgs.apq.DgsAPQSupportAutoConfiguration uses a module listed above it, which is the healthy direction.
23→16 dgs.client.ErrorType uses dgs.client✕
- Connections
- 8 pairs of types, where a type in dgs.client.ErrorType uses a type in dgs.client.
- The types involved
com.netflix.graphql.dgs.client.ErrorType.BAD_REQUEST→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.FAILED_PRECONDITION→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.INTERNAL→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.NOT_FOUND→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.PERMISSION_DENIED→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.UNAUTHENTICATED→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.UNAVAILABLE→com.netflix.graphql.dgs.client.ErrorTypecom.netflix.graphql.dgs.client.ErrorType.UNKNOWN→com.netflix.graphql.dgs.client.ErrorType
- Direction
- dgs.client.ErrorType uses dgs.client, so a change to dgs.client can break dgs.client.ErrorType, while a change to dgs.client.ErrorType can't break dgs.client.
- Position
- Below the diagonal: dgs.client.ErrorType uses a module listed above it, which is the healthy direction.
24→1 dgs.internal uses dgs.DgsDataLoaderReloadController✕
- Connections
- 1 pair of types, where a type in dgs.internal uses a type in dgs.DgsDataLoaderReloadController.
- The types involved
com.netflix.graphql.dgs.internal.DefaultDgsDataLoaderReloadController→com.netflix.graphql.dgs.DgsDataLoaderReloadController.DgsDataLoaderReloadStats
- Direction
- dgs.internal uses dgs.DgsDataLoaderReloadController, so a change to dgs.DgsDataLoaderReloadController can break dgs.internal, while a change to dgs.internal can't break dgs.DgsDataLoaderReloadController.
- Position
- Below the diagonal: dgs.internal uses a module listed above it, which is the healthy direction.
24→7 dgs.internal uses dgs.json✕
- Connections
- 1 pair of types, where a type in dgs.internal uses a type in dgs.json.
- The types involved
com.netflix.graphql.dgs.internal.Jackson3DgsJsonMapper→com.netflix.graphql.dgs.json.DgsJsonMapper
- Direction
- dgs.internal uses dgs.json, so a change to dgs.json can break dgs.internal, while a change to dgs.internal can't break dgs.json.
- Position
- Below the diagonal: dgs.internal uses a module listed above it, which is the healthy direction.
24→17 dgs.internal uses dgs.internal.DgsSchemaProvider.Companion✕
- Connections
- 3 pairs of types, where a type in dgs.internal uses a type in dgs.internal.DgsSchemaProvider.Companion.
- The types involved
com.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.internal.DgsSchemaProvider.Companion.DataFetcherInfocom.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.internal.DgsSchemaProvider.Companion.DgsBeancom.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.internal.DgsSchemaProvider.Companion.MutableDataFetcherInfo
- Direction
- dgs.internal uses dgs.internal.DgsSchemaProvider.Companion, so a change to dgs.internal.DgsSchemaProvider.Companion can break dgs.internal, while a change to dgs.internal can't break dgs.internal.DgsSchemaProvider.Companion.
- Position
- Below the diagonal: dgs.internal uses a module listed above it, which is the healthy direction.
24→18 dgs.internal uses dgs.internal.method✕
- Connections
- 2 pairs of types, where a type in dgs.internal uses a type in dgs.internal.method.
- The types involved
com.netflix.graphql.dgs.internal.DataFetcherInvoker→com.netflix.graphql.dgs.internal.method.ArgumentResolverCompositecom.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.internal.method.MethodDataFetcherFactory
- Direction
- dgs.internal uses dgs.internal.method, so a change to dgs.internal.method can break dgs.internal, while a change to dgs.internal can't break dgs.internal.method.
- Position
- Below the diagonal: dgs.internal uses a module listed above it, which is the healthy direction.
24→27 dgs.internal uses dgs.context part of a loop✕
- Connections
- 4 pairs of types, where a type in dgs.internal uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.internal.BaseDgsQueryExecutor→com.netflix.graphql.dgs.context.DgsContextcom.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuilder→com.netflix.graphql.dgs.context.DgsContextcom.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuilder→com.netflix.graphql.dgs.context.DgsCustomContextBuildercom.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuilder→com.netflix.graphql.dgs.context.DgsCustomContextBuilderWithRequest
- Direction
- dgs.internal uses dgs.context, so a change to dgs.context can break dgs.internal, while a change to dgs.internal can't break dgs.context.
- 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→28 dgs.internal uses dgs part of a loop✕
- Connections
- 24 pairs of types, where a type in dgs.internal uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.internal.BatchLoaderWithContextInstrumentationDriver→com.netflix.graphql.dgs.DgsDataLoaderInstrumentationcom.netflix.graphql.dgs.internal.BatchLoaderWithContextInstrumentationDriver→com.netflix.graphql.dgs.DgsDataLoaderRegistryConsumercom.netflix.graphql.dgs.internal.BatchLoaderWithContextWrapper→com.netflix.graphql.dgs.DgsDataLoaderRegistryConsumercom.netflix.graphql.dgs.internal.DataFetcherResultProcessor→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.internal.DefaultDataLoaderOptionsProvider→com.netflix.graphql.dgs.DgsDataLoaderOptionsProvidercom.netflix.graphql.dgs.internal.DefaultDgsDataLoaderProvider→com.netflix.graphql.dgs.DataLoaderInstrumentationExtensionProvidercom.netflix.graphql.dgs.internal.DefaultDgsDataLoaderProvider→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.internal.DefaultDgsDataLoaderProvider→com.netflix.graphql.dgs.DgsDataLoaderOptionsProvidercom.netflix.graphql.dgs.internal.DefaultDgsDataLoaderReloadController→com.netflix.graphql.dgs.DgsDataLoaderReloadControllercom.netflix.graphql.dgs.internal.DgsDataLoaderInstrumentationDataLoaderCustomizer→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.internal.DgsDataLoaderInstrumentationDataLoaderCustomizer→com.netflix.graphql.dgs.DgsDataLoaderInstrumentationcom.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.DgsCodeRegistryBuildercom.netflix.graphql.dgs.internal.DgsSchemaProvider→com.netflix.graphql.dgs.DgsFederationResolvercom.netflix.graphql.dgs.internal.DgsWrapWithContextDataLoaderCustomizer→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.internal.FlowDataFetcherResultProcessor→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.internal.FluxDataFetcherResultProcessor→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.internal.MappedBatchLoaderWithContextInstrumentationDriver→com.netflix.graphql.dgs.DgsDataLoaderInstrumentationcom.netflix.graphql.dgs.internal.MappedBatchLoaderWithContextInstrumentationDriver→com.netflix.graphql.dgs.DgsDataLoaderRegistryConsumercom.netflix.graphql.dgs.internal.MappedBatchLoaderWithContextWrapper→com.netflix.graphql.dgs.DgsDataLoaderRegistryConsumercom.netflix.graphql.dgs.internal.MonoDataFetcherResultProcessor→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.internal.ReactiveDataFetcherResultProcessorKt→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.internal.ReloadableDgsDataLoaderProvider→com.netflix.graphql.dgs.DataLoaderInstrumentationExtensionProvidercom.netflix.graphql.dgs.internal.ReloadableDgsDataLoaderProvider→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.internal.ReloadableDgsDataLoaderProvider→com.netflix.graphql.dgs.DgsDataLoaderOptionsProvider
- Direction
- dgs.internal uses dgs, so a change to dgs can break dgs.internal, while a change to dgs.internal can't break dgs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→19 dgs.metrics.micrometer.tagging uses dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation✕
- Connections
- 4 pairs of types, where a type in dgs.metrics.micrometer.tagging uses a type in dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsExecutionTagCustomizer→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationStatecom.netflix.graphql.dgs.metrics.micrometer.tagging.DgsFieldFetchTagCustomizer→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationStatecom.netflix.graphql.dgs.metrics.micrometer.tagging.DgsGraphQLMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationStatecom.netflix.graphql.dgs.metrics.micrometer.tagging.SimpleGqlOutcomeTagCustomizer→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationState
- Direction
- dgs.metrics.micrometer.tagging uses dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation, so a change to dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation can break dgs.metrics.micrometer.tagging, while a change to dgs.metrics.micrometer.tagging can't break dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.
- Position
- Below the diagonal: dgs.metrics.micrometer.tagging uses a module listed above it, which is the healthy direction.
26→3 dgs.autoconfig uses dgs.autoconfig.DgsConfigurationProperties✕
- Connections
- 4 pairs of types, where a type in dgs.autoconfig uses a type in dgs.autoconfig.DgsConfigurationProperties.
- The types involved
com.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties→com.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties.DgsFederationPropertiescom.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties→com.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties.DgsIntrospectionConfigurationPropertiescom.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties→com.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties.DgsPreparsedDocumentProviderConfigurationPropertiescom.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties→com.netflix.graphql.dgs.autoconfig.DgsConfigurationProperties.DgsStrictModeProperties
- Direction
- dgs.autoconfig uses dgs.autoconfig.DgsConfigurationProperties, so a change to dgs.autoconfig.DgsConfigurationProperties can break dgs.autoconfig, while a change to dgs.autoconfig can't break dgs.autoconfig.DgsConfigurationProperties.
- Position
- Below the diagonal: dgs.autoconfig uses a module listed above it, which is the healthy direction.
26→5 dgs.autoconfig uses dgs.autoconfig.DgsExtendedValidationAutoConfiguration✕
- Connections
- 1 pair of types, where a type in dgs.autoconfig uses a type in dgs.autoconfig.DgsExtendedValidationAutoConfiguration.
- The types involved
com.netflix.graphql.dgs.autoconfig.DgsExtendedValidationAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsExtendedValidationAutoConfiguration.ExtendedValidationRegistrar
- Direction
- dgs.autoconfig uses dgs.autoconfig.DgsExtendedValidationAutoConfiguration, so a change to dgs.autoconfig.DgsExtendedValidationAutoConfiguration can break dgs.autoconfig, while a change to dgs.autoconfig can't break dgs.autoconfig.DgsExtendedValidationAutoConfiguration.
- Position
- Below the diagonal: dgs.autoconfig uses a module listed above it, which is the healthy direction.
26→18 dgs.autoconfig uses dgs.internal.method✕
- Connections
- 1 pair of types, where a type in dgs.autoconfig uses a type in dgs.internal.method.
- The types involved
com.netflix.graphql.dgs.autoconfig.DgsInputArgumentConfiguration→com.netflix.graphql.dgs.internal.method.ArgumentResolver
- Direction
- dgs.autoconfig uses dgs.internal.method, so a change to dgs.internal.method can break dgs.autoconfig, while a change to dgs.autoconfig can't break dgs.internal.method.
- Position
- Below the diagonal: dgs.autoconfig uses a module listed above it, which is the healthy direction.
26→24 dgs.autoconfig uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs.autoconfig uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.autoconfig.DgsInputArgumentConfiguration→com.netflix.graphql.dgs.internal.InputObjectMapper
- Direction
- dgs.autoconfig uses dgs.internal, so a change to dgs.internal can break dgs.autoconfig, while a change to dgs.autoconfig can't break dgs.internal.
- Position
- Below the diagonal: dgs.autoconfig uses a module listed above it, which is the healthy direction.
27→24 dgs.context uses dgs.internal✕
- Connections
- 3 pairs of types, where a type in dgs.context uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.context.DgsContext→com.netflix.graphql.dgs.internal.DgsRequestDatacom.netflix.graphql.dgs.context.GraphQLContextContributor→com.netflix.graphql.dgs.internal.DgsRequestDatacom.netflix.graphql.dgs.context.ReactiveDgsContext→com.netflix.graphql.dgs.internal.DgsRequestData
- Direction
- dgs.context uses dgs.internal, so a change to dgs.internal can break dgs.context, while a change to dgs.context can't break dgs.internal.
- Position
- Below the diagonal: dgs.context uses a module listed above it, which is the healthy direction.
28→1 dgs uses dgs.DgsDataLoaderReloadController✕
- Connections
- 1 pair of types, where a type in dgs uses a type in dgs.DgsDataLoaderReloadController.
- The types involved
com.netflix.graphql.dgs.DgsDataLoaderReloadController→com.netflix.graphql.dgs.DgsDataLoaderReloadController.DgsDataLoaderReloadStats
- Direction
- dgs uses dgs.DgsDataLoaderReloadController, so a change to dgs.DgsDataLoaderReloadController can break dgs, while a change to dgs can't break dgs.DgsDataLoaderReloadController.
- Position
- Below the diagonal: dgs uses a module listed above it, which is the healthy direction.
28→24 dgs uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.DgsCodeRegistryBuilder→com.netflix.graphql.dgs.internal.DataFetcherResultProcessor
- Direction
- dgs uses dgs.internal, so a change to dgs.internal can break dgs, while a change to dgs can't break dgs.internal.
- Position
- Below the diagonal: dgs uses a module listed above it, which is the healthy direction.
28→27 dgs uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.DgsDataFetchingEnvironment→com.netflix.graphql.dgs.context.DgsContext
- Direction
- dgs uses dgs.context, so a change to dgs.context can break dgs, while a change to dgs can't break dgs.context.
- Position
- Below the diagonal: dgs uses a module listed above it, which is the healthy direction.
29→24 dgs.context.DgsContext uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs.context.DgsContext uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.context.DgsContext.Companion→com.netflix.graphql.dgs.internal.DgsRequestData
- Direction
- dgs.context.DgsContext uses dgs.internal, so a change to dgs.internal can break dgs.context.DgsContext, while a change to dgs.context.DgsContext can't break dgs.internal.
- Position
- Below the diagonal: dgs.context.DgsContext uses a module listed above it, which is the healthy direction.
29→27 dgs.context.DgsContext uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs.context.DgsContext uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.context.DgsContext.Companion→com.netflix.graphql.dgs.context.DgsContext
- Direction
- dgs.context.DgsContext uses dgs.context, so a change to dgs.context can break dgs.context.DgsContext, while a change to dgs.context.DgsContext can't break dgs.context.
- Position
- Below the diagonal: dgs.context.DgsContext uses a module listed above it, which is the healthy direction.
30→11 dgs.reactive.internal uses dgs.reactive✕
- Connections
- 1 pair of types, where a type in dgs.reactive.internal uses a type in dgs.reactive.
- The types involved
com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuilder→com.netflix.graphql.dgs.reactive.DgsReactiveCustomContextBuilderWithRequest
- Direction
- dgs.reactive.internal uses dgs.reactive, so a change to dgs.reactive can break dgs.reactive.internal, while a change to dgs.reactive.internal can't break dgs.reactive.
- Position
- Below the diagonal: dgs.reactive.internal uses a module listed above it, which is the healthy direction.
30→24 dgs.reactive.internal uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs.reactive.internal uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.reactive.internal.DgsReactiveRequestData→com.netflix.graphql.dgs.internal.DgsRequestData
- Direction
- dgs.reactive.internal uses dgs.internal, so a change to dgs.internal can break dgs.reactive.internal, while a change to dgs.reactive.internal can't break dgs.internal.
- Position
- Below the diagonal: dgs.reactive.internal uses a module listed above it, which is the healthy direction.
30→27 dgs.reactive.internal uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs.reactive.internal uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuilder→com.netflix.graphql.dgs.context.DgsContext
- Direction
- dgs.reactive.internal uses dgs.context, so a change to dgs.context can break dgs.reactive.internal, while a change to dgs.reactive.internal can't break dgs.context.
- Position
- Below the diagonal: dgs.reactive.internal uses a module listed above it, which is the healthy direction.
31→24 dgs.springgraphql.webmvc uses dgs.internal✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.webmvc uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.webmvc.DgsWebMvcGraphQLInterceptor→com.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuildercom.netflix.graphql.dgs.springgraphql.webmvc.DgsWebMvcGraphQLInterceptor→com.netflix.graphql.dgs.internal.DgsDataLoaderProvider
- Direction
- dgs.springgraphql.webmvc uses dgs.internal, so a change to dgs.internal can break dgs.springgraphql.webmvc, while a change to dgs.springgraphql.webmvc can't break dgs.internal.
- Position
- Below the diagonal: dgs.springgraphql.webmvc uses a module listed above it, which is the healthy direction.
31→27 dgs.springgraphql.webmvc uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.webmvc uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.springgraphql.webmvc.DgsWebMvcGraphQLInterceptor→com.netflix.graphql.dgs.context.GraphQLContextContributor
- Direction
- dgs.springgraphql.webmvc uses dgs.context, so a change to dgs.context can break dgs.springgraphql.webmvc, while a change to dgs.springgraphql.webmvc can't break dgs.context.
- Position
- Below the diagonal: dgs.springgraphql.webmvc uses a module listed above it, which is the healthy direction.
31→40 dgs.springgraphql.webmvc uses dgs.springgraphql.autoconfig part of a loop✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.webmvc uses a type in dgs.springgraphql.autoconfig.
- The types involved
com.netflix.graphql.dgs.springgraphql.webmvc.DgsWebMvcGraphQLInterceptor→com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLConfigurationProperties
- Direction
- dgs.springgraphql.webmvc uses dgs.springgraphql.autoconfig, so a change to dgs.springgraphql.autoconfig can break dgs.springgraphql.webmvc, while a change to dgs.springgraphql.webmvc can't break dgs.springgraphql.autoconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→28 dgs.DgsExecutionResult uses dgs✕
- Connections
- 1 pair of types, where a type in dgs.DgsExecutionResult uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.DgsExecutionResult.Builder→com.netflix.graphql.dgs.DgsExecutionResult
- Direction
- dgs.DgsExecutionResult uses dgs, so a change to dgs can break dgs.DgsExecutionResult, while a change to dgs.DgsExecutionResult can't break dgs.
- Position
- Below the diagonal: dgs.DgsExecutionResult uses a module listed above it, which is the healthy direction.
33→24 dgs.federation uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs.federation uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.federation.DefaultDgsFederationResolver→com.netflix.graphql.dgs.internal.EntityFetcherRegistry
- Direction
- dgs.federation uses dgs.internal, so a change to dgs.internal can break dgs.federation, while a change to dgs.federation can't break dgs.internal.
- Position
- Below the diagonal: dgs.federation uses a module listed above it, which is the healthy direction.
33→28 dgs.federation uses dgs✕
- Connections
- 2 pairs of types, where a type in dgs.federation uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.federation.DefaultDgsFederationResolver→com.netflix.graphql.dgs.DgsDataFetchingEnvironmentcom.netflix.graphql.dgs.federation.DefaultDgsFederationResolver→com.netflix.graphql.dgs.DgsFederationResolver
- Direction
- dgs.federation uses dgs, so a change to dgs can break dgs.federation, while a change to dgs.federation can't break dgs.
- Position
- Below the diagonal: dgs.federation uses a module listed above it, which is the healthy direction.
34→28 dgs.metrics.micrometer.dataloader uses dgs✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.dataloader uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.dataloader.DgsDataLoaderInstrumentationProvider→com.netflix.graphql.dgs.DataLoaderInstrumentationExtensionProvider
- Direction
- dgs.metrics.micrometer.dataloader uses dgs, so a change to dgs can break dgs.metrics.micrometer.dataloader, while a change to dgs.metrics.micrometer.dataloader can't break dgs.
- Position
- Below the diagonal: dgs.metrics.micrometer.dataloader uses a module listed above it, which is the healthy direction.
34→37 dgs.metrics.micrometer.dataloader uses dgs.metrics.micrometer part of a loop✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.dataloader uses a type in dgs.metrics.micrometer.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.dataloader.DgsDataLoaderInstrumentationProvider→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySupplier
- Direction
- dgs.metrics.micrometer.dataloader uses dgs.metrics.micrometer, so a change to dgs.metrics.micrometer can break dgs.metrics.micrometer.dataloader, while a change to dgs.metrics.micrometer.dataloader can't break dgs.metrics.micrometer.
- 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→7 dgs.springgraphql uses dgs.json✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql uses a type in dgs.json.
- The types involved
com.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsReactiveQueryExecutor→com.netflix.graphql.dgs.json.DgsJsonMapper
- Direction
- dgs.springgraphql uses dgs.json, so a change to dgs.json can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.json.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
35→11 dgs.springgraphql uses dgs.reactive✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql uses a type in dgs.reactive.
- The types involved
com.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsReactiveQueryExecutor→com.netflix.graphql.dgs.reactive.DgsReactiveQueryExecutor
- Direction
- dgs.springgraphql uses dgs.reactive, so a change to dgs.reactive can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.reactive.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
35→24 dgs.springgraphql uses dgs.internal✕
- Connections
- 7 pairs of types, where a type in dgs.springgraphql uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.DgsGraphQLSourceBuilder→com.netflix.graphql.dgs.internal.DataFetcherReferencecom.netflix.graphql.dgs.springgraphql.DgsGraphQLSourceBuilder→com.netflix.graphql.dgs.internal.DgsSchemaProvidercom.netflix.graphql.dgs.springgraphql.DgsGraphQLSourceBuilder→com.netflix.graphql.dgs.internal.SchemaProviderResultcom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuildercom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.internal.DgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.internal.DgsQueryExecutorRequestCustomizercom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsReactiveQueryExecutor→com.netflix.graphql.dgs.internal.DgsDataLoaderProvider
- Direction
- dgs.springgraphql uses dgs.internal, so a change to dgs.internal can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.internal.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
35→27 dgs.springgraphql uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.context.GraphQLContextContributor
- Direction
- dgs.springgraphql uses dgs.context, so a change to dgs.context can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.context.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
35→28 dgs.springgraphql uses dgs✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.springgraphql.ReloadableGraphQLSource→com.netflix.graphql.dgs.ReloadSchemaIndicatorcom.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsQueryExecutor→com.netflix.graphql.dgs.DgsQueryExecutor
- Direction
- dgs.springgraphql uses dgs, so a change to dgs can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
35→30 dgs.springgraphql uses dgs.reactive.internal✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql uses a type in dgs.reactive.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.SpringGraphQLDgsReactiveQueryExecutor→com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuilder
- Direction
- dgs.springgraphql uses dgs.reactive.internal, so a change to dgs.reactive.internal can break dgs.springgraphql, while a change to dgs.springgraphql can't break dgs.reactive.internal.
- Position
- Below the diagonal: dgs.springgraphql uses a module listed above it, which is the healthy direction.
36→24 dgs.springgraphql.webflux uses dgs.internal✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.webflux uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.webflux.DgsWebFluxGraphQLInterceptor→com.netflix.graphql.dgs.internal.DgsDataLoaderProvider
- Direction
- dgs.springgraphql.webflux uses dgs.internal, so a change to dgs.internal can break dgs.springgraphql.webflux, while a change to dgs.springgraphql.webflux can't break dgs.internal.
- Position
- Below the diagonal: dgs.springgraphql.webflux uses a module listed above it, which is the healthy direction.
36→30 dgs.springgraphql.webflux uses dgs.reactive.internal✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.webflux uses a type in dgs.reactive.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.webflux.DgsWebFluxGraphQLInterceptor→com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuilder
- Direction
- dgs.springgraphql.webflux uses dgs.reactive.internal, so a change to dgs.reactive.internal can break dgs.springgraphql.webflux, while a change to dgs.springgraphql.webflux can't break dgs.reactive.internal.
- Position
- Below the diagonal: dgs.springgraphql.webflux uses a module listed above it, which is the healthy direction.
37→9 dgs.metrics.micrometer uses dgs.metrics.micrometer.DgsGraphQLMetricsProperties✕
- Connections
- 5 pairs of types, where a type in dgs.metrics.micrometer uses a type in dgs.metrics.micrometer.DgsGraphQLMetricsProperties.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties.QueryMetricPropertiescom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties.ResolverMetricPropertiescom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties.TagsPropertiescom.netflix.graphql.dgs.metrics.micrometer.SpectatorLimitedTagMetricResolver→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties.CardinalityLimiterPropertiescom.netflix.graphql.dgs.metrics.micrometer.SpectatorLimitedTagMetricResolver→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsProperties.TagsProperties
- Direction
- dgs.metrics.micrometer uses dgs.metrics.micrometer.DgsGraphQLMetricsProperties, so a change to dgs.metrics.micrometer.DgsGraphQLMetricsProperties can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.metrics.micrometer.DgsGraphQLMetricsProperties.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
37→19 dgs.metrics.micrometer uses dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation✕
- Connections
- 3 pairs of types, where a type in dgs.metrics.micrometer uses a type in dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLCollatedMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationStatecom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.MetricsInstrumentationStatecom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.PersistedQueryType
- Direction
- dgs.metrics.micrometer uses dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation, so a change to dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
37→20 dgs.metrics.micrometer uses dgs.metrics.micrometer.utils✕
- Connections
- 2 pairs of types, where a type in dgs.metrics.micrometer uses a type in dgs.metrics.micrometer.utils.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepositorycom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository
- Direction
- dgs.metrics.micrometer uses dgs.metrics.micrometer.utils, so a change to dgs.metrics.micrometer.utils can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.metrics.micrometer.utils.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
37→24 dgs.metrics.micrometer uses dgs.internal✕
- Connections
- 2 pairs of types, where a type in dgs.metrics.micrometer uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation→com.netflix.graphql.dgs.internal.DgsSchemaProvidercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.internal.DgsSchemaProvider
- Direction
- dgs.metrics.micrometer uses dgs.internal, so a change to dgs.internal can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.internal.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
37→25 dgs.metrics.micrometer uses dgs.metrics.micrometer.tagging✕
- Connections
- 9 pairs of types, where a type in dgs.metrics.micrometer uses a type in dgs.metrics.micrometer.tagging.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLCollatedMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsContextualTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLCollatedMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsExecutionTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLCollatedMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsFieldFetchTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLCollatedMetricsTagsProvider→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsGraphQLMetricsTagsProvidercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsInstrumentation→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsGraphQLMetricsTagsProvidercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsContextualTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsExecutionTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsFieldFetchTagCustomizercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.tagging.DgsGraphQLMetricsTagsProvider
- Direction
- dgs.metrics.micrometer uses dgs.metrics.micrometer.tagging, so a change to dgs.metrics.micrometer.tagging can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.metrics.micrometer.tagging.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
37→34 dgs.metrics.micrometer uses dgs.metrics.micrometer.dataloader✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer uses a type in dgs.metrics.micrometer.dataloader.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration→com.netflix.graphql.dgs.metrics.micrometer.dataloader.DgsDataLoaderInstrumentationProvider
- Direction
- dgs.metrics.micrometer uses dgs.metrics.micrometer.dataloader, so a change to dgs.metrics.micrometer.dataloader can break dgs.metrics.micrometer, while a change to dgs.metrics.micrometer can't break dgs.metrics.micrometer.dataloader.
- Position
- Below the diagonal: dgs.metrics.micrometer uses a module listed above it, which is the healthy direction.
38→7 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.json✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.json.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.Jackson3DgsJsonMapperConfiguration→com.netflix.graphql.dgs.json.DgsJsonMappercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.ReactiveConfiguration→com.netflix.graphql.dgs.json.DgsJsonMapper
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.json, so a change to dgs.json can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.json.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→11 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.reactive✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.reactive.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.ReactiveConfiguration→com.netflix.graphql.dgs.reactive.DgsReactiveCustomContextBuilderWithRequest
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.reactive, so a change to dgs.reactive can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.reactive.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→18 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.internal.method✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.internal.method.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebFluxArgumentHandlerConfiguration→com.netflix.graphql.dgs.internal.method.ArgumentResolvercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcArgumentHandlerConfiguration→com.netflix.graphql.dgs.internal.method.ArgumentResolver
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.internal.method, so a change to dgs.internal.method can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.internal.method.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→24 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.internal✕
- Connections
- 5 pairs of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.internal.ReloadableDgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.ReactiveConfiguration→com.netflix.graphql.dgs.internal.DgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebFluxConfiguration→com.netflix.graphql.dgs.internal.DgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcConfiguration→com.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuildercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcConfiguration→com.netflix.graphql.dgs.internal.DgsDataLoaderProvider
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.internal, so a change to dgs.internal can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.internal.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→26 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.autoconfig✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.autoconfig.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsDataloaderConfigurationProperties
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.autoconfig, so a change to dgs.autoconfig can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.autoconfig.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→27 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.context✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcConfiguration→com.netflix.graphql.dgs.context.GraphQLContextContributor
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.context, so a change to dgs.context can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.context.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→28 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs✕
- Connections
- 4 pairs of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.DataLoaderInstrumentationExtensionProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderOptionsProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsDataLoaderReloadAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderReloadController
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs, so a change to dgs can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→30 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.reactive.internal✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.reactive.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.ReactiveConfiguration→com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuildercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebFluxConfiguration→com.netflix.graphql.dgs.reactive.internal.DefaultDgsReactiveGraphQLContextBuilder
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.reactive.internal, so a change to dgs.reactive.internal can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.reactive.internal.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→31 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.webmvc✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.springgraphql.webmvc.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcConfiguration→com.netflix.graphql.dgs.springgraphql.webmvc.DgsWebMvcGraphQLInterceptor
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.webmvc, so a change to dgs.springgraphql.webmvc can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.springgraphql.webmvc.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→36 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.webflux✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.springgraphql.webflux.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebFluxConfiguration→com.netflix.graphql.dgs.springgraphql.webflux.DgsWebFluxGraphQLInterceptor
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.webflux, so a change to dgs.springgraphql.webflux can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.springgraphql.webflux.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a module listed above it, which is the healthy direction.
38→40 dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.autoconfig part of a loop✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses a type in dgs.springgraphql.autoconfig.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.WebMvcConfiguration→com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLConfigurationProperties
- Direction
- dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration uses dgs.springgraphql.autoconfig, so a change to dgs.springgraphql.autoconfig can break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, while a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can't break dgs.springgraphql.autoconfig.
- 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.
39→20 dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer.utils✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a type in dgs.metrics.micrometer.utils.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.QuerySignatureRepositoryConfiguration→com.netflix.graphql.dgs.metrics.micrometer.utils.QuerySignatureRepository
- Direction
- dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer.utils, so a change to dgs.metrics.micrometer.utils can break dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration, while a change to dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration can't break dgs.metrics.micrometer.utils.
- Position
- Below the diagonal: dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a module listed above it, which is the healthy direction.
39→25 dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer.tagging✕
- Connections
- 1 pair of types, where a type in dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a type in dgs.metrics.micrometer.tagging.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.OptionalTagCustomizersConfiguration→com.netflix.graphql.dgs.metrics.micrometer.tagging.SimpleGqlOutcomeTagCustomizer
- Direction
- dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer.tagging, so a change to dgs.metrics.micrometer.tagging can break dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration, while a change to dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration can't break dgs.metrics.micrometer.tagging.
- Position
- Below the diagonal: dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a module listed above it, which is the healthy direction.
39→37 dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer✕
- Connections
- 4 pairs of types, where a type in dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a type in dgs.metrics.micrometer.
- The types involved
com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.DefaultMeterRegistrySupplier→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySuppliercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.MeterRegistryConfiguration→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySuppliercom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.QuerySignatureRepositoryConfiguration→com.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMetricsPropertiescom.netflix.graphql.dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration.QuerySignatureRepositoryConfiguration→com.netflix.graphql.dgs.metrics.micrometer.DgsMeterRegistrySupplier
- Direction
- dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses dgs.metrics.micrometer, so a change to dgs.metrics.micrometer can break dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration, while a change to dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration can't break dgs.metrics.micrometer.
- Position
- Below the diagonal: dgs.metrics.micrometer.DgsGraphQLMicrometerAutoConfiguration uses a module listed above it, which is the healthy direction.
40→7 dgs.springgraphql.autoconfig uses dgs.json✕
- Connections
- 1 pair of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.json.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.json.DgsJsonMapper
- Direction
- dgs.springgraphql.autoconfig uses dgs.json, so a change to dgs.json can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.json.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→18 dgs.springgraphql.autoconfig uses dgs.internal.method✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.internal.method.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.method.ArgumentResolvercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.method.MethodDataFetcherFactory
- Direction
- dgs.springgraphql.autoconfig uses dgs.internal.method, so a change to dgs.internal.method can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.internal.method.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→24 dgs.springgraphql.autoconfig uses dgs.internal✕
- Connections
- 12 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.internal.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DataFetcherResultProcessorcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DefaultDgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DefaultDgsGraphQLContextBuildercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DgsDataLoaderProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DgsQueryExecutorRequestCustomizercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DgsSchemaProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.DgsWrapWithContextDataLoaderCustomizercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.EntityFetcherRegistrycom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.FlowDataFetcherResultProcessorcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.FluxDataFetcherResultProcessorcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.MonoDataFetcherResultProcessorcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.internal.QueryValueCustomizer
- Direction
- dgs.springgraphql.autoconfig uses dgs.internal, so a change to dgs.internal can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.internal.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→26 dgs.springgraphql.autoconfig uses dgs.autoconfig✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.autoconfig.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsConfigurationPropertiescom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.autoconfig.DgsDataloaderConfigurationProperties
- Direction
- dgs.springgraphql.autoconfig uses dgs.autoconfig, so a change to dgs.autoconfig can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.autoconfig.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→27 dgs.springgraphql.autoconfig uses dgs.context✕
- Connections
- 3 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.context.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.context.DgsCustomContextBuildercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.context.DgsCustomContextBuilderWithRequestcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.context.GraphQLContextContributor
- Direction
- dgs.springgraphql.autoconfig uses dgs.context, so a change to dgs.context can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.context.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→28 dgs.springgraphql.autoconfig uses dgs✕
- Connections
- 6 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.DataLoaderInstrumentationExtensionProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderCustomizercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderInstrumentationcom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.DgsDataLoaderOptionsProvidercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.DgsFederationResolvercom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.ReloadSchemaIndicator
- Direction
- dgs.springgraphql.autoconfig uses dgs, so a change to dgs can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig uses a module listed above it, which is the healthy direction.
40→38 dgs.springgraphql.autoconfig uses dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration✕
- Connections
- 2 pairs of types, where a type in dgs.springgraphql.autoconfig uses a type in dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.
- The types involved
com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsRuntimeWiringConfigurerBridgecom.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration→com.netflix.graphql.dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.DgsTypeDefinitionConfigurerBridge
- Direction
- dgs.springgraphql.autoconfig uses dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration, so a change to dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration can break dgs.springgraphql.autoconfig, while a change to dgs.springgraphql.autoconfig can't break dgs.springgraphql.autoconfig.DgsSpringGraphQLAutoConfiguration.
- Position
- Below the diagonal: dgs.springgraphql.autoconfig 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 |
|---|---|---|
| A05:2025 — Injection | 27 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 `toGraphQlError` spells `Ql` where 15 names in the project spell it `QL` finding(s) in Naming Consistency — start with DgsException.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +5.3 pts | Low | ADR Quality |
| Resolve the 1 `toGraphQlError` spells `Ql` where 15 names in the project spell it `QL` finding(s) in Naming Consistency — start with DgsException.kt. | +4.8 pts | Low | Naming Consistency |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.2 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +2.0 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.6 pts | Low | Supply-chain Provenance & Signing |
| 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. | +2.5 pts | Medium | Documentation (README) |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.0 pts | Medium | Security & performance tooling |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt | 7.2 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (22 corresponding lines) |
| graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DefaultDgsDataLoaderProvider.kt | 7.8 | Mixed | Cognitive Complexity: DefaultDgsDataLoaderProvider.addDataLoaderComponents (cognitive 17) |
| graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt | 7.8 | Mixed | God Classes: ClassTooLong: DgsSchemaProvider |
| graphql-dgs-spring-graphql/src/main/kotlin/com/netflix/graphql/dgs/springgraphql/autoconfig/DgsSpringGraphQLAutoConfiguration.kt | 7.8 | Mixed | God Classes: FileTooLong: autoconfig/DgsSpringGraphQLAutoConfiguration.kt |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (29 corresponding lines) |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt | 7.8 | Mixed | Code Duplication: Edited copies of one member (4 members, 12+ corresponding lines) |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt | 7.8 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/datafetcher/ConcurrentDataFetcher.java | 7.8 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/WebSocketGraphQLClient.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/GraphQLJavaErrorInstrumentation.kt | 8.5 | Near-clean | Cognitive Complexity: GraphQLJavaErrorInstrumentation.instrumentExecutionResult (cognitive 30) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 50 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, 80 of 320 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/Jackson3DgsJsonMapperAdapter.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/MonoRequestExecutor.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/RequestExecutor.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/WebClientGraphQLClient.kt`, … (+17 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.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 54 commits in the last 90 days, yet 55 of 87 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: the service booted and listens, but no port it opened answered HTTP — nothing to crawl.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was GraphQLJavaErrorInstrumentation.instrumentExecutionResult at 30.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with GraphQLJavaErrorInstrumentation.instrumentExecutionResult (cognitive 30), DefaultDgsFederationResolver.dgsEntityFetchers (cognitive 22), MultipartVariableMapper.mapVariable (cognitive 22). — 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 4 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with DgsSchemaProvider.kt, DgsSpringGraphQLAutoConfiguration.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with DgsSchemaProvider.kt, DgsSpringGraphQLAutoConfiguration.kt. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 3.3 % of the production lines (559 of 17,093) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 6 of the 25 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with DgsDataLoaderInstrumentationDataLoaderCustomizer.java, GraphQLRequestOptions.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copies of one member (3 members, 4+ corresponding lines) finding(s) in Code Duplication — start with GraphQLRequestOptions.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Jackson2DgsJsonMapperAdapter.kt, ReactiveSpringGraphQLExampleApp.java. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
20 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 13 of the 20 (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).
D6 · Cohesion (LCOM4)
1 of 46 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DgsGraphQLSourceBuilder.kt. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 261 artifact(s) resolved, 261 of them gradable against Maven Central, and 229 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 4 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 27 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. A further 2 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is graphql-dgs-spring-boot-micrometer/src/main/kotlin/com/netflix/graphql/dgs/metrics/micrometer/DgsGraphQLMicrometerAutoConfiguration.kt. Counted over 87 of the 287 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
1 deducted task-comment markers across 17093 LoC (0.0/KLoC) → score 10.0. 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 1 TodoComment finding(s) in Explicit Debt — start with WebSocketGraphQLClient.kt. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 13 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `toGraphQlError` spells `Ql` where 15 names in the project spell it `QL` finding(s) in Naming Consistency — start with DgsException.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 14 build units (Gradle, Python) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
27 finding(s): 0 critical, 23 high, 0 medium, 4 low. 19 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `gradlew` (line 74, line 178), `graphql-dgs-example-shared/src/main/resources/static/static/js/2.e650732d.chunk.js` — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
- No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/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 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 14 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
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 7/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `graphql-dgs-example-jackson-both`, `graphql-dgs-example-jackson2-only`, `graphql-dgs-example-jackson3-only`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — graphql-dgs-spring-boot-micrometer/src/jmh/kotlin/com/netflix/graphql/dgs/metrics/micrometer/DgsGraphQLMetricsInstrumentationBenchmark.kt
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (ex: 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. — graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/CompletableFutureWrapper.kt:36
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `warn` at line 53 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:53
- `warn` at line 66 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:66
- `warn` at line 80 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:80
- `warn` at line 115 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:115
- `warn` at line 132 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:132
- `warn` at line 150 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:150
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Strong | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 24% of this repository's production lines — kotlin (12,786 lines), python (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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 runtime tier booted this repository's service, but the service booted and listens, but no port it opened answered HTTP — nothing to crawl. This repository also has a user interface (1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~18271 lines of test source are present (.java, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Java, Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .kt, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 22 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (57 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 44 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: DgsSchemaProvider graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt:99
- ClassTooLong: DgsSpringGraphQLAutoConfiguration graphql-dgs-spring-graphql/src/main/kotlin/com/netflix/graphql/dgs/springgraphql/autoconfig/DgsSpringGraphQLAutoConfiguration.kt:177
- FileTooLong: internal/DgsSchemaProvider.kt graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DgsSchemaProvider.kt
- FileTooLong: autoconfig/DgsSpringGraphQLAutoConfiguration.kt graphql-dgs-spring-graphql/src/main/kotlin/com/netflix/graphql/dgs/springgraphql/autoconfig/DgsSpringGraphQLAutoConfiguration.kt
- Edited copy of a member (22 corresponding lines) graphql-dgs/src/main/java/com/netflix/graphql/dgs/internal/DgsDataLoaderInstrumentationDataLoaderCustomizer.java:83
- Edited copy of a member (22 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt:91
- Edited copies of one member (3 members, 4+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt:67
- Edited copies of one member (3 members, 4+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLRequestOptions.kt:84
- Duplicated block (6 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/Jackson2DgsJsonMapperAdapter.kt:54
- Duplicated block (6 lines × 2) graphql-dgs-spring-graphql-example-java-webflux/src/main/java/com/netflix/graphql/dgs/example/reactive/ReactiveSpringGraphQLExampleApp.java:47
- Edited copy of a member (8 corresponding lines) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/types/ActionMovie.java:65
- Edited copy of a member (8 corresponding lines) graphql-dgs-spring-boot-micrometer/src/jmh/kotlin/com/netflix/graphql/dgs/metrics/micrometer/DgsGraphQLMetricsInstrumentationBenchmark.kt:109
- TodoComment graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/WebSocketGraphQLClient.kt:96
- GraphQLJavaErrorInstrumentation.instrumentExecutionResult (cognitive 30) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/GraphQLJavaErrorInstrumentation.kt:17
- DefaultDgsFederationResolver.dgsEntityFetchers (cognitive 22) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/federation/DefaultDgsFederationResolver.kt:113
- MultipartVariableMapper.mapVariable (cognitive 22) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/utils/MultipartVariableMapper.kt:79
- DefaultDgsDataLoaderProvider.addDataLoaderComponents (cognitive 17) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DefaultDgsDataLoaderProvider.kt:137
- REDACTED
- Edited copy of a member (27 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt:47
- Edited copy of a member (29 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt:48
- Edited copies of one member (4 members, 12+ corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt:61
- Edited copy of a member (11 corresponding lines) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt:88
- Edited copy of a member (13 corresponding lines) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/DefaultDgsDataLoaderProvider.kt:253
- Duplicated block (25 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsRestClientGraphQLClient.kt:49
- Duplicated block (17 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt:67
- Duplicated block (14 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt:52
- Duplicated block (7–11 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt:67
- Duplicated block (9–10 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomGraphQLClient.kt:62
- Duplicated block (8 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/CustomMonoGraphQLClient.kt:63
- Duplicated block (9 lines × 2) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:48
- Duplicated block (9 lines × 4) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:61
- Duplicated block (5 lines × 7) graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphqlSSESubscriptionGraphQLClient.kt:76
- Edited copy of a member (18 corresponding lines) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/datafetcher/ConcurrentDataFetcher.java:30
- Duplicated block (16 lines × 2) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/datafetcher/ConcurrentDataFetcher.java:32
- Duplicated block (35 lines × 2) graphql-dgs-example-shared/src/main/java/com/netflix/graphql/dgs/example/shared/dataLoader/MessageDataLoader.java:1
- Off the main sequence: :graphql-dgs-subscription-types
- Low cohesion: DgsGraphQLSourceBuilder (LCOM4 4) graphql-dgs-spring-graphql/src/main/kotlin/com/netflix/graphql/dgs/springgraphql/DgsGraphQLSourceBuilder.kt:42
- Swallowed exception (caught, then discarded) graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/internal/CompletableFutureWrapper.kt:36
Minor — 24 finding(s)
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:53
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:66
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsGraphQLResponse.kt:80
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:115
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:132
- Interpolated log message defeats structured logging graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLResponse.kt:150
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found build.gradle.kts:83
- `toGraphQlError` spells `Ql` where 15 names in the project spell it `QL` graphql-dgs/src/main/kotlin/com/netflix/graphql/dgs/exceptions/DgsException.kt:41
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:4
- Benchmarks don't track allocations graphql-dgs-spring-boot-micrometer/src/jmh/kotlin/com/netflix/graphql/dgs/metrics/micrometer/DgsGraphQLMetricsInstrumentationBenchmark.kt
Minor — 229 finding(s)
- Outdated (compile): io.projectreactor:reactor-core
- Outdated (compile): com.graphql-java:graphql-java
- Outdated (compile): org.apache.logging.log4j:log4j-to-slf4j
- Outdated (compile): org.apache.logging.log4j:log4j-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): org.springframework.boot:spring-boot-starter-graphql
- Outdated (compile): org.springframework.boot:spring-boot-starter
- Outdated (compile): org.springframework.boot:spring-boot-starter-logging
- Outdated (compile): ch.qos.logback:logback-classic
- Outdated (compile): ch.qos.logback:logback-core
- Outdated (compile): org.slf4j:slf4j-api
- Outdated (compile): biz.aQute.bnd:biz.aQute.bnd.annotation
- Outdated (compile): org.osgi:org.osgi.resource
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): org.slf4j:jul-to-slf4j
- Outdated (compile): org.springframework.boot:spring-boot-autoconfigure
- Outdated (compile): org.springframework.boot:spring-boot
- Outdated (compile): org.springframework:spring-core
- Outdated (compile): commons-logging:commons-logging
- Outdated (compile): org.springframework:spring-context
- Outdated (compile): org.springframework:spring-aop
- Outdated (compile): org.springframework:spring-beans
- Outdated (compile): org.springframework:spring-expression
- Outdated (compile): io.micrometer:micrometer-observation
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f0d692b7d7d24cfe8067e753f9839471/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f0d692b7d7d24cfe8067e753f9839471/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 27 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.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 22 file(s) — `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/DgsWebClientGraphQLClient.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/Jackson3DgsJsonMapperAdapter.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/MonoRequestExecutor.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/RequestExecutor.kt`, `graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/WebClientGraphQLClient.kt`, … (+17 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |