Executive summary
ghostdogpr/caliban falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 58 out of 100 and is rated Adequate, and all 29 of its critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 54, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, worth about 3 points.
Twenty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step runs a download nobody checks, and one setting leaves the servers or containers unsafe. Pinning each tool to an exact version, checking the download against a checksum and correcting the unsafe settings would close these risks.
The product code is 42,794 lines, about €92,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 49 findings
- Code Duplication · Edited copies of one member (3 members, 54+ corresponding lines) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala
- Code Duplication · Edited copy of a member (39 corresponding lines) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/package.scala
- Code Duplication · Edited copy of a member (21 corresponding lines) core/src/main/scala/caliban/introspection/adt/__DirectiveLocation.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) adapters/http4s/src/main/scala/caliban/Http4sAdapter.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) core/src/main/scala/caliban/Incremental.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) core/src/main/scala/caliban/wrappers/ApolloTracing.scala
- Code Duplication · Edited copy of a member (20 corresponding lines) core/src/main/scala/caliban/validation/SchemaValidator.scala
- Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) federation/src/main/scala/caliban/federation/EntityResolver.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala
- Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) core/src/main/scala/caliban/schema/Schema.scala
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) core/src/main/scala/caliban/schema/Schema.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala-3/caliban/schema/ArgBuilderDerivation.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/rendering/Renderer.scala
- Code Duplication · Edited copies of one member (8 members, 3+ corresponding lines) client/src/main/scala/caliban/client/SelectionBuilder.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) interop/cats/src/main/scala/caliban/interop/cats/CatsInterop.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) core/src/main/scala/caliban/schema/Schema.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) interop/cats/src/main/scala/caliban/interop/cats/InjectEnv.scala
- Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) core/src/main/scala/caliban/GraphQL.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/relay/PaginationArgs.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/TapirAdapter.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/HttpInterpreter.scala
- Code Duplication · Edited copy of a member (3 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) core/src/main/scala/caliban/introspection/adt/__Field.scala
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) core/src/main/scala/caliban/rendering/DocumentRenderer.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) core/src/main/scala/caliban/execution/Fragment.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/caliban/CalibanError.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/relay/NodeResolver.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) core/src/main/scala/caliban/relay/RelaySupport.scala
- Code Duplication · Duplicated block (25 lines × 2) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala
- Code Duplication · Edited copy of a member (44 corresponding lines) examples/src/main/scala/example/federation/CharacterService.scala
- Code Duplication · Edited copy of a member (29 corresponding lines) examples/src/main/scala/example/interop/cats/ContextualCatsInterop.scala
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) examples/src/main/scala/example/federation/EpisodeService.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala
- Code Duplication · Edited copy of a member (20 corresponding lines) examples/src/main/scala/example/interop/cats/ContextualCatsInterop.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) examples/src/main/scala/example/http4s/AuthExampleApp.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala
- Churn × Complexity Hotspots · Hotspot: core/src/main/scala/caliban/validation/SchemaValidator.scala core/src/main/scala/caliban/validation/SchemaValidator.scala
- Churn × Complexity Hotspots · Hotspot: gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala
Fixed since the last survey: 5 findings
- God Classes · TooManyMethods: SchemaComparison tools/src/main/scala/caliban/tools/SchemaComparison.scala
- Code Duplication · Duplicated block (17 lines × 2) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala
- Code Duplication · Duplicated block (11 lines × 3) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala
- Code Duplication · Duplicated block (5 lines × 2) core/src/main/scala/caliban/parsing/Parser.scala
- Documentation (README) · README may be stale
Rebuild cost: about €92,000 · Estimate
| Cost to rebuild | €31,000 to €150,000, for 511 to 1,620 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 42,794 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 caliban.client | 2 caliban.ResponseValue | 3 caliban.parsing.adt.Definition | 4 caliban.parsing.adt.Type | 5 caliban.parsing.adt.Definition.ExecutableDefinition | 6 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition | 7 caliban.parsing.adt.Definition.TypeSystemDefinition | 8 caliban.introspection.adt | 9 caliban.relay | 10 caliban.wrappers.Wrapper | 11 caliban.execution | 12 caliban.schema | 13 caliban.interop.cats | 14 caliban.interop.tapir | 15 caliban.parsing | 16 caliban.parsing.adt | 17 caliban.CalibanError | 18 caliban.gateway.PhaseHooks | 19 caliban.rendering | 20 caliban | 21 caliban.tools | 22 caliban.federation | 23 caliban.gateway.internal.composition.DirectiveComposition | 24 caliban.gateway.internal.execution.EntityLookup | 25 caliban.gateway.internal.execution.PlanExecutor | 26 caliban.gateway.internal.planning | 27 caliban.parsing.parsers | 28 caliban.validation | 29 (global) | 30 caliban.federation.v2x | 31 caliban.gateway.internal.composition.FederationCompilation | 32 caliban.gateway.internal.execution | 33 caliban.gateway.internal.planning.OperationPlan | 34 caliban.gateway.internal.composition | 35 caliban.gateway.internal.composition.ComposedGraph | 36 caliban.gateway.internal.OperationPreparation | 37 caliban.gateway.internal.planning.OperationPlanner | 38 caliban.gateway.internal | 39 caliban.gateway | 40 caliban.gateway.internal.acquisition |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 caliban.client | ||||||||||||||||||||||||||||||||||||||||
| 2 caliban.ResponseValue | 3 | |||||||||||||||||||||||||||||||||||||||
| 3 caliban.parsing.adt.Definition | 3 | |||||||||||||||||||||||||||||||||||||||
| 4 caliban.parsing.adt.Type | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 caliban.parsing.adt.Definition.ExecutableDefinition | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 6 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition | 2 | 6 | 11 | 1 | ||||||||||||||||||||||||||||||||||||
| 7 caliban.parsing.adt.Definition.TypeSystemDefinition | 3 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 8 caliban.introspection.adt | 4 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 9 caliban.relay | 1 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 10 caliban.wrappers.Wrapper | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 caliban.execution | 3 | 1 | 3 | 8 | 2 | 10 | ||||||||||||||||||||||||||||||||||
| 12 caliban.schema | 1 | 19 | 1 | 1 | 8 | 7 | 6 | |||||||||||||||||||||||||||||||||
| 13 caliban.interop.cats | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 caliban.interop.tapir | 8 | 21 | ||||||||||||||||||||||||||||||||||||||
| 15 caliban.parsing | 1 | 1 | 6 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 16 caliban.parsing.adt | 1 | 2 | 6 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 17 caliban.CalibanError | 3 | 3 | 7 | |||||||||||||||||||||||||||||||||||||
| 18 caliban.gateway.PhaseHooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 caliban.rendering | 1 | 1 | 2 | 9 | 4 | 1 | 6 | 3 | ||||||||||||||||||||||||||||||||
| 20 caliban | 5 | 6 | 5 | 2 | 2 | 16 | 7 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||
| 21 caliban.tools | 2 | 11 | 8 | 1 | 1 | 8 | 1 | |||||||||||||||||||||||||||||||||
| 22 caliban.federation | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 23 caliban.gateway.internal.composition.DirectiveComposition | 9 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 caliban.gateway.internal.execution.EntityLookup | 2 | 6 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 caliban.gateway.internal.execution.PlanExecutor | 1 | 19 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 26 caliban.gateway.internal.planning | 2 | 7 | 5 | 1 | 3 | 1 | 6 | 4 | ||||||||||||||||||||||||||||||||
| 27 caliban.parsing.parsers | 3 | 3 | 2 | 9 | 4 | 1 | 7 | 3 | ||||||||||||||||||||||||||||||||
| 28 caliban.validation | 2 | 3 | 2 | 14 | 2 | 5 | 11 | 5 | 3 | |||||||||||||||||||||||||||||||
| 29 (global) | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 caliban.federation.v2x | 1 | 6 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 31 caliban.gateway.internal.composition.FederationCompilation | 1 | 3 | 6 | |||||||||||||||||||||||||||||||||||||
| 32 caliban.gateway.internal.execution | 2 | 2 | 4 | 1 | 4 | 35 | 3 | 9 | 1 | 7 | 1 | |||||||||||||||||||||||||||||
| 33 caliban.gateway.internal.planning.OperationPlan | 1 | 5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 caliban.gateway.internal.composition | 1 | 2 | 1 | 17 | 1 | 6 | 18 | 1 | 5 | 1 | 1 | 21 | 3 | |||||||||||||||||||||||||||
| 35 caliban.gateway.internal.composition.ComposedGraph | 3 | 1 | 1 | 3 | 1 | 3 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||
| 36 caliban.gateway.internal.OperationPreparation | 1 | 1 | 1 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 caliban.gateway.internal.planning.OperationPlanner | 4 | 9 | 4 | 1 | 1 | 14 | 6 | |||||||||||||||||||||||||||||||||
| 38 caliban.gateway.internal | 1 | 1 | 1 | 5 | 1 | 1 | 4 | 2 | ||||||||||||||||||||||||||||||||
| 39 caliban.gateway | 3 | 3 | 6 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 caliban.gateway.internal.acquisition | 1 | 1 | 3 | 3 | 6 | 3 | 5 | 9 |
2→20 caliban.ResponseValue uses caliban part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.ResponseValue uses a type in caliban.
- The types involved
caliban.ResponseValue.ListValue→caliban.ResponseValuecaliban.ResponseValue.ObjectValue→caliban.ResponseValuecaliban.ResponseValue.StreamValue→caliban.ResponseValue
- Direction
- caliban.ResponseValue uses caliban, so a change to caliban can break caliban.ResponseValue, while a change to caliban.ResponseValue can't break caliban.
- 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.
3→16 caliban.parsing.adt.Definition uses caliban.parsing.adt part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.adt.Definition uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.adt.Definition.ExecutableDefinition→caliban.parsing.adt.Definitioncaliban.parsing.adt.Definition.TypeSystemDefinition→caliban.parsing.adt.Definitioncaliban.parsing.adt.Definition.TypeSystemExtension→caliban.parsing.adt.Definition
- Direction
- caliban.parsing.adt.Definition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.adt.Definition, while a change to caliban.parsing.adt.Definition can't break caliban.parsing.adt.
- 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.
4→16 caliban.parsing.adt.Type uses caliban.parsing.adt part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt.Type uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.adt.Type.ListType→caliban.parsing.adt.Typecaliban.parsing.adt.Type.NamedType→caliban.parsing.adt.Type
- Direction
- caliban.parsing.adt.Type uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.adt.Type, while a change to caliban.parsing.adt.Type can't break caliban.parsing.adt.
- 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.
5→3 caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt.Definition✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt.Definition.ExecutableDefinition uses a type in caliban.parsing.adt.Definition.
- The types involved
caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinition→caliban.parsing.adt.Definition.ExecutableDefinitioncaliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition→caliban.parsing.adt.Definition.ExecutableDefinition
- Direction
- caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt.Definition, so a change to caliban.parsing.adt.Definition can break caliban.parsing.adt.Definition.ExecutableDefinition, while a change to caliban.parsing.adt.Definition.ExecutableDefinition can't break caliban.parsing.adt.Definition.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.ExecutableDefinition uses a module listed above it, which is the healthy direction.
5→4 caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt.Type✕
- Connections
- 1 pair of types, where a type in caliban.parsing.adt.Definition.ExecutableDefinition uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinition→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.parsing.adt.Definition.ExecutableDefinition, while a change to caliban.parsing.adt.Definition.ExecutableDefinition can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.ExecutableDefinition uses a module listed above it, which is the healthy direction.
5→16 caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt part of a loop✕
- Connections
- 6 pairs of types, where a type in caliban.parsing.adt.Definition.ExecutableDefinition uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinition→caliban.parsing.adt.Selectioncaliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition→caliban.parsing.adt.OperationTypecaliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition→caliban.parsing.adt.Selectioncaliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition→caliban.parsing.adt.VariableDefinition
- Direction
- caliban.parsing.adt.Definition.ExecutableDefinition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.adt.Definition.ExecutableDefinition, while a change to caliban.parsing.adt.Definition.ExecutableDefinition can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt.Type✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinition→caliban.parsing.adt.Type.NamedTypecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinition→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses a module listed above it, which is the healthy direction.
6→7 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt.Definition.TypeSystemDefinition part of a loop✕
- Connections
- 6 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.AggregationTypeDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.AggregationTypeDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ScalarTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→16 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt part of a loop✕
- Connections
- 11 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinition→caliban.parsing.adt.Typecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition→caliban.parsing.adt.Typecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ScalarTypeDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition→caliban.parsing.adt.Directive
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses a type in caliban.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition→caliban.InputValue
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition uses caliban, so a change to caliban can break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Definition✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition uses a type in caliban.parsing.adt.Definition.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinition→caliban.parsing.adt.Definition.TypeSystemDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinition→caliban.parsing.adt.Definition.TypeSystemDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Definition, so a change to caliban.parsing.adt.Definition can break caliban.parsing.adt.Definition.TypeSystemDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition can't break caliban.parsing.adt.Definition.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.TypeSystemDefinition uses a module listed above it, which is the healthy direction.
7→4 caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Type✕
- Connections
- 1 pair of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.AggregationTypeDefinition→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.parsing.adt.Definition.TypeSystemDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.TypeSystemDefinition uses a module listed above it, which is the healthy direction.
7→6 caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.AggregationTypeDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.parsing.adt.Definition.TypeSystemDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.parsing.adt.Definition.TypeSystemDefinition uses a module listed above it, which is the healthy direction.
7→16 caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt.Definition.TypeSystemDefinition uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinition→caliban.parsing.adt.Directivecaliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition→caliban.parsing.adt.Directive
- Direction
- caliban.parsing.adt.Definition.TypeSystemDefinition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.adt.Definition.TypeSystemDefinition, while a change to caliban.parsing.adt.Definition.TypeSystemDefinition can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→6 caliban.introspection.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 4 pairs of types, where a type in caliban.introspection.adt uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.introspection.adt.__EnumValue→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.introspection.adt.__Field→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.introspection.adt.__Field→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinitioncaliban.introspection.adt.__InputValue→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition
- Direction
- caliban.introspection.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.introspection.adt, while a change to caliban.introspection.adt can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.introspection.adt uses a module listed above it, which is the healthy direction.
8→7 caliban.introspection.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 3 pairs of types, where a type in caliban.introspection.adt uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.introspection.adt.__Directive→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.introspection.adt.__DirectiveLocation→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveLocationcaliban.introspection.adt.__Type→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.introspection.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.introspection.adt, while a change to caliban.introspection.adt can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.introspection.adt uses a module listed above it, which is the healthy direction.
8→16 caliban.introspection.adt uses caliban.parsing.adt part of a loop✕
- Connections
- 5 pairs of types, where a type in caliban.introspection.adt uses a type in caliban.parsing.adt.
- The types involved
caliban.introspection.adt.__EnumValue→caliban.parsing.adt.Directivecaliban.introspection.adt.__Field→caliban.parsing.adt.Directivecaliban.introspection.adt.__InputValue→caliban.parsing.adt.Directivecaliban.introspection.adt.__Type→caliban.parsing.adt.Directivecaliban.introspection.adt.__Type→caliban.parsing.adt.Type
- Direction
- caliban.introspection.adt uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.introspection.adt, while a change to caliban.introspection.adt can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→8 caliban.relay uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.relay uses a type in caliban.introspection.adt.
- The types involved
caliban.relay.NodeResolver→caliban.introspection.adt.__Type
- Direction
- caliban.relay uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.relay, while a change to caliban.relay can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.relay uses a module listed above it, which is the healthy direction.
9→12 caliban.relay uses caliban.schema part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.relay uses a type in caliban.schema.
- The types involved
caliban.relay.NodeResolver→caliban.schema.Stepcaliban.relay.RelaySupport→caliban.schema.Schema
- Direction
- caliban.relay uses caliban.schema, so a change to caliban.schema can break caliban.relay, while a change to caliban.relay can't break caliban.schema.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→17 caliban.relay uses caliban.CalibanError part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.relay uses a type in caliban.CalibanError.
- The types involved
caliban.relay.TypeResolver→caliban.CalibanError.ExecutionError
- Direction
- caliban.relay uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.relay, while a change to caliban.relay can't break caliban.CalibanError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→20 caliban.relay uses caliban part of a loop✕
- Connections
- 5 pairs of types, where a type in caliban.relay uses a type in caliban.
- The types involved
caliban.relay.BackwardPaginationArgs→caliban.CalibanErrorcaliban.relay.ForwardPaginationArgs→caliban.CalibanErrorcaliban.relay.Pagination→caliban.CalibanErrorcaliban.relay.PaginationArgs→caliban.CalibanErrorcaliban.relay.RelaySupport→caliban.GraphQL
- Direction
- caliban.relay uses caliban, so a change to caliban can break caliban.relay, while a change to caliban.relay can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 caliban.wrappers.Wrapper uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.wrappers.Wrapper uses a type in caliban.introspection.adt.
- The types involved
caliban.wrappers.Wrapper.IntrospectionWrapper→caliban.introspection.adt.__Introspection
- Direction
- caliban.wrappers.Wrapper uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.wrappers.Wrapper, while a change to caliban.wrappers.Wrapper can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.wrappers.Wrapper uses a module listed above it, which is the healthy direction.
10→11 caliban.wrappers.Wrapper uses caliban.execution part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.wrappers.Wrapper uses a type in caliban.execution.
- The types involved
caliban.wrappers.Wrapper.FieldWrapper→caliban.execution.FieldInfo
- Direction
- caliban.wrappers.Wrapper uses caliban.execution, so a change to caliban.execution can break caliban.wrappers.Wrapper, while a change to caliban.wrappers.Wrapper can't break caliban.execution.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→17 caliban.wrappers.Wrapper uses caliban.CalibanError part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.wrappers.Wrapper uses a type in caliban.CalibanError.
- The types involved
caliban.wrappers.Wrapper.FieldWrapper→caliban.CalibanError.ExecutionErrorcaliban.wrappers.Wrapper.IntrospectionWrapper→caliban.CalibanError.ExecutionError
- Direction
- caliban.wrappers.Wrapper uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.wrappers.Wrapper, while a change to caliban.wrappers.Wrapper can't break caliban.CalibanError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 caliban.wrappers.Wrapper uses caliban part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.wrappers.Wrapper uses a type in caliban.
- The types involved
caliban.wrappers.Wrapper.Empty→caliban.GraphQLcaliban.wrappers.Wrapper.FieldWrapper→caliban.ResponseValue
- Direction
- caliban.wrappers.Wrapper uses caliban, so a change to caliban can break caliban.wrappers.Wrapper, while a change to caliban.wrappers.Wrapper can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→8 caliban.execution uses caliban.introspection.adt✕
- Connections
- 3 pairs of types, where a type in caliban.execution uses a type in caliban.introspection.adt.
- The types involved
caliban.execution.Feature→caliban.introspection.adt.__Directivecaliban.execution.Field→caliban.introspection.adt.__Typecaliban.execution.FieldInfo→caliban.introspection.adt.__Type
- Direction
- caliban.execution uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.execution, while a change to caliban.execution can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.execution uses a module listed above it, which is the healthy direction.
11→10 caliban.execution uses caliban.wrappers.Wrapper✕
- Connections
- 1 pair of types, where a type in caliban.execution uses a type in caliban.wrappers.Wrapper.
- The types involved
caliban.execution.Executor→caliban.wrappers.Wrapper.FieldWrapper
- Direction
- caliban.execution uses caliban.wrappers.Wrapper, so a change to caliban.wrappers.Wrapper can break caliban.execution, while a change to caliban.execution can't break caliban.wrappers.Wrapper.
- Position
- Below the diagonal: caliban.execution uses a module listed above it, which is the healthy direction.
11→12 caliban.execution uses caliban.schema part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.execution uses a type in caliban.schema.
- The types involved
caliban.execution.DeferredFragment→caliban.schema.ReducedStepcaliban.execution.Executor→caliban.schema.Stepcaliban.execution.RequestPreparation→caliban.schema.RootType
- Direction
- caliban.execution uses caliban.schema, so a change to caliban.schema can break caliban.execution, while a change to caliban.execution can't break caliban.schema.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 caliban.execution uses caliban.parsing.adt part of a loop✕
- Connections
- 8 pairs of types, where a type in caliban.execution uses a type in caliban.parsing.adt.
- The types involved
caliban.execution.ExecutionRequest→caliban.parsing.adt.OperationTypecaliban.execution.Executor→caliban.parsing.adt.LocationInfocaliban.execution.Field→caliban.parsing.adt.Directivecaliban.execution.Field→caliban.parsing.adt.LocationInfocaliban.execution.Field→caliban.parsing.adt.Selectioncaliban.execution.FieldInfo→caliban.parsing.adt.Directivecaliban.execution.Fragment→caliban.parsing.adt.Directivecaliban.execution.RequestPreparation→caliban.parsing.adt.Document
- Direction
- caliban.execution uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.execution, while a change to caliban.execution can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 caliban.execution uses caliban.CalibanError part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.execution uses a type in caliban.CalibanError.
- The types involved
caliban.execution.Executor→caliban.CalibanError.ExecutionErrorcaliban.execution.RequestPreparation→caliban.CalibanError.ValidationError
- Direction
- caliban.execution uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.execution, while a change to caliban.execution can't break caliban.CalibanError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 caliban.execution uses caliban part of a loop✕
- Connections
- 10 pairs of types, where a type in caliban.execution uses a type in caliban.
- The types involved
caliban.execution.Deferred→caliban.PathValuecaliban.execution.DeferredFragment→caliban.PathValuecaliban.execution.DeferredStream→caliban.PathValuecaliban.execution.Executor→caliban.CalibanErrorcaliban.execution.Executor→caliban.GraphQLResponsecaliban.execution.Executor→caliban.PathValuecaliban.execution.Field→caliban.InputValuecaliban.execution.FieldInfo→caliban.PathValuecaliban.execution.RequestPreparation→caliban.GraphQLRequestcaliban.execution.RequestPreparation→caliban.InputValue
- Direction
- caliban.execution uses caliban, so a change to caliban can break caliban.execution, while a change to caliban.execution can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 caliban.schema uses caliban.ResponseValue✕
- Connections
- 1 pair of types, where a type in caliban.schema uses a type in caliban.ResponseValue.
- The types involved
caliban.schema.Extended→caliban.ResponseValue.ObjectValue
- Direction
- caliban.schema uses caliban.ResponseValue, so a change to caliban.ResponseValue can break caliban.schema, while a change to caliban.schema can't break caliban.ResponseValue.
- Position
- Below the diagonal: caliban.schema uses a module listed above it, which is the healthy direction.
12→8 caliban.schema uses caliban.introspection.adt✕
- Connections
- 19 pairs of types, where a type in caliban.schema uses a type in caliban.introspection.adt.
- The types involved
caliban.schema.EnumValueSchema→caliban.introspection.adt.__Typecaliban.schema.GenericSchema→caliban.introspection.adt.__EnumValuecaliban.schema.ObjectSchema→caliban.introspection.adt.__Typecaliban.schema.Operation→caliban.introspection.adt.__Typecaliban.schema.PartiallyAppliedFieldBase→caliban.introspection.adt.__Fieldcaliban.schema.RootSchemaBuilder→caliban.introspection.adt.TypeVisitorcaliban.schema.RootSchemaBuilder→caliban.introspection.adt.__Typecaliban.schema.RootType→caliban.introspection.adt.SchemaElementcaliban.schema.RootType→caliban.introspection.adt.__Directivecaliban.schema.RootType→caliban.introspection.adt.__Typecaliban.schema.Schema→caliban.introspection.adt.__InputValuecaliban.schema.Schema→caliban.introspection.adt.__Typecaliban.schema.SchemaUtils→caliban.introspection.adt.__Typecaliban.schema.SumSchema→caliban.introspection.adt.__Typecaliban.schema.Types→caliban.introspection.adt.__EnumValuecaliban.schema.Types→caliban.introspection.adt.__Fieldcaliban.schema.Types→caliban.introspection.adt.__InputValuecaliban.schema.Types→caliban.introspection.adt.__Typecaliban.schema.ValueTypeSchema→caliban.introspection.adt.__Type
- Direction
- caliban.schema uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.schema, while a change to caliban.schema can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.schema uses a module listed above it, which is the healthy direction.
12→9 caliban.schema uses caliban.relay✕
- Connections
- 1 pair of types, where a type in caliban.schema uses a type in caliban.relay.
- The types involved
caliban.schema.GenericSchema→caliban.relay.Base64Cursor
- Direction
- caliban.schema uses caliban.relay, so a change to caliban.relay can break caliban.schema, while a change to caliban.schema can't break caliban.relay.
- Position
- Below the diagonal: caliban.schema uses a module listed above it, which is the healthy direction.
12→11 caliban.schema uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.schema uses a type in caliban.execution.
- The types involved
caliban.schema.GenericSchema→caliban.execution.Field
- Direction
- caliban.schema uses caliban.execution, so a change to caliban.execution can break caliban.schema, while a change to caliban.schema can't break caliban.execution.
- Position
- Below the diagonal: caliban.schema uses a module listed above it, which is the healthy direction.
12→16 caliban.schema uses caliban.parsing.adt part of a loop✕
- Connections
- 8 pairs of types, where a type in caliban.schema uses a type in caliban.parsing.adt.
- The types involved
caliban.schema.CommonSchemaDerivation→caliban.parsing.adt.Directivecaliban.schema.GenericSchema→caliban.parsing.adt.Directivecaliban.schema.PartiallyAppliedField→caliban.parsing.adt.Directivecaliban.schema.PartiallyAppliedFieldLazy→caliban.parsing.adt.Directivecaliban.schema.PartiallyAppliedFieldWithArgs→caliban.parsing.adt.Directivecaliban.schema.RootSchemaBuilder→caliban.parsing.adt.Directivecaliban.schema.RootType→caliban.parsing.adt.SchemaCoordinatecaliban.schema.Types→caliban.parsing.adt.Directive
- Direction
- caliban.schema uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.schema, while a change to caliban.schema can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 caliban.schema uses caliban.CalibanError part of a loop✕
- Connections
- 7 pairs of types, where a type in caliban.schema uses a type in caliban.CalibanError.
- The types involved
caliban.schema.ArgBuilder→caliban.CalibanError.ExecutionErrorcaliban.schema.ArgBuilderInstances→caliban.CalibanError.ExecutionErrorcaliban.schema.InvalidInputArgument→caliban.CalibanError.ExecutionErrorcaliban.schema.OneOfArgBuilder→caliban.CalibanError.ExecutionErrorcaliban.schema.ProductArgBuilder→caliban.CalibanError.ExecutionErrorcaliban.schema.RootType→caliban.CalibanError.ValidationErrorcaliban.schema.SumArgBuilder→caliban.CalibanError.ExecutionError
- Direction
- caliban.schema uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.schema, while a change to caliban.schema can't break caliban.CalibanError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→20 caliban.schema uses caliban part of a loop✕
- Connections
- 6 pairs of types, where a type in caliban.schema uses a type in caliban.
- The types involved
caliban.schema.ArgBuilder→caliban.InputValuecaliban.schema.ArgBuilderInstances→caliban.InputValuecaliban.schema.OneOfArgBuilder→caliban.InputValuecaliban.schema.ProductArgBuilder→caliban.InputValuecaliban.schema.PureStep→caliban.ResponseValuecaliban.schema.SumArgBuilder→caliban.InputValue
- Direction
- caliban.schema uses caliban, so a change to caliban can break caliban.schema, while a change to caliban.schema can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→12 caliban.interop.cats uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.interop.cats uses a type in caliban.schema.
- The types involved
caliban.interop.cats.implicits→caliban.schema.Schema
- Direction
- caliban.interop.cats uses caliban.schema, so a change to caliban.schema can break caliban.interop.cats, while a change to caliban.interop.cats can't break caliban.schema.
- Position
- Below the diagonal: caliban.interop.cats uses a module listed above it, which is the healthy direction.
14→12 caliban.interop.tapir uses caliban.schema✕
- Connections
- 8 pairs of types, where a type in caliban.interop.tapir uses a type in caliban.schema.
- The types involved
caliban.interop.tapir.GraphQLEndpoint→caliban.schema.ArgBuildercaliban.interop.tapir.GraphQLEndpoint→caliban.schema.Schemacaliban.interop.tapir.GraphQLInfallibleEndpoint→caliban.schema.ArgBuildercaliban.interop.tapir.GraphQLInfallibleEndpoint→caliban.schema.Schemacaliban.interop.tapir.GraphQLInfallibleServerEndpoint→caliban.schema.ArgBuildercaliban.interop.tapir.GraphQLInfallibleServerEndpoint→caliban.schema.Schemacaliban.interop.tapir.GraphQLServerEndpoint→caliban.schema.ArgBuildercaliban.interop.tapir.GraphQLServerEndpoint→caliban.schema.Schema
- Direction
- caliban.interop.tapir uses caliban.schema, so a change to caliban.schema can break caliban.interop.tapir, while a change to caliban.interop.tapir can't break caliban.schema.
- Position
- Below the diagonal: caliban.interop.tapir uses a module listed above it, which is the healthy direction.
14→20 caliban.interop.tapir uses caliban part of a loop✕
- Connections
- 21 pairs of types, where a type in caliban.interop.tapir uses a type in caliban.
- The types involved
caliban.interop.tapir.GraphQLEndpoint→caliban.GraphQLcaliban.interop.tapir.GraphQLInfallibleEndpoint→caliban.GraphQLcaliban.interop.tapir.GraphQLInfallibleServerEndpoint→caliban.GraphQLcaliban.interop.tapir.GraphQLServerEndpoint→caliban.GraphQLcaliban.interop.tapir.HttpInterpreter→caliban.Configuratorcaliban.interop.tapir.HttpInterpreter→caliban.GraphQLRequestcaliban.interop.tapir.HttpUploadInterpreter→caliban.Configuratorcaliban.interop.tapir.HttpUploadInterpreter→caliban.GraphQLRequestcaliban.interop.tapir.HttpUploadInterpreter→caliban.PathValuecaliban.interop.tapir.JsonCodecs→caliban.GraphQLRequestcaliban.interop.tapir.JsonCodecs→caliban.ResponseValuecaliban.interop.tapir.TapirAdapter→caliban.GraphQLInterpretercaliban.interop.tapir.TapirAdapter→caliban.GraphQLRequestcaliban.interop.tapir.TapirAdapter→caliban.GraphQLResponsecaliban.interop.tapir.TapirAdapter→caliban.ResponseValuecaliban.interop.tapir.WebSocketInterpreter→caliban.Configuratorcaliban.interop.tapir.schema→caliban.GraphQLRequestcaliban.interop.tapir.schema→caliban.GraphQLResponsecaliban.interop.tapir.schema→caliban.GraphQLWSInputcaliban.interop.tapir.schema→caliban.GraphQLWSOutputcaliban.interop.tapir.schema→caliban.ResponseValue
- Direction
- caliban.interop.tapir uses caliban, so a change to caliban can break caliban.interop.tapir, while a change to caliban.interop.tapir can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→8 caliban.parsing uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.parsing uses a type in caliban.introspection.adt.
- The types involved
caliban.parsing.VariablesCoercer→caliban.introspection.adt.__Type
- Direction
- caliban.parsing uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.parsing, while a change to caliban.parsing can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.parsing uses a module listed above it, which is the healthy direction.
15→12 caliban.parsing uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.parsing uses a type in caliban.schema.
- The types involved
caliban.parsing.VariablesCoercer→caliban.schema.RootType
- Direction
- caliban.parsing uses caliban.schema, so a change to caliban.schema can break caliban.parsing, while a change to caliban.parsing can't break caliban.schema.
- Position
- Below the diagonal: caliban.parsing uses a module listed above it, which is the healthy direction.
15→16 caliban.parsing uses caliban.parsing.adt part of a loop✕
- Connections
- 6 pairs of types, where a type in caliban.parsing uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.ParsedDocument→caliban.parsing.adt.Definitioncaliban.parsing.Parser→caliban.parsing.adt.Documentcaliban.parsing.Parser→caliban.parsing.adt.SchemaCoordinatecaliban.parsing.SourceMapper→caliban.parsing.adt.LocationInfocaliban.parsing.VariablesCoercer→caliban.parsing.adt.Documentcaliban.parsing.VariablesCoercer→caliban.parsing.adt.Type
- Direction
- caliban.parsing uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing, while a change to caliban.parsing can't break caliban.parsing.adt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→17 caliban.parsing uses caliban.CalibanError part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.parsing uses a type in caliban.CalibanError.
- The types involved
caliban.parsing.Parser→caliban.CalibanError.ParsingErrorcaliban.parsing.VariablesCoercer→caliban.CalibanError.ValidationError
- Direction
- caliban.parsing uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.parsing, while a change to caliban.parsing can't break caliban.CalibanError.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→20 caliban.parsing uses caliban part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.parsing uses a type in caliban.
- The types involved
caliban.parsing.Parser→caliban.InputValuecaliban.parsing.VariablesCoercer→caliban.InputValue
- Direction
- caliban.parsing uses caliban, so a change to caliban can break caliban.parsing, while a change to caliban.parsing can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→3 caliban.parsing.adt uses caliban.parsing.adt.Definition✕
- Connections
- 1 pair of types, where a type in caliban.parsing.adt uses a type in caliban.parsing.adt.Definition.
- The types involved
caliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemExtension
- Direction
- caliban.parsing.adt uses caliban.parsing.adt.Definition, so a change to caliban.parsing.adt.Definition can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.parsing.adt.Definition.
- Position
- Below the diagonal: caliban.parsing.adt uses a module listed above it, which is the healthy direction.
16→5 caliban.parsing.adt uses caliban.parsing.adt.Definition.ExecutableDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.adt uses a type in caliban.parsing.adt.Definition.ExecutableDefinition.
- The types involved
caliban.parsing.adt.Document→caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition
- Direction
- caliban.parsing.adt uses caliban.parsing.adt.Definition.ExecutableDefinition, so a change to caliban.parsing.adt.Definition.ExecutableDefinition can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.parsing.adt.Definition.ExecutableDefinition.
- Position
- Below the diagonal: caliban.parsing.adt uses a module listed above it, which is the healthy direction.
16→6 caliban.parsing.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 6 pairs of types, where a type in caliban.parsing.adt uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ScalarTypeDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition
- Direction
- caliban.parsing.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.parsing.adt uses a module listed above it, which is the healthy direction.
16→7 caliban.parsing.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.adt uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.parsing.adt.Document→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.parsing.adt uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.parsing.adt uses a module listed above it, which is the healthy direction.
16→15 caliban.parsing.adt uses caliban.parsing✕
- Connections
- 1 pair of types, where a type in caliban.parsing.adt uses a type in caliban.parsing.
- The types involved
caliban.parsing.adt.Document→caliban.parsing.SourceMapper
- Direction
- caliban.parsing.adt uses caliban.parsing, so a change to caliban.parsing can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.parsing.
- Position
- Below the diagonal: caliban.parsing.adt uses a module listed above it, which is the healthy direction.
16→20 caliban.parsing.adt uses caliban part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.adt uses a type in caliban.
- The types involved
caliban.parsing.adt.Directive→caliban.InputValuecaliban.parsing.adt.LocationInfo→caliban.ResponseValuecaliban.parsing.adt.VariableDefinition→caliban.InputValue
- Direction
- caliban.parsing.adt uses caliban, so a change to caliban can break caliban.parsing.adt, while a change to caliban.parsing.adt can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 caliban.CalibanError uses caliban.ResponseValue✕
- Connections
- 3 pairs of types, where a type in caliban.CalibanError uses a type in caliban.ResponseValue.
- The types involved
caliban.CalibanError.ExecutionError→caliban.ResponseValue.ObjectValuecaliban.CalibanError.ParsingError→caliban.ResponseValue.ObjectValuecaliban.CalibanError.ValidationError→caliban.ResponseValue.ObjectValue
- Direction
- caliban.CalibanError uses caliban.ResponseValue, so a change to caliban.ResponseValue can break caliban.CalibanError, while a change to caliban.CalibanError can't break caliban.ResponseValue.
- Position
- Below the diagonal: caliban.CalibanError uses a module listed above it, which is the healthy direction.
17→16 caliban.CalibanError uses caliban.parsing.adt✕
- Connections
- 3 pairs of types, where a type in caliban.CalibanError uses a type in caliban.parsing.adt.
- The types involved
caliban.CalibanError.ExecutionError→caliban.parsing.adt.LocationInfocaliban.CalibanError.ParsingError→caliban.parsing.adt.LocationInfocaliban.CalibanError.ValidationError→caliban.parsing.adt.LocationInfo
- Direction
- caliban.CalibanError uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.CalibanError, while a change to caliban.CalibanError can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.CalibanError uses a module listed above it, which is the healthy direction.
17→20 caliban.CalibanError uses caliban part of a loop✕
- Connections
- 7 pairs of types, where a type in caliban.CalibanError uses a type in caliban.
- The types involved
caliban.CalibanError.ExecutionError→caliban.CalibanErrorcaliban.CalibanError.ExecutionError→caliban.PathValuecaliban.CalibanError.ExecutionError→caliban.ResponseValuecaliban.CalibanError.ParsingError→caliban.CalibanErrorcaliban.CalibanError.ParsingError→caliban.ResponseValuecaliban.CalibanError.ValidationError→caliban.CalibanErrorcaliban.CalibanError.ValidationError→caliban.ResponseValue
- Direction
- caliban.CalibanError uses caliban, so a change to caliban can break caliban.CalibanError, while a change to caliban.CalibanError can't break caliban.
- 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→16 caliban.gateway.PhaseHooks uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.PhaseHooks uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.PhaseHooks.Result→caliban.parsing.adt.OperationType
- Direction
- caliban.gateway.PhaseHooks uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.PhaseHooks, while a change to caliban.gateway.PhaseHooks can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.PhaseHooks uses a module listed above it, which is the healthy direction.
19→3 caliban.rendering uses caliban.parsing.adt.Definition✕
- Connections
- 1 pair of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.Definition.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemExtension
- Direction
- caliban.rendering uses caliban.parsing.adt.Definition, so a change to caliban.parsing.adt.Definition can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.Definition.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→4 caliban.rendering uses caliban.parsing.adt.Type✕
- Connections
- 1 pair of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.rendering uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→5 caliban.rendering uses caliban.parsing.adt.Definition.ExecutableDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.Definition.ExecutableDefinition.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition
- Direction
- caliban.rendering uses caliban.parsing.adt.Definition.ExecutableDefinition, so a change to caliban.parsing.adt.Definition.ExecutableDefinition can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.Definition.ExecutableDefinition.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→6 caliban.rendering uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 9 pairs of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ScalarTypeDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition
- Direction
- caliban.rendering uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→7 caliban.rendering uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 4 pairs of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveLocationcaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.rendering uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→8 caliban.rendering uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.rendering uses a type in caliban.introspection.adt.
- The types involved
caliban.rendering.DocumentRenderer→caliban.introspection.adt.__Type
- Direction
- caliban.rendering uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.rendering, while a change to caliban.rendering can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→16 caliban.rendering uses caliban.parsing.adt✕
- Connections
- 6 pairs of types, where a type in caliban.rendering uses a type in caliban.parsing.adt.
- The types involved
caliban.rendering.DocumentRenderer→caliban.parsing.adt.Directivecaliban.rendering.DocumentRenderer→caliban.parsing.adt.Documentcaliban.rendering.DocumentRenderer→caliban.parsing.adt.OperationTypecaliban.rendering.DocumentRenderer→caliban.parsing.adt.Selectioncaliban.rendering.DocumentRenderer→caliban.parsing.adt.Typecaliban.rendering.DocumentRenderer→caliban.parsing.adt.VariableDefinition
- Direction
- caliban.rendering uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.rendering, while a change to caliban.rendering can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.rendering uses a module listed above it, which is the healthy direction.
19→20 caliban.rendering uses caliban part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.rendering uses a type in caliban.
- The types involved
caliban.rendering.DocumentRenderer→caliban.InputValuecaliban.rendering.ValueRenderer→caliban.InputValuecaliban.rendering.ValueRenderer→caliban.ResponseValue
- Direction
- caliban.rendering uses caliban, so a change to caliban can break caliban.rendering, while a change to caliban.rendering can't break caliban.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 caliban uses caliban.ResponseValue✕
- Connections
- 5 pairs of types, where a type in caliban uses a type in caliban.ResponseValue.
- The types involved
caliban.GraphQLResponse→caliban.ResponseValue.ObjectValuecaliban.HttpUtils→caliban.ResponseValue.ObjectValuecaliban.Incremental→caliban.ResponseValue.ListValuecaliban.Incremental→caliban.ResponseValue.ObjectValuecaliban.gateway→caliban.ResponseValue.ObjectValue
- Direction
- caliban uses caliban.ResponseValue, so a change to caliban.ResponseValue can break caliban, while a change to caliban can't break caliban.ResponseValue.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→8 caliban uses caliban.introspection.adt✕
- Connections
- 6 pairs of types, where a type in caliban uses a type in caliban.introspection.adt.
- The types involved
caliban.GraphQL→caliban.introspection.adt.SchemaElementcaliban.GraphQL→caliban.introspection.adt.__Directivecaliban.GraphQL→caliban.introspection.adt.__Typecaliban.gateway→caliban.introspection.adt.__Fieldcaliban.gateway→caliban.introspection.adt.__InputValuecaliban.gateway→caliban.introspection.adt.__Type
- Direction
- caliban uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban, while a change to caliban can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→11 caliban uses caliban.execution✕
- Connections
- 5 pairs of types, where a type in caliban uses a type in caliban.execution.
- The types involved
caliban.Configurator→caliban.execution.QueryExecutioncaliban.GraphQL→caliban.execution.Featurecaliban.RemoteMutation→caliban.execution.Fieldcaliban.RemoteQuery→caliban.execution.Fieldcaliban.gateway→caliban.execution.Field
- Direction
- caliban uses caliban.execution, so a change to caliban.execution can break caliban, while a change to caliban can't break caliban.execution.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→12 caliban uses caliban.schema✕
- Connections
- 2 pairs of types, where a type in caliban uses a type in caliban.schema.
- The types involved
caliban.GraphQL→caliban.schema.RootSchemacaliban.GraphQL→caliban.schema.RootSchemaBuilder
- Direction
- caliban uses caliban.schema, so a change to caliban.schema can break caliban, while a change to caliban can't break caliban.schema.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→13 caliban uses caliban.interop.cats✕
- Connections
- 2 pairs of types, where a type in caliban uses a type in caliban.interop.cats.
- The types involved
caliban.Http4sAdapter→caliban.interop.cats.CatsInteropcaliban.Http4sAdapter→caliban.interop.cats.ToEffect
- Direction
- caliban uses caliban.interop.cats, so a change to caliban.interop.cats can break caliban, while a change to caliban can't break caliban.interop.cats.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→14 caliban uses caliban.interop.tapir✕
- Connections
- 16 pairs of types, where a type in caliban uses a type in caliban.interop.tapir.
- The types involved
caliban.AkkaHttpAdapter→caliban.interop.tapir.HttpInterpretercaliban.AkkaHttpAdapter→caliban.interop.tapir.HttpUploadInterpretercaliban.AkkaHttpAdapter→caliban.interop.tapir.StreamConstructorcaliban.AkkaHttpAdapter→caliban.interop.tapir.WebSocketInterpretercaliban.Http4sAdapter→caliban.interop.tapir.HttpInterpretercaliban.Http4sAdapter→caliban.interop.tapir.HttpUploadInterpretercaliban.Http4sAdapter→caliban.interop.tapir.StreamConstructorcaliban.Http4sAdapter→caliban.interop.tapir.WebSocketInterpretercaliban.PekkoHttpAdapter→caliban.interop.tapir.HttpInterpretercaliban.PekkoHttpAdapter→caliban.interop.tapir.HttpUploadInterpretercaliban.PekkoHttpAdapter→caliban.interop.tapir.StreamConstructorcaliban.PekkoHttpAdapter→caliban.interop.tapir.WebSocketInterpretercaliban.PlayAdapter→caliban.interop.tapir.HttpInterpretercaliban.PlayAdapter→caliban.interop.tapir.HttpUploadInterpretercaliban.PlayAdapter→caliban.interop.tapir.StreamConstructorcaliban.PlayAdapter→caliban.interop.tapir.WebSocketInterpreter
- Direction
- caliban uses caliban.interop.tapir, so a change to caliban.interop.tapir can break caliban, while a change to caliban can't break caliban.interop.tapir.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→16 caliban uses caliban.parsing.adt✕
- Connections
- 7 pairs of types, where a type in caliban uses a type in caliban.parsing.adt.
- The types involved
caliban.GraphQL→caliban.parsing.adt.Directivecaliban.GraphQL→caliban.parsing.adt.Documentcaliban.GraphQL→caliban.parsing.adt.SchemaCoordinatecaliban.RemoteMutation→caliban.parsing.adt.Documentcaliban.RemoteQuery→caliban.parsing.adt.Documentcaliban.gateway→caliban.parsing.adt.Directivecaliban.gateway→caliban.parsing.adt.Selection
- Direction
- caliban uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban, while a change to caliban can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→17 caliban uses caliban.CalibanError✕
- Connections
- 2 pairs of types, where a type in caliban uses a type in caliban.CalibanError.
- The types involved
caliban.GraphQL→caliban.CalibanError.ValidationErrorcaliban.HttpUtils→caliban.CalibanError.ValidationError
- Direction
- caliban uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban, while a change to caliban can't break caliban.CalibanError.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→19 caliban uses caliban.rendering✕
- Connections
- 1 pair of types, where a type in caliban uses a type in caliban.rendering.
- The types involved
caliban.GraphQL→caliban.rendering.Renderer
- Direction
- caliban uses caliban.rendering, so a change to caliban.rendering can break caliban, while a change to caliban can't break caliban.rendering.
- Position
- Below the diagonal: caliban uses a module listed above it, which is the healthy direction.
20→29 caliban uses (global) part of a loop✕
- Connections
- 1 pair of types, where a type in caliban uses a type in (global).
- The types involved
caliban.RootResolver→Query
- Direction
- caliban uses (global), so a change to (global) can break caliban, while a change to caliban can't break (global).
- 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→1 caliban.tools uses caliban.client✕
- Connections
- 2 pairs of types, where a type in caliban.tools uses a type in caliban.client.
- The types involved
caliban.tools.IntrospectionClient→caliban.client.CalibanClientErrorcaliban.tools.IntrospectionClient→caliban.client.SelectionBuilder
- Direction
- caliban.tools uses caliban.client, so a change to caliban.client can break caliban.tools, while a change to caliban.tools can't break caliban.client.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→6 caliban.tools uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 11 pairs of types, where a type in caliban.tools uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition
- Direction
- caliban.tools uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.tools, while a change to caliban.tools can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→7 caliban.tools uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 8 pairs of types, where a type in caliban.tools uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.tools.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.tools.RemoteSchema→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.tools.RemoteSchema→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.tools.SchemaComparison→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.tools uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.tools, while a change to caliban.tools can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→8 caliban.tools uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.tools uses a type in caliban.introspection.adt.
- The types involved
caliban.tools.RemoteSchema→caliban.introspection.adt.__Schema
- Direction
- caliban.tools uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.tools, while a change to caliban.tools can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→12 caliban.tools uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.tools uses a type in caliban.schema.
- The types involved
caliban.tools.RemoteSchema→caliban.schema.RootType
- Direction
- caliban.tools uses caliban.schema, so a change to caliban.schema can break caliban.tools, while a change to caliban.tools can't break caliban.schema.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→16 caliban.tools uses caliban.parsing.adt✕
- Connections
- 8 pairs of types, where a type in caliban.tools uses a type in caliban.parsing.adt.
- The types involved
caliban.tools.IntrospectionClient→caliban.parsing.adt.Directivecaliban.tools.IntrospectionClient→caliban.parsing.adt.Documentcaliban.tools.IntrospectionClient→caliban.parsing.adt.Typecaliban.tools.RemoteSchema→caliban.parsing.adt.Documentcaliban.tools.SchemaComparison→caliban.parsing.adt.Directivecaliban.tools.SchemaComparison→caliban.parsing.adt.Documentcaliban.tools.SchemaComparisonChange→caliban.parsing.adt.SchemaCoordinatecaliban.tools.SchemaLoader→caliban.parsing.adt.Document
- Direction
- caliban.tools uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.tools, while a change to caliban.tools can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
21→17 caliban.tools uses caliban.CalibanError✕
- Connections
- 1 pair of types, where a type in caliban.tools uses a type in caliban.CalibanError.
- The types involved
caliban.tools.RemoteSchema→caliban.CalibanError.ValidationError
- Direction
- caliban.tools uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.tools, while a change to caliban.tools can't break caliban.CalibanError.
- Position
- Below the diagonal: caliban.tools uses a module listed above it, which is the healthy direction.
22→8 caliban.federation uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.federation uses a type in caliban.introspection.adt.
- The types involved
caliban.federation.EntityResolver→caliban.introspection.adt.__Type
- Direction
- caliban.federation uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.federation, while a change to caliban.federation can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.federation uses a module listed above it, which is the healthy direction.
22→12 caliban.federation uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.federation uses a type in caliban.schema.
- The types involved
caliban.federation.EntityResolver→caliban.schema.Step
- Direction
- caliban.federation uses caliban.schema, so a change to caliban.schema can break caliban.federation, while a change to caliban.federation can't break caliban.schema.
- Position
- Below the diagonal: caliban.federation uses a module listed above it, which is the healthy direction.
22→16 caliban.federation uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in caliban.federation uses a type in caliban.parsing.adt.
- The types involved
caliban.federation.connect→caliban.parsing.adt.Directive
- Direction
- caliban.federation uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.federation, while a change to caliban.federation can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.federation uses a module listed above it, which is the healthy direction.
22→20 caliban.federation uses caliban✕
- Connections
- 3 pairs of types, where a type in caliban.federation uses a type in caliban.
- The types involved
caliban.federation.EntityResolver→caliban.InputValuecaliban.federation.FederationSupport→caliban.GraphQLcaliban.federation.FederationSupport→caliban.GraphQLAspect
- Direction
- caliban.federation uses caliban, so a change to caliban can break caliban.federation, while a change to caliban.federation can't break caliban.
- Position
- Below the diagonal: caliban.federation uses a module listed above it, which is the healthy direction.
23→8 caliban.gateway.internal.composition.DirectiveComposition uses caliban.introspection.adt✕
- Connections
- 9 pairs of types, where a type in caliban.gateway.internal.composition.DirectiveComposition uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.introspection.adt.__Directivecaliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.introspection.adt.__EnumValuecaliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.introspection.adt.__Fieldcaliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.introspection.adt.__InputValuecaliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.DirectiveComposition.Coordinate→caliban.introspection.adt.__DirectiveLocationcaliban.gateway.internal.composition.DirectiveComposition.DefinitionSignature→caliban.introspection.adt.__DirectiveLocationcaliban.gateway.internal.composition.DirectiveComposition.LocalDefinition→caliban.introspection.adt.__Directivecaliban.gateway.internal.composition.DirectiveComposition.TypeCoordinate→caliban.introspection.adt.__DirectiveLocation
- Direction
- caliban.gateway.internal.composition.DirectiveComposition uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.composition.DirectiveComposition, while a change to caliban.gateway.internal.composition.DirectiveComposition can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.DirectiveComposition uses a module listed above it, which is the healthy direction.
23→12 caliban.gateway.internal.composition.DirectiveComposition uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.DirectiveComposition uses a type in caliban.schema.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.schema.RootType
- Direction
- caliban.gateway.internal.composition.DirectiveComposition uses caliban.schema, so a change to caliban.schema can break caliban.gateway.internal.composition.DirectiveComposition, while a change to caliban.gateway.internal.composition.DirectiveComposition can't break caliban.schema.
- Position
- Below the diagonal: caliban.gateway.internal.composition.DirectiveComposition uses a module listed above it, which is the healthy direction.
23→16 caliban.gateway.internal.composition.DirectiveComposition uses caliban.parsing.adt✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition.DirectiveComposition uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition.Application→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.DirectiveComposition.ComposedDirectives→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.DirectiveComposition.Coordinate→caliban.parsing.adt.SchemaCoordinate
- Direction
- caliban.gateway.internal.composition.DirectiveComposition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.composition.DirectiveComposition, while a change to caliban.gateway.internal.composition.DirectiveComposition can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.DirectiveComposition uses a module listed above it, which is the healthy direction.
23→20 caliban.gateway.internal.composition.DirectiveComposition uses caliban✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.DirectiveComposition uses a type in caliban.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition.InputSignature→caliban.InputValue
- Direction
- caliban.gateway.internal.composition.DirectiveComposition uses caliban, so a change to caliban can break caliban.gateway.internal.composition.DirectiveComposition, while a change to caliban.gateway.internal.composition.DirectiveComposition can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.composition.DirectiveComposition uses a module listed above it, which is the healthy direction.
23→35 caliban.gateway.internal.composition.DirectiveComposition uses caliban.gateway.internal.composition.ComposedGraph part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.DirectiveComposition uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition.SourceDirectives→caliban.gateway.internal.composition.ComposedGraph.Source
- Direction
- caliban.gateway.internal.composition.DirectiveComposition uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.composition.DirectiveComposition, while a change to caliban.gateway.internal.composition.DirectiveComposition can't break caliban.gateway.internal.composition.ComposedGraph.
- 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→16 caliban.gateway.internal.execution.EntityLookup uses caliban.parsing.adt✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.execution.EntityLookup uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.execution.EntityLookup.ByKeyVariant→caliban.parsing.adt.Selectioncaliban.gateway.internal.execution.EntityLookup.SingleVariant→caliban.parsing.adt.Selection
- Direction
- caliban.gateway.internal.execution.EntityLookup uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.execution.EntityLookup, while a change to caliban.gateway.internal.execution.EntityLookup can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.execution.EntityLookup uses a module listed above it, which is the healthy direction.
24→20 caliban.gateway.internal.execution.EntityLookup uses caliban✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.execution.EntityLookup uses a type in caliban.
- The types involved
caliban.gateway.internal.execution.EntityLookup.Call→caliban.CalibanErrorcaliban.gateway.internal.execution.EntityLookup.Call→caliban.GraphQLResponsecaliban.gateway.internal.execution.EntityLookup.Call→caliban.ResponseValuecaliban.gateway.internal.execution.EntityLookup.CallPart→caliban.InputValuecaliban.gateway.internal.execution.EntityLookup.ResponseShape→caliban.PathValuecaliban.gateway.internal.execution.EntityLookup.ResponseShape→caliban.ResponseValue
- Direction
- caliban.gateway.internal.execution.EntityLookup uses caliban, so a change to caliban can break caliban.gateway.internal.execution.EntityLookup, while a change to caliban.gateway.internal.execution.EntityLookup can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.execution.EntityLookup uses a module listed above it, which is the healthy direction.
24→32 caliban.gateway.internal.execution.EntityLookup uses caliban.gateway.internal.execution part of a loop✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.execution.EntityLookup uses a type in caliban.gateway.internal.execution.
- The types involved
caliban.gateway.internal.execution.EntityLookup.ByKeyVariant→caliban.gateway.internal.execution.ResponseProjectioncaliban.gateway.internal.execution.EntityLookup.FederationVariant→caliban.gateway.internal.execution.ResponseProjectioncaliban.gateway.internal.execution.EntityLookup.SingleVariant→caliban.gateway.internal.execution.ResponseProjectioncaliban.gateway.internal.execution.EntityLookup.Variant→caliban.gateway.internal.execution.ResponseProjection
- Direction
- caliban.gateway.internal.execution.EntityLookup uses caliban.gateway.internal.execution, so a change to caliban.gateway.internal.execution can break caliban.gateway.internal.execution.EntityLookup, while a change to caliban.gateway.internal.execution.EntityLookup can't break caliban.gateway.internal.execution.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→33 caliban.gateway.internal.execution.EntityLookup uses caliban.gateway.internal.planning.OperationPlan part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.execution.EntityLookup uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.execution.EntityLookup.ByKeyVariant→caliban.gateway.internal.planning.OperationPlan.RequiredSelection
- Direction
- caliban.gateway.internal.execution.EntityLookup uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.execution.EntityLookup, while a change to caliban.gateway.internal.execution.EntityLookup can't break caliban.gateway.internal.planning.OperationPlan.
- 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→11 caliban.gateway.internal.execution.PlanExecutor uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.execution.PlanExecutor uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.execution.Field
- Direction
- caliban.gateway.internal.execution.PlanExecutor uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.execution.PlanExecutor, while a change to caliban.gateway.internal.execution.PlanExecutor can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.execution.PlanExecutor uses a module listed above it, which is the healthy direction.
25→20 caliban.gateway.internal.execution.PlanExecutor uses caliban✕
- Connections
- 19 pairs of types, where a type in caliban.gateway.internal.execution.PlanExecutor uses a type in caliban.
- The types involved
caliban.gateway.internal.execution.PlanExecutor.Batch→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.Executed→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.Executed→caliban.GraphQLResponsecaliban.gateway.internal.execution.PlanExecutor.Fetched→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.Fetched→caliban.ResponseValuecaliban.gateway.internal.execution.PlanExecutor.Guard→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.PreparedFragment→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.PreparedFragment→caliban.Incrementalcaliban.gateway.internal.execution.PlanExecutor.PreparedFragment→caliban.PathValuecaliban.gateway.internal.execution.PlanExecutor.PreparedFragment→caliban.ResponseValuecaliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.GraphQLRequestcaliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.GraphQLResponsecaliban.gateway.internal.execution.PlanExecutor.RootResult→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.RootResult→caliban.ResponseValuecaliban.gateway.internal.execution.PlanExecutor.Subscription→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor.Subscription→caliban.GraphQLResponsecaliban.gateway.internal.execution.PlanExecutor.View→caliban.PathValuecaliban.gateway.internal.execution.PlanExecutor.View→caliban.ResponseValue
- Direction
- caliban.gateway.internal.execution.PlanExecutor uses caliban, so a change to caliban can break caliban.gateway.internal.execution.PlanExecutor, while a change to caliban.gateway.internal.execution.PlanExecutor can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.execution.PlanExecutor uses a module listed above it, which is the healthy direction.
25→32 caliban.gateway.internal.execution.PlanExecutor uses caliban.gateway.internal.execution part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.execution.PlanExecutor uses a type in caliban.gateway.internal.execution.
- The types involved
caliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.gateway.internal.execution.ResponseCompletioncaliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.gateway.internal.execution.ResponseProjection
- Direction
- caliban.gateway.internal.execution.PlanExecutor uses caliban.gateway.internal.execution, so a change to caliban.gateway.internal.execution can break caliban.gateway.internal.execution.PlanExecutor, while a change to caliban.gateway.internal.execution.PlanExecutor can't break caliban.gateway.internal.execution.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→33 caliban.gateway.internal.execution.PlanExecutor uses caliban.gateway.internal.planning.OperationPlan part of a loop✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.execution.PlanExecutor uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.execution.PlanExecutor.Fetched→caliban.gateway.internal.planning.OperationPlan.FetchIdcaliban.gateway.internal.execution.PlanExecutor.PreparedFragment→caliban.gateway.internal.planning.OperationPlan.DeferredFragmentcaliban.gateway.internal.execution.PlanExecutor.PreparedRoot→caliban.gateway.internal.planning.OperationPlan.RootFetchcaliban.gateway.internal.execution.PlanExecutor.RootResult→caliban.gateway.internal.planning.OperationPlan.FetchId
- Direction
- caliban.gateway.internal.execution.PlanExecutor uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.execution.PlanExecutor, while a change to caliban.gateway.internal.execution.PlanExecutor can't break caliban.gateway.internal.planning.OperationPlan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→8 caliban.gateway.internal.planning uses caliban.introspection.adt✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.planning.OperationCost→caliban.introspection.adt.__InputValuecaliban.gateway.internal.planning.OperationCost→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.planning uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning uses a module listed above it, which is the healthy direction.
26→11 caliban.gateway.internal.planning uses caliban.execution✕
- Connections
- 7 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.planning.Deferral→caliban.execution.Fieldcaliban.gateway.internal.planning.FetchGraphOptimizer→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationCost→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlan→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner→caliban.execution.ExecutionRequestcaliban.gateway.internal.planning.OperationPlanner→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationSecurity→caliban.execution.Field
- Direction
- caliban.gateway.internal.planning uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.planning uses a module listed above it, which is the healthy direction.
26→16 caliban.gateway.internal.planning uses caliban.parsing.adt✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.planning.Deferral→caliban.parsing.adt.Directivecaliban.gateway.internal.planning.Deferral→caliban.parsing.adt.Documentcaliban.gateway.internal.planning.OperationCost→caliban.parsing.adt.OperationTypecaliban.gateway.internal.planning.OperationPlan→caliban.parsing.adt.OperationTypecaliban.gateway.internal.planning.OperationPlanner→caliban.parsing.adt.Document
- Direction
- caliban.gateway.internal.planning uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning uses a module listed above it, which is the healthy direction.
26→18 caliban.gateway.internal.planning uses caliban.gateway.PhaseHooks✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning uses a type in caliban.gateway.PhaseHooks.
- The types involved
caliban.gateway.internal.planning.OperationSecurity→caliban.gateway.PhaseHooks.SecurityRequirement
- Direction
- caliban.gateway.internal.planning uses caliban.gateway.PhaseHooks, so a change to caliban.gateway.PhaseHooks can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.gateway.PhaseHooks.
- Position
- Below the diagonal: caliban.gateway.internal.planning uses a module listed above it, which is the healthy direction.
26→20 caliban.gateway.internal.planning uses caliban✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.
- The types involved
caliban.gateway.internal.planning.Deferral→caliban.InputValuecaliban.gateway.internal.planning.OperationCost→caliban.InputValuecaliban.gateway.internal.planning.OperationPlan→caliban.InputValue
- Direction
- caliban.gateway.internal.planning uses caliban, so a change to caliban can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.planning uses a module listed above it, which is the healthy direction.
26→32 caliban.gateway.internal.planning uses caliban.gateway.internal.execution part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning uses a type in caliban.gateway.internal.execution.
- The types involved
caliban.gateway.internal.planning.OperationPlan→caliban.gateway.internal.execution.ResponseCompletion
- Direction
- caliban.gateway.internal.planning uses caliban.gateway.internal.execution, so a change to caliban.gateway.internal.execution can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.gateway.internal.execution.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→33 caliban.gateway.internal.planning uses caliban.gateway.internal.planning.OperationPlan part of a loop✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.planning.FetchGraphOptimizer→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.planning.FetchGraphOptimizer→caliban.gateway.internal.planning.OperationPlan.FetchIdcaliban.gateway.internal.planning.FetchGraphOptimizer→caliban.gateway.internal.planning.OperationPlan.RootFetchcaliban.gateway.internal.planning.OperationCost→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.planning.OperationPlan→caliban.gateway.internal.planning.OperationPlan.Payloadcaliban.gateway.internal.planning.OperationPlan→caliban.gateway.internal.planning.OperationPlan.TypenameSelection
- Direction
- caliban.gateway.internal.planning uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.gateway.internal.planning.OperationPlan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→35 caliban.gateway.internal.planning uses caliban.gateway.internal.composition.ComposedGraph part of a loop✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.planning uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.planning.OperationCost→caliban.gateway.internal.composition.ComposedGraph.ListSizecaliban.gateway.internal.planning.OperationCost→caliban.gateway.internal.composition.ComposedGraph.SlicingArgumentcaliban.gateway.internal.planning.OperationCost→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner→caliban.gateway.internal.composition.ComposedGraph.OverrideLabel
- Direction
- caliban.gateway.internal.planning uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.planning, while a change to caliban.gateway.internal.planning can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→3 caliban.parsing.parsers uses caliban.parsing.adt.Definition✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.Definition.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.ExecutableDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemExtension
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt.Definition, so a change to caliban.parsing.adt.Definition can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.Definition.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→4 caliban.parsing.parsers uses caliban.parsing.adt.Type✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Type.NamedTypecaliban.parsing.parsers.SelectionParsers→caliban.parsing.adt.Type.ListTypecaliban.parsing.parsers.SelectionParsers→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→5 caliban.parsing.parsers uses caliban.parsing.adt.Definition.ExecutableDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.Definition.ExecutableDefinition.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinition
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt.Definition.ExecutableDefinition, so a change to caliban.parsing.adt.Definition.ExecutableDefinition can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.Definition.ExecutableDefinition.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→6 caliban.parsing.parsers uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 9 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputObjectTypeDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InterfaceTypeDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ObjectTypeDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.ScalarTypeDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.UnionTypeDefinition
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→7 caliban.parsing.parsers uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 4 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveLocationcaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.SchemaDefinitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→15 caliban.parsing.parsers uses caliban.parsing✕
- Connections
- 1 pair of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.ParsedDocument
- Direction
- caliban.parsing.parsers uses caliban.parsing, so a change to caliban.parsing can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→16 caliban.parsing.parsers uses caliban.parsing.adt✕
- Connections
- 7 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.parsing.adt.
- The types involved
caliban.parsing.parsers.Parsers→caliban.parsing.adt.Definitioncaliban.parsing.parsers.Parsers→caliban.parsing.adt.OperationTypecaliban.parsing.parsers.Parsers→caliban.parsing.adt.SchemaCoordinatecaliban.parsing.parsers.Parsers→caliban.parsing.adt.VariableDefinitioncaliban.parsing.parsers.SelectionParsers→caliban.parsing.adt.Directivecaliban.parsing.parsers.SelectionParsers→caliban.parsing.adt.Selectioncaliban.parsing.parsers.SelectionParsers→caliban.parsing.adt.Type
- Direction
- caliban.parsing.parsers uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
27→20 caliban.parsing.parsers uses caliban✕
- Connections
- 3 pairs of types, where a type in caliban.parsing.parsers uses a type in caliban.
- The types involved
caliban.parsing.parsers.Parsers→caliban.InputValuecaliban.parsing.parsers.SelectionParsers→caliban.InputValuecaliban.parsing.parsers.ValueParsers→caliban.InputValue
- Direction
- caliban.parsing.parsers uses caliban, so a change to caliban can break caliban.parsing.parsers, while a change to caliban.parsing.parsers can't break caliban.
- Position
- Below the diagonal: caliban.parsing.parsers uses a module listed above it, which is the healthy direction.
28→4 caliban.validation uses caliban.parsing.adt.Type✕
- Connections
- 2 pairs of types, where a type in caliban.validation uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.validation.Utils→caliban.parsing.adt.Type.NamedTypecaliban.validation.Validator→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.validation uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.validation, while a change to caliban.validation can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→5 caliban.validation uses caliban.parsing.adt.Definition.ExecutableDefinition✕
- Connections
- 3 pairs of types, where a type in caliban.validation uses a type in caliban.parsing.adt.Definition.ExecutableDefinition.
- The types involved
caliban.validation.Context→caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinitioncaliban.validation.Context→caliban.parsing.adt.Definition.ExecutableDefinition.OperationDefinitioncaliban.validation.Validator→caliban.parsing.adt.Definition.ExecutableDefinition.FragmentDefinition
- Direction
- caliban.validation uses caliban.parsing.adt.Definition.ExecutableDefinition, so a change to caliban.parsing.adt.Definition.ExecutableDefinition can break caliban.validation, while a change to caliban.validation can't break caliban.parsing.adt.Definition.ExecutableDefinition.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→7 caliban.validation uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.validation uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.validation.SchemaValidator→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinitioncaliban.validation.Validator→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinition
- Direction
- caliban.validation uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.validation, while a change to caliban.validation can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→8 caliban.validation uses caliban.introspection.adt✕
- Connections
- 14 pairs of types, where a type in caliban.validation uses a type in caliban.introspection.adt.
- The types involved
caliban.validation.FieldMap→caliban.introspection.adt.__Typecaliban.validation.FragmentValidator→caliban.introspection.adt.__Typecaliban.validation.SchemaValidator→caliban.introspection.adt.__Directivecaliban.validation.SchemaValidator→caliban.introspection.adt.__Fieldcaliban.validation.SchemaValidator→caliban.introspection.adt.__InputValuecaliban.validation.SchemaValidator→caliban.introspection.adt.__Typecaliban.validation.SelectedField→caliban.introspection.adt.__Fieldcaliban.validation.SelectedField→caliban.introspection.adt.__Typecaliban.validation.Utils→caliban.introspection.adt.__Typecaliban.validation.Validator→caliban.introspection.adt.__Fieldcaliban.validation.Validator→caliban.introspection.adt.__InputValuecaliban.validation.Validator→caliban.introspection.adt.__Typecaliban.validation.ValueValidator→caliban.introspection.adt.__InputValuecaliban.validation.ValueValidator→caliban.introspection.adt.__Type
- Direction
- caliban.validation uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.validation, while a change to caliban.validation can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→11 caliban.validation uses caliban.execution✕
- Connections
- 2 pairs of types, where a type in caliban.validation uses a type in caliban.execution.
- The types involved
caliban.validation.Validator→caliban.execution.ExecutionRequestcaliban.validation.Validator→caliban.execution.Field
- Direction
- caliban.validation uses caliban.execution, so a change to caliban.execution can break caliban.validation, while a change to caliban.validation can't break caliban.execution.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→12 caliban.validation uses caliban.schema✕
- Connections
- 5 pairs of types, where a type in caliban.validation uses a type in caliban.schema.
- The types involved
caliban.validation.Context→caliban.schema.RootTypecaliban.validation.SchemaValidator→caliban.schema.RootSchemacaliban.validation.SchemaValidator→caliban.schema.RootSchemaBuildercaliban.validation.SchemaValidator→caliban.schema.RootTypecaliban.validation.Validator→caliban.schema.RootType
- Direction
- caliban.validation uses caliban.schema, so a change to caliban.schema can break caliban.validation, while a change to caliban.validation can't break caliban.schema.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→16 caliban.validation uses caliban.parsing.adt✕
- Connections
- 11 pairs of types, where a type in caliban.validation uses a type in caliban.parsing.adt.
- The types involved
caliban.validation.Context→caliban.parsing.adt.Documentcaliban.validation.Context→caliban.parsing.adt.Selectioncaliban.validation.Context→caliban.parsing.adt.VariableDefinitioncaliban.validation.FieldMap→caliban.parsing.adt.Selectioncaliban.validation.FragmentValidator→caliban.parsing.adt.Selectioncaliban.validation.SchemaValidator→caliban.parsing.adt.Documentcaliban.validation.Validator→caliban.parsing.adt.Directivecaliban.validation.Validator→caliban.parsing.adt.Documentcaliban.validation.Validator→caliban.parsing.adt.Selectioncaliban.validation.Validator→caliban.parsing.adt.Typecaliban.validation.Validator→caliban.parsing.adt.VariableDefinition
- Direction
- caliban.validation uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.validation, while a change to caliban.validation can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→17 caliban.validation uses caliban.CalibanError✕
- Connections
- 5 pairs of types, where a type in caliban.validation uses a type in caliban.CalibanError.
- The types involved
caliban.validation.FragmentValidator→caliban.CalibanError.ValidationErrorcaliban.validation.SchemaValidator→caliban.CalibanError.ValidationErrorcaliban.validation.ValidationOps→caliban.CalibanError.ValidationErrorcaliban.validation.Validator→caliban.CalibanError.ValidationErrorcaliban.validation.ValueValidator→caliban.CalibanError.ValidationError
- Direction
- caliban.validation uses caliban.CalibanError, so a change to caliban.CalibanError can break caliban.validation, while a change to caliban.validation can't break caliban.CalibanError.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
28→20 caliban.validation uses caliban✕
- Connections
- 3 pairs of types, where a type in caliban.validation uses a type in caliban.
- The types involved
caliban.validation.Context→caliban.InputValuecaliban.validation.Validator→caliban.InputValuecaliban.validation.ValueValidator→caliban.InputValue
- Direction
- caliban.validation uses caliban, so a change to caliban can break caliban.validation, while a change to caliban.validation can't break caliban.
- Position
- Below the diagonal: caliban.validation uses a module listed above it, which is the healthy direction.
29→8 (global) uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in (global) uses a type in caliban.introspection.adt.
- The types involved
caliban→caliban.introspection.adt.__Directive
- Direction
- (global) uses caliban.introspection.adt, so a change to caliban.introspection.adt can break (global), while a change to (global) can't break caliban.introspection.adt.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
29→12 (global) uses caliban.schema✕
- Connections
- 2 pairs of types, where a type in (global) uses a type in caliban.schema.
- The types involved
ProductSchema→caliban.schema.GenericSchemacaliban→caliban.schema.Schema
- Direction
- (global) uses caliban.schema, so a change to caliban.schema can break (global), while a change to (global) can't break caliban.schema.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
29→16 (global) uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in (global) uses a type in caliban.parsing.adt.
- The types involved
caliban→caliban.parsing.adt.Directive
- Direction
- (global) uses caliban.parsing.adt, so a change to caliban.parsing.adt can break (global), while a change to (global) can't break caliban.parsing.adt.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
29→20 (global) uses caliban✕
- Connections
- 1 pair of types, where a type in (global) uses a type in caliban.
- The types involved
ProductSchema→caliban.GraphQL
- Direction
- (global) uses caliban, so a change to caliban can break (global), while a change to (global) can't break caliban.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
29→22 (global) uses caliban.federation✕
- Connections
- 1 pair of types, where a type in (global) uses a type in caliban.federation.
- The types involved
ProductSchema→caliban.federation.EntityResolver
- Direction
- (global) uses caliban.federation, so a change to caliban.federation can break (global), while a change to (global) can't break caliban.federation.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
30→12 caliban.federation.v2x uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.federation.v2x uses a type in caliban.schema.
- The types involved
caliban.federation.v2x.FederationDirectivesV2_12→caliban.schema.Extended
- Direction
- caliban.federation.v2x uses caliban.schema, so a change to caliban.schema can break caliban.federation.v2x, while a change to caliban.federation.v2x can't break caliban.schema.
- Position
- Below the diagonal: caliban.federation.v2x uses a module listed above it, which is the healthy direction.
30→16 caliban.federation.v2x uses caliban.parsing.adt✕
- Connections
- 6 pairs of types, where a type in caliban.federation.v2x uses a type in caliban.parsing.adt.
- The types involved
caliban.federation.v2x.ComposeDirective→caliban.parsing.adt.Directivecaliban.federation.v2x.Extension→caliban.parsing.adt.Directivecaliban.federation.v2x.FederationDirectivesV2_10→caliban.parsing.adt.Directivecaliban.federation.v2x.FederationDirectivesV2_12→caliban.parsing.adt.Directivecaliban.federation.v2x.FederationDirectivesV2_7→caliban.parsing.adt.Directivecaliban.federation.v2x.Link→caliban.parsing.adt.Directive
- Direction
- caliban.federation.v2x uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.federation.v2x, while a change to caliban.federation.v2x can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.federation.v2x uses a module listed above it, which is the healthy direction.
30→19 caliban.federation.v2x uses caliban.rendering✕
- Connections
- 1 pair of types, where a type in caliban.federation.v2x uses a type in caliban.rendering.
- The types involved
caliban.federation.v2x.FederationV2→caliban.rendering.Renderer
- Direction
- caliban.federation.v2x uses caliban.rendering, so a change to caliban.rendering can break caliban.federation.v2x, while a change to caliban.federation.v2x can't break caliban.rendering.
- Position
- Below the diagonal: caliban.federation.v2x uses a module listed above it, which is the healthy direction.
30→20 caliban.federation.v2x uses caliban✕
- Connections
- 2 pairs of types, where a type in caliban.federation.v2x uses a type in caliban.
- The types involved
caliban.federation.v2x.FederationV2→caliban.GraphQLcaliban.federation.v2x.Import→caliban.InputValue
- Direction
- caliban.federation.v2x uses caliban, so a change to caliban can break caliban.federation.v2x, while a change to caliban.federation.v2x can't break caliban.
- Position
- Below the diagonal: caliban.federation.v2x uses a module listed above it, which is the healthy direction.
30→22 caliban.federation.v2x uses caliban.federation✕
- Connections
- 2 pairs of types, where a type in caliban.federation.v2x uses a type in caliban.federation.
- The types involved
caliban.federation.v2x.FederationV2→caliban.federation.FederationDirectivescaliban.federation.v2x.FederationV2→caliban.federation.FederationSupport
- Direction
- caliban.federation.v2x uses caliban.federation, so a change to caliban.federation can break caliban.federation.v2x, while a change to caliban.federation.v2x can't break caliban.federation.
- Position
- Below the diagonal: caliban.federation.v2x uses a module listed above it, which is the healthy direction.
31→8 caliban.gateway.internal.composition.FederationCompilation uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.FederationCompilation uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.composition.FederationCompilation.FederationDirective→caliban.introspection.adt.__Directive
- Direction
- caliban.gateway.internal.composition.FederationCompilation uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.composition.FederationCompilation, while a change to caliban.gateway.internal.composition.FederationCompilation can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.FederationCompilation uses a module listed above it, which is the healthy direction.
31→16 caliban.gateway.internal.composition.FederationCompilation uses caliban.parsing.adt✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition.FederationCompilation uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.composition.FederationCompilation.FederationApplication→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.FederationCompilation.FederationDirectiveNames→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.FederationCompilation.TypeSystemDirectiveApplication→caliban.parsing.adt.Directive
- Direction
- caliban.gateway.internal.composition.FederationCompilation uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.composition.FederationCompilation, while a change to caliban.gateway.internal.composition.FederationCompilation can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.FederationCompilation uses a module listed above it, which is the healthy direction.
31→23 caliban.gateway.internal.composition.FederationCompilation uses caliban.gateway.internal.composition.DirectiveComposition✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.composition.FederationCompilation uses a type in caliban.gateway.internal.composition.DirectiveComposition.
- The types involved
caliban.gateway.internal.composition.FederationCompilation.FederationApplication→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.FederationCompilation.FederationDirective→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.FederationCompilation.FederationDirective→caliban.gateway.internal.composition.DirectiveComposition.FeatureVersioncaliban.gateway.internal.composition.FederationCompilation.FederationDirectiveNames→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.FederationCompilation.FederationDirectiveNames→caliban.gateway.internal.composition.DirectiveComposition.LinkedFeaturecaliban.gateway.internal.composition.FederationCompilation.TypeSystemDirectiveApplication→caliban.gateway.internal.composition.DirectiveComposition.Coordinate
- Direction
- caliban.gateway.internal.composition.FederationCompilation uses caliban.gateway.internal.composition.DirectiveComposition, so a change to caliban.gateway.internal.composition.DirectiveComposition can break caliban.gateway.internal.composition.FederationCompilation, while a change to caliban.gateway.internal.composition.FederationCompilation can't break caliban.gateway.internal.composition.DirectiveComposition.
- Position
- Below the diagonal: caliban.gateway.internal.composition.FederationCompilation uses a module listed above it, which is the healthy direction.
32→2 caliban.gateway.internal.execution uses caliban.ResponseValue✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.ResponseValue.
- The types involved
caliban.gateway.internal.execution.RemoteError→caliban.ResponseValue.ObjectValuecaliban.gateway.internal.execution.ResponseMerge→caliban.ResponseValue.ObjectValue
- Direction
- caliban.gateway.internal.execution uses caliban.ResponseValue, so a change to caliban.ResponseValue can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.ResponseValue.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→8 caliban.gateway.internal.execution uses caliban.introspection.adt✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.execution.EntityLookup→caliban.introspection.adt.__Typecaliban.gateway.internal.execution.RemoteError→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.execution uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→11 caliban.gateway.internal.execution uses caliban.execution✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.execution.EntityLookup→caliban.execution.Fieldcaliban.gateway.internal.execution.PlanExecutor→caliban.execution.ExecutionRequestcaliban.gateway.internal.execution.PlanExecutor→caliban.execution.Fieldcaliban.gateway.internal.execution.RemoteError→caliban.execution.Field
- Direction
- caliban.gateway.internal.execution uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→12 caliban.gateway.internal.execution uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.execution uses a type in caliban.schema.
- The types involved
caliban.gateway.internal.execution.PlanExecutor→caliban.schema.RootSchema
- Direction
- caliban.gateway.internal.execution uses caliban.schema, so a change to caliban.schema can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.schema.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→16 caliban.gateway.internal.execution uses caliban.parsing.adt✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.execution.EntityLookup→caliban.parsing.adt.Selectioncaliban.gateway.internal.execution.LocalSubgraphExecutor→caliban.parsing.adt.OperationTypecaliban.gateway.internal.execution.RemoteSubgraphExecutor→caliban.parsing.adt.OperationTypecaliban.gateway.internal.execution.SubgraphExecutor→caliban.parsing.adt.OperationType
- Direction
- caliban.gateway.internal.execution uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→20 caliban.gateway.internal.execution uses caliban✕
- Connections
- 35 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
caliban.gateway.internal.execution.EntityExecutor→caliban.InputValuecaliban.gateway.internal.execution.EntityExecutor→caliban.PathValuecaliban.gateway.internal.execution.EntityExecutor→caliban.ResponseValuecaliban.gateway.internal.execution.EntityLookup→caliban.CalibanErrorcaliban.gateway.internal.execution.EntityLookup→caliban.GraphQLRequestcaliban.gateway.internal.execution.EntityLookup→caliban.GraphQLResponsecaliban.gateway.internal.execution.EntityLookup→caliban.InputValuecaliban.gateway.internal.execution.EntityLookup→caliban.PathValuecaliban.gateway.internal.execution.IndexedFields→caliban.ResponseValuecaliban.gateway.internal.execution.LocalSubgraphExecutor→caliban.CalibanErrorcaliban.gateway.internal.execution.LocalSubgraphExecutor→caliban.GraphQLRequestcaliban.gateway.internal.execution.LocalSubgraphExecutor→caliban.GraphQLResponsecaliban.gateway.internal.execution.PathIndex→caliban.PathValuecaliban.gateway.internal.execution.PlanExecutor→caliban.CalibanErrorcaliban.gateway.internal.execution.PlanExecutor→caliban.GraphQLRequestcaliban.gateway.internal.execution.PlanExecutor→caliban.GraphQLResponsecaliban.gateway.internal.execution.PlanExecutor→caliban.Incrementalcaliban.gateway.internal.execution.RemoteError→caliban.CalibanErrorcaliban.gateway.internal.execution.RemoteError→caliban.PathValuecaliban.gateway.internal.execution.RemoteSubgraphExecutor→caliban.CalibanErrorcaliban.gateway.internal.execution.RemoteSubgraphExecutor→caliban.GraphQLRequestcaliban.gateway.internal.execution.RemoteSubgraphExecutor→caliban.GraphQLResponsecaliban.gateway.internal.execution.RemoteSubgraphExecutor→caliban.ResponseValuecaliban.gateway.internal.execution.RemoteSubscription→caliban.CalibanErrorcaliban.gateway.internal.execution.RemoteSubscription→caliban.GraphQLRequest
- Direction
- caliban.gateway.internal.execution uses caliban, so a change to caliban can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→24 caliban.gateway.internal.execution uses caliban.gateway.internal.execution.EntityLookup✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.gateway.internal.execution.EntityLookup.
- The types involved
caliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.execution.EntityLookup.CallPartcaliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.execution.EntityLookup.FederationVariantcaliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.execution.EntityLookup.Variant
- Direction
- caliban.gateway.internal.execution uses caliban.gateway.internal.execution.EntityLookup, so a change to caliban.gateway.internal.execution.EntityLookup can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.gateway.internal.execution.EntityLookup.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→25 caliban.gateway.internal.execution uses caliban.gateway.internal.execution.PlanExecutor✕
- Connections
- 9 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.gateway.internal.execution.PlanExecutor.
- The types involved
caliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.Batchcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.Executedcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.Fetchedcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.Guardcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.PreparedFragmentcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.PreparedRootcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.RootResultcaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.Subscriptioncaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.execution.PlanExecutor.View
- Direction
- caliban.gateway.internal.execution uses caliban.gateway.internal.execution.PlanExecutor, so a change to caliban.gateway.internal.execution.PlanExecutor can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.gateway.internal.execution.PlanExecutor.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→26 caliban.gateway.internal.execution uses caliban.gateway.internal.planning✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.execution uses a type in caliban.gateway.internal.planning.
- The types involved
caliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.planning.OperationPlan
- Direction
- caliban.gateway.internal.execution uses caliban.gateway.internal.planning, so a change to caliban.gateway.internal.planning can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.gateway.internal.planning.
- Position
- Below the diagonal: caliban.gateway.internal.execution uses a module listed above it, which is the healthy direction.
32→33 caliban.gateway.internal.execution uses caliban.gateway.internal.planning.OperationPlan part of a loop✕
- Connections
- 7 pairs of types, where a type in caliban.gateway.internal.execution uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.execution.EntityExecutor→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.execution.EntityExecutor→caliban.gateway.internal.planning.OperationPlan.FetchIdcaliban.gateway.internal.execution.EntityExecutor→caliban.gateway.internal.planning.OperationPlan.RequiredSelectioncaliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.planning.OperationPlan.ContextualArgumentcaliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.planning.OperationPlan.RequiredSelectioncaliban.gateway.internal.execution.PlanExecutor→caliban.gateway.internal.planning.OperationPlan.EntityFetch
- Direction
- caliban.gateway.internal.execution uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.gateway.internal.planning.OperationPlan.
- 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→35 caliban.gateway.internal.execution uses caliban.gateway.internal.composition.ComposedGraph part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.execution uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.execution.EntityLookup→caliban.gateway.internal.composition.ComposedGraph.Source
- Direction
- caliban.gateway.internal.execution uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.execution, while a change to caliban.gateway.internal.execution can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→8 caliban.gateway.internal.planning.OperationPlan uses caliban.introspection.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.planning.OperationPlan.DeferredFragment→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
33→11 caliban.gateway.internal.planning.OperationPlan uses caliban.execution✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.planning.OperationPlan.EntityFetch→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlan.Payload→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlan.PlanVariables→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlan.PlanVariables→caliban.execution.Fragmentcaliban.gateway.internal.planning.OperationPlan.RootFetch→caliban.execution.Field
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
33→16 caliban.gateway.internal.planning.OperationPlan uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.planning.OperationPlan.PlanVariables→caliban.parsing.adt.Directive
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
33→20 caliban.gateway.internal.planning.OperationPlan uses caliban✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.
- The types involved
caliban.gateway.internal.planning.OperationPlan.PlanVariables→caliban.InputValue
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban, so a change to caliban can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
33→26 caliban.gateway.internal.planning.OperationPlan uses caliban.gateway.internal.planning✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.gateway.internal.planning.
- The types involved
caliban.gateway.internal.planning.OperationPlan.PlanVariables→caliban.gateway.internal.planning.OperationPlan
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban.gateway.internal.planning, so a change to caliban.gateway.internal.planning can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.gateway.internal.planning.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
33→32 caliban.gateway.internal.planning.OperationPlan uses caliban.gateway.internal.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlan uses a type in caliban.gateway.internal.execution.
- The types involved
caliban.gateway.internal.planning.OperationPlan.EntityTarget→caliban.gateway.internal.execution.EntityLookup
- Direction
- caliban.gateway.internal.planning.OperationPlan uses caliban.gateway.internal.execution, so a change to caliban.gateway.internal.execution can break caliban.gateway.internal.planning.OperationPlan, while a change to caliban.gateway.internal.planning.OperationPlan can't break caliban.gateway.internal.execution.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlan uses a module listed above it, which is the healthy direction.
34→4 caliban.gateway.internal.composition uses caliban.parsing.adt.Type✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.gateway.internal.composition.SchemaMapping→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.gateway.internal.composition uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→6 caliban.gateway.internal.composition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumTypeDefinitioncaliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinition
- Direction
- caliban.gateway.internal.composition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→7 caliban.gateway.internal.composition uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.gateway.internal.composition uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→8 caliban.gateway.internal.composition uses caliban.introspection.adt✕
- Connections
- 17 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.composition.ComposedGraph→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.ContextCompilation→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.CostCompilation→caliban.introspection.adt.__Fieldcaliban.gateway.internal.composition.CostCompilation→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.DirectiveComposition→caliban.introspection.adt.__Directivecaliban.gateway.internal.composition.DirectiveComposition→caliban.introspection.adt.__DirectiveLocationcaliban.gateway.internal.composition.DirectiveComposition→caliban.introspection.adt.__InputValuecaliban.gateway.internal.composition.DirectiveComposition→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.DirectiveComposition→caliban.introspection.adt.__TypeKindcaliban.gateway.internal.composition.FederationCompilation→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.LookupCompilation→caliban.introspection.adt.__InputValuecaliban.gateway.internal.composition.LookupCompilation→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.SchemaComposer→caliban.introspection.adt.__Fieldcaliban.gateway.internal.composition.SchemaComposer→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.SchemaMapping→caliban.introspection.adt.__Fieldcaliban.gateway.internal.composition.TypeComposition→caliban.introspection.adt.__InputValuecaliban.gateway.internal.composition.TypeComposition→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.composition uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→11 caliban.gateway.internal.composition uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.composition.SchemaMapping→caliban.execution.Field
- Direction
- caliban.gateway.internal.composition uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→12 caliban.gateway.internal.composition uses caliban.schema✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.schema.
- The types involved
caliban.gateway.internal.composition.ComposedGraph→caliban.schema.RootTypecaliban.gateway.internal.composition.DirectiveComposition→caliban.schema.RootTypecaliban.gateway.internal.composition.FederationCompilation→caliban.schema.RootTypecaliban.gateway.internal.composition.SchemaComposer→caliban.schema.RootTypecaliban.gateway.internal.composition.SchemaMapping→caliban.schema.RootTypecaliban.gateway.internal.composition.SecurityCompilation→caliban.schema.RootType
- Direction
- caliban.gateway.internal.composition uses caliban.schema, so a change to caliban.schema can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.schema.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→16 caliban.gateway.internal.composition uses caliban.parsing.adt✕
- Connections
- 18 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.composition.ComposedGraph→caliban.parsing.adt.OperationTypecaliban.gateway.internal.composition.ContextCompilation→caliban.parsing.adt.Selectioncaliban.gateway.internal.composition.CostCompilation→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.DirectiveComposition→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.DirectiveComposition→caliban.parsing.adt.Documentcaliban.gateway.internal.composition.FederationCompilation→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.FederationCompilation→caliban.parsing.adt.Documentcaliban.gateway.internal.composition.FederationCompilation→caliban.parsing.adt.Selectioncaliban.gateway.internal.composition.SchemaComposer→caliban.parsing.adt.Documentcaliban.gateway.internal.composition.SchemaComposer→caliban.parsing.adt.Selectioncaliban.gateway.internal.composition.SchemaMapping→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.SchemaMapping→caliban.parsing.adt.Documentcaliban.gateway.internal.composition.SchemaMapping→caliban.parsing.adt.Selectioncaliban.gateway.internal.composition.SchemaMapping→caliban.parsing.adt.Typecaliban.gateway.internal.composition.SecurityCompilation→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Documentcaliban.gateway.internal.composition.SupergraphDecomposition→caliban.parsing.adt.Type
- Direction
- caliban.gateway.internal.composition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→20 caliban.gateway.internal.composition uses caliban✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.
- The types involved
caliban.gateway.internal.composition.DirectiveComposition→caliban.InputValue
- Direction
- caliban.gateway.internal.composition uses caliban, so a change to caliban can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→23 caliban.gateway.internal.composition uses caliban.gateway.internal.composition.DirectiveComposition✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.gateway.internal.composition.DirectiveComposition.
- The types involved
caliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.DirectiveComposition.FieldCoordinatecaliban.gateway.internal.composition.CostCompilation→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.FederationCompilation→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.SchemaMapping→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.SupergraphDecomposition→caliban.gateway.internal.composition.DirectiveComposition.LinkedFeature
- Direction
- caliban.gateway.internal.composition uses caliban.gateway.internal.composition.DirectiveComposition, so a change to caliban.gateway.internal.composition.DirectiveComposition can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.gateway.internal.composition.DirectiveComposition.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→31 caliban.gateway.internal.composition uses caliban.gateway.internal.composition.FederationCompilation✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.gateway.internal.composition.FederationCompilation.
- The types involved
caliban.gateway.internal.composition.SchemaComposer→caliban.gateway.internal.composition.FederationCompilation.FederationApplication
- Direction
- caliban.gateway.internal.composition uses caliban.gateway.internal.composition.FederationCompilation, so a change to caliban.gateway.internal.composition.FederationCompilation can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.gateway.internal.composition.FederationCompilation.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→33 caliban.gateway.internal.composition uses caliban.gateway.internal.planning.OperationPlan✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.composition.SchemaMapping→caliban.gateway.internal.planning.OperationPlan.RequiredSelection
- Direction
- caliban.gateway.internal.composition uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.gateway.internal.planning.OperationPlan.
- Position
- Below the diagonal: caliban.gateway.internal.composition uses a module listed above it, which is the healthy direction.
34→35 caliban.gateway.internal.composition uses caliban.gateway.internal.composition.ComposedGraph part of a loop✕
- Connections
- 21 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.CostMetadatacaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.KeyFieldcaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.OverrideLabelcaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.ProgressiveRoutecaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.SecurityDirectiveApplicationcaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.composition.ComposedGraph→caliban.gateway.internal.composition.ComposedGraph.SourceTypecaliban.gateway.internal.composition.ContextCompilation→caliban.gateway.internal.composition.ComposedGraph.ContextDeclarationcaliban.gateway.internal.composition.ContextCompilation→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.composition.CostCompilation→caliban.gateway.internal.composition.ComposedGraph.CostMetadatacaliban.gateway.internal.composition.CostCompilation→caliban.gateway.internal.composition.ComposedGraph.SlicingArgumentcaliban.gateway.internal.composition.DirectiveComposition→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.composition.FederationCompilation→caliban.gateway.internal.composition.ComposedGraph.KeyFieldcaliban.gateway.internal.composition.LookupCompilation→caliban.gateway.internal.composition.ComposedGraph.KeyArgumentcaliban.gateway.internal.composition.SchemaComposer→caliban.gateway.internal.composition.ComposedGraph.KeyFieldcaliban.gateway.internal.composition.SchemaComposer→caliban.gateway.internal.composition.ComposedGraph.OverrideLabelcaliban.gateway.internal.composition.SchemaComposer→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.composition.SecurityCompilation→caliban.gateway.internal.composition.ComposedGraph.SecurityDirectiveApplicationcaliban.gateway.internal.composition.SecurityCompilation→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.composition.TypeComposition→caliban.gateway.internal.composition.ComposedGraph.ProgressiveRoutecaliban.gateway.internal.composition.TypeComposition→caliban.gateway.internal.composition.ComposedGraph.Source
- Direction
- caliban.gateway.internal.composition uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→39 caliban.gateway.internal.composition uses caliban.gateway part of a loop✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition uses a type in caliban.gateway.
- The types involved
caliban.gateway.internal.composition.SchemaComposer→caliban.gateway.GatewayBuildErrorcaliban.gateway.internal.composition.SchemaComposer→caliban.gateway.Subgraphcaliban.gateway.internal.composition.SchemaComposer→caliban.gateway.SubgraphBuildError
- Direction
- caliban.gateway.internal.composition uses caliban.gateway, so a change to caliban.gateway can break caliban.gateway.internal.composition, while a change to caliban.gateway.internal.composition can't break caliban.gateway.
- 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→8 caliban.gateway.internal.composition.ComposedGraph uses caliban.introspection.adt✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.KeyArgument→caliban.introspection.adt.__Typecaliban.gateway.internal.composition.ComposedGraph.Source→caliban.introspection.adt.__Fieldcaliban.gateway.internal.composition.ComposedGraph.Source→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→11 caliban.gateway.internal.composition.ComposedGraph uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.Source→caliban.execution.Field
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→12 caliban.gateway.internal.composition.ComposedGraph uses caliban.schema✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.schema.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.Source→caliban.schema.RootType
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.schema, so a change to caliban.schema can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.schema.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→16 caliban.gateway.internal.composition.ComposedGraph uses caliban.parsing.adt✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.ContextArgument→caliban.parsing.adt.Selectioncaliban.gateway.internal.composition.ComposedGraph.Source→caliban.parsing.adt.Directivecaliban.gateway.internal.composition.ComposedGraph.Source→caliban.parsing.adt.Selection
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→20 caliban.gateway.internal.composition.ComposedGraph uses caliban✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.SlicingArgument→caliban.InputValue
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban, so a change to caliban can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→23 caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition.DirectiveComposition✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.gateway.internal.composition.DirectiveComposition.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.ContextArgument→caliban.gateway.internal.composition.DirectiveComposition.ArgumentCoordinatecaliban.gateway.internal.composition.ComposedGraph.CostMetadata→caliban.gateway.internal.composition.DirectiveComposition.Coordinatecaliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.DirectiveComposition.Coordinate
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition.DirectiveComposition, so a change to caliban.gateway.internal.composition.DirectiveComposition can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.gateway.internal.composition.DirectiveComposition.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→31 caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition.FederationCompilation✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.gateway.internal.composition.FederationCompilation.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.FederationCompilation.FederationApplicationcaliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.FederationCompilation.FederationDirectivecaliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.FederationCompilation.FederationDirectiveNamescaliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.FederationCompilation.TypeSystemDirectiveApplication
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition.FederationCompilation, so a change to caliban.gateway.internal.composition.FederationCompilation can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.gateway.internal.composition.FederationCompilation.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→34 caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.gateway.internal.composition.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.internal.composition.SchemaMapping
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway.internal.composition, so a change to caliban.gateway.internal.composition can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.gateway.internal.composition.
- Position
- Below the diagonal: caliban.gateway.internal.composition.ComposedGraph uses a module listed above it, which is the healthy direction.
35→39 caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway part of a loop✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.composition.ComposedGraph uses a type in caliban.gateway.
- The types involved
caliban.gateway.internal.composition.ComposedGraph.Source→caliban.gateway.Lookup
- Direction
- caliban.gateway.internal.composition.ComposedGraph uses caliban.gateway, so a change to caliban.gateway can break caliban.gateway.internal.composition.ComposedGraph, while a change to caliban.gateway.internal.composition.ComposedGraph can't break caliban.gateway.
- 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.
36→11 caliban.gateway.internal.OperationPreparation uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.OperationPreparation.ExecutableOperation→caliban.execution.ExecutionRequest
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
36→16 caliban.gateway.internal.OperationPreparation uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.OperationPreparation.ExecutableOperation→caliban.parsing.adt.Document
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
36→18 caliban.gateway.internal.OperationPreparation uses caliban.gateway.PhaseHooks✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.gateway.PhaseHooks.
- The types involved
caliban.gateway.internal.OperationPreparation.Failure→caliban.gateway.PhaseHooks.Outcome
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban.gateway.PhaseHooks, so a change to caliban.gateway.PhaseHooks can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.gateway.PhaseHooks.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
36→20 caliban.gateway.internal.OperationPreparation uses caliban✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.
- The types involved
caliban.gateway.internal.OperationPreparation.CacheKey→caliban.GraphQLRequestcaliban.gateway.internal.OperationPreparation.ExecutableOperation→caliban.GraphQLRequestcaliban.gateway.internal.OperationPreparation.Failure→caliban.CalibanErrorcaliban.gateway.internal.OperationPreparation.Internal→caliban.CalibanErrorcaliban.gateway.internal.OperationPreparation.Rejected→caliban.CalibanError
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban, so a change to caliban can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
36→26 caliban.gateway.internal.OperationPreparation uses caliban.gateway.internal.planning✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.gateway.internal.planning.
- The types involved
caliban.gateway.internal.OperationPreparation.ExecutableOperation→caliban.gateway.internal.planning.OperationPlan
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban.gateway.internal.planning, so a change to caliban.gateway.internal.planning can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.gateway.internal.planning.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
36→35 caliban.gateway.internal.OperationPreparation uses caliban.gateway.internal.composition.ComposedGraph✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.OperationPreparation uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.OperationPreparation.CacheKey→caliban.gateway.internal.composition.ComposedGraph.OverrideLabel
- Direction
- caliban.gateway.internal.OperationPreparation uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.OperationPreparation, while a change to caliban.gateway.internal.OperationPreparation can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Below the diagonal: caliban.gateway.internal.OperationPreparation uses a module listed above it, which is the healthy direction.
37→8 caliban.gateway.internal.planning.OperationPlanner uses caliban.introspection.adt✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.introspection.adt.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.EntityFetchContext→caliban.introspection.adt.__Typecaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.introspection.adt.__Typecaliban.gateway.internal.planning.OperationPlanner.RequiredKeyField→caliban.introspection.adt.__Fieldcaliban.gateway.internal.planning.OperationPlanner.ResolvedLookup→caliban.introspection.adt.__Type
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.introspection.adt, so a change to caliban.introspection.adt can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.introspection.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→11 caliban.gateway.internal.planning.OperationPlanner uses caliban.execution✕
- Connections
- 9 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.EntityCandidate→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.EntityFetchContext→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.EntityFetchState→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.FieldRouting→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.InjectedKeyFields→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.PendingFetch→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.execution.ExecutionRequestcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.execution.Fieldcaliban.gateway.internal.planning.OperationPlanner.RootCandidate→caliban.execution.Field
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→16 caliban.gateway.internal.planning.OperationPlanner uses caliban.parsing.adt✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.PendingFetch→caliban.parsing.adt.Selectioncaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.parsing.adt.Directivecaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.parsing.adt.Documentcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.parsing.adt.Selection
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→23 caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.composition.DirectiveComposition✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.gateway.internal.composition.DirectiveComposition.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.composition.DirectiveComposition.FieldCoordinate
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.composition.DirectiveComposition, so a change to caliban.gateway.internal.composition.DirectiveComposition can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.gateway.internal.composition.DirectiveComposition.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→26 caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.planning✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.gateway.internal.planning.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.planning, so a change to caliban.gateway.internal.planning can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.gateway.internal.planning.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→33 caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.planning.OperationPlan✕
- Connections
- 14 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.gateway.internal.planning.OperationPlan.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.ActiveContext→caliban.gateway.internal.planning.OperationPlan.ContextualArgumentcaliban.gateway.internal.planning.OperationPlanner.EntityCandidate→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.planning.OperationPlanner.EntityCandidate→caliban.gateway.internal.planning.OperationPlan.EntityTargetcaliban.gateway.internal.planning.OperationPlanner.EntityCandidate→caliban.gateway.internal.planning.OperationPlan.FetchIdcaliban.gateway.internal.planning.OperationPlanner.InjectedKeyFields→caliban.gateway.internal.planning.OperationPlan.RequiredSelectioncaliban.gateway.internal.planning.OperationPlanner.PlanCandidate→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.planning.OperationPlanner.PlanCandidate→caliban.gateway.internal.planning.OperationPlan.RootFetchcaliban.gateway.internal.planning.OperationPlanner.PlannedRootFetches→caliban.gateway.internal.planning.OperationPlan.RootFetchcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.ContextualArgumentcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.EntityFetchcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.Payloadcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.RequiredSelectioncaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.RootFetchcaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.planning.OperationPlan.TypenameSelection
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.planning.OperationPlan, so a change to caliban.gateway.internal.planning.OperationPlan can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.gateway.internal.planning.OperationPlan.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
37→35 caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.composition.ComposedGraph✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.planning.OperationPlanner uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.planning.OperationPlanner.ActiveContext→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner.EntityFetchKey→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner.FieldPlanningScope→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner.PendingFetch→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner.PlanningSession→caliban.gateway.internal.composition.ComposedGraph.Sourcecaliban.gateway.internal.planning.OperationPlanner.RootCandidate→caliban.gateway.internal.composition.ComposedGraph.Source
- Direction
- caliban.gateway.internal.planning.OperationPlanner uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal.planning.OperationPlanner, while a change to caliban.gateway.internal.planning.OperationPlanner can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Below the diagonal: caliban.gateway.internal.planning.OperationPlanner uses a module listed above it, which is the healthy direction.
38→11 caliban.gateway.internal uses caliban.execution✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal uses a type in caliban.execution.
- The types involved
caliban.gateway.internal.OperationPreparation→caliban.execution.ExecutionRequest
- Direction
- caliban.gateway.internal uses caliban.execution, so a change to caliban.execution can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.execution.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→16 caliban.gateway.internal uses caliban.parsing.adt✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.OperationPreparation→caliban.parsing.adt.Document
- Direction
- caliban.gateway.internal uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→18 caliban.gateway.internal uses caliban.gateway.PhaseHooks✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal uses a type in caliban.gateway.PhaseHooks.
- The types involved
caliban.gateway.internal.OperationCache→caliban.gateway.PhaseHooks.CacheResult
- Direction
- caliban.gateway.internal uses caliban.gateway.PhaseHooks, so a change to caliban.gateway.PhaseHooks can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.gateway.PhaseHooks.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→20 caliban.gateway.internal uses caliban✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal uses a type in caliban.
- The types involved
caliban.gateway.internal.GatewayInterpreterImpl→caliban.CalibanErrorcaliban.gateway.internal.GatewayInterpreterImpl→caliban.GraphQLResponsecaliban.gateway.internal.OperationPreparation→caliban.CalibanErrorcaliban.gateway.internal.OperationPreparation→caliban.GraphQLRequestcaliban.gateway.internal.OperationPreparation→caliban.InputValue
- Direction
- caliban.gateway.internal uses caliban, so a change to caliban can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→26 caliban.gateway.internal uses caliban.gateway.internal.planning✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal uses a type in caliban.gateway.internal.planning.
- The types involved
caliban.gateway.internal.OperationPreparation→caliban.gateway.internal.planning.OperationPlan
- Direction
- caliban.gateway.internal uses caliban.gateway.internal.planning, so a change to caliban.gateway.internal.planning can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.gateway.internal.planning.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→35 caliban.gateway.internal uses caliban.gateway.internal.composition.ComposedGraph✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal uses a type in caliban.gateway.internal.composition.ComposedGraph.
- The types involved
caliban.gateway.internal.OperationPreparation→caliban.gateway.internal.composition.ComposedGraph.OverrideLabel
- Direction
- caliban.gateway.internal uses caliban.gateway.internal.composition.ComposedGraph, so a change to caliban.gateway.internal.composition.ComposedGraph can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.gateway.internal.composition.ComposedGraph.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→36 caliban.gateway.internal uses caliban.gateway.internal.OperationPreparation✕
- Connections
- 4 pairs of types, where a type in caliban.gateway.internal uses a type in caliban.gateway.internal.OperationPreparation.
- The types involved
caliban.gateway.internal.GatewayInterpreterImpl→caliban.gateway.internal.OperationPreparation.ExecutableOperationcaliban.gateway.internal.OperationPreparation→caliban.gateway.internal.OperationPreparation.CacheKeycaliban.gateway.internal.OperationPreparation→caliban.gateway.internal.OperationPreparation.ExecutableOperationcaliban.gateway.internal.OperationPreparation→caliban.gateway.internal.OperationPreparation.Failure
- Direction
- caliban.gateway.internal uses caliban.gateway.internal.OperationPreparation, so a change to caliban.gateway.internal.OperationPreparation can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.gateway.internal.OperationPreparation.
- Position
- Below the diagonal: caliban.gateway.internal uses a module listed above it, which is the healthy direction.
38→39 caliban.gateway.internal uses caliban.gateway part of a loop✕
- Connections
- 2 pairs of types, where a type in caliban.gateway.internal uses a type in caliban.gateway.
- The types involved
caliban.gateway.internal.GatewayInterpreterImpl→caliban.gateway.OperationEventcaliban.gateway.internal.ReloadableGatewayInterpreterImpl→caliban.gateway.ReloadableGatewayInterpreter
- Direction
- caliban.gateway.internal uses caliban.gateway, so a change to caliban.gateway can break caliban.gateway.internal, while a change to caliban.gateway.internal can't break caliban.gateway.
- 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→16 caliban.gateway uses caliban.parsing.adt✕
- Connections
- 3 pairs of types, where a type in caliban.gateway uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.Gateway→caliban.parsing.adt.Documentcaliban.gateway.OperationEvent→caliban.parsing.adt.OperationTypecaliban.gateway.Supergraph→caliban.parsing.adt.Document
- Direction
- caliban.gateway uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway, while a change to caliban.gateway can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway uses a module listed above it, which is the healthy direction.
39→18 caliban.gateway uses caliban.gateway.PhaseHooks✕
- Connections
- 3 pairs of types, where a type in caliban.gateway uses a type in caliban.gateway.PhaseHooks.
- The types involved
caliban.gateway.GatewayMetrics→caliban.gateway.PhaseHooks.Resultcaliban.gateway.PhaseHooks→caliban.gateway.PhaseHooks.Eventcaliban.gateway.PhaseHooks→caliban.gateway.PhaseHooks.Result
- Direction
- caliban.gateway uses caliban.gateway.PhaseHooks, so a change to caliban.gateway.PhaseHooks can break caliban.gateway, while a change to caliban.gateway can't break caliban.gateway.PhaseHooks.
- Position
- Below the diagonal: caliban.gateway uses a module listed above it, which is the healthy direction.
39→20 caliban.gateway uses caliban✕
- Connections
- 6 pairs of types, where a type in caliban.gateway uses a type in caliban.
- The types involved
caliban.gateway.GatewayInterpreter→caliban.CalibanErrorcaliban.gateway.GatewayInterpreter→caliban.GraphQLInterpretercaliban.gateway.GatewayInterpreter→caliban.GraphQLRequestcaliban.gateway.GatewayInterpreter→caliban.GraphQLResponsecaliban.gateway.OperationEvent→caliban.CalibanErrorcaliban.gateway.RemoteSubscriptionConfig→caliban.InputValue
- Direction
- caliban.gateway uses caliban, so a change to caliban can break caliban.gateway, while a change to caliban.gateway can't break caliban.
- Position
- Below the diagonal: caliban.gateway uses a module listed above it, which is the healthy direction.
39→38 caliban.gateway uses caliban.gateway.internal✕
- Connections
- 3 pairs of types, where a type in caliban.gateway uses a type in caliban.gateway.internal.
- The types involved
caliban.gateway.Gateway→caliban.gateway.internal.GatewayHttpClientcaliban.gateway.Gateway→caliban.gateway.internal.GatewayInterpreterImplcaliban.gateway.Subgraph→caliban.gateway.internal.GatewayHttpClient
- Direction
- caliban.gateway uses caliban.gateway.internal, so a change to caliban.gateway.internal can break caliban.gateway, while a change to caliban.gateway can't break caliban.gateway.internal.
- Position
- Below the diagonal: caliban.gateway uses a module listed above it, which is the healthy direction.
40→2 caliban.gateway.internal.acquisition uses caliban.ResponseValue✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.ResponseValue.
- The types involved
caliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.ResponseValue.ObjectValue
- Direction
- caliban.gateway.internal.acquisition uses caliban.ResponseValue, so a change to caliban.ResponseValue can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.ResponseValue.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→4 caliban.gateway.internal.acquisition uses caliban.parsing.adt.Type✕
- Connections
- 1 pair of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.parsing.adt.Type.
- The types involved
caliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Type.NamedType
- Direction
- caliban.gateway.internal.acquisition uses caliban.parsing.adt.Type, so a change to caliban.parsing.adt.Type can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.parsing.adt.Type.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→6 caliban.gateway.internal.acquisition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- The types involved
caliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.EnumValueDefinitioncaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.FieldDefinitioncaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.InputValueDefinition
- Direction
- caliban.gateway.internal.acquisition uses caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→7 caliban.gateway.internal.acquisition uses caliban.parsing.adt.Definition.TypeSystemDefinition✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.parsing.adt.Definition.TypeSystemDefinition.
- The types involved
caliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveDefinitioncaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.DirectiveLocationcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Definition.TypeSystemDefinition.TypeDefinition
- Direction
- caliban.gateway.internal.acquisition uses caliban.parsing.adt.Definition.TypeSystemDefinition, so a change to caliban.parsing.adt.Definition.TypeSystemDefinition can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.parsing.adt.Definition.TypeSystemDefinition.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→16 caliban.gateway.internal.acquisition uses caliban.parsing.adt✕
- Connections
- 6 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.parsing.adt.
- The types involved
caliban.gateway.internal.acquisition.FederationClient→caliban.parsing.adt.Documentcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Directivecaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Documentcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.parsing.adt.Typecaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.parsing.adt.Documentcaliban.gateway.internal.acquisition.SupergraphAcquisition→caliban.parsing.adt.Document
- Direction
- caliban.gateway.internal.acquisition uses caliban.parsing.adt, so a change to caliban.parsing.adt can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.parsing.adt.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→20 caliban.gateway.internal.acquisition uses caliban✕
- Connections
- 3 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.
- The types involved
caliban.gateway.internal.acquisition.ApolloUplinkClient→caliban.GraphQLRequestcaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.CalibanErrorcaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.GraphQLRequest
- Direction
- caliban.gateway.internal.acquisition uses caliban, so a change to caliban can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→38 caliban.gateway.internal.acquisition uses caliban.gateway.internal✕
- Connections
- 5 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.gateway.internal.
- The types involved
caliban.gateway.internal.acquisition.ApolloUplinkClient→caliban.gateway.internal.GatewayHttpClientcaliban.gateway.internal.acquisition.FederationClient→caliban.gateway.internal.GatewayHttpClientcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.gateway.internal.GatewayHttpClientcaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.gateway.internal.GatewayHttpClientcaliban.gateway.internal.acquisition.SupergraphAcquisition→caliban.gateway.internal.GatewayHttpClient
- Direction
- caliban.gateway.internal.acquisition uses caliban.gateway.internal, so a change to caliban.gateway.internal can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.gateway.internal.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition uses a module listed above it, which is the healthy direction.
40→39 caliban.gateway.internal.acquisition uses caliban.gateway✕
- Connections
- 9 pairs of types, where a type in caliban.gateway.internal.acquisition uses a type in caliban.gateway.
- The types involved
caliban.gateway.internal.acquisition.ApolloUplinkClient→caliban.gateway.SupergraphAcquisitionErrorcaliban.gateway.internal.acquisition.ApolloUplinkClient→caliban.gateway.SupergraphUplinkConfigcaliban.gateway.internal.acquisition.FederationClient→caliban.gateway.SubgraphAcquisitionErrorcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.gateway.SchemaAcquisitionErrorcaliban.gateway.internal.acquisition.IntrospectionClient→caliban.gateway.SubgraphAcquisitionErrorcaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.gateway.SchemaAcquisitionErrorcaliban.gateway.internal.acquisition.RemoteSchemaAcquisition→caliban.gateway.SubgraphAcquisitionErrorcaliban.gateway.internal.acquisition.SupergraphAcquisition→caliban.gateway.SupergraphAcquisitionErrorcaliban.gateway.internal.acquisition.SupergraphAcquisition→caliban.gateway.SupergraphUplinkConfig
- Direction
- caliban.gateway.internal.acquisition uses caliban.gateway, so a change to caliban.gateway can break caliban.gateway.internal.acquisition, while a change to caliban.gateway.internal.acquisition can't break caliban.gateway.
- Position
- Below the diagonal: caliban.gateway.internal.acquisition 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 | 28 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt; 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 SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt. | +3.5 pts | Low | ADR Quality |
| Resolve the 2 `ConnectHTTP` spells `HTTP` where 32 names in the project spell it… finding(s) in Naming Consistency — start with ConnectHTTP.scala, FederationDirectivesV2_10.scala. | +2.2 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. | +3.3 pts | Medium | Architecture documentation |
| Resolve the 1 `ExtraZioEffectOps` spells `Zio` where 12 names in the project spell it… finding(s) in Naming Consistency — start with MonixInterop.scala. | +1.4 pts | Low | Naming Consistency |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.7 pts | Medium | Security & performance tooling |
| Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`). | +1.9 pts | Medium | Web-Security Posture |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala | 4.9 | Mixed | Code Duplication: Edited copies of one member (3 members, 54+ corresponding lines) |
| core/src/main/scala/caliban/rendering/DocumentRenderer.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| interop/cats/src/main/scala/caliban/interop/cats/CatsInterop.scala | 7.0 | Mixed | Code Duplication: Edited copies of one member (4 members, 7+ corresponding lines) |
| gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala | 7.0 | Mixed | Cyclomatic Complexity: PlanningSession.findFieldCandidates (cyclomatic 21) |
| gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala | 7.0 | Mixed | Cyclomatic Complexity: IntrospectionClient.typeDefinition (cyclomatic 17) |
| core/src/main/scala-2/caliban/schema/SchemaDerivation.scala | 7.1 | Mixed | Cyclomatic Complexity: CommonSchemaDerivation.join (cyclomatic 21) |
| core/src/main/scala/caliban/schema/Schema.scala | 7.1 | Mixed | Cognitive Complexity: Schema.rename (cognitive 18) |
| core/src/main/scala/caliban/execution/Executor.scala | 7.1 | Mixed | Cyclomatic Complexity: StepReducer.reduceStep (cyclomatic 29) |
| core/src/main/scala/caliban/ws/Protocol.scala | 7.1 | Mixed | Cyclomatic Complexity: GraphQLWS.make (cyclomatic 22) |
| core/src/main/scala/caliban/validation/Validator.scala | 7.1 | Mixed | Cognitive Complexity: Validator.collectAllDirectives (cognitive 41) |
| core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala | 7.1 | Mixed | Cognitive Complexity: ValueJsoniter.decodeInputValue (cognitive 24) |
| core/src/main/scala/caliban/parsing/parsers/Parsers.scala | 7.1 | Mixed | God Classes: TooManyMethods: Parsers |
| tools/src/main/scala/caliban/tools/SchemaComparison.scala | 7.1 | Mixed | Code Duplication: Edited copies of one member (3 members, 12+ corresponding lines) |
| codegen/src/main/scala/caliban/codegen/ClientWriter.scala | 7.2 | Mixed | Cyclomatic Complexity: ClientWriter.write (cyclomatic 147) |
| core/src/main/scala/caliban/parsing/VariablesCoercer.scala | 7.2 | Mixed | Cyclomatic Complexity: VariablesCoercer.coerceValues (cyclomatic 32) |
| core/src/main/scala/caliban/validation/SchemaValidator.scala | 7.2 | Mixed | Cyclomatic Complexity: SchemaValidator.validateObject (cyclomatic 28) |
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 52 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 — 52 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, 270 of 317 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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 (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 220 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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.
- 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.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — 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. `core/src/main/scala-3/caliban/schema/ArgBuilderDerivation.scala`, `core/src/main/scala-3/caliban/schema/ArgBuilderInstances.scala`, `core/src/main/scala-3/caliban/schema/DerivationUtils.scala`, `core/src/main/scala-3/caliban/schema/SchemaDerivation.scala`, `core/src/main/scala-3/caliban/schema/SchemaVersionSpecific.scala`, … (+8 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX2 Stateful singletons — 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. Those languages run requests on shared-memory threads, so a shared instance mutated without a lock is the same defect this card counts in C#, Java, Kotlin, Python, Go, Swift, Scala, Ruby and F#, but their singleton shapes are not read yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
- 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. Render strategy: boot via DockerCompose (apollo-compatibility/docker-compose.yaml). compose up failed (exit 17 — an image could not be built) — resolve : lstat apollo-compatibility/apollo-compatibility: no such file or directory; runtime evidence skipped.
- C1 Data Protection — 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 personal data 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 personal data controls.
- 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
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.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClientWriter.write at 147. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being __DirectiveLocation.toDirectiveLocation at 20 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/src/main/scala/caliban/introspection/adt/__DirectiveLocation.scala (__DirectiveLocation.toDirectiveLocation at 20), core/src/main/scala/caliban/parsing/parsers/Parsers.scala (Parsers.directiveLocation at 20), core/src/main/scala/caliban/tools/RemoteSchema.scala (Converter.toDirectiveLocation at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ClientWriter.write (cyclomatic 147), SchemaWriter.write (cyclomatic 71), VariablesCoercer.coerceValues (cyclomatic 32). — 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 3 together lifts Cyclomatic Complexity from 5.8 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
72 method(s) exceeded the cognitive complexity threshold of 15; the worst was ClientWriter.write at 196.
What to do
- Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with ClientWriter.write (cognitive 196), RemoteSubscription.openWebSocket (cognitive 159). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 4.9 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with OperationPlanner.scala, Parsers.scala, Validator.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with OperationPlanner.scala, Validator.scala, Schema.scala. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
25 duplicated block group(s) detected. 4.4 % of the production lines (1,901 of 42,794) are in a reported copy. A further 47 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 13 of the 72 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 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with ArgBuilderDerivation.scala, Renderer.scala, Parsers.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with Parsers.scala (2), package.scala, NodeResolver.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SchemaDerivation.scala, __Type.scala, VariablesCoercer.scala. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
29 production modules (npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 4 module(s) off the main sequence, with abstractness counted on 24 of the 29 (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 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
4 of 40 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with OperationCost.scala, ComplexQueryBenchmark.scala, FragmentsQueryBenchmark.scala. — One of this dimension's main actionable groups (4 warning-level).
D12 · Dependency Hygiene
28 outdated direct sbt declarations. 50 of 51 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 49 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 4 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 3 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. 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 sbt dependencies and nothing else. The repository also declares package.json, 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
Top hotspots: core/src/main/scala/caliban/validation/SchemaValidator.scala (5×28=140); core/src/main/scala/caliban/execution/Field.scala (4×21=84); gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala (3×17=51)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with SchemaValidator.scala, Field.scala, OperationPlanner.scala. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
45 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala. Counted over 181 of the 385 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 42794 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 DocumentRenderer.scala. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 35 document(s) read across 3 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.sbt. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
3 naming inconsistencies among 47 declarations measured against a convention their peers follow.
What to do
- Resolve the 2 `ConnectHTTP` spells `HTTP` where 32 names in the project spell it… finding(s) in Naming Consistency — start with ConnectHTTP.scala, FederationDirectivesV2_10.scala. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 `ExtraZioEffectOps` spells `Zio` where 12 names in the project spell it… finding(s) in Naming Consistency — start with MonixInterop.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
28 finding(s): 0 critical, 28 high, 0 medium, 0 low. 11 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 20 file(s) — `core/src/main/scala-3/caliban/schema/ArgBuilderInstances.scala`, `core/src/main/scala-3/caliban/schema/DerivationUtils.scala`, `core/src/main/scala-3/caliban/schema/SchemaDerivation.scala`, `core/src/main/scala-3/caliban/schema/macros/Macros.scala`, `core/src/main/scala/caliban/tools/RemoteSchema.scala`, … (+15 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). — One of this dimension's main actionable groups (16 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 11 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 (11 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 1 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
34 of 181 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/main/scala/caliban/wrappers/CostEstimation.scala. Counted over 181 of the 385 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with CostEstimation.scala, Caching.scala, ReportSchemaErrorCode.scala. — One of this dimension's main actionable groups (34 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: AkkaHttpAdapter.scala↔PlayAdapter.scala 55%; CatsInterop.scala↔MonixInterop.scala 53%; AkkaHttpAdapter.scala↔Http4sAdapter.scala 50%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with AkkaHttpAdapter.scala (2), CatsInterop.scala, GraphQLRequest.scala. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `client-laminext/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — client-laminext/package.json:6
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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. — benchmarks/src/main/scala/caliban/ComplexQueryBenchmark.scala
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
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: adapters/quick/src/main/scala/caliban/QuickAdapter.scala:71 — `Server.serve`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: adapters/quick/src/main/scala/caliban/QuickAdapter.scala:71 — `Server.serve`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
- No build over this repository's 355 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (7 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — resolve : lstat apollo-compatibility/apollo-compatibility: no such file or directory; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data 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 personal data 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.
- 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 Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) 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 Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) 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 Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~45947 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- 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 Scala 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 .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 795 value object(s); 17 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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, JavaScript/TypeScript 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.
- 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
- 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
- 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 Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- 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
- X23 Unguarded diagnostic materialisation — 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
- X25 Inert configuration knob — 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 198 finding(s)
- Edited copy of a member (10 corresponding lines) core/src/main/scala-3/caliban/schema/ArgBuilderDerivation.scala:43
- Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/rendering/Renderer.scala:67
- Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala:70
- Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala:225
- Edited copy of a member (10 corresponding lines) core/src/main/scala/caliban/relay/PaginationArgs.scala:16
- Edited copy of a member (10 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala:265
- TooManyMethods: PlanningSession gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:57
- TooManyMethods: Parsers core/src/main/scala/caliban/parsing/parsers/Parsers.scala:18
- TooManyMethods: Validator core/src/main/scala/caliban/validation/Validator.scala:28
- TooManyMethods: GenericSchema core/src/main/scala/caliban/schema/Schema.scala:175
- Change coupling: AkkaHttpAdapter.scala ↔ PlayAdapter.scala adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:1
- Change coupling: CatsInterop.scala ↔ MonixInterop.scala interop/cats/src/main/scala/caliban/interop/cats/CatsInterop.scala:1
- Change coupling: AkkaHttpAdapter.scala ↔ Http4sAdapter.scala adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:1
- Change coupling: GraphQLRequest.scala ↔ GraphQLResponse.scala core/src/main/scala/caliban/GraphQLRequest.scala:1
- Edited copy of a member (9 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/package.scala:190
- Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala:142
- Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala:99
- Edited copy of a member (9 corresponding lines) core/src/main/scala/caliban/relay/NodeResolver.scala:29
- Duplicated block (7 lines × 2) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:202
- Duplicated block (7 lines × 2) core/src/main/scala/caliban/introspection/adt/__Type.scala:82
- Duplicated block (7 lines × 2) core/src/main/scala/caliban/parsing/VariablesCoercer.scala:113
- Duplicated block (7 lines × 2) core/src/main/scala/caliban/wrappers/Wrappers.scala:104
- Off the main sequence: macros
- Off the main sequence: client
- Off the main sequence: core
- Off the main sequence: quickAdapter
- Low cohesion: OperationCost (LCOM4 6) gateway/src/main/scala/caliban/gateway/internal/planning/OperationCost.scala:19
- Low cohesion: ComplexQueryBenchmark (LCOM4 4) benchmarks/src/main/scala/caliban/ComplexQueryBenchmark.scala:14
- Low cohesion: FragmentsQueryBenchmark (LCOM4 4) benchmarks/src/main/scala/caliban/FragmentsQueryBenchmark.scala:14
- Low cohesion: SimpleQueryBenchmark (LCOM4 4) benchmarks/src/main/scala/caliban/SimpleQueryBenchmark.scala:14
- JavaScript dependencies are not locked client-laminext/package.json:6
- JavaScript dependencies are not locked examples/src/main/resources/gateway/package.json:11
- JavaScript dependencies are not locked examples/src/main/resources/gateway_v2/package.json:12
- JavaScript dependencies are not locked vuepress/package.json:2
- Hotspot: core/src/main/scala/caliban/validation/SchemaValidator.scala core/src/main/scala/caliban/validation/SchemaValidator.scala:334
- Hotspot: core/src/main/scala/caliban/execution/Field.scala core/src/main/scala/caliban/execution/Field.scala:203
- Hotspot: gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:64
- FileTooLong: planning/OperationPlanner.scala gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala
- FileTooLong: validation/Validator.scala core/src/main/scala/caliban/validation/Validator.scala
- FileTooLong: schema/Schema.scala core/src/main/scala/caliban/schema/Schema.scala
- Edited copy of a member (11 corresponding lines) adapters/http4s/src/main/scala/caliban/Http4sAdapter.scala:105
- Edited copy of a member (11 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/HttpInterpreter.scala:91
- Edited copy of a member (11 corresponding lines) core/src/main/scala/caliban/introspection/adt/__Field.scala:21
- Edited copy of a member (13 corresponding lines) core/src/main/scala/caliban/schema/Schema.scala:775
- Edited copy of a member (13 corresponding lines) examples/src/main/scala/example/federation/EpisodeService.scala:19
- Edited copy of a member (13 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala:206
- Duplicated block (5 lines × 2) core/src/main/scala/caliban/ws/Protocol.scala:135
- Duplicated block (5 lines × 2) core/src/main/scala/caliban/wrappers/CostEstimation.scala:187
- Duplicated block (5 lines × 2) tools/src/main/scala/caliban/tools/SchemaComparison.scala:207
- REDACTED
- REDACTED
- Edited copy of a member (14 corresponding lines) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala:32
- Edited copy of a member (14 corresponding lines) core/src/main/scala/caliban/Incremental.scala:26
- Edited copy of a member (20 corresponding lines) core/src/main/scala/caliban/validation/SchemaValidator.scala:480
- Edited copy of a member (20 corresponding lines) examples/src/main/scala/example/interop/cats/ContextualCatsInterop.scala:48
- Edited copy of a member (7 corresponding lines) interop/cats/src/main/scala/caliban/interop/cats/InjectEnv.scala:142
- Edited copy of a member (7 corresponding lines) core/src/main/scala/caliban/execution/Fragment.scala:11
- Edited copy of a member (6 corresponding lines) interop/tapir/src/main/scala/caliban/interop/tapir/TapirAdapter.scala:222
- Edited copy of a member (6 corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala:268
- Edited copy of a member (8 corresponding lines) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:71
- Edited copy of a member (8 corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala:80
- Edited copy of a member (17 corresponding lines) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:43
- Edited copy of a member (17 corresponding lines) examples/src/main/scala/example/http4s/AuthExampleApp.scala:55
- ClientWriter.write (cyclomatic 147) codegen/src/main/scala/caliban/codegen/ClientWriter.scala:17
- SchemaWriter.write (cyclomatic 71) codegen/src/main/scala/caliban/codegen/SchemaWriter.scala:14
- VariablesCoercer.coerceValues (cyclomatic 32) core/src/main/scala/caliban/parsing/VariablesCoercer.scala:153
- StepReducer.reduceStep (cyclomatic 29) core/src/main/scala/caliban/execution/Executor.scala:183
- ReducedStepExecutor.makeQuery (cyclomatic 29) core/src/main/scala/caliban/execution/Executor.scala:423
- SchemaValidator.validateObject (cyclomatic 28) core/src/main/scala/caliban/validation/SchemaValidator.scala:334
- RemoteSubscription.openWebSocket (cyclomatic 25) gateway/src/main/scala/caliban/gateway/internal/execution/RemoteSubscription.scala:88
- GraphQLWS.make (cyclomatic 22) core/src/main/scala/caliban/ws/Protocol.scala:75
- WebSocketHooks.++ (cyclomatic 22) core/src/main/scala/caliban/ws/WebSocketHooks.scala:15
- CommonSchemaDerivation.join (cyclomatic 21) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:52
- Field.apply (cyclomatic 21) core/src/main/scala/caliban/execution/Field.scala:203
- PlanningSession.findFieldCandidates (cyclomatic 21) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:567
- CommonSchemaDerivation.split (cyclomatic 20) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:147
- Legacy.make (cyclomatic 18) core/src/main/scala/caliban/ws/Protocol.scala:231
- Completer.completeValue (cyclomatic 18) gateway/src/main/scala/caliban/gateway/internal/execution/ResponseCompletion.scala:66
- QuickRequestHandler.buildResponse (cyclomatic 17) adapters/quick/src/main/scala/caliban/QuickRequestHandler.scala:199
- IntrospectionClient.typeDefinition (cyclomatic 17) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:48
- RemoteSchemaAcquisition.withinGraphQLDepth (cyclomatic 17) gateway/src/main/scala/caliban/gateway/internal/acquisition/RemoteSchemaAcquisition.scala:199
- SseDecoder.feed (cyclomatic 17) gateway/src/main/scala/caliban/gateway/internal/execution/RemoteSubscription.scala:228
- PlanningSession.plan (cyclomatic 17) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:64
- ValueValidator.validateType (cyclomatic 16) core/src/main/scala/caliban/validation/ValueValidator.scala:45
- ContextCompilation.compile (cyclomatic 16) gateway/src/main/scala/caliban/gateway/internal/composition/ContextCompilation.scala:15
- FederationCompilation.federationDirectiveNames (cyclomatic 16) gateway/src/main/scala/caliban/gateway/internal/composition/FederationCompilation.scala:138
- TodoComment core/src/main/scala/caliban/rendering/DocumentRenderer.scala:376
- ClientWriter.write (cognitive 196) codegen/src/main/scala/caliban/codegen/ClientWriter.scala:17
- RemoteSubscription.openWebSocket (cognitive 159) gateway/src/main/scala/caliban/gateway/internal/execution/RemoteSubscription.scala:88
- SchemaWriter.write (cognitive 89) codegen/src/main/scala/caliban/codegen/SchemaWriter.scala:14
- GraphQLWS.make (cognitive 79) core/src/main/scala/caliban/ws/Protocol.scala:75
- Legacy.make (cognitive 67) core/src/main/scala/caliban/ws/Protocol.scala:231
- ContextCompilation.compile (cognitive 67) gateway/src/main/scala/caliban/gateway/internal/composition/ContextCompilation.scala:15
- PlanningSession.plan (cognitive 67) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:64
- IntrospectionClient.typeDefinition (cognitive 66) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:48
- SchemaValidator.validateSchema (cognitive 45) core/src/main/scala/caliban/validation/SchemaValidator.scala:69
- Field.apply (cognitive 44) core/src/main/scala/caliban/execution/Field.scala:203
- ConflictFinder.validateSelectionSets (cognitive 41) core/src/main/scala/caliban/validation/FragmentValidator.scala:325
- Validator.collectAllDirectives (cognitive 41) core/src/main/scala/caliban/validation/Validator.scala:223
- CommonSchemaDerivation.join (cognitive 40) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:52
- StepReducer.reduceStep (cognitive 40) core/src/main/scala/caliban/execution/Executor.scala:183
- VariablesCoercer.coerceValues (cognitive 40) core/src/main/scala/caliban/parsing/VariablesCoercer.scala:153
- SseDecoder.feed (cognitive 40) gateway/src/main/scala/caliban/gateway/internal/execution/RemoteSubscription.scala:228
- SchemaValidator.validateObject (cognitive 39) core/src/main/scala/caliban/validation/SchemaValidator.scala:334
- PlanningSession.findFieldCandidates (cognitive 36) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:567
- QuickRequestHandler.transformUploadRequest (cognitive 34) adapters/quick/src/main/scala/caliban/QuickRequestHandler.scala:142
- CommonSchemaDerivation.split (cognitive 34) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:147
- ReducedStepExecutor.makeQuery (cognitive 33) core/src/main/scala/caliban/execution/Executor.scala:423
- Completer.completeValue (cognitive 29) gateway/src/main/scala/caliban/gateway/internal/execution/ResponseCompletion.scala:66
- FederationCompilation.federationDirectiveNames (cognitive 28) gateway/src/main/scala/caliban/gateway/internal/composition/FederationCompilation.scala:138
- GraphQLResponse.fromResponseValue (cognitive 27) core/src/main/scala/caliban/GraphQLResponse.scala:55
- ValueValidator.validateType (cognitive 26) core/src/main/scala/caliban/validation/ValueValidator.scala:45
- RemoteSchemaAcquisition.withinGraphQLDepth (cognitive 26) gateway/src/main/scala/caliban/gateway/internal/acquisition/RemoteSchemaAcquisition.scala:199
- CalibanSourceGenerator.apply (cognitive 25) codegen-sbt/src/main/scala/caliban/codegen/sbt/CalibanSourceGenerator.scala:66
- __Value.decodeJsonValue (cognitive 24) client/src/main/scala/caliban/client/__Value.scala:110
- Codegen.generate (cognitive 24) codegen/src/main/scala/caliban/codegen/Codegen.scala:18
- ValueJsoniter.decodeInputValue (cognitive 24) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala:120
- ValueJsoniter.decodeResponseValue (cognitive 24) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala:166
- FetchGraphOptimizer.addFetchDependencies (cognitive 24) gateway/src/main/scala/caliban/gateway/internal/planning/FetchGraphOptimizer.scala:81
- Field.coerceArgument (cognitive 23) core/src/main/scala/caliban/execution/Field.scala:452
- RemoteSubgraphExecutor.execute (cognitive 23) gateway/src/main/scala/caliban/gateway/internal/execution/RemoteSubgraphExecutor.scala:35
- ConflictFinder.collectConflictsBetween (cognitive 22) core/src/main/scala/caliban/validation/FragmentValidator.scala:201
- SubscriptionControl.register (cognitive 22) gateway/src/main/scala/caliban/gateway/internal/SubscriptionControl.scala:45
- CostCompilation.listSize (cognitive 22) gateway/src/main/scala/caliban/gateway/internal/composition/CostCompilation.scala:41
- QuickRequestHandler.transformHttpRequest (cognitive 21) adapters/quick/src/main/scala/caliban/QuickRequestHandler.scala:89
- ArgBuilderInstances.map (cognitive 21) core/src/main/scala/caliban/schema/ArgBuilder.scala:247
- RemoteSchema.mergeSchemaDeclarations (cognitive 21) core/src/main/scala/caliban/tools/RemoteSchema.scala:114
- OperationPreparation.buildCacheEntry (cognitive 21) gateway/src/main/scala/caliban/gateway/internal/OperationPreparation.scala:80
- IntrospectionClient.decode (cognitive 21) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:33
- IntrospectionClient.field (cognitive 21) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:70
- IntrospectionClient.inputValue (cognitive 21) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:80
- IntrospectionClient.directive (cognitive 21) gateway/src/main/scala/caliban/gateway/internal/acquisition/IntrospectionClient.scala:99
- HttpUploadInterpreter.serverEndpoint (cognitive 21) interop/tapir/src/main/scala/caliban/interop/tapir/HttpUploadInterpreter.scala:29
- ChoiceOf.fromGraphQL (cognitive 20) client/src/main/scala/caliban/client/FieldBuilder.scala:55
- RemoteSchemaAcquisition.fetchData (cognitive 20) gateway/src/main/scala/caliban/gateway/internal/acquisition/RemoteSchemaAcquisition.scala:41
- SelectionBuilder.decode (cognitive 19) client/src/main/scala/caliban/client/SelectionBuilder.scala:71
- VariablesCoercer.coerceVariablesUnsafe (cognitive 19) core/src/main/scala/caliban/parsing/VariablesCoercer.scala:31
- Types.collectTypes (cognitive 19) core/src/main/scala/caliban/schema/Types.scala:142
- ApolloTracing.apolloTracingOverall (cognitive 19) core/src/main/scala/caliban/wrappers/ApolloTracing.scala:129
- Gateway.buildInterpreter (cognitive 19) gateway/src/main/scala/caliban/gateway/Gateway.scala:103
- QuickRequestHandler.buildResponse (cognitive 18) adapters/quick/src/main/scala/caliban/QuickRequestHandler.scala:199
- Schema.rename (cognitive 18) core/src/main/scala/caliban/schema/Schema.scala:116
- SchemaComposer.prepare (cognitive 18) gateway/src/main/scala/caliban/gateway/internal/composition/SchemaComposer.scala:33
- TypeComposition.mergeOutputType (cognitive 18) gateway/src/main/scala/caliban/gateway/internal/composition/TypeComposition.scala:400
- PlanExecutor.resolveFragment (cognitive 18) gateway/src/main/scala/caliban/gateway/internal/execution/PlanExecutor.scala:112
- tapir.toGraphQL (cognitive 18) interop/tapir/src/main/scala/caliban/interop/tapir/package.scala:73
- Field.collectFields (cognitive 17) core/src/main/scala/caliban/execution/Field.scala:73
- Types.unify (cognitive 17) core/src/main/scala/caliban/schema/Types.scala:215
- Validator.collectVariablesUsed (cognitive 17) core/src/main/scala/caliban/validation/Validator.scala:153
- ValueValidator.validateScalar (cognitive 17) core/src/main/scala/caliban/validation/ValueValidator.scala:146
- SupergraphDecomposition.projectType (cognitive 17) gateway/src/main/scala/caliban/gateway/internal/composition/SupergraphDecomposition.scala:427
- EntityExecutor.prepareGroup (cognitive 17) gateway/src/main/scala/caliban/gateway/internal/execution/EntityExecutor.scala:95
- whitespace.loop (cognitive 16) core/src/main/scala/caliban/parsing/parsers/StringParsers.scala:29
- ConflictFinder.collectConflictsBetweenFragments (cognitive 16) core/src/main/scala/caliban/validation/FragmentValidator.scala:248
- Validator.validateVariables (cognitive 16) core/src/main/scala/caliban/validation/Validator.scala:362
- RemoteTransport.withinJsonDepth (cognitive 16) gateway/src/main/scala/caliban/gateway/internal/RemoteTransport.scala:22
- SupergraphDecomposition.contextArguments (cognitive 16) gateway/src/main/scala/caliban/gateway/internal/composition/SupergraphDecomposition.scala:120
- PlanningSession.planFieldCandidates (cognitive 16) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:480
- PlanningSession.planEntityFetch (cognitive 16) gateway/src/main/scala/caliban/gateway/internal/planning/OperationPlanner.scala:835
- REDACTED
- REDACTED
- Members sharing a duplicated core (8 members, 50+ identical tokens) client/src/main/scala/caliban/client/Zippable.scala:136
- Edited copies of one member (3 members, 54+ corresponding lines) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:145
- Edited copy of a member (39 corresponding lines) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala:121
- Edited copy of a member (21 corresponding lines) core/src/main/scala/caliban/introspection/adt/__DirectiveLocation.scala:8
- Edited copy of a member (19 corresponding lines) core/src/main/scala/caliban/wrappers/ApolloTracing.scala:156
- Edited copies of one member (5 members, 13+ corresponding lines) federation/src/main/scala/caliban/federation/EntityResolver.scala:25
- Edited copies of one member (6 members, 6+ corresponding lines) core/src/main/scala/caliban/schema/Schema.scala:569
- Edited copies of one member (4 members, 12+ corresponding lines) core/src/main/scala/caliban/wrappers/CostEstimation.scala:185
- Edited copies of one member (8 members, 3+ corresponding lines) client/src/main/scala/caliban/client/SelectionBuilder.scala:273
- Edited copies of one member (4 members, 7+ corresponding lines) interop/cats/src/main/scala/caliban/interop/cats/CatsInterop.scala:183
- Edited copies of one member (3 members, 6+ corresponding lines) core/src/main/scala/caliban/schema/Schema.scala:420
- Edited copies of one member (7 members, 7+ corresponding lines) core/src/main/scala/caliban/GraphQL.scala:188
- Edited copy of a member (3 corresponding lines) core/src/main/scala/caliban/parsing/parsers/Parsers.scala:128
- Edited copies of one member (3 members, 13+ corresponding lines) core/src/main/scala/caliban/rendering/DocumentRenderer.scala:494
- Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/caliban/CalibanError.scala:81
- Edited copy of a member (4 corresponding lines) core/src/main/scala/caliban/relay/RelaySupport.scala:104
- Duplicated block (47–48 lines × 3) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:152
- Duplicated block (35 lines × 3) codegen/src/main/scala/caliban/codegen/ClientWriter.scala:325
- Duplicated block (27 lines × 3) adapters/akka-http/src/main/scala/caliban/AkkaHttpAdapter.scala:92
- Duplicated block (25 lines × 2) core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:224
- Duplicated block (19–20 lines × 2) core/src/main/scala/caliban/introspection/adt/__DirectiveLocation.scala:9
- Duplicated block (16 lines × 7) client/src/main/scala/caliban/client/Zippable.scala:169
- Duplicated block (15 lines × 8) client/src/main/scala/caliban/client/Zippable.scala:142
- Duplicated block (13 lines × 2) core/src/main/scala/caliban/interop/jsoniter/jsoniter.scala:121
- Duplicated block (11 lines × 2) core/src/main/scala/caliban/Incremental.scala:29
- Duplicated block (10 lines × 2) core/src/main/scala-2/caliban/schema/ArgBuilderDerivation.scala:46
- Duplicated block (7–10 lines × 2) core/src/main/scala/caliban/execution/Executor.scala:65
- Duplicated block (8 lines × 2) federation/src/main/scala/caliban/federation/EntityResolver.scala:25
- Duplicated block (6 lines × 2) gateway/src/main/scala/caliban/gateway/internal/composition/SchemaMapping.scala:166
- Duplicated block (6 lines × 3) core/src/main/scala/caliban/relay/NodeResolver.scala:56
- Duplicated block (7 lines × 3) codegen/src/main/scala/caliban/codegen/ClientWriter.scala:901
- Edited copy of a member (44 corresponding lines) examples/src/main/scala/example/federation/CharacterService.scala:37
- Edited copy of a member (29 corresponding lines) examples/src/main/scala/example/interop/cats/ContextualCatsInterop.scala:75
- Edited copies of one member (3 members, 12+ corresponding lines) tools/src/main/scala/caliban/tools/SchemaComparison.scala:64
- Duplicated block (27 lines × 2) examples/src/main/scala/example/federation/CharacterService.scala:49
- Duplicated block (8–10 lines × 3) examples/src/main/scala/example/ExampleService.scala:28
- Duplicated block (2–7 lines × 3) examples/src/main/scala/example/ExampleService.scala:25
Minor — 62 finding(s)
- Orphaned file core/src/main/scala/caliban/wrappers/CostEstimation.scala:1
- Orphaned file core/src/main/scala/caliban/wrappers/Caching.scala:1
- Orphaned file reporting/src/main/scala/caliban/reporting/client/ReportSchemaErrorCode.scala:1
- Orphaned file adapters/pekko-http/src/main/scala/caliban/PekkoHttpAdapter.scala:1
- Orphaned file benchmarks/src/main/scala/caliban/execution/NestedZQueryBenchmarkSchema.scala:1
- Orphaned file codegen-sbt/src/main/scala/caliban/codegen/sbt/CalibanSourceGenerator.scala:1
- Orphaned file client/src/main/scala/caliban/client/__Value.scala:1
- Orphaned file benchmarks/src/main/scala/caliban/execution/NestedZQueryBenchmark.scala:1
- Orphaned file adapters/quick/src/main/scala/caliban/quick/package.scala:1
- Orphaned file core/src/main/scala/caliban/wrappers/FieldMetrics.scala:1
- Orphaned file interop/cats/src/main/scala/caliban/interop/cats/InjectEnv.scala:1
- Orphaned file core/src/main/scala-3/caliban/schema/macros/Macros.scala:1
- Orphaned file core/src/main/scala/caliban/rendering/ValueRenderer.scala:1
- Orphaned file core/src/main/scala/caliban/ws/WebSocketHooks.scala:1
- Orphaned file federation/src/main/scala/caliban/federation/FederationSupport.scala:1
- Orphaned file interop/cats/src/main/scala/caliban/interop/cats/ToEffect.scala:1
- Orphaned file interop/cats/src/main/scala/caliban/interop/cats/FromEffect.scala:1
- Orphaned file reporting/src/main/scala/caliban/reporting/SchemaReporter.scala:1
- Orphaned file core/src/main/scala/caliban/relay/RelaySupport.scala:1
- Orphaned file apollo-compatibility/src/main/scala/ProductSchema.scala:1
- Orphaned file benchmarks/src/main/scala/caliban/validation/ValidationBenchmark.scala:1
- Orphaned file codegen-sbt/src/main/scala/caliban/codegen/sbt/OptionsParser.scala:1
- Orphaned file federation/src/main/scala/caliban/federation/v2x/FederationV2.scala:1
- Orphaned file core/src/main/scala/caliban/relay/NodeResolver.scala:1
- Orphaned file apollo-compatibility/src/main/scala/services/ProductService.scala:1
- Duplicated predicate core/src/main/scala/caliban/validation/Validator.scala:896
- Duplicated predicate core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:229
- Duplicated predicate core/src/main/scala/caliban/rendering/DocumentRenderer.scala:931
- Duplicated predicate codegen/src/main/scala/caliban/codegen/ClientWriter.scala:903
- Duplicated predicate core/src/main/scala-2/caliban/schema/SchemaDerivation.scala:165
- Duplicated predicate codegen/src/main/scala/caliban/codegen/ClientWriter.scala:317
- `ConnectHTTP` spells `HTTP` where 32 names in the project spell it `Http` federation/src/main/scala/caliban/federation/connect/ConnectHTTP.scala:3
- `ConnectHTTP` spells `HTTP` where 32 names in the project spell it `Http` federation/src/main/scala/caliban/federation/v2x/FederationDirectivesV2_10.scala:31
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found build.sbt:81
- `ExtraZioEffectOps` spells `Zio` where 12 names in the project spell it `ZIO` interop/monix/src/main/scala/caliban/interop/monix/MonixInterop.scala:38
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation client-laminext/package.json:6
- No rollback/health safety
- No changelog
- Benchmarks don't track allocations benchmarks/src/main/scala/caliban/ComplexQueryBenchmark.scala
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Scala's null is not held to the type system everywhere
Minor — 28 finding(s)
- Outdated: com.softwaremill.sttp.client3:core_2.13
- Outdated: com.softwaremill.sttp.client3:zio_2.13
- Outdated: com.softwaremill.sttp.client4:core_2.13
- Outdated: com.softwaremill.sttp.client4:zio_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-akka-http-server_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-core_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-http4s-server-zio_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-jsoniter-scala_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-pekko-http-server_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-play-server_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-swagger-ui-bundle_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-zio-http-server_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-zio_2.13
- Outdated: com.typesafe.akka:akka-actor-typed_2.13
- Outdated: com.typesafe.akka:akka-http_2.13
- Outdated: com.typesafe.akka:akka-serialization-jackson_2.13
- Outdated: dev.zio:zio-config-magnolia_2.13
- Outdated: dev.zio:zio-config_2.13
- Outdated: dev.zio:zio-json_2.13
- Outdated: dev.zio:zio-opentelemetry_2.13
- Outdated: io.github.valdemargr:gql-server_2.13
- Outdated: io.monix:monix_2.13
- Outdated: org.apache.pekko:pekko-http_2.13
- Outdated: org.http4s:http4s-dsl_2.13
- Outdated: org.http4s:http4s-ember-server_2.13
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-87387134c8604b468b2a0aa845289409/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-87387134c8604b468b2a0aa845289409/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 . | 28 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| 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 13 file(s) — `core/src/main/scala-3/caliban/schema/ArgBuilderDerivation.scala`, `core/src/main/scala-3/caliban/schema/ArgBuilderInstances.scala`, `core/src/main/scala-3/caliban/schema/DerivationUtils.scala`, `core/src/main/scala-3/caliban/schema/SchemaDerivation.scala`, `core/src/main/scala-3/caliban/schema/SchemaVersionSpecific.scala`, … (+8 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |