Executive summary
cequence-io/openai-scala-client falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 58 out of 100 and is rated Adequate, and 13 of its 15 critical findings are security problems in the build pipeline.
Code Health, at 53, is the weakest lens and counts most in the score. The best first steps are declaring which values may be missing and writing log messages as searchable templates, each worth about 4 points. Raising Code Health to 70 would lift the score to about 63.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, limiting the secret to its own step and making the hidden dependencies explicit would close these risks.
The product code is 89,323 lines, about €150,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Code Health rose from 53 to 70, the lowest score rated Strong, the score would rise from 58 to about 63.
New since the last survey: 17 findings
- Cyclomatic Complexity · RetryEngine.run (cyclomatic 32) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala
- Cyclomatic Complexity · impl.toVertexAIContents (cyclomatic 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- Cyclomatic Complexity · JsonSchemaShape.toJsonSchema (cyclomatic 16) openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala
- Cyclomatic Complexity · OpenAIResponsesChatCompletionService.convertMessages (cyclomatic 16) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala
- Cognitive Complexity · RetryEngine.run (cognitive 38) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala
- Cognitive Complexity · impl.toVertexAIContents (cognitive 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- God Classes · MethodTooLong: RetryEngine.run openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala
- God Classes · TooManyMethods: ChatCompletionSettingsConversions openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala
- Code Duplication · Duplicated block (15–18 lines × 2) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala
- Code Duplication · Duplicated block (12–15 lines × 2) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/OpenAIVertexAIChatCompletionService.scala
- Code Duplication · Duplicated block (10 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala
- Code Duplication · Near-duplicate member pair (81 shared lines) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala
- Code Duplication · Duplicated block (25–26 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala
- Churn × Complexity Hotspots · Hotspot: google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- Churn × Complexity Hotspots · Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala
- Change Coupling · Boundary-crossing change coupling: NonOpenAIModelId.scala ↔ DecisionProviderSettings.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/NonOpenAIModelId.scala
- Exception handling · Swallowed exception (caught, then discarded) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala
Fixed since the last survey: 10 findings
- Cyclomatic Complexity · JsonFormats.jsonSchemaWrites (cyclomatic 17) openai-core/src/main/scala/io/cequence/openaiscala/JsonFormats.scala
- Cyclomatic Complexity · impl.toNonSystemVertexAI (cyclomatic 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- Cognitive Complexity · ChatCompletionBodyMaker.handleJsonSchema (cognitive 18) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala
- Cognitive Complexity · impl.toNonSystemVertexAI (cognitive 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- Cognitive Complexity · JsonFormats.jsonSchemaWrites (cognitive 16) openai-core/src/main/scala/io/cequence/openaiscala/JsonFormats.scala
- Code Duplication · Duplicated block (24–25 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala
- Code Duplication · Duplicated block (11 lines × 2) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/OpenAIVertexAIChatCompletionService.scala
- Code Duplication · Duplicated block (9 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala
- Code Duplication · Near-duplicate member pair (59 shared lines) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala
- Cohesion (LCOM4) · Low cohesion: OpenAIAnthropicChatCompletionService (LCOM4 5) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala
Rebuild cost: about €150,000 · Estimate
| Cost to rebuild | €49,000 to €250,000, for 818 to 2,594 hours of work, about 1.0 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: 89,323 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 RetryHelpers | 2 typesafe.domain | 3 vertexai.domain | 4 domain.response | 5 domain.responsesapi.tools.mcp | 6 gemini.domain.response | 7 gemini.domain.settings | 8 domain.settings | 9 gemini.domain | 10 domain | 11 domain.guardrails | 12 perplexity.domain.agent | 13 anthropic.domain.skills | 14 anthropic.domain.tools | 15 domain.Batch | 16 domain.graders | 17 domain.responsesapi.tools | 18 io.cequence.openaiscala | 19 anthropic.domain.managedagents | 20 domain.responsesapi | 21 anthropic.domain.settings | 22 domain.agents | 23 domain.decisions | 24 anthropic.domain | 25 service.adapter | 26 service.impl | 27 anthropic.domain.Content | 28 service | 29 anthropic.domain.Content.ContentBlock | 30 gemini.service.impl | 31 perplexity.service | 32 service.OpenAIStreamedServiceImplicits | 33 typesafe.service | 34 vertexai.service | 35 anthropic.domain.response | 36 perplexity.service.impl | 37 typesafe.service.impl | 38 vertexai.service.impl | 39 anthropic.service | 40 anthropic.service.impl |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 RetryHelpers | ||||||||||||||||||||||||||||||||||||||||
| 2 typesafe.domain | ||||||||||||||||||||||||||||||||||||||||
| 3 vertexai.domain | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.response | 18 | |||||||||||||||||||||||||||||||||||||||
| 5 domain.responsesapi.tools.mcp | 2 | 8 | ||||||||||||||||||||||||||||||||||||||
| 6 gemini.domain.response | 7 | |||||||||||||||||||||||||||||||||||||||
| 7 gemini.domain.settings | 7 | |||||||||||||||||||||||||||||||||||||||
| 8 domain.settings | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 gemini.domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 domain | 7 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 domain.guardrails | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 perplexity.domain.agent | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 anthropic.domain.skills | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 anthropic.domain.tools | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 domain.Batch | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 domain.graders | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 domain.responsesapi.tools | 11 | 2 | 26 | |||||||||||||||||||||||||||||||||||||
| 18 io.cequence.openaiscala | 1 | 52 | 9 | 59 | 2 | 6 | ||||||||||||||||||||||||||||||||||
| 19 anthropic.domain.managedagents | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 domain.responsesapi | 1 | 2 | 11 | |||||||||||||||||||||||||||||||||||||
| 21 anthropic.domain.settings | 3 | 5 | 20 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 domain.agents | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 23 domain.decisions | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 anthropic.domain | 10 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 service.adapter | 1 | 60 | 1 | 34 | 74 | 6 | 5 | 1 | 3 | 2 | 11 | 17 | 4 | 41 | ||||||||||||||||||||||||||
| 26 service.impl | 22 | 23 | 34 | 5 | 1 | 2 | 9 | 18 | 4 | 18 | ||||||||||||||||||||||||||||||
| 27 anthropic.domain.Content | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 28 service | 1 | 38 | 29 | 46 | 5 | 1 | 1 | 10 | 19 | 4 | 1 | 1 | ||||||||||||||||||||||||||||
| 29 anthropic.domain.Content.ContentBlock | 1 | 7 | 17 | |||||||||||||||||||||||||||||||||||||
| 30 gemini.service.impl | 1 | 5 | 1 | 1 | 10 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 perplexity.service | 7 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 service.OpenAIStreamedServiceImplicits | 6 | 4 | 6 | 4 | 5 | 4 | 17 | |||||||||||||||||||||||||||||||||
| 33 typesafe.service | 1 | 10 | 1 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 34 vertexai.service | 4 | 1 | 2 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 anthropic.domain.response | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 perplexity.service.impl | 4 | 3 | 3 | 7 | 8 | 3 | 7 | 2 | ||||||||||||||||||||||||||||||||
| 37 typesafe.service.impl | 19 | 1 | 1 | 1 | 22 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 38 vertexai.service.impl | 1 | 5 | 1 | 6 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 39 anthropic.service | 4 | 2 | 2 | 7 | 1 | 30 | 18 | 14 | 3 | 1 | 7 | |||||||||||||||||||||||||||||
| 40 anthropic.service.impl | 9 | 3 | 10 | 14 | 2 | 51 | 33 | 30 | 3 | 6 | 10 | 4 |
4→10 domain.response uses domain part of a loop✕
- Connections
- 18 pairs of types, where a type in domain.response uses a type in domain.
- The types involved
io.cequence.openaiscala.domain.response.AssembledChatCompletion→io.cequence.openaiscala.domain.AssistantToolMessageio.cequence.openaiscala.domain.response.AssembledChatCompletion→io.cequence.openaiscala.domain.ToolCallio.cequence.openaiscala.domain.response.Assistant→io.cequence.openaiscala.domain.AssistantToolio.cequence.openaiscala.domain.response.ChatCompletionChoiceInfo→io.cequence.openaiscala.domain.AssistantMessageio.cequence.openaiscala.domain.response.ChatCompletionChoiceInfo→io.cequence.openaiscala.domain.ReasoningMessageio.cequence.openaiscala.domain.response.ChatCompletionResponse→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.domain.response.ChatCompletionResponse→io.cequence.openaiscala.domain.ReasoningMessageio.cequence.openaiscala.domain.response.ChatFunCompletionChoiceInfo→io.cequence.openaiscala.domain.AssistantFunMessageio.cequence.openaiscala.domain.response.ChatToolCompletionChoiceInfo→io.cequence.openaiscala.domain.AssistantToolMessageio.cequence.openaiscala.domain.response.ChatToolCompletionChoiceInfo→io.cequence.openaiscala.domain.ReasoningMessageio.cequence.openaiscala.domain.response.ChatToolCompletionResponse→io.cequence.openaiscala.domain.AssistantToolMessageio.cequence.openaiscala.domain.response.ChatToolCompletionResponse→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.domain.response.ChatToolCompletionResponse→io.cequence.openaiscala.domain.ReasoningMessageio.cequence.openaiscala.domain.response.ChatWebSearchCompletionChoiceInfo→io.cequence.openaiscala.domain.AssistantWebSearchMessageio.cequence.openaiscala.domain.response.ChatWebSearchCompletionResponse→io.cequence.openaiscala.domain.Annotationio.cequence.openaiscala.domain.response.ChunkMessageSpec→io.cequence.openaiscala.domain.ChatRoleio.cequence.openaiscala.domain.response.ChunkMessageSpec→io.cequence.openaiscala.domain.ToolCallChunkSpecio.cequence.openaiscala.domain.response.RunResponse→io.cequence.openaiscala.domain.Run
- Direction
- domain.response uses domain, so a change to domain can break domain.response, while a change to domain.response can't break domain.
- 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→17 domain.responsesapi.tools.mcp uses domain.responsesapi.tools part of a loop✕
- Connections
- 2 pairs of types, where a type in domain.responsesapi.tools.mcp uses a type in domain.responsesapi.tools.
- The types involved
io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPTool→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolCall→io.cequence.openaiscala.domain.responsesapi.tools.ToolCall
- Direction
- domain.responsesapi.tools.mcp uses domain.responsesapi.tools, so a change to domain.responsesapi.tools can break domain.responsesapi.tools.mcp, while a change to domain.responsesapi.tools.mcp can't break domain.responsesapi.tools.
- 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→20 domain.responsesapi.tools.mcp uses domain.responsesapi part of a loop✕
- Connections
- 8 pairs of types, where a type in domain.responsesapi.tools.mcp uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPApprovalRequest→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPApprovalRequest→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPApprovalResponse→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPListTools→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPListTools→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolCall→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolCall→io.cequence.openaiscala.domain.responsesapi.Output
- Direction
- domain.responsesapi.tools.mcp uses domain.responsesapi, so a change to domain.responsesapi can break domain.responsesapi.tools.mcp, while a change to domain.responsesapi.tools.mcp can't break domain.responsesapi.
- 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→9 gemini.domain.response uses gemini.domain part of a loop✕
- Connections
- 7 pairs of types, where a type in gemini.domain.response uses a type in gemini.domain.
- The types involved
io.cequence.openaiscala.gemini.domain.response.Candidate→io.cequence.openaiscala.gemini.domain.Contentio.cequence.openaiscala.gemini.domain.response.GroundingAttribution→io.cequence.openaiscala.gemini.domain.Contentio.cequence.openaiscala.gemini.domain.response.ListCachedContentsResponse→io.cequence.openaiscala.gemini.domain.CachedContentio.cequence.openaiscala.gemini.domain.response.ListModelsResponse→io.cequence.openaiscala.gemini.domain.Modelio.cequence.openaiscala.gemini.domain.response.ModalityTokenCount→io.cequence.openaiscala.gemini.domain.Modalityio.cequence.openaiscala.gemini.domain.response.SafetyRating→io.cequence.openaiscala.gemini.domain.HarmCategoryio.cequence.openaiscala.gemini.domain.response.SafetyRating→io.cequence.openaiscala.gemini.domain.HarmProbability
- Direction
- gemini.domain.response uses gemini.domain, so a change to gemini.domain can break gemini.domain.response, while a change to gemini.domain.response can't break gemini.domain.
- 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→9 gemini.domain.settings uses gemini.domain part of a loop✕
- Connections
- 7 pairs of types, where a type in gemini.domain.settings uses a type in gemini.domain.
- The types involved
io.cequence.openaiscala.gemini.domain.settings.GenerateContentSettings→io.cequence.openaiscala.gemini.domain.Contentio.cequence.openaiscala.gemini.domain.settings.GenerateContentSettings→io.cequence.openaiscala.gemini.domain.Toolio.cequence.openaiscala.gemini.domain.settings.GenerationConfig→io.cequence.openaiscala.gemini.domain.Modalityio.cequence.openaiscala.gemini.domain.settings.GenerationConfig→io.cequence.openaiscala.gemini.domain.Schemaio.cequence.openaiscala.gemini.domain.settings.SafetySetting→io.cequence.openaiscala.gemini.domain.HarmBlockThresholdio.cequence.openaiscala.gemini.domain.settings.SafetySetting→io.cequence.openaiscala.gemini.domain.HarmCategoryio.cequence.openaiscala.gemini.domain.settings.ThinkingConfig→io.cequence.openaiscala.gemini.domain.ThinkingLevel
- Direction
- gemini.domain.settings uses gemini.domain, so a change to gemini.domain can break gemini.domain.settings, while a change to gemini.domain.settings can't break gemini.domain.
- 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→4 domain.settings uses domain.response✕
- Connections
- 2 pairs of types, where a type in domain.settings uses a type in domain.response.
- The types involved
io.cequence.openaiscala.domain.settings.CreateRunSettings→io.cequence.openaiscala.domain.response.ResponseFormatio.cequence.openaiscala.domain.settings.CreateThreadAndRunSettings→io.cequence.openaiscala.domain.response.ResponseFormat
- Direction
- domain.settings uses domain.response, so a change to domain.response can break domain.settings, while a change to domain.settings can't break domain.response.
- Position
- Below the diagonal: domain.settings uses a module listed above it, which is the healthy direction.
8→18 domain.settings uses io.cequence.openaiscala part of a loop✕
- Connections
- 2 pairs of types, where a type in domain.settings uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.domain.settings.ResponsesChatCompletionSettingsOps→io.cequence.openaiscala.OpenAIScalaClientExceptionio.cequence.openaiscala.domain.settings.ToolApprovalSettingsOps→io.cequence.openaiscala.OpenAIScalaClientException
- Direction
- domain.settings uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break domain.settings, while a change to domain.settings can't break io.cequence.openaiscala.
- 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→6 gemini.domain uses gemini.domain.response✕
- Connections
- 1 pair of types, where a type in gemini.domain uses a type in gemini.domain.response.
- The types involved
io.cequence.openaiscala.gemini.domain.BatchInlinedResponse→io.cequence.openaiscala.gemini.domain.response.GenerateContentResponse
- Direction
- gemini.domain uses gemini.domain.response, so a change to gemini.domain.response can break gemini.domain, while a change to gemini.domain can't break gemini.domain.response.
- Position
- Below the diagonal: gemini.domain uses a module listed above it, which is the healthy direction.
9→7 gemini.domain uses gemini.domain.settings✕
- Connections
- 1 pair of types, where a type in gemini.domain uses a type in gemini.domain.settings.
- The types involved
io.cequence.openaiscala.gemini.domain.CachedContent→io.cequence.openaiscala.gemini.domain.settings.ToolConfig
- Direction
- gemini.domain uses gemini.domain.settings, so a change to gemini.domain.settings can break gemini.domain, while a change to gemini.domain can't break gemini.domain.settings.
- Position
- Below the diagonal: gemini.domain uses a module listed above it, which is the healthy direction.
10→4 domain uses domain.response✕
- Connections
- 7 pairs of types, where a type in domain uses a type in domain.response.
- The types involved
io.cequence.openaiscala.domain.ChatCompletionBatchResultItem→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.domain.ChatCompletionBatchTypedResultItem→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.domain.ChatCompletionInterceptData→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.domain.Run→io.cequence.openaiscala.domain.response.UsageInfoio.cequence.openaiscala.domain.RunStep→io.cequence.openaiscala.domain.response.UsageInfoio.cequence.openaiscala.domain.Thread→io.cequence.openaiscala.domain.response.AssistantToolResourceResponseio.cequence.openaiscala.domain.responsesapi→io.cequence.openaiscala.domain.response.TracedBlock
- Direction
- domain uses domain.response, so a change to domain.response can break domain, while a change to domain can't break domain.response.
- Position
- Below the diagonal: domain uses a module listed above it, which is the healthy direction.
10→8 domain uses domain.settings✕
- Connections
- 2 pairs of types, where a type in domain uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.domain.ChatCompletionErrorInterceptData→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.domain.ChatCompletionInterceptData→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- domain uses domain.settings, so a change to domain.settings can break domain, while a change to domain can't break domain.settings.
- Position
- Below the diagonal: domain uses a module listed above it, which is the healthy direction.
11→4 domain.guardrails uses domain.response✕
- Connections
- 1 pair of types, where a type in domain.guardrails uses a type in domain.response.
- The types involved
io.cequence.openaiscala.domain.guardrails.GuardrailVerdict→io.cequence.openaiscala.domain.response.UsageInfo
- Direction
- domain.guardrails uses domain.response, so a change to domain.response can break domain.guardrails, while a change to domain.guardrails can't break domain.response.
- Position
- Below the diagonal: domain.guardrails uses a module listed above it, which is the healthy direction.
11→8 domain.guardrails uses domain.settings✕
- Connections
- 2 pairs of types, where a type in domain.guardrails uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.domain.guardrails.ModelGuardrailSettings→io.cequence.openaiscala.domain.settings.ChatCompletionResponseFormatTypeio.cequence.openaiscala.domain.guardrails.ModelGuardrailSettings→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- domain.guardrails uses domain.settings, so a change to domain.settings can break domain.guardrails, while a change to domain.guardrails can't break domain.settings.
- Position
- Below the diagonal: domain.guardrails uses a module listed above it, which is the healthy direction.
12→8 perplexity.domain.agent uses domain.settings✕
- Connections
- 2 pairs of types, where a type in perplexity.domain.agent uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.perplexity.domain.agent.CreateAgentResponseSettings→io.cequence.openaiscala.domain.settings.JsonSchemaDefio.cequence.openaiscala.perplexity.domain.agent.CreateAgentResponseSettings→io.cequence.openaiscala.domain.settings.ReasoningEffort
- Direction
- perplexity.domain.agent uses domain.settings, so a change to domain.settings can break perplexity.domain.agent, while a change to perplexity.domain.agent can't break domain.settings.
- Position
- Below the diagonal: perplexity.domain.agent uses a module listed above it, which is the healthy direction.
13→10 anthropic.domain.skills uses domain✕
- Connections
- 4 pairs of types, where a type in anthropic.domain.skills uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillResponse→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.skills.DeleteSkillVersionResponse→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.skills.Skill→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.skills.SkillVersion→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.skills uses domain, so a change to domain can break anthropic.domain.skills, while a change to anthropic.domain.skills can't break domain.
- Position
- Below the diagonal: anthropic.domain.skills uses a module listed above it, which is the healthy direction.
14→10 anthropic.domain.tools uses domain✕
- Connections
- 4 pairs of types, where a type in anthropic.domain.tools uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.tools.CustomTool→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinition→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.tools.Tool→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.tools.ToolChoice→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.tools uses domain, so a change to domain can break anthropic.domain.tools, while a change to anthropic.domain.tools can't break domain.
- Position
- Below the diagonal: anthropic.domain.tools uses a module listed above it, which is the healthy direction.
14→24 anthropic.domain.tools uses anthropic.domain part of a loop✕
- Connections
- 2 pairs of types, where a type in anthropic.domain.tools uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.tools.MCPToolset→io.cequence.openaiscala.anthropic.domain.CacheControlio.cequence.openaiscala.anthropic.domain.tools.TextEditorTool→io.cequence.openaiscala.anthropic.domain.CacheControl
- Direction
- anthropic.domain.tools uses anthropic.domain, so a change to anthropic.domain can break anthropic.domain.tools, while a change to anthropic.domain.tools can't break anthropic.domain.
- 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→10 domain.Batch uses domain✕
- Connections
- 2 pairs of types, where a type in domain.Batch uses a type in domain.
- The types involved
io.cequence.openaiscala.domain.Batch.BatchRow→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.domain.Batch.BatchRowBase→io.cequence.openaiscala.domain.BaseMessage
- Direction
- domain.Batch uses domain, so a change to domain can break domain.Batch, while a change to domain.Batch can't break domain.
- Position
- Below the diagonal: domain.Batch uses a module listed above it, which is the healthy direction.
16→8 domain.graders uses domain.settings✕
- Connections
- 1 pair of types, where a type in domain.graders uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.domain.graders.SamplingParams→io.cequence.openaiscala.domain.settings.ReasoningEffort
- Direction
- domain.graders uses domain.settings, so a change to domain.settings can break domain.graders, while a change to domain.graders can't break domain.settings.
- Position
- Below the diagonal: domain.graders uses a module listed above it, which is the healthy direction.
16→10 domain.graders uses domain✕
- Connections
- 1 pair of types, where a type in domain.graders uses a type in domain.
- The types involved
io.cequence.openaiscala.domain.graders.GraderModelInput→io.cequence.openaiscala.domain.ChatRole
- Direction
- domain.graders uses domain, so a change to domain can break domain.graders, while a change to domain.graders can't break domain.
- Position
- Below the diagonal: domain.graders uses a module listed above it, which is the healthy direction.
17→5 domain.responsesapi.tools uses domain.responsesapi.tools.mcp✕
- Connections
- 11 pairs of types, where a type in domain.responsesapi.tools uses a type in domain.responsesapi.tools.mcp.
- The types involved
io.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPAllowedToolsio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPApprovalRequestio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPApprovalResponseio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPListToolsio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPRequireApprovalio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolCallio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolErrorio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolErrorContentio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolFilterio.cequence.openaiscala.domain.responsesapi.tools.JsonFormats→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPToolRef
- Direction
- domain.responsesapi.tools uses domain.responsesapi.tools.mcp, so a change to domain.responsesapi.tools.mcp can break domain.responsesapi.tools, while a change to domain.responsesapi.tools can't break domain.responsesapi.tools.mcp.
- Position
- Below the diagonal: domain.responsesapi.tools uses a module listed above it, which is the healthy direction.
17→10 domain.responsesapi.tools uses domain✕
- Connections
- 2 pairs of types, where a type in domain.responsesapi.tools uses a type in domain.
- The types involved
io.cequence.openaiscala.domain.responsesapi.tools.FunctionTool→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.domain.responsesapi.tools.Tool→io.cequence.openaiscala.domain.HasType
- Direction
- domain.responsesapi.tools uses domain, so a change to domain can break domain.responsesapi.tools, while a change to domain.responsesapi.tools can't break domain.
- Position
- Below the diagonal: domain.responsesapi.tools uses a module listed above it, which is the healthy direction.
17→20 domain.responsesapi.tools uses domain.responsesapi part of a loop✕
- Connections
- 26 pairs of types, where a type in domain.responsesapi.tools uses a type in domain.responsesapi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.domain.responsesapi.tools.CodeInterpreterToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.CodeInterpreterToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.ComputerToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.ComputerToolCall→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.ComputerToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.ComputerToolCallOutput→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.ComputerToolCallOutput→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.CustomToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.CustomToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.CustomToolCallOutput→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.FileSearchToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.FileSearchToolCall→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.FileSearchToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCall→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCallOutput→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCallOutput→io.cequence.openaiscala.domain.responsesapi.ModelStatusio.cequence.openaiscala.domain.responsesapi.tools.ImageGenerationToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.ImageGenerationToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.LocalShellToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.LocalShellToolCall→io.cequence.openaiscala.domain.responsesapi.Outputio.cequence.openaiscala.domain.responsesapi.tools.LocalShellToolCallOutput→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.WebSearchToolCall→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.domain.responsesapi.tools.WebSearchToolCall→io.cequence.openaiscala.domain.responsesapi.ModelStatus
- Direction
- domain.responsesapi.tools uses domain.responsesapi, so a change to domain.responsesapi can break domain.responsesapi.tools, while a change to domain.responsesapi.tools can't break domain.responsesapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 io.cequence.openaiscala uses RetryHelpers✕
- Connections
- 1 pair of types, where a type in io.cequence.openaiscala uses a type in RetryHelpers.
- The types involved
io.cequence.openaiscala.RetryHelpers→io.cequence.openaiscala.RetryHelpers.RetrySettings
- Direction
- io.cequence.openaiscala uses RetryHelpers, so a change to RetryHelpers can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break RetryHelpers.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
18→4 io.cequence.openaiscala uses domain.response✕
- Connections
- 52 pairs of types, where a type in io.cequence.openaiscala uses a type in domain.response. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.Assistantio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.AssistantToolResourceResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.BatchErrorio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.BatchResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatCompletionBatchResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatCompletionChoiceChunkInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatCompletionChoiceInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatFunCompletionChoiceInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatFunCompletionResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatToolCompletionChoiceInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatWebSearchCompletionChoiceInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChatWebSearchCompletionResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.ChunkMessageSpecio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.CompletionTokenDetailsio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.CreateBatchResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.CreateBatchResponsesio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.EmbeddingBatchResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.EmbeddingInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.EmbeddingResponseio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.EmbeddingUsageInfoio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.response.FileInfo
- Direction
- io.cequence.openaiscala uses domain.response, so a change to domain.response can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break domain.response.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
18→8 io.cequence.openaiscala uses domain.settings✕
- Connections
- 9 pairs of types, where a type in io.cequence.openaiscala uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.ApproximateLocationio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.ChatCompletionResponseFormatTypeio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.JsonSchemaDefio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.ReasoningEffortio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.SearchContextSizeio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.ServiceTierio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.UserLocationio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.Verbosityio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.settings.WebSearchOptions
- Direction
- io.cequence.openaiscala uses domain.settings, so a change to domain.settings can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break domain.settings.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
18→10 io.cequence.openaiscala uses domain✕
- Connections
- 59 pairs of types, where a type in io.cequence.openaiscala uses a type in domain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Annotationio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantFunMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantToolio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantToolMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantToolOutputio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantToolResourceio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.AssistantWebSearchMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Attachmentio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.ChatRoleio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.ChunkingStrategyio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Contentio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.DeveloperMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FileAnnotationio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FileAnnotationTypeio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FileCitationio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FileCountsio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FileIdio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FunMessageio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FunctionCallChunkSpecio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.FunctionCallSpecio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.JsonType
- Direction
- io.cequence.openaiscala uses domain, so a change to domain can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break domain.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
18→11 io.cequence.openaiscala uses domain.guardrails✕
- Connections
- 2 pairs of types, where a type in io.cequence.openaiscala uses a type in domain.guardrails.
- The types involved
io.cequence.openaiscala.OpenAIScalaGuardrailException→io.cequence.openaiscala.domain.guardrails.GuardrailStageio.cequence.openaiscala.OpenAIScalaGuardrailException→io.cequence.openaiscala.domain.guardrails.GuardrailVerdict
- Direction
- io.cequence.openaiscala uses domain.guardrails, so a change to domain.guardrails can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break domain.guardrails.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
18→15 io.cequence.openaiscala uses domain.Batch✕
- Connections
- 6 pairs of types, where a type in io.cequence.openaiscala uses a type in domain.Batch.
- The types involved
io.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.Batchio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.BatchEndpointio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.BatchProcessingErrorio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.BatchProcessingErrorsio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.BatchRowio.cequence.openaiscala.JsonFormats→io.cequence.openaiscala.domain.Batch.CompletionWindow
- Direction
- io.cequence.openaiscala uses domain.Batch, so a change to domain.Batch can break io.cequence.openaiscala, while a change to io.cequence.openaiscala can't break domain.Batch.
- Position
- Below the diagonal: io.cequence.openaiscala uses a module listed above it, which is the healthy direction.
19→10 anthropic.domain.managedagents uses domain✕
- Connections
- 1 pair of types, where a type in anthropic.domain.managedagents uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.managedagents.AgentTool→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.managedagents uses domain, so a change to domain can break anthropic.domain.managedagents, while a change to anthropic.domain.managedagents can't break domain.
- Position
- Below the diagonal: anthropic.domain.managedagents uses a module listed above it, which is the healthy direction.
19→13 anthropic.domain.managedagents uses anthropic.domain.skills✕
- Connections
- 1 pair of types, where a type in anthropic.domain.managedagents uses a type in anthropic.domain.skills.
- The types involved
io.cequence.openaiscala.anthropic.domain.managedagents.Agent→io.cequence.openaiscala.anthropic.domain.skills.SkillParams
- Direction
- anthropic.domain.managedagents uses anthropic.domain.skills, so a change to anthropic.domain.skills can break anthropic.domain.managedagents, while a change to anthropic.domain.managedagents can't break anthropic.domain.skills.
- Position
- Below the diagonal: anthropic.domain.managedagents uses a module listed above it, which is the healthy direction.
19→14 anthropic.domain.managedagents uses anthropic.domain.tools✕
- Connections
- 2 pairs of types, where a type in anthropic.domain.managedagents uses a type in anthropic.domain.tools.
- The types involved
io.cequence.openaiscala.anthropic.domain.managedagents.Agent→io.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinitionio.cequence.openaiscala.anthropic.domain.managedagents.SessionAgentOverride→io.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinition
- Direction
- anthropic.domain.managedagents uses anthropic.domain.tools, so a change to anthropic.domain.tools can break anthropic.domain.managedagents, while a change to anthropic.domain.managedagents can't break anthropic.domain.tools.
- Position
- Below the diagonal: anthropic.domain.managedagents uses a module listed above it, which is the healthy direction.
19→21 anthropic.domain.managedagents uses anthropic.domain.settings part of a loop✕
- Connections
- 1 pair of types, where a type in anthropic.domain.managedagents uses a type in anthropic.domain.settings.
- The types involved
io.cequence.openaiscala.anthropic.domain.managedagents.AgentModelConfig→io.cequence.openaiscala.anthropic.domain.settings.Speed
- Direction
- anthropic.domain.managedagents uses anthropic.domain.settings, so a change to anthropic.domain.settings can break anthropic.domain.managedagents, while a change to anthropic.domain.managedagents can't break anthropic.domain.settings.
- 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→8 domain.responsesapi uses domain.settings✕
- Connections
- 1 pair of types, where a type in domain.responsesapi uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.domain.responsesapi.ReasoningConfig→io.cequence.openaiscala.domain.settings.ReasoningEffort
- Direction
- domain.responsesapi uses domain.settings, so a change to domain.settings can break domain.responsesapi, while a change to domain.responsesapi can't break domain.settings.
- Position
- Below the diagonal: domain.responsesapi uses a module listed above it, which is the healthy direction.
20→10 domain.responsesapi uses domain✕
- Connections
- 2 pairs of types, where a type in domain.responsesapi uses a type in domain.
- The types involved
io.cequence.openaiscala.domain.responsesapi.JsonFormats→io.cequence.openaiscala.domain.FileCitationio.cequence.openaiscala.domain.responsesapi.JsonFormats→io.cequence.openaiscala.domain.UrlCitation
- Direction
- domain.responsesapi uses domain, so a change to domain can break domain.responsesapi, while a change to domain.responsesapi can't break domain.
- Position
- Below the diagonal: domain.responsesapi uses a module listed above it, which is the healthy direction.
20→17 domain.responsesapi uses domain.responsesapi.tools✕
- Connections
- 11 pairs of types, where a type in domain.responsesapi uses a type in domain.responsesapi.tools.
- The types involved
io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettings→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettings→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoiceio.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsAuxPart2→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsAuxPart2→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoiceio.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettings→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettings→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoiceio.cequence.openaiscala.domain.responsesapi.Response→io.cequence.openaiscala.domain.responsesapi.tools.FunctionToolCallio.cequence.openaiscala.domain.responsesapi.Response→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.Response→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoiceio.cequence.openaiscala.domain.responsesapi.ResponseSettings→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.domain.responsesapi.ResponseSettings→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoice
- Direction
- domain.responsesapi uses domain.responsesapi.tools, so a change to domain.responsesapi.tools can break domain.responsesapi, while a change to domain.responsesapi can't break domain.responsesapi.tools.
- Position
- Below the diagonal: domain.responsesapi uses a module listed above it, which is the healthy direction.
21→13 anthropic.domain.settings uses anthropic.domain.skills✕
- Connections
- 3 pairs of types, where a type in anthropic.domain.settings uses a type in anthropic.domain.skills.
- The types involved
io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettings→io.cequence.openaiscala.anthropic.domain.skills.SkillParamsio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings→io.cequence.openaiscala.anthropic.domain.skills.Containerio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings→io.cequence.openaiscala.anthropic.domain.skills.SkillParams
- Direction
- anthropic.domain.settings uses anthropic.domain.skills, so a change to anthropic.domain.skills can break anthropic.domain.settings, while a change to anthropic.domain.settings can't break anthropic.domain.skills.
- Position
- Below the diagonal: anthropic.domain.settings uses a module listed above it, which is the healthy direction.
21→14 anthropic.domain.settings uses anthropic.domain.tools✕
- Connections
- 5 pairs of types, where a type in anthropic.domain.settings uses a type in anthropic.domain.tools.
- The types involved
io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettings→io.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinitionio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings→io.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinitionio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings→io.cequence.openaiscala.anthropic.domain.tools.Toolio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings→io.cequence.openaiscala.anthropic.domain.tools.ToolChoiceio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings→io.cequence.openaiscala.anthropic.domain.tools.MCPServerURLDefinition
- Direction
- anthropic.domain.settings uses anthropic.domain.tools, so a change to anthropic.domain.tools can break anthropic.domain.settings, while a change to anthropic.domain.settings can't break anthropic.domain.tools.
- Position
- Below the diagonal: anthropic.domain.settings uses a module listed above it, which is the healthy direction.
21→19 anthropic.domain.settings uses anthropic.domain.managedagents✕
- Connections
- 20 pairs of types, where a type in anthropic.domain.settings uses a type in anthropic.domain.managedagents.
- The types involved
io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.AgentModelConfigio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.AgentToolio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.Multiagentio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateCredentialSettings→io.cequence.openaiscala.anthropic.domain.managedagents.CredentialAuthio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.DeploymentInitialEventio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.Scheduleio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.SessionResourceio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateEnvironmentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentConfigio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateEnvironmentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentScopeio.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateSessionSettings→io.cequence.openaiscala.anthropic.domain.managedagents.SessionResourceio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.AgentModelConfigio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.AgentToolio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.Multiagentio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateCredentialSettings→io.cequence.openaiscala.anthropic.domain.managedagents.CredentialAuthUpdateio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.DeploymentInitialEventio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.Scheduleio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateDeploymentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.SessionResourceio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateEnvironmentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentConfigio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateEnvironmentSettings→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentScopeio.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateSessionSettings→io.cequence.openaiscala.anthropic.domain.managedagents.SessionAgentOverride
- Direction
- anthropic.domain.settings uses anthropic.domain.managedagents, so a change to anthropic.domain.managedagents can break anthropic.domain.settings, while a change to anthropic.domain.settings can't break anthropic.domain.managedagents.
- Position
- Below the diagonal: anthropic.domain.settings uses a module listed above it, which is the healthy direction.
21→24 anthropic.domain.settings uses anthropic.domain part of a loop✕
- Connections
- 2 pairs of types, where a type in anthropic.domain.settings uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings→io.cequence.openaiscala.anthropic.domain.OutputFormatio.cequence.openaiscala.anthropic.domain.settings.OutputConfig→io.cequence.openaiscala.anthropic.domain.OutputFormat
- Direction
- anthropic.domain.settings uses anthropic.domain, so a change to anthropic.domain can break anthropic.domain.settings, while a change to anthropic.domain.settings can't break anthropic.domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→8 domain.agents uses domain.settings✕
- Connections
- 4 pairs of types, where a type in domain.agents uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.domain.agents.AgentConfig→io.cequence.openaiscala.domain.settings.ServiceTierio.cequence.openaiscala.domain.agents.AgentReasoning→io.cequence.openaiscala.domain.settings.ReasoningEffortio.cequence.openaiscala.domain.agents.CreateAgentSettings→io.cequence.openaiscala.domain.settings.ServiceTierio.cequence.openaiscala.domain.agents.UpdateAgentSettings→io.cequence.openaiscala.domain.settings.ServiceTier
- Direction
- domain.agents uses domain.settings, so a change to domain.settings can break domain.agents, while a change to domain.agents can't break domain.settings.
- Position
- Below the diagonal: domain.agents uses a module listed above it, which is the healthy direction.
22→20 domain.agents uses domain.responsesapi✕
- Connections
- 4 pairs of types, where a type in domain.agents uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.domain.agents.Agent→io.cequence.openaiscala.domain.responsesapi.MultiAgentConfigio.cequence.openaiscala.domain.agents.AgentConfig→io.cequence.openaiscala.domain.responsesapi.MultiAgentConfigio.cequence.openaiscala.domain.agents.CreateAgentSettings→io.cequence.openaiscala.domain.responsesapi.MultiAgentConfigio.cequence.openaiscala.domain.agents.UpdateAgentSettings→io.cequence.openaiscala.domain.responsesapi.MultiAgentConfig
- Direction
- domain.agents uses domain.responsesapi, so a change to domain.responsesapi can break domain.agents, while a change to domain.agents can't break domain.responsesapi.
- Position
- Below the diagonal: domain.agents uses a module listed above it, which is the healthy direction.
23→20 domain.decisions uses domain.responsesapi✕
- Connections
- 1 pair of types, where a type in domain.decisions uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.domain.decisions.Decision→io.cequence.openaiscala.domain.responsesapi.UsageInfo
- Direction
- domain.decisions uses domain.responsesapi, so a change to domain.responsesapi can break domain.decisions, while a change to domain.decisions can't break domain.responsesapi.
- Position
- Below the diagonal: domain.decisions uses a module listed above it, which is the healthy direction.
24→10 anthropic.domain uses domain✕
- Connections
- 10 pairs of types, where a type in anthropic.domain uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.BashCodeExecutionToolResultContent→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.CodeExecutionToolResultContent→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.FileDeleteResponse→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.FileMetadata→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.MCPToolResultItem→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.MessageBatch→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.MessageBatchDeleteResponse→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.OutputFormat→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.TextEditorCodeExecutionToolResultContent→io.cequence.openaiscala.domain.HasTypeio.cequence.openaiscala.anthropic.domain.WebFetchToolResultContent→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain uses domain, so a change to domain can break anthropic.domain, while a change to anthropic.domain can't break domain.
- Position
- Below the diagonal: anthropic.domain uses a module listed above it, which is the healthy direction.
24→21 anthropic.domain uses anthropic.domain.settings✕
- Connections
- 1 pair of types, where a type in anthropic.domain uses a type in anthropic.domain.settings.
- The types involved
io.cequence.openaiscala.anthropic.domain.MessageBatchRequest→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettings
- Direction
- anthropic.domain uses anthropic.domain.settings, so a change to anthropic.domain.settings can break anthropic.domain, while a change to anthropic.domain can't break anthropic.domain.settings.
- Position
- Below the diagonal: anthropic.domain uses a module listed above it, which is the healthy direction.
25→1 service.adapter uses RetryHelpers✕
- Connections
- 1 pair of types, where a type in service.adapter uses a type in RetryHelpers.
- The types involved
io.cequence.openaiscala.service.adapter.ServiceAdapters→io.cequence.openaiscala.RetryHelpers.RetrySettings
- Direction
- service.adapter uses RetryHelpers, so a change to RetryHelpers can break service.adapter, while a change to service.adapter can't break RetryHelpers.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→4 service.adapter uses domain.response✕
- Connections
- 60 pairs of types, where a type in service.adapter uses a type in domain.response. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatToCompletionAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.ChatToCompletionAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.ChatToCompletionAdapter→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.adapter.DelegatedChatCompletionCloseableServiceWrapper→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.DelegatedChatCompletionCloseableServiceWrapper→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.GuardedReplies→io.cequence.openaiscala.domain.response.UsageInfoio.cequence.openaiscala.service.adapter.GuardrailsAdapter→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.adapter.GuardrailsAdapter→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.adapter.GuardrailsStreamedAdapter→io.cequence.openaiscala.domain.response.ChatChunk
- Direction
- service.adapter uses domain.response, so a change to domain.response can break service.adapter, while a change to service.adapter can't break domain.response.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→5 service.adapter uses domain.responsesapi.tools.mcp✕
- Connections
- 1 pair of types, where a type in service.adapter uses a type in domain.responsesapi.tools.mcp.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.responsesapi.tools.mcp.MCPTool
- Direction
- service.adapter uses domain.responsesapi.tools.mcp, so a change to domain.responsesapi.tools.mcp can break service.adapter, while a change to service.adapter can't break domain.responsesapi.tools.mcp.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→8 service.adapter uses domain.settings✕
- Connections
- 34 pairs of types, where a type in service.adapter uses a type in domain.settings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionSettingsConversions→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.ChatCompletionSettingsConversions→io.cequence.openaiscala.domain.settings.ReasoningEffortio.cequence.openaiscala.service.adapter.ChatToCompletionAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.DelegatedChatCompletionBatchCloseableServiceWrapper→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.DelegatedChatCompletionCloseableServiceWrapper→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.GuardrailsAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.GuardrailsStreamedAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceWrapper→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAICoreServiceWrapper→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAICoreServiceWrapper→io.cequence.openaiscala.domain.settings.CreateEmbeddingsSettingsio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionMappingExt→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.settings.CreateEditSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.settings.CreateFineTuneSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.settings.CreateImageEditSettings
- Direction
- service.adapter uses domain.settings, so a change to domain.settings can break service.adapter, while a change to service.adapter can't break domain.settings.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→10 service.adapter uses domain✕
- Connections
- 74 pairs of types, where a type in service.adapter uses a type in domain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.domain.ChatCompletionTool
- Direction
- service.adapter uses domain, so a change to domain can break service.adapter, while a change to service.adapter can't break domain.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→11 service.adapter uses domain.guardrails✕
- Connections
- 6 pairs of types, where a type in service.adapter uses a type in domain.guardrails.
- The types involved
io.cequence.openaiscala.service.adapter.GuardedReplies→io.cequence.openaiscala.domain.guardrails.GuardrailVerdictio.cequence.openaiscala.service.adapter.GuardrailRunner→io.cequence.openaiscala.domain.guardrails.GuardrailVerdictio.cequence.openaiscala.service.adapter.GuardrailsStreamedAdapter→io.cequence.openaiscala.domain.guardrails.GuardrailVerdictio.cequence.openaiscala.service.adapter.OpenAIServiceAdapters→io.cequence.openaiscala.domain.guardrails.GuardrailActionio.cequence.openaiscala.service.adapter.OpenAIServiceAdapters→io.cequence.openaiscala.domain.guardrails.GuardrailVerdictio.cequence.openaiscala.service.adapter.Violation→io.cequence.openaiscala.domain.guardrails.GuardrailVerdict
- Direction
- service.adapter uses domain.guardrails, so a change to domain.guardrails can break service.adapter, while a change to service.adapter can't break domain.guardrails.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→15 service.adapter uses domain.Batch✕
- Connections
- 5 pairs of types, where a type in service.adapter uses a type in domain.Batch.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.Batch.Batchio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.Batch.BatchEndpointio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.Batch.BatchRowio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.Batch.BatchRowBaseio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.Batch.CompletionWindow
- Direction
- service.adapter uses domain.Batch, so a change to domain.Batch can break service.adapter, while a change to service.adapter can't break domain.Batch.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→16 service.adapter uses domain.graders✕
- Connections
- 1 pair of types, where a type in service.adapter uses a type in domain.graders.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.graders.Grader
- Direction
- service.adapter uses domain.graders, so a change to domain.graders can break service.adapter, while a change to service.adapter can't break domain.graders.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→17 service.adapter uses domain.responsesapi.tools✕
- Connections
- 3 pairs of types, where a type in service.adapter uses a type in domain.responsesapi.tools.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionMappingExt→io.cequence.openaiscala.domain.responsesapi.tools.Toolio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionMappingExt→io.cequence.openaiscala.domain.responsesapi.tools.ToolChoiceio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.responsesapi.tools.Tool
- Direction
- service.adapter uses domain.responsesapi.tools, so a change to domain.responsesapi.tools can break service.adapter, while a change to service.adapter can't break domain.responsesapi.tools.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→18 service.adapter uses io.cequence.openaiscala✕
- Connections
- 2 pairs of types, where a type in service.adapter uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.service.adapter.GuardrailRunner→io.cequence.openaiscala.OpenAIScalaGuardrailExceptionio.cequence.openaiscala.service.adapter.RetryServiceAdapter→io.cequence.openaiscala.RetryHelpers
- Direction
- service.adapter uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break service.adapter, while a change to service.adapter can't break io.cequence.openaiscala.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→20 service.adapter uses domain.responsesapi✕
- Connections
- 11 pairs of types, where a type in service.adapter uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionMappingExt→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionMappingExt→io.cequence.openaiscala.domain.responsesapi.Responseio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.responsesapi.Inputio.cequence.openaiscala.service.adapter.OpenAIResponsesChatCompletionService→io.cequence.openaiscala.domain.responsesapi.Responseio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.InputItemsResponseio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.InputTokensCountio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.responsesapi.Response
- Direction
- service.adapter uses domain.responsesapi, so a change to domain.responsesapi can break service.adapter, while a change to service.adapter can't break domain.responsesapi.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→22 service.adapter uses domain.agents✕
- Connections
- 17 pairs of types, where a type in service.adapter uses a type in domain.agents.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionService→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionService→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.Agentio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentConfigio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentEnvironmentTemplateio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentSessionio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentSessionArtifactio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentSessionInputio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentSessionItemio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentSubagentio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentTurnio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentsDeletedio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.AgentsPageio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.CreateAgentSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.agents.UpdateAgentSettings
- Direction
- service.adapter uses domain.agents, so a change to domain.agents can break service.adapter, while a change to service.adapter can't break domain.agents.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→23 service.adapter uses domain.decisions✕
- Connections
- 4 pairs of types, where a type in service.adapter uses a type in domain.decisions.
- The types involved
io.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.service.adapter.OpenAIServiceWrapper→io.cequence.openaiscala.domain.decisions.DecisionQuestion
- Direction
- service.adapter uses domain.decisions, so a change to domain.decisions can break service.adapter, while a change to service.adapter can't break domain.decisions.
- Position
- Below the diagonal: service.adapter uses a module listed above it, which is the healthy direction.
25→28 service.adapter uses service part of a loop✕
- Connections
- 41 pairs of types, where a type in service.adapter uses a type in service. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.service.adapter.ChatCompletionBatchEmulationAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.service.adapter.ChatCompletionBatchServiceAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionErrorInterceptAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionInputAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.service.adapter.ChatCompletionInputBatchAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionInterceptAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionOutputAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatCompletionServiceAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.ChatToCompletionAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.DelegatedChatCompletionBatchCloseableServiceWrapper→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.service.adapter.DelegatedChatCompletionCloseableServiceWrapper→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.GuardrailsAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.GuardrailsStreamedAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.GuardrailsStreamedAdapter→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceAdaptersImpl→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceBatchExtWrapperImpl→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceExtWrapperImpl→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceRouter→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceWrapper→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceWrapperImpl→io.cequence.openaiscala.service.OpenAIChatCompletionService
- Direction
- service.adapter uses service, so a change to service can break service.adapter, while a change to service.adapter can't break service.
- 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→4 service.impl uses domain.response✕
- Connections
- 22 pairs of types, where a type in service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.domain.response.EmbeddingResponseio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.domain.response.ModelInfoio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.Assistantio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.ChatFunCompletionResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.ChatWebSearchCompletionResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.CreateBatchResponsesio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.DeleteResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.FileInfoio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.FineTuneCheckpointio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.FineTuneEventio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.FineTuneJobio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.ImageInfoio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.ModelInfoio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.ModerationResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.TextEditResponseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.response.TranscriptResponse
- Direction
- service.impl uses domain.response, so a change to domain.response can break service.impl, while a change to service.impl can't break domain.response.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→8 service.impl uses domain.settings✕
- Connections
- 23 pairs of types, where a type in service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.service.impl.ChatCompletionBodyMaker→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.impl.CompletionBodyMaker→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.domain.settings.CreateEmbeddingsSettingsio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateEditSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateFineTuneSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateImageEditSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateImageSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateModerationSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateRunSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateSpeechSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateThreadAndRunSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateTranscriptionSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.CreateTranslationSettingsio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.FileUploadPurposeio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.TranscriptResponseFormatTypeio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.settings.WebSearchOptionsio.cequence.openaiscala.service.impl.RunBodyMaker→io.cequence.openaiscala.domain.settings.CreateRunSettingsio.cequence.openaiscala.service.impl.ThreadAndRunBodyMaker→io.cequence.openaiscala.domain.settings.CreateThreadAndRunSettings
- Direction
- service.impl uses domain.settings, so a change to domain.settings can break service.impl, while a change to service.impl can't break domain.settings.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→10 service.impl uses domain✕
- Connections
- 34 pairs of types, where a type in service.impl uses a type in domain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.impl.ChatCompletionBodyMaker→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.impl.ChatCompletionBodyMaker→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.SortOrderio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.SortOrderio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.AssistantToolio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.AssistantToolOutputio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.AssistantToolResourceio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Attachmentio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChatRoleio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.ChunkingStrategyio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.FileIdio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Paginationio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Runio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.RunStepio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.SortOrderio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Thread
- Direction
- service.impl uses domain, so a change to domain can break service.impl, while a change to service.impl can't break domain.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→15 service.impl uses domain.Batch✕
- Connections
- 5 pairs of types, where a type in service.impl uses a type in domain.Batch.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Batch.Batchio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Batch.BatchEndpointio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Batch.BatchRowio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Batch.BatchRowBaseio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.domain.Batch.CompletionWindow
- Direction
- service.impl uses domain.Batch, so a change to domain.Batch can break service.impl, while a change to service.impl can't break domain.Batch.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→16 service.impl uses domain.graders✕
- Connections
- 1 pair of types, where a type in service.impl uses a type in domain.graders.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIGraderServiceImpl→io.cequence.openaiscala.domain.graders.Grader
- Direction
- service.impl uses domain.graders, so a change to domain.graders can break service.impl, while a change to service.impl can't break domain.graders.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→18 service.impl uses io.cequence.openaiscala✕
- Connections
- 2 pairs of types, where a type in service.impl uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.OpenAIScalaClientExceptionio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.OpenAIScalaClientException
- Direction
- service.impl uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break service.impl, while a change to service.impl can't break io.cequence.openaiscala.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→20 service.impl uses domain.responsesapi✕
- Connections
- 9 pairs of types, where a type in service.impl uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.responsesapi.ResponseStreamEventio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettingsio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.InputItemsResponseio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.InputTokensCountio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.domain.responsesapi.Response
- Direction
- service.impl uses domain.responsesapi, so a change to domain.responsesapi can break service.impl, while a change to service.impl can't break domain.responsesapi.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→22 service.impl uses domain.agents✕
- Connections
- 18 pairs of types, where a type in service.impl uses a type in domain.agents.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.Agentio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentConfigio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentEnvironmentTemplateio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentSessionio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentSessionArtifactio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentSessionInputio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentSessionItemio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentSubagentio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentTurnio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentsDeletedio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.AgentsPageio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettingsio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.CreateAgentSettingsio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.domain.agents.UpdateAgentSettingsio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettings
- Direction
- service.impl uses domain.agents, so a change to domain.agents can break service.impl, while a change to service.impl can't break domain.agents.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→23 service.impl uses domain.decisions✕
- Connections
- 4 pairs of types, where a type in service.impl uses a type in domain.decisions.
- The types involved
io.cequence.openaiscala.service.impl.OpenAIDecisionsServiceImpl→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.service.impl.OpenAIDecisionsServiceImpl→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.service.impl.OpenAIDecisionsServiceImpl→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.service.impl.OpenAIDecisionsServiceImpl→io.cequence.openaiscala.domain.decisions.DecisionQuestion
- Direction
- service.impl uses domain.decisions, so a change to domain.decisions can break service.impl, while a change to service.impl can't break domain.decisions.
- Position
- Below the diagonal: service.impl uses a module listed above it, which is the healthy direction.
26→28 service.impl uses service part of a loop✕
- Connections
- 18 pairs of types, where a type in service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.service.impl.ChatCompletionBodyMaker→io.cequence.openaiscala.service.ProducedReasoningio.cequence.openaiscala.service.impl.OpenAIAgentsServiceImpl→io.cequence.openaiscala.service.OpenAIAgentsServiceio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceImpl→io.cequence.openaiscala.service.ProducedReasoningio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.service.ClassifiedStreamingWSClientio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.service.HandleOpenAIErrorCodesio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.impl.OpenAIChatCompletionServiceStreamedExtraImpl→io.cequence.openaiscala.service.ProducedReasoningio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.service.HandleOpenAIErrorCodesio.cequence.openaiscala.service.impl.OpenAICoreServiceImpl→io.cequence.openaiscala.service.OpenAICoreServiceio.cequence.openaiscala.service.impl.OpenAICoreServiceStreamedExtraImpl→io.cequence.openaiscala.service.OpenAIStreamedServiceExtraio.cequence.openaiscala.service.impl.OpenAIDecisionsServiceImpl→io.cequence.openaiscala.service.OpenAIDecisionsServiceio.cequence.openaiscala.service.impl.OpenAIGraderServiceImpl→io.cequence.openaiscala.service.OpenAIGraderServiceio.cequence.openaiscala.service.impl.OpenAIResponseServiceImpl→io.cequence.openaiscala.service.OpenAIResponsesServiceio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.service.HandleOpenAIErrorCodesio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.impl.OpenAIServiceImpl→io.cequence.openaiscala.service.OpenAIServiceio.cequence.openaiscala.service.impl.OpenAIServiceWSBase→io.cequence.openaiscala.service.OpenAIServiceConsts
- Direction
- service.impl uses service, so a change to service can break service.impl, while a change to service.impl can't break service.
- 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→10 anthropic.domain.Content uses domain✕
- Connections
- 1 pair of types, where a type in anthropic.domain.Content uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.Content.ContentBlock→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.Content uses domain, so a change to domain can break anthropic.domain.Content, while a change to anthropic.domain.Content can't break domain.
- Position
- Below the diagonal: anthropic.domain.Content uses a module listed above it, which is the healthy direction.
27→24 anthropic.domain.Content uses anthropic.domain✕
- Connections
- 7 pairs of types, where a type in anthropic.domain.Content uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.Content.ContentBlockBase→io.cequence.openaiscala.anthropic.domain.CacheControlio.cequence.openaiscala.anthropic.domain.Content.ContentBlockBase→io.cequence.openaiscala.anthropic.domain.Cacheableio.cequence.openaiscala.anthropic.domain.Content.ContentBlockBase→io.cequence.openaiscala.anthropic.domain.Contentio.cequence.openaiscala.anthropic.domain.Content.ContentBlocks→io.cequence.openaiscala.anthropic.domain.Contentio.cequence.openaiscala.anthropic.domain.Content.SingleString→io.cequence.openaiscala.anthropic.domain.CacheControlio.cequence.openaiscala.anthropic.domain.Content.SingleString→io.cequence.openaiscala.anthropic.domain.Cacheableio.cequence.openaiscala.anthropic.domain.Content.SingleString→io.cequence.openaiscala.anthropic.domain.Content
- Direction
- anthropic.domain.Content uses anthropic.domain, so a change to anthropic.domain can break anthropic.domain.Content, while a change to anthropic.domain.Content can't break anthropic.domain.
- Position
- Below the diagonal: anthropic.domain.Content uses a module listed above it, which is the healthy direction.
28→1 service uses RetryHelpers✕
- Connections
- 1 pair of types, where a type in service uses a type in RetryHelpers.
- The types involved
io.cequence.openaiscala.service.FailoverChain→io.cequence.openaiscala.RetryHelpers.RetrySettings
- Direction
- service uses RetryHelpers, so a change to RetryHelpers can break service, while a change to service can't break RetryHelpers.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→4 service uses domain.response✕
- Connections
- 38 pairs of types, where a type in service uses a type in domain.response. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.AttemptWrapper→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.ChatChunks→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.ChatChunks→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.service.FailoverChain→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.OpenAIChatCompletionExtra→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.OpenAIChatCompletionIOConversionAdapter→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.OpenAIChatCompletionIOConversionAdapter→io.cequence.openaiscala.domain.response.ChunkMessageSpecio.cequence.openaiscala.service.OpenAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.OpenAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.service.OpenAIChatCompletionStreamedOutputConversionAdapter→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.OpenAIChatCompletionStreamedOutputConversionAdapter→io.cequence.openaiscala.domain.response.ChunkMessageSpecio.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.service.OpenAICompletionService→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.response.EmbeddingResponseio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.response.ModelInfoio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.Assistantio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.ChatFunCompletionResponseio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.ChatWebSearchCompletionResponseio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.CreateBatchResponsesio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.DeleteResponseio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.FileInfoio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.response.FineTuneCheckpoint
- Direction
- service uses domain.response, so a change to domain.response can break service, while a change to service can't break domain.response.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→8 service uses domain.settings✕
- Connections
- 29 pairs of types, where a type in service uses a type in domain.settings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.InferredJsonSchema→io.cequence.openaiscala.domain.settings.JsonSchemaDefio.cequence.openaiscala.service.OpenAIChatCompletionBatchService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIChatCompletionExtra→io.cequence.openaiscala.domain.settings.ChatCompletionResponseFormatTypeio.cequence.openaiscala.service.OpenAIChatCompletionExtra→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIChatCompletionIOConversionAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIChatCompletionStreamedConversionAdapter→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAICompletionService→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.settings.CreateEmbeddingsSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateEditSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateFineTuneSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateImageEditSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateImageSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateModerationSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateRunSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateSpeechSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateThreadAndRunSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateTranscriptionSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.CreateTranslationSettingsio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.settings.FileUploadPurpose
- Direction
- service uses domain.settings, so a change to domain.settings can break service, while a change to service can't break domain.settings.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→10 service uses domain✕
- Connections
- 46 pairs of types, where a type in service uses a type in domain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.service.FunctionCallOpenAISerializer→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.service.IOpenAIChatCompletionServiceFactory→io.cequence.openaiscala.domain.ProviderSettingsio.cequence.openaiscala.service.JsonSchemaOf→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.service.JsonSchemaReflectionHelper→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.SortOrderio.cequence.openaiscala.service.OpenAIChatCompletionBatchService→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.service.OpenAIChatCompletionBatchService→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.service.OpenAIChatCompletionBatchService→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.service.OpenAIChatCompletionExtra→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIChatCompletionExtra→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.service.OpenAIChatCompletionIOConversionAdapter→io.cequence.openaiscala.domain.AssistantMessageio.cequence.openaiscala.service.OpenAIChatCompletionIOConversionAdapter→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIChatCompletionService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.OpenAICoreService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAICountTokensHelper→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.SortOrderio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.AssistantToolio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.AssistantToolOutputio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.AssistantToolResourceio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Attachmentio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.ChatCompletionTool
- Direction
- service uses domain, so a change to domain can break service, while a change to service can't break domain.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→15 service uses domain.Batch✕
- Connections
- 5 pairs of types, where a type in service uses a type in domain.Batch.
- The types involved
io.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Batch.Batchio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Batch.BatchEndpointio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Batch.BatchRowio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Batch.BatchRowBaseio.cequence.openaiscala.service.OpenAIService→io.cequence.openaiscala.domain.Batch.CompletionWindow
- Direction
- service uses domain.Batch, so a change to domain.Batch can break service, while a change to service can't break domain.Batch.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→16 service uses domain.graders✕
- Connections
- 1 pair of types, where a type in service uses a type in domain.graders.
- The types involved
io.cequence.openaiscala.service.OpenAIGraderService→io.cequence.openaiscala.domain.graders.Grader
- Direction
- service uses domain.graders, so a change to domain.graders can break service, while a change to service can't break domain.graders.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→18 service uses io.cequence.openaiscala✕
- Connections
- 1 pair of types, where a type in service uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.service.OpenAIErrorCodes→io.cequence.openaiscala.OpenAIScalaClientException
- Direction
- service uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break service, while a change to service can't break io.cequence.openaiscala.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→20 service uses domain.responsesapi✕
- Connections
- 10 pairs of types, where a type in service uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.service.ChatChunks→io.cequence.openaiscala.domain.responsesapi.ResponseStreamEventio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettingsio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.InputItemsResponseio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.InputTokensCountio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.OpenAIResponsesService→io.cequence.openaiscala.domain.responsesapi.Responseio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.responsesapi.ResponseStreamEvent
- Direction
- service uses domain.responsesapi, so a change to domain.responsesapi can break service, while a change to service can't break domain.responsesapi.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→22 service uses domain.agents✕
- Connections
- 19 pairs of types, where a type in service uses a type in domain.agents.
- The types involved
io.cequence.openaiscala.service.AgentSessionEvents→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.Agentio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentConfigio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentEnvironmentTemplateio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentSessionio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentSessionArtifactio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentSessionInputio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentSessionItemio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentSubagentio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentTurnio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentsDeletedio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.AgentsPageio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettingsio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.CreateAgentSettingsio.cequence.openaiscala.service.OpenAIAgentsService→io.cequence.openaiscala.domain.agents.UpdateAgentSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.service.OpenAIStreamedServiceExtra→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettings
- Direction
- service uses domain.agents, so a change to domain.agents can break service, while a change to service can't break domain.agents.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→23 service uses domain.decisions✕
- Connections
- 4 pairs of types, where a type in service uses a type in domain.decisions.
- The types involved
io.cequence.openaiscala.service.OpenAIDecisionsService→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.service.OpenAIDecisionsService→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.service.OpenAIDecisionsService→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.service.OpenAIDecisionsService→io.cequence.openaiscala.domain.decisions.DecisionQuestion
- Direction
- service uses domain.decisions, so a change to domain.decisions can break service, while a change to service can't break domain.decisions.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→25 service uses service.adapter✕
- Connections
- 1 pair of types, where a type in service uses a type in service.adapter.
- The types involved
io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceRouter→io.cequence.openaiscala.service.adapter.MappedModel
- Direction
- service uses service.adapter, so a change to service.adapter can break service, while a change to service can't break service.adapter.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
28→26 service uses service.impl✕
- Connections
- 1 pair of types, where a type in service uses a type in service.impl.
- The types involved
io.cequence.openaiscala.service.OpenAIServiceClassImpl→io.cequence.openaiscala.service.impl.OpenAIServiceImpl
- Direction
- service uses service.impl, so a change to service.impl can break service, while a change to service can't break service.impl.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
29→10 anthropic.domain.Content.ContentBlock uses domain✕
- Connections
- 1 pair of types, where a type in anthropic.domain.Content.ContentBlock uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.Content.ContentBlock.Citation→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.Content.ContentBlock uses domain, so a change to domain can break anthropic.domain.Content.ContentBlock, while a change to anthropic.domain.Content.ContentBlock can't break domain.
- Position
- Below the diagonal: anthropic.domain.Content.ContentBlock uses a module listed above it, which is the healthy direction.
29→24 anthropic.domain.Content.ContentBlock uses anthropic.domain✕
- Connections
- 7 pairs of types, where a type in anthropic.domain.Content.ContentBlock uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.Content.ContentBlock.BashCodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.BashCodeExecutionToolResultContentio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.CodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.CodeExecutionToolResultContentio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.McpToolResultBlock→io.cequence.openaiscala.anthropic.domain.McpToolResultContentio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ServerToolUseBlock→io.cequence.openaiscala.anthropic.domain.ServerToolNameio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.TextEditorCodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.TextEditorCodeExecutionToolResultContentio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.WebFetchToolResultBlock→io.cequence.openaiscala.anthropic.domain.WebFetchToolResultContentio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.WebSearchToolResultBlock→io.cequence.openaiscala.anthropic.domain.WebSearchToolResultContent
- Direction
- anthropic.domain.Content.ContentBlock uses anthropic.domain, so a change to anthropic.domain can break anthropic.domain.Content.ContentBlock, while a change to anthropic.domain.Content.ContentBlock can't break anthropic.domain.
- Position
- Below the diagonal: anthropic.domain.Content.ContentBlock uses a module listed above it, which is the healthy direction.
29→27 anthropic.domain.Content.ContentBlock uses anthropic.domain.Content✕
- Connections
- 17 pairs of types, where a type in anthropic.domain.Content.ContentBlock uses a type in anthropic.domain.Content.
- The types involved
io.cequence.openaiscala.anthropic.domain.Content.ContentBlock.BashCodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.CodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ContainerUploadBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.FileDocumentContentBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.McpToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.McpToolUseBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.MediaBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.RedactedThinkingBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ServerToolUseBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.TextBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.TextEditorCodeExecutionToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.TextsContentBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ThinkingBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ToolUseBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.WebFetchToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.domain.Content.ContentBlock.WebSearchToolResultBlock→io.cequence.openaiscala.anthropic.domain.Content.ContentBlock
- Direction
- anthropic.domain.Content.ContentBlock uses anthropic.domain.Content, so a change to anthropic.domain.Content can break anthropic.domain.Content.ContentBlock, while a change to anthropic.domain.Content.ContentBlock can't break anthropic.domain.Content.
- Position
- Below the diagonal: anthropic.domain.Content.ContentBlock uses a module listed above it, which is the healthy direction.
30→4 gemini.service.impl uses domain.response✕
- Connections
- 1 pair of types, where a type in gemini.service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.domain.response.ChatChunk
- Direction
- gemini.service.impl uses domain.response, so a change to domain.response can break gemini.service.impl, while a change to gemini.service.impl can't break domain.response.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→6 gemini.service.impl uses gemini.domain.response✕
- Connections
- 5 pairs of types, where a type in gemini.service.impl uses a type in gemini.domain.response.
- The types involved
io.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.response.GenerateContentResponseio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.response.ListCachedContentsResponseio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.response.ListModelsResponseio.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.gemini.domain.response.GenerateContentResponseio.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.gemini.domain.response.UsageMetadata
- Direction
- gemini.service.impl uses gemini.domain.response, so a change to gemini.domain.response can break gemini.service.impl, while a change to gemini.service.impl can't break gemini.domain.response.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→7 gemini.service.impl uses gemini.domain.settings✕
- Connections
- 1 pair of types, where a type in gemini.service.impl uses a type in gemini.domain.settings.
- The types involved
io.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.settings.GenerateContentSettings
- Direction
- gemini.service.impl uses gemini.domain.settings, so a change to gemini.domain.settings can break gemini.service.impl, while a change to gemini.service.impl can't break gemini.domain.settings.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→8 gemini.service.impl uses domain.settings✕
- Connections
- 1 pair of types, where a type in gemini.service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- gemini.service.impl uses domain.settings, so a change to domain.settings can break gemini.service.impl, while a change to gemini.service.impl can't break domain.settings.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→9 gemini.service.impl uses gemini.domain✕
- Connections
- 10 pairs of types, where a type in gemini.service.impl uses a type in gemini.domain.
- The types involved
io.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.BatchRequestItemio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.CachedContentio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.Contentio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.Expirationio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.GeminiFileio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.GenerateContentBatchio.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.gemini.domain.ListBatchesResponseio.cequence.openaiscala.gemini.service.impl.GeminiThinking→io.cequence.openaiscala.gemini.domain.ThinkingLevelio.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.gemini.domain.Contentio.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.gemini.domain.Part
- Direction
- gemini.service.impl uses gemini.domain, so a change to gemini.domain can break gemini.service.impl, while a change to gemini.service.impl can't break gemini.domain.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→10 gemini.service.impl uses domain✕
- Connections
- 1 pair of types, where a type in gemini.service.impl uses a type in domain.
- The types involved
io.cequence.openaiscala.gemini.service.impl.OpenAIGeminiChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionTool
- Direction
- gemini.service.impl uses domain, so a change to domain can break gemini.service.impl, while a change to gemini.service.impl can't break domain.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
30→28 gemini.service.impl uses service✕
- Connections
- 1 pair of types, where a type in gemini.service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.gemini.service.impl.GeminiServiceImpl→io.cequence.openaiscala.service.ClassifiedStreamingWSClient
- Direction
- gemini.service.impl uses service, so a change to service can break gemini.service.impl, while a change to gemini.service.impl can't break service.
- Position
- Below the diagonal: gemini.service.impl uses a module listed above it, which is the healthy direction.
31→12 perplexity.service uses perplexity.domain.agent✕
- Connections
- 7 pairs of types, where a type in perplexity.service uses a type in perplexity.domain.agent.
- The types involved
io.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentCancelResponseio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentInputio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentModelio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentResponseio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentResponseFileio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.AgentStreamEventio.cequence.openaiscala.perplexity.service.SonarService→io.cequence.openaiscala.perplexity.domain.agent.CreateAgentResponseSettings
- Direction
- perplexity.service uses perplexity.domain.agent, so a change to perplexity.domain.agent can break perplexity.service, while a change to perplexity.service can't break perplexity.domain.agent.
- Position
- Below the diagonal: perplexity.service uses a module listed above it, which is the healthy direction.
31→18 perplexity.service uses io.cequence.openaiscala✕
- Connections
- 2 pairs of types, where a type in perplexity.service uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.perplexity.service.PerplexityScalaClientException→io.cequence.openaiscala.ProviderErrorDetailsio.cequence.openaiscala.perplexity.service.SonarServiceFactory→io.cequence.openaiscala.EnvHelper
- Direction
- perplexity.service uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break perplexity.service, while a change to perplexity.service can't break io.cequence.openaiscala.
- Position
- Below the diagonal: perplexity.service uses a module listed above it, which is the healthy direction.
31→28 perplexity.service uses service✕
- Connections
- 1 pair of types, where a type in perplexity.service uses a type in service.
- The types involved
io.cequence.openaiscala.perplexity.service.SonarServiceFactory→io.cequence.openaiscala.service.OpenAIChatCompletionService
- Direction
- perplexity.service uses service, so a change to service can break perplexity.service, while a change to perplexity.service can't break service.
- Position
- Below the diagonal: perplexity.service uses a module listed above it, which is the healthy direction.
32→4 service.OpenAIStreamedServiceImplicits uses domain.response✕
- Connections
- 6 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in domain.response.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.response.TextCompletionResponseio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ResponsesChatCompletionStreamExt→io.cequence.openaiscala.domain.response.ChatChunk
- Direction
- service.OpenAIStreamedServiceImplicits uses domain.response, so a change to domain.response can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break domain.response.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→8 service.OpenAIStreamedServiceImplicits uses domain.settings✕
- Connections
- 4 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.settings.CreateCompletionSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ResponsesChatCompletionStreamExt→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- service.OpenAIStreamedServiceImplicits uses domain.settings, so a change to domain.settings can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break domain.settings.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→10 service.OpenAIStreamedServiceImplicits uses domain✕
- Connections
- 6 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in domain.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ResponsesChatCompletionStreamExt→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ResponsesChatCompletionStreamExt→io.cequence.openaiscala.domain.ChatCompletionTool
- Direction
- service.OpenAIStreamedServiceImplicits uses domain, so a change to domain can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break domain.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→20 service.OpenAIStreamedServiceImplicits uses domain.responsesapi✕
- Connections
- 4 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.AgentsChatCompletionStreamExt→io.cequence.openaiscala.domain.responsesapi.MultiAgentConfigio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.responsesapi.ResponseStreamEvent
- Direction
- service.OpenAIStreamedServiceImplicits uses domain.responsesapi, so a change to domain.responsesapi can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break domain.responsesapi.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→22 service.OpenAIStreamedServiceImplicits uses domain.agents✕
- Connections
- 5 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in domain.agents.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.AgentsChatCompletionStreamExt→io.cequence.openaiscala.domain.agents.AgentEnvironmentio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.AgentsChatCompletionStreamExt→io.cequence.openaiscala.domain.agents.AgentToolio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettings
- Direction
- service.OpenAIStreamedServiceImplicits uses domain.agents, so a change to domain.agents can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break domain.agents.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→25 service.OpenAIStreamedServiceImplicits uses service.adapter✕
- Connections
- 4 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in service.adapter.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.AgentsChatCompletionStreamExt→io.cequence.openaiscala.service.adapter.OpenAIAgentsChatCompletionServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAIChatCompletionStreamedServiceWrapper→io.cequence.openaiscala.service.adapter.OpenAIChatCompletionServiceWrapperio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAICoreStreamedServiceWrapper→io.cequence.openaiscala.service.adapter.OpenAICoreServiceWrapperio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAIStreamedServiceWrapper→io.cequence.openaiscala.service.adapter.OpenAIServiceWrapper
- Direction
- service.OpenAIStreamedServiceImplicits uses service.adapter, so a change to service.adapter can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break service.adapter.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
32→28 service.OpenAIStreamedServiceImplicits uses service✕
- Connections
- 17 pairs of types, where a type in service.OpenAIStreamedServiceImplicits uses a type in service.
- The types involved
io.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamCoreExt→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamCoreExt→io.cequence.openaiscala.service.OpenAICoreServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamExt→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamFactoryExt→io.cequence.openaiscala.service.IOpenAIChatCompletionServiceFactoryio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamFullExt→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.ChatCompletionStreamFullExt→io.cequence.openaiscala.service.OpenAIServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.CoreStreamExt→io.cequence.openaiscala.service.OpenAIStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIChatCompletionStreamedExtraBase→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAICoreStreamedExtra→io.cequence.openaiscala.service.OpenAIStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.HasOpenAIFullStreamedExtra→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAIChatCompletionStreamedServiceWrapper→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAIChatCompletionStreamedServiceWrapper→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAICoreStreamedServiceWrapper→io.cequence.openaiscala.service.OpenAICoreServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.OpenAIStreamedServiceWrapper→io.cequence.openaiscala.service.OpenAIServiceio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.StreamExt→io.cequence.openaiscala.service.OpenAIStreamedServiceExtraio.cequence.openaiscala.service.OpenAIStreamedServiceImplicits.StreamFactoryExt→io.cequence.openaiscala.service.OpenAIServiceFactoryHelper
- Direction
- service.OpenAIStreamedServiceImplicits uses service, so a change to service can break service.OpenAIStreamedServiceImplicits, while a change to service.OpenAIStreamedServiceImplicits can't break service.
- Position
- Below the diagonal: service.OpenAIStreamedServiceImplicits uses a module listed above it, which is the healthy direction.
33→1 typesafe.service uses RetryHelpers✕
- Connections
- 1 pair of types, where a type in typesafe.service uses a type in RetryHelpers.
- The types involved
io.cequence.openaiscala.typesafe.service.TypeSafeServiceAdapters→io.cequence.openaiscala.RetryHelpers.RetrySettings
- Direction
- typesafe.service uses RetryHelpers, so a change to RetryHelpers can break typesafe.service, while a change to typesafe.service can't break RetryHelpers.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
33→2 typesafe.service uses typesafe.domain✕
- Connections
- 10 pairs of types, where a type in typesafe.service uses a type in typesafe.domain.
- The types involved
io.cequence.openaiscala.typesafe.service.DecisionProviderSettings→io.cequence.openaiscala.typesafe.domain.DecisionProviderio.cequence.openaiscala.typesafe.service.DecisionServiceExtra→io.cequence.openaiscala.typesafe.domain.RerankSettingsio.cequence.openaiscala.typesafe.service.RetryTypeSafeService→io.cequence.openaiscala.typesafe.domain.ModelMetadataio.cequence.openaiscala.typesafe.service.RetryTypeSafeService→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.RetryTypeSafeService→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.TypeSafeChatMapping→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.TypeSafeService→io.cequence.openaiscala.typesafe.domain.ModelMetadataio.cequence.openaiscala.typesafe.service.TypeSafeService→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.TypeSafeService→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.TypeSafeServiceFactory→io.cequence.openaiscala.typesafe.domain.DecisionProvider
- Direction
- typesafe.service uses typesafe.domain, so a change to typesafe.domain can break typesafe.service, while a change to typesafe.service can't break typesafe.domain.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
33→8 typesafe.service uses domain.settings✕
- Connections
- 1 pair of types, where a type in typesafe.service uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.typesafe.service.TypeSafeChatMapping→io.cequence.openaiscala.domain.settings.JsonSchemaDef
- Direction
- typesafe.service uses domain.settings, so a change to domain.settings can break typesafe.service, while a change to typesafe.service can't break domain.settings.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
33→10 typesafe.service uses domain✕
- Connections
- 2 pairs of types, where a type in typesafe.service uses a type in domain.
- The types involved
io.cequence.openaiscala.typesafe.service.TypeSafeChatMapping→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.typesafe.service.TypeSafeChatMapping→io.cequence.openaiscala.domain.Content
- Direction
- typesafe.service uses domain, so a change to domain can break typesafe.service, while a change to typesafe.service can't break domain.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
33→18 typesafe.service uses io.cequence.openaiscala✕
- Connections
- 3 pairs of types, where a type in typesafe.service uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.typesafe.service.RetryTypeSafeService→io.cequence.openaiscala.RetryHelpersio.cequence.openaiscala.typesafe.service.TypeSafeScalaClientException→io.cequence.openaiscala.ProviderErrorDetailsio.cequence.openaiscala.typesafe.service.TypeSafeServiceFactory→io.cequence.openaiscala.EnvHelper
- Direction
- typesafe.service uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break typesafe.service, while a change to typesafe.service can't break io.cequence.openaiscala.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
33→28 typesafe.service uses service✕
- Connections
- 2 pairs of types, where a type in typesafe.service uses a type in service.
- The types involved
io.cequence.openaiscala.typesafe.service.TypeSafeServiceFactory→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.typesafe.service.TypeSafeServiceFactory→io.cequence.openaiscala.service.OpenAIDecisionsService
- Direction
- typesafe.service uses service, so a change to service can break typesafe.service, while a change to typesafe.service can't break service.
- Position
- Below the diagonal: typesafe.service uses a module listed above it, which is the healthy direction.
34→3 vertexai.service uses vertexai.domain✕
- Connections
- 4 pairs of types, where a type in vertexai.service uses a type in vertexai.domain.
- The types involved
io.cequence.openaiscala.vertexai.service.VertexAIBatchPredictionService→io.cequence.openaiscala.vertexai.domain.BatchPredictionJobio.cequence.openaiscala.vertexai.service.VertexAIBatchPredictionService→io.cequence.openaiscala.vertexai.domain.CreateBatchPredictionJobSettingsio.cequence.openaiscala.vertexai.service.VertexAIBatchPredictionService→io.cequence.openaiscala.vertexai.domain.ListBatchPredictionJobsResponseio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.vertexai.domain.Schema
- Direction
- vertexai.service uses vertexai.domain, so a change to vertexai.domain can break vertexai.service, while a change to vertexai.service can't break vertexai.domain.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
34→4 vertexai.service uses domain.response✕
- Connections
- 1 pair of types, where a type in vertexai.service uses a type in domain.response.
- The types involved
io.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.response.ChatCompletionResponse
- Direction
- vertexai.service uses domain.response, so a change to domain.response can break vertexai.service, while a change to vertexai.service can't break domain.response.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
34→8 vertexai.service uses domain.settings✕
- Connections
- 2 pairs of types, where a type in vertexai.service uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.settings.ReasoningEffort
- Direction
- vertexai.service uses domain.settings, so a change to domain.settings can break vertexai.service, while a change to vertexai.service can't break domain.settings.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
34→10 vertexai.service uses domain✕
- Connections
- 5 pairs of types, where a type in vertexai.service uses a type in domain.
- The types involved
io.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.AssistantMessageio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.ReasoningBlockio.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.domain.ReasoningMessage
- Direction
- vertexai.service uses domain, so a change to domain can break vertexai.service, while a change to vertexai.service can't break domain.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
34→18 vertexai.service uses io.cequence.openaiscala✕
- Connections
- 1 pair of types, where a type in vertexai.service uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.vertexai.service.VertexAIServiceFactory→io.cequence.openaiscala.EnvHelper
- Direction
- vertexai.service uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break vertexai.service, while a change to vertexai.service can't break io.cequence.openaiscala.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
34→28 vertexai.service uses service✕
- Connections
- 1 pair of types, where a type in vertexai.service uses a type in service.
- The types involved
io.cequence.openaiscala.vertexai.service.impl→io.cequence.openaiscala.service.HasOpenAIConfig
- Direction
- vertexai.service uses service, so a change to service can break vertexai.service, while a change to vertexai.service can't break service.
- Position
- Below the diagonal: vertexai.service uses a module listed above it, which is the healthy direction.
35→10 anthropic.domain.response uses domain✕
- Connections
- 1 pair of types, where a type in anthropic.domain.response uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.response.DeltaBlock→io.cequence.openaiscala.domain.HasType
- Direction
- anthropic.domain.response uses domain, so a change to domain can break anthropic.domain.response, while a change to anthropic.domain.response can't break domain.
- Position
- Below the diagonal: anthropic.domain.response uses a module listed above it, which is the healthy direction.
35→24 anthropic.domain.response uses anthropic.domain✕
- Connections
- 1 pair of types, where a type in anthropic.domain.response uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponse→io.cequence.openaiscala.anthropic.domain.ChatRole
- Direction
- anthropic.domain.response uses anthropic.domain, so a change to anthropic.domain can break anthropic.domain.response, while a change to anthropic.domain.response can't break anthropic.domain.
- Position
- Below the diagonal: anthropic.domain.response uses a module listed above it, which is the healthy direction.
35→27 anthropic.domain.response uses anthropic.domain.Content✕
- Connections
- 1 pair of types, where a type in anthropic.domain.response uses a type in anthropic.domain.Content.
- The types involved
io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponse→io.cequence.openaiscala.anthropic.domain.Content.ContentBlocks
- Direction
- anthropic.domain.response uses anthropic.domain.Content, so a change to anthropic.domain.Content can break anthropic.domain.response, while a change to anthropic.domain.response can't break anthropic.domain.Content.
- Position
- Below the diagonal: anthropic.domain.response uses a module listed above it, which is the healthy direction.
35→29 anthropic.domain.response uses anthropic.domain.Content.ContentBlock✕
- Connections
- 2 pairs of types, where a type in anthropic.domain.response uses a type in anthropic.domain.Content.ContentBlock.
- The types involved
io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponse→io.cequence.openaiscala.anthropic.domain.Content.ContentBlock.Citationio.cequence.openaiscala.anthropic.domain.response.CreateMessageResponse→io.cequence.openaiscala.anthropic.domain.Content.ContentBlock.ToolUseBlock
- Direction
- anthropic.domain.response uses anthropic.domain.Content.ContentBlock, so a change to anthropic.domain.Content.ContentBlock can break anthropic.domain.response, while a change to anthropic.domain.response can't break anthropic.domain.Content.ContentBlock.
- Position
- Below the diagonal: anthropic.domain.response uses a module listed above it, which is the healthy direction.
36→4 perplexity.service.impl uses domain.response✕
- Connections
- 4 pairs of types, where a type in perplexity.service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.response.TextCompletionResponse
- Direction
- perplexity.service.impl uses domain.response, so a change to domain.response can break perplexity.service.impl, while a change to perplexity.service.impl can't break domain.response.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→8 perplexity.service.impl uses domain.settings✕
- Connections
- 3 pairs of types, where a type in perplexity.service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.settings.CreateCompletionSettings
- Direction
- perplexity.service.impl uses domain.settings, so a change to domain.settings can break perplexity.service.impl, while a change to perplexity.service.impl can't break domain.settings.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→10 perplexity.service.impl uses domain✕
- Connections
- 3 pairs of types, where a type in perplexity.service.impl uses a type in domain.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.SortOrder
- Direction
- perplexity.service.impl uses domain, so a change to domain can break perplexity.service.impl, while a change to perplexity.service.impl can't break domain.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→12 perplexity.service.impl uses perplexity.domain.agent✕
- Connections
- 7 pairs of types, where a type in perplexity.service.impl uses a type in perplexity.domain.agent.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentCancelResponseio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentInputio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentModelio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentResponseio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentResponseFileio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.AgentStreamEventio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.domain.agent.CreateAgentResponseSettings
- Direction
- perplexity.service.impl uses perplexity.domain.agent, so a change to perplexity.domain.agent can break perplexity.service.impl, while a change to perplexity.service.impl can't break perplexity.domain.agent.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→20 perplexity.service.impl uses domain.responsesapi✕
- Connections
- 8 pairs of types, where a type in perplexity.service.impl uses a type in domain.responsesapi.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.CreateModelResponseSettingsio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.DeleteResponseio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.GetInputTokensCountSettingsio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.InputItemsResponseio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.InputTokensCountio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.Inputsio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.Responseio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.responsesapi.ResponseStreamEvent
- Direction
- perplexity.service.impl uses domain.responsesapi, so a change to domain.responsesapi can break perplexity.service.impl, while a change to perplexity.service.impl can't break domain.responsesapi.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→22 perplexity.service.impl uses domain.agents✕
- Connections
- 3 pairs of types, where a type in perplexity.service.impl uses a type in domain.agents.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.agents.AgentInputio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.agents.AgentSessionEventio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.domain.agents.CreateAgentSessionSettings
- Direction
- perplexity.service.impl uses domain.agents, so a change to domain.agents can break perplexity.service.impl, while a change to perplexity.service.impl can't break domain.agents.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→28 perplexity.service.impl uses service✕
- Connections
- 7 pairs of types, where a type in perplexity.service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.service.ClassifiedStreamingWSClientio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.service.OpenAIResponsesServiceio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.service.OpenAIStreamedServiceExtraio.cequence.openaiscala.perplexity.service.impl.PerplexityResponsesServiceImpl→io.cequence.openaiscala.service.ResponsesToolApprovalsUnsupportedio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.service.ClassifiedStreamingWSClient
- Direction
- perplexity.service.impl uses service, so a change to service can break perplexity.service.impl, while a change to perplexity.service.impl can't break service.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
36→31 perplexity.service.impl uses perplexity.service✕
- Connections
- 2 pairs of types, where a type in perplexity.service.impl uses a type in perplexity.service.
- The types involved
io.cequence.openaiscala.perplexity.service.impl.OpenAISonarChatCompletionService→io.cequence.openaiscala.perplexity.service.SonarConstsio.cequence.openaiscala.perplexity.service.impl.SonarServiceImpl→io.cequence.openaiscala.perplexity.service.SonarService
- Direction
- perplexity.service.impl uses perplexity.service, so a change to perplexity.service can break perplexity.service.impl, while a change to perplexity.service.impl can't break perplexity.service.
- Position
- Below the diagonal: perplexity.service.impl uses a module listed above it, which is the healthy direction.
37→2 typesafe.service.impl uses typesafe.domain✕
- Connections
- 19 pairs of types, where a type in typesafe.service.impl uses a type in typesafe.domain.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.DecisionCodec→io.cequence.openaiscala.typesafe.domain.SystemOneRequestio.cequence.openaiscala.typesafe.service.impl.DecisionCodec→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsCodec→io.cequence.openaiscala.typesafe.domain.SystemOneRequestio.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsCodec→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.typesafe.domain.Answerio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.OpenAITypeSafeChatCompletionService→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.ScaleDownCodec→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.impl.ScaleDownCodec→io.cequence.openaiscala.typesafe.domain.SystemOneRequestio.cequence.openaiscala.typesafe.service.impl.ScaleDownCodec→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.SchemaQuestions→io.cequence.openaiscala.typesafe.domain.Answerio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.typesafe.domain.Answerio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.typesafe.domain.NoulQuestionio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.typesafe.domain.SystemOneResponseio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.typesafe.domain.ModelMetadataio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.typesafe.domain.Questionio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.typesafe.domain.SystemOneResponse
- Direction
- typesafe.service.impl uses typesafe.domain, so a change to typesafe.domain can break typesafe.service.impl, while a change to typesafe.service.impl can't break typesafe.domain.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→4 typesafe.service.impl uses domain.response✕
- Connections
- 1 pair of types, where a type in typesafe.service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAITypeSafeChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponse
- Direction
- typesafe.service.impl uses domain.response, so a change to domain.response can break typesafe.service.impl, while a change to typesafe.service.impl can't break domain.response.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→8 typesafe.service.impl uses domain.settings✕
- Connections
- 1 pair of types, where a type in typesafe.service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAITypeSafeChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- typesafe.service.impl uses domain.settings, so a change to domain.settings can break typesafe.service.impl, while a change to typesafe.service.impl can't break domain.settings.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→10 typesafe.service.impl uses domain✕
- Connections
- 1 pair of types, where a type in typesafe.service.impl uses a type in domain.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAITypeSafeChatCompletionService→io.cequence.openaiscala.domain.BaseMessage
- Direction
- typesafe.service.impl uses domain, so a change to domain can break typesafe.service.impl, while a change to typesafe.service.impl can't break domain.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→23 typesafe.service.impl uses domain.decisions✕
- Connections
- 22 pairs of types, where a type in typesafe.service.impl uses a type in domain.decisions.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsOverTypeSafe→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsOverTypeSafe→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsOverTypeSafe→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsOverTypeSafe→io.cequence.openaiscala.domain.decisions.DecisionQuestionio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.DecisionAnswerio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.DecisionMessageio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.DecisionQuestionio.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.domain.decisions.DecisionValueio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionAnswerio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionContentio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionLevelio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionQuestionio.cequence.openaiscala.typesafe.service.impl.SystemOneToOpenAI→io.cequence.openaiscala.domain.decisions.DecisionValueio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.domain.decisions.CreateDecisionSettingsio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.domain.decisions.Decisionio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.domain.decisions.DecisionInputio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.domain.decisions.DecisionQuestion
- Direction
- typesafe.service.impl uses domain.decisions, so a change to domain.decisions can break typesafe.service.impl, while a change to typesafe.service.impl can't break domain.decisions.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→28 typesafe.service.impl uses service✕
- Connections
- 3 pairs of types, where a type in typesafe.service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAIDecisionsOverTypeSafe→io.cequence.openaiscala.service.OpenAIDecisionsServiceio.cequence.openaiscala.typesafe.service.impl.OpenAITypeSafeChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.service.OpenAIDecisionsService
- Direction
- typesafe.service.impl uses service, so a change to service can break typesafe.service.impl, while a change to typesafe.service.impl can't break service.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
37→33 typesafe.service.impl uses typesafe.service✕
- Connections
- 2 pairs of types, where a type in typesafe.service.impl uses a type in typesafe.service.
- The types involved
io.cequence.openaiscala.typesafe.service.impl.OpenAIToSystemOne→io.cequence.openaiscala.typesafe.service.TypeSafeServiceio.cequence.openaiscala.typesafe.service.impl.TypeSafeServiceImpl→io.cequence.openaiscala.typesafe.service.TypeSafeService
- Direction
- typesafe.service.impl uses typesafe.service, so a change to typesafe.service can break typesafe.service.impl, while a change to typesafe.service.impl can't break typesafe.service.
- Position
- Below the diagonal: typesafe.service.impl uses a module listed above it, which is the healthy direction.
38→3 vertexai.service.impl uses vertexai.domain✕
- Connections
- 1 pair of types, where a type in vertexai.service.impl uses a type in vertexai.domain.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.vertexai.domain.BatchPredictionJob
- Direction
- vertexai.service.impl uses vertexai.domain, so a change to vertexai.domain can break vertexai.service.impl, while a change to vertexai.service.impl can't break vertexai.domain.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→4 vertexai.service.impl uses domain.response✕
- Connections
- 5 pairs of types, where a type in vertexai.service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.vertexai.service.impl.VertexAIChatChunks→io.cequence.openaiscala.domain.response.ChatChunk
- Direction
- vertexai.service.impl uses domain.response, so a change to domain.response can break vertexai.service.impl, while a change to vertexai.service.impl can't break domain.response.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→8 vertexai.service.impl uses domain.settings✕
- Connections
- 1 pair of types, where a type in vertexai.service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- vertexai.service.impl uses domain.settings, so a change to domain.settings can break vertexai.service.impl, while a change to vertexai.service.impl can't break domain.settings.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→10 vertexai.service.impl uses domain✕
- Connections
- 6 pairs of types, where a type in vertexai.service.impl uses a type in domain.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.domain.JsonSchema
- Direction
- vertexai.service.impl uses domain, so a change to domain can break vertexai.service.impl, while a change to vertexai.service.impl can't break domain.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→18 vertexai.service.impl uses io.cequence.openaiscala✕
- Connections
- 1 pair of types, where a type in vertexai.service.impl uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.VertexAIErrors→io.cequence.openaiscala.OpenAIScalaClientException
- Direction
- vertexai.service.impl uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break vertexai.service.impl, while a change to vertexai.service.impl can't break io.cequence.openaiscala.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→28 vertexai.service.impl uses service✕
- Connections
- 3 pairs of types, where a type in vertexai.service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra
- Direction
- vertexai.service.impl uses service, so a change to service can break vertexai.service.impl, while a change to vertexai.service.impl can't break service.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
38→34 vertexai.service.impl uses vertexai.service✕
- Connections
- 1 pair of types, where a type in vertexai.service.impl uses a type in vertexai.service.
- The types involved
io.cequence.openaiscala.vertexai.service.impl.OpenAIVertexAIChatCompletionService→io.cequence.openaiscala.vertexai.service.VertexAIBatchSupport
- Direction
- vertexai.service.impl uses vertexai.service, so a change to vertexai.service can break vertexai.service.impl, while a change to vertexai.service.impl can't break vertexai.service.
- Position
- Below the diagonal: vertexai.service.impl uses a module listed above it, which is the healthy direction.
39→4 anthropic.service uses domain.response✕
- Connections
- 4 pairs of types, where a type in anthropic.service uses a type in domain.response.
- The types involved
io.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.response.TracedBlock
- Direction
- anthropic.service uses domain.response, so a change to domain.response can break anthropic.service, while a change to anthropic.service can't break domain.response.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→8 anthropic.service uses domain.settings✕
- Connections
- 2 pairs of types, where a type in anthropic.service uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.settings.ReasoningEffort
- Direction
- anthropic.service uses domain.settings, so a change to domain.settings can break anthropic.service, while a change to anthropic.service can't break domain.settings.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→10 anthropic.service uses domain✕
- Connections
- 2 pairs of types, where a type in anthropic.service uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.JsonSchemaio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.domain.ReasoningMessage
- Direction
- anthropic.service uses domain, so a change to domain can break anthropic.service, while a change to anthropic.service can't break domain.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→13 anthropic.service uses anthropic.domain.skills✕
- Connections
- 7 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.skills.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillVersionResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.ListSkillVersionsResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.ListSkillsResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.Skillio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.SkillSourceio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.skills.SkillVersion
- Direction
- anthropic.service uses anthropic.domain.skills, so a change to anthropic.domain.skills can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.skills.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→18 anthropic.service uses io.cequence.openaiscala✕
- Connections
- 1 pair of types, where a type in anthropic.service uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicServiceFactory→io.cequence.openaiscala.EnvHelper
- Direction
- anthropic.service uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break anthropic.service, while a change to anthropic.service can't break io.cequence.openaiscala.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→19 anthropic.service uses anthropic.domain.managedagents✕
- Connections
- 30 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.managedagents. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicDeploymentService→io.cequence.openaiscala.anthropic.domain.managedagents.Deploymentio.cequence.openaiscala.anthropic.service.AnthropicDeploymentService→io.cequence.openaiscala.anthropic.domain.managedagents.DeploymentRunio.cequence.openaiscala.anthropic.service.AnthropicDeploymentService→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.Environmentio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentDeleteResponseio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.SelfHostedWorkio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.WorkHeartbeatResponseio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.managedagents.WorkQueueStatsio.cequence.openaiscala.anthropic.service.AnthropicManagedAgentService→io.cequence.openaiscala.anthropic.domain.managedagents.Agentio.cequence.openaiscala.anthropic.service.AnthropicManagedAgentService→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.Memoryio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryEntryio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryStoreio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryVersionio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryVersionOperationio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryViewio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.AnthropicServiceFactory→io.cequence.openaiscala.anthropic.domain.managedagents.AgentToolio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.Sessionio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.SessionDeleteResponseio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.SessionEventio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.SessionEventEnvelopeio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.managedagents.SessionResource
- Direction
- anthropic.service uses anthropic.domain.managedagents, so a change to anthropic.domain.managedagents can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.managedagents.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→21 anthropic.service uses anthropic.domain.settings✕
- Connections
- 18 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.settings.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicDeploymentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettingsio.cequence.openaiscala.anthropic.service.AnthropicDeploymentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateDeploymentSettingsio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateEnvironmentSettingsio.cequence.openaiscala.anthropic.service.AnthropicEnvironmentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateEnvironmentSettingsio.cequence.openaiscala.anthropic.service.AnthropicManagedAgentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettingsio.cequence.openaiscala.anthropic.service.AnthropicManagedAgentService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettingsio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMemoryStoreSettingsio.cequence.openaiscala.anthropic.service.AnthropicMemoryStoreService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateMemoryStoreSettingsio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettingsio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateSessionSettingsio.cequence.openaiscala.anthropic.service.AnthropicSessionService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateSessionSettingsio.cequence.openaiscala.anthropic.service.AnthropicVaultService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateCredentialSettingsio.cequence.openaiscala.anthropic.service.AnthropicVaultService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateVaultSettingsio.cequence.openaiscala.anthropic.service.AnthropicVaultService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateCredentialSettingsio.cequence.openaiscala.anthropic.service.AnthropicVaultService→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateVaultSettingsio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettingsio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.settings.OutputEffortio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.settings.ThinkingSettings
- Direction
- anthropic.service uses anthropic.domain.settings, so a change to anthropic.domain.settings can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.settings.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→24 anthropic.service uses anthropic.domain✕
- Connections
- 14 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchInferenceService→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobio.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchInferenceService→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobStatusio.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchInferenceService→io.cequence.openaiscala.anthropic.domain.CreateBatchInferenceJobSettingsio.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchInferenceService→io.cequence.openaiscala.anthropic.domain.ListBatchInferenceJobsResponseio.cequence.openaiscala.anthropic.service.AnthropicMessageBatchService→io.cequence.openaiscala.anthropic.domain.ListMessageBatchesResponseio.cequence.openaiscala.anthropic.service.AnthropicMessageBatchService→io.cequence.openaiscala.anthropic.domain.MessageBatchio.cequence.openaiscala.anthropic.service.AnthropicMessageBatchService→io.cequence.openaiscala.anthropic.domain.MessageBatchDeleteResponseio.cequence.openaiscala.anthropic.service.AnthropicMessageBatchService→io.cequence.openaiscala.anthropic.domain.MessageBatchIndividualResponseio.cequence.openaiscala.anthropic.service.AnthropicMessageBatchService→io.cequence.openaiscala.anthropic.domain.MessageBatchRequestio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.FileDeleteResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.FileListResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.FileMetadataio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.Messageio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.Message
- Direction
- anthropic.service uses anthropic.domain, so a change to anthropic.domain can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→27 anthropic.service uses anthropic.domain.Content✕
- Connections
- 3 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.Content.
- The types involved
io.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockBaseio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.Content.ContentBlocks
- Direction
- anthropic.service uses anthropic.domain.Content, so a change to anthropic.domain.Content can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.Content.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→28 anthropic.service uses service✕
- Connections
- 1 pair of types, where a type in anthropic.service uses a type in service.
- The types involved
io.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.service.HasOpenAIConfig
- Direction
- anthropic.service uses service, so a change to service can break anthropic.service, while a change to anthropic.service can't break service.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
39→35 anthropic.service uses anthropic.domain.response✕
- Connections
- 7 pairs of types, where a type in anthropic.service uses a type in anthropic.domain.response.
- The types involved
io.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.response.ContentBlockDeltaio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponseio.cequence.openaiscala.anthropic.service.AnthropicService→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEventio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.response.ContentBlockDeltaio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponseio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.response.MessageDeltaUsageio.cequence.openaiscala.anthropic.service.impl→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEvent
- Direction
- anthropic.service uses anthropic.domain.response, so a change to anthropic.domain.response can break anthropic.service, while a change to anthropic.service can't break anthropic.domain.response.
- Position
- Below the diagonal: anthropic.service uses a module listed above it, which is the healthy direction.
40→4 anthropic.service.impl uses domain.response✕
- Connections
- 9 pairs of types, where a type in anthropic.service.impl uses a type in domain.response.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.response.ChatToolCompletionResponseio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.response.ChatChunkio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionChunkResponseio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.response.ChatCompletionResponseio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.response.ToolApprovalDecisionio.cequence.openaiscala.anthropic.service.impl.StreamedChunkMapper→io.cequence.openaiscala.domain.response.ChatChunk
- Direction
- anthropic.service.impl uses domain.response, so a change to domain.response can break anthropic.service.impl, while a change to anthropic.service.impl can't break domain.response.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→8 anthropic.service.impl uses domain.settings✕
- Connections
- 3 pairs of types, where a type in anthropic.service.impl uses a type in domain.settings.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicBedrockChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettingsio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.settings.CreateChatCompletionSettings
- Direction
- anthropic.service.impl uses domain.settings, so a change to domain.settings can break anthropic.service.impl, while a change to anthropic.service.impl can't break domain.settings.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→10 anthropic.service.impl uses domain✕
- Connections
- 10 pairs of types, where a type in anthropic.service.impl uses a type in domain.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicBedrockChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicBedrockChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicBedrockChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchInfoio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchRequestio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionBatchResultItemio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionToolio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.BaseMessageio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.domain.ChatCompletionTool
- Direction
- anthropic.service.impl uses domain, so a change to domain can break anthropic.service.impl, while a change to anthropic.service.impl can't break domain.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→13 anthropic.service.impl uses anthropic.domain.skills✕
- Connections
- 14 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain.skills.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillVersionResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.ListSkillVersionsResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.ListSkillsResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.Skillio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.SkillSourceio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.SkillVersionio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.DeleteSkillVersionResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.ListSkillVersionsResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.ListSkillsResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.Skillio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.SkillSourceio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.skills.SkillVersion
- Direction
- anthropic.service.impl uses anthropic.domain.skills, so a change to anthropic.domain.skills can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.skills.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→18 anthropic.service.impl uses io.cequence.openaiscala✕
- Connections
- 2 pairs of types, where a type in anthropic.service.impl uses a type in io.cequence.openaiscala.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.OpenAIScalaClientExceptionio.cequence.openaiscala.anthropic.service.impl.UnanswerablePauseException→io.cequence.openaiscala.OpenAIScalaClientException
- Direction
- anthropic.service.impl uses io.cequence.openaiscala, so a change to io.cequence.openaiscala can break anthropic.service.impl, while a change to anthropic.service.impl can't break io.cequence.openaiscala.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→19 anthropic.service.impl uses anthropic.domain.managedagents✕
- Connections
- 51 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain.managedagents. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Agentio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Credentialio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Deploymentio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.DeploymentRunio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Environmentio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.EnvironmentDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Memoryio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryEntryio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryStoreio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryVersionio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryVersionOperationio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.MemoryViewio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.PagedResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SelfHostedWorkio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Sessionio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionEventio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionEventEnvelopeio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionResourceio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionStatusio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.SessionThreadio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Vaultio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.WorkHeartbeatResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.WorkQueueStatsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.managedagents.Agent
- Direction
- anthropic.service.impl uses anthropic.domain.managedagents, so a change to anthropic.domain.managedagents can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.managedagents.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→21 anthropic.service.impl uses anthropic.domain.settings✕
- Connections
- 33 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain.settings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateCredentialSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateEnvironmentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMemoryStoreSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateSessionSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateVaultSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateCredentialSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateDeploymentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateEnvironmentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateMemoryStoreSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateSessionSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateVaultSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateAgentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateCredentialSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateDeploymentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateEnvironmentSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMemoryStoreSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateMessageSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateSessionSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicCreateVaultSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.settings.AnthropicUpdateAgentSettings
- Direction
- anthropic.service.impl uses anthropic.domain.settings, so a change to anthropic.domain.settings can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.settings.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→24 anthropic.service.impl uses anthropic.domain✕
- Connections
- 30 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.anthropic.domain.Messageio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockBatchInferenceServiceImpl→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockBatchInferenceServiceImpl→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobStatusio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockBatchInferenceServiceImpl→io.cequence.openaiscala.anthropic.domain.CreateBatchInferenceJobSettingsio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockBatchInferenceServiceImpl→io.cequence.openaiscala.anthropic.domain.ListBatchInferenceJobsResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.FileDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.FileListResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.FileMetadataio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.ListMessageBatchesResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.Messageio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchIndividualResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchRequestio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.FileDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.FileListResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.FileMetadataio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.ListMessageBatchesResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.Messageio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchDeleteResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchIndividualResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.MessageBatchRequestio.cequence.openaiscala.anthropic.service.impl.BedrockBatchJsonFormats→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobio.cequence.openaiscala.anthropic.service.impl.BedrockBatchJsonFormats→io.cequence.openaiscala.anthropic.domain.BatchInferenceJobStatus
- Direction
- anthropic.service.impl uses anthropic.domain, so a change to anthropic.domain can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→27 anthropic.service.impl uses anthropic.domain.Content✕
- Connections
- 3 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain.Content.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockBaseio.cequence.openaiscala.anthropic.service.impl.StreamedBlockBuilder→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockBaseio.cequence.openaiscala.anthropic.service.impl.StreamedChunkMapper→io.cequence.openaiscala.anthropic.domain.Content.ContentBlockBase
- Direction
- anthropic.service.impl uses anthropic.domain.Content, so a change to anthropic.domain.Content can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.Content.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→28 anthropic.service.impl uses service✕
- Connections
- 6 pairs of types, where a type in anthropic.service.impl uses a type in service.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.service.ClassifiedStreamingWSClientio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionBatchServiceio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtraio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionServiceio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicManagedAgentChatCompletionService→io.cequence.openaiscala.service.OpenAIChatCompletionStreamedServiceExtra
- Direction
- anthropic.service.impl uses service, so a change to service can break anthropic.service.impl, while a change to anthropic.service.impl can't break service.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→35 anthropic.service.impl uses anthropic.domain.response✕
- Connections
- 10 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.domain.response.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEventio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.response.ContentBlockDeltaio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockServiceImpl→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEventio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.response.ContentBlockDeltaio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponseio.cequence.openaiscala.anthropic.service.impl.AnthropicServiceImpl→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEventio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicChatCompletionService→io.cequence.openaiscala.anthropic.domain.response.CreateMessageResponseio.cequence.openaiscala.anthropic.service.impl.StreamedBlockBuilder→io.cequence.openaiscala.anthropic.domain.response.DeltaBlockio.cequence.openaiscala.anthropic.service.impl.StreamedChunkMapper→io.cequence.openaiscala.anthropic.domain.response.MessageStreamEvent
- Direction
- anthropic.service.impl uses anthropic.domain.response, so a change to anthropic.domain.response can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.domain.response.
- Position
- Below the diagonal: anthropic.service.impl uses a module listed above it, which is the healthy direction.
40→39 anthropic.service.impl uses anthropic.service✕
- Connections
- 4 pairs of types, where a type in anthropic.service.impl uses a type in anthropic.service.
- The types involved
io.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.anthropic.service.AnthropicServiceio.cequence.openaiscala.anthropic.service.impl.Anthropic→io.cequence.openaiscala.anthropic.service.HandleAnthropicErrorCodesio.cequence.openaiscala.anthropic.service.impl.AnthropicBedrockBatchInferenceServiceImpl→io.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchInferenceServiceio.cequence.openaiscala.anthropic.service.impl.OpenAIAnthropicBedrockChatCompletionService→io.cequence.openaiscala.anthropic.service.AnthropicBedrockBatchSupport
- Direction
- anthropic.service.impl uses anthropic.service, so a change to anthropic.service can break anthropic.service.impl, while a change to anthropic.service.impl can't break anthropic.service.
- Position
- Below the diagonal: anthropic.service.impl 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 | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: 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; Interpolated log message defeats structured logging; Bring the 33 bodies over 15 down to 15 or less in Cognitive Complexity — start with ChatChunks.fromResponseEvents (cognitive 64), JsonSchemaMacros.shapeExprOf (cognitive 56), RetryEngine.run (cognitive 38).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +4.2 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +3.9 pts | Medium | Structured logging |
| Bring the 33 bodies over 15 down to 15 or less in Cognitive Complexity — start with ChatChunks.fromResponseEvents (cognitive 64), JsonSchemaMacros.shapeExprOf (cognitive 56), RetryEngine.run (cognitive 38). | +3.6 pts | High | Cognitive Complexity |
| Swallowed exception (caught, then discarded) | +2.6 pts | Medium | Exception handling |
| Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking. | +2.2 pts | Medium | Async & latency hygiene |
| Resolve the 20 FileTooLong finding(s) in God Classes — start with JsonFormats.scala (5), package.scala (2), AnthropicServiceImpl.scala. | +1.0 pts | High | God Classes |
| 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. | +1.0 pts | Medium | Architecture documentation |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +1.0 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala | 1.9 | Slop | Change Coupling: Boundary-crossing change coupling: OpenAIServiceImpl.scala ↔ OpenAIServiceWrapper.scala |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| openai-core/src/main/scala/io/cequence/openaiscala/domain/NonOpenAIModelId.scala | 4.7 | Mixed | Change Coupling: Boundary-crossing change coupling: NonOpenAIModelId.scala ↔ DecisionProviderSettings.scala |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/OpenAIVertexAIChatCompletionService.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala | 6.6 | Mixed | Explicit Debt: FixmeComment |
| openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateChatCompletionSettings.scala | 6.6 | Mixed | Explicit Debt: TodoComment |
| anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/JsonFormats.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala | 7.0 | Mixed | Cyclomatic Complexity: ChatChunks.fromResponseEvents (cyclomatic 82) |
| openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala | 7.0 | Mixed | Cyclomatic Complexity: TurnState.onEvent (cyclomatic 26) |
| openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala | 7.1 | Mixed | Cyclomatic Complexity: OpenAIResponsesChatCompletionService.toResponsesSettings (cyclomatic 26) |
| google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala | 7.1 | Mixed | Cyclomatic Complexity: OpenAIGeminiChatCompletionService.chatChunksFlow (cyclomatic 19) |
| openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala | 7.1 | Mixed | Code Duplication: Near-duplicate member pair (81 shared lines) |
| google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala | 7.1 | Mixed | Cyclomatic Complexity: impl.toVertexAIContents (cyclomatic 16) |
| typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala | 7.2 | Mixed | Cyclomatic Complexity: SchemaQuestions.plan (cyclomatic 30) |
| anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicManagedAgentChatCompletionService.scala | 7.2 | Mixed | Cyclomatic Complexity: TypedTurnMapper.map (cyclomatic 17) |
| google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/VertexAIChatChunks.scala | 7.2 | Mixed | Cyclomatic Complexity: VertexAIChatChunks.toChatChunks (cyclomatic 16) |
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 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 58 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, 311 of 319 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — 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, 161 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/google/cloud/google-cloud-vertexai/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (12 contributor(s) across 1403 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 11 hold 1.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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. `openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala` 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 Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice and scala-guice, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
26 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ChatChunks.fromResponseEvents at 82. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AssembledChatCompletion.add at 23 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: openai-core/src/main/scala/io/cequence/openaiscala/domain/response/AssembledChatCompletion.scala (AssembledChatCompletion.add at 23). 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 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with ChatChunks.fromResponseEvents (cyclomatic 82). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
33 method(s) exceeded the cognitive complexity threshold of 15; the worst was ChatChunks.fromResponseEvents at 64.
What to do
- Bring the 33 bodies over 15 down to 15 or less in Cognitive Complexity — start with ChatChunks.fromResponseEvents (cognitive 64), JsonSchemaMacros.shapeExprOf (cognitive 56), RetryEngine.run (cognitive 38). — 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 33 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
27 god class(es) detected.
What to do
- Resolve the 20 FileTooLong finding(s) in God Classes — start with JsonFormats.scala (5), package.scala (2), AnthropicServiceImpl.scala. — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with ChatChunks.scala (2), VertexAIChatChunks.scala (2), RetryEngine.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with OpenAIServiceWrapper.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
71 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 55 of the 73 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 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with OpenAIGeminiChatCompletionService.scala, REDACTED, CreateChatToolCompletionWithFeedback.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with package.scala, CreateChatCompletionBatchWithCaching.scala, CreateVectorStoreFile.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with REDACTED, OctoMLCreateChatCompletionStreamed.scala, AnthropicCreateMessageWithImage.scala. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
12 production modules (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; 1 module(s) off the main sequence, with abstractness counted on 11 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 32 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with GeminiServiceImpl.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1536 test methods: 1536 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 1536 test case(s) across 156 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala (7×82=574); openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala (19×30=570); anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala (11×26=286)
What to do
- Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with package.scala (2), JsonSchemaReflectionHelper.scala (2), ChatChunks.scala. — One of this dimension's main actionable groups (16 warning-level).
D17 · Explicit Debt
41 deducted task-comment markers across 89323 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 39 TodoComment finding(s) in Explicit Debt — start with CreateChatCompletionSettings.scala (4), OpenAIService.scala (3), OpenAIServiceImpl.scala (3). — One of this dimension's main actionable groups (39 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with OpenAICountTokensServiceSpec.scala, OpenAIService.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
2 of 12 build units (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)
17 finding(s): 0 critical, 13 high, 4 medium, 0 low. 12 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 1 file(s) — `openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala` — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 12 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 (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
8 of 358 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is openai-core/src/main/scala/io/cequence/openaiscala/domain/Batch.scala. Counted over 358 of the 830 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: NonOpenAIModelId.scala↔DecisionProviderSettings.scala 90%; OpenAIServiceImpl.scala↔OpenAIServiceWrapper.scala 74%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with NonOpenAIModelId.scala, OpenAIServiceImpl.scala. — One of this dimension's main actionable groups (2 issue-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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `AnthropicService` declares 16 abstract members: `createMessage`, `createMessageStreamed`, `createMessageStreamedEvents`, `createSkill`, `listSkills`, `getSkill`, `deleteSkill`, `createSkillVersion`, `listSkillVersions`, `getSkillVersion`, `deleteSkillVersion`, `createFile`, `listFiles`, `getFileMetadata`, `downloadFile`, `deleteFile`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicService.scala:32
- `AnthropicSessionService` declares 17 abstract members: `createSession`, `listSessions`, `getSession`, `updateSession`, `deleteSession`, `archiveSession`, `sendSessionEvents`, `listSessionEvents`, `streamSessionEvents`, `addSessionResource`, `listSessionResources`, `getSessionResource`, `updateSessionResource`, `deleteSessionResource`, `listSessionThreads`, `getSessionThread`, `archiveSessionThread`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicSessionService.scala:30
- `GeminiService` declares 17 abstract members: `generateContent`, `generateContentStreamed`, `listModels`, `createCachedContent`, `updateCachedContent`, `listCachedContents`, `getCachedContent`, `deleteCachedContent`, `createBatchGenerateContent`, `getBatch`, `listBatches`, `cancelBatch`, `deleteBatch`, `uploadFile`, `getFile`, `deleteFile`, `downloadFile`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/GeminiService.scala:26
- `OpenAIAgentsService` declares 28 abstract members: `createAgent`, `listAgents`, `getAgent`, `updateAgent`, `deleteAgent`, `createAgentSession`, `listAgentSessions`, `getAgentSession`, `updateAgentSession`, `deleteAgentSession`, `sendAgentSessionEvents`, `listAgentSessionItems`, `listAgentSessionTurns`, `getAgentSessionTurn`, `listAgentSessionSubagents`, `getAgentSessionSubagent`, `listAgentSessionArtifacts`, `getAgentSessionArtifact`, `getAgentSessionArtifactContent`, `deleteAgentSessionArtifact`, `createAgentEnvironmentTemplate`, `listAgentEnvironmentTemplates`, `getAgentEnvironmentTemplate`, `updateAgentEnvironmentTemplate`, `deleteAgentEnvironmentTemplate`, `getAgentEnvironment`, `listAgentEnvironmentFiles`, `addAgentEnvironmentFile`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIAgentsService.scala:31
- `OpenAIService` declares 70 abstract members: `createCompletion`, `retrieveModel`, `createChatFunCompletion`, `createChatWebSearchCompletion`, `createEdit`, `createImage`, `createImageEdit`, `createImageVariation`, `createAudioSpeech`, `createAudioTranscription`, `createAudioTranslation`, `listFiles`, `uploadFile`, `uploadBatchFile`, `buildAndUploadBatchFile`, `buildBatchFileContent`, `deleteFile`, `retrieveFile`, `retrieveFileContent`, `retrieveFileContentAsSource`, `createFineTune`, `listFineTunes`, `retrieveFineTune`, `cancelFineTune`, `listFineTuneEvents`, `listFineTuneCheckpoints`, `deleteFineTuneModel`, `createModeration`, `createAssistant`, `listAssistants`, `retrieveAssistant`, `modifyAssistant`, `deleteAssistant`, `deleteAssistantFile`, `createThread`, `retrieveThread`, `modifyThread`, `deleteThread`, `createThreadMessage`, `retrieveThreadMessage`, and 30 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:52
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×10) — anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:12, anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:25, anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:31, …
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 7 of 13 project(s) that lack one — worth up to 1.1 pts.
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.
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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P5 · DR & Backup
What to do
- Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `runExperiment` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionJsonCaching.scala:290
- `run` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. (×2) — openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateCompletionStreamed.scala:25, openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateRunWithFunctionCall.scala:52
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 100 is called with an argument built by `verdict.flagged.map(_.name).mkString("…")` (line 102), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:100
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case scala.util.control.NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala:223
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:318
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn` at line 278 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/DecisionTranslation.scala:278
- `warn` at line 90 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/FailoverChain.scala:90
- `debug` at line 79 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/InferredJsonSchema.scala:79
- `debug` at line 449 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:449
- `warn` at line 460 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:460
- `debug` at line 470 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:470
- `warn` at line 629 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:629
- `error` at line 712 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:712
- `error` at line 737 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:737
- `debug` at line 754 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:754
- `debug` at line 824 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:824
- `debug` at line 837 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:837
- `debug` at line 869 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:869
- `debug` at line 879 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:879
- `debug` at line 66 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/ProducedReasoning.scala:66
- `debug` at line 70 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/ProducedReasoning.scala:70
- `warn` at line 93 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:93
- `warn` at line 100 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:100
- `info` at line 106 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:106
- `warn` at line 110 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:110
- `warn` at line 115 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:115
- `warn` at line 139 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:139
- `warn` at line 796 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala:796
- `warn` at line 801 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala:801
- `info` at line 402 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/GuardrailsAdapter.scala:402
- `warn` at line 443 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/GuardrailsAdapter.scala:443
- `warn` at line 24 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/MessageConversions.scala:24
- `warn` at line 336 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:336
- `warn` at line 429 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:429
- `warn` at line 634 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:634
- `warn` at line 646 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:646
- `warn` at line 218 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:218
- `debug` at line 244 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:244
- `warn` at line 522 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:522
- `warn` at line 631 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:631
- `warn` at line 119 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/JsonFormats.scala:119
- `warn` at line 701 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/JsonFormats.scala:701
- `debug` at line 140 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala:140
- `warn` at line 502 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala:502
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 467 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 | 53% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Strongest area. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 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
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — ~51411 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
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 11 pinned sbt dependency coordinate(s) were read from its 15 sbt build file(s), but Maven Central could not be asked for the licence of 8 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/typesafe/scala-logging/scala-logging_2.13/3.9.5/scala-logging_2.13-3.9.5.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 2 aggregate root(s) (entities that raise its domain events); 1225 value object(s); 28 domain event(s); a Domain/Aggregates/ValueObjects layer; a top-level openai-examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 467 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: NonOpenAIModelId.scala ↔ DecisionProviderSettings.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/NonOpenAIModelId.scala:1
- Boundary-crossing change coupling: OpenAIServiceImpl.scala ↔ OpenAIServiceWrapper.scala openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala:1
- REDACTED
Serious — 230 finding(s)
- TodoComment perplexity-sonar-client/src/main/scala/io/cequence/openaiscala/perplexity/domain/settings/SonarCreateChatCompletionSettings.scala:65
- TodoComment openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiCreateChatCompletion.scala:13
- TodoComment openai-examples/src/main/scala/io/cequence/openaiscala/examples/adapters/ChatCompletionInputAdapterForFireworksAI.scala:74
- TodoComment openai-count-tokens/src/test/scala/io/cequence/openaiscala/service/OpenAICountTokensServiceSpec.scala:146
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:1143
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:1376
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:1398
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionInterceptAdapter.scala:83
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatToCompletionAdapter.scala:113
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ServiceAdapters.scala:15
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/NonOpenAIModelId.scala:3
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/Run.scala:28
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/ThreadAndRun.scala:6
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/ThreadFullMessage.scala:37
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateChatCompletionSettings.scala:29
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateChatCompletionSettings.scala:113
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateChatCompletionSettings.scala:118
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateChatCompletionSettings.scala:122
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateFineTuneSettings.scala:29
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateRunSettings.scala:49
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/ResponseFormat.scala:35
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/tools/WebSearchTool.scala:56
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/response/ChatCompletionResponse.scala:227
- TodoComment openai-core/src/main/scala/io/cequence/openaiscala/domain/response/FineTuneJob.scala:20
- TodoComment openai-client-stream/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionStreamedRoundRobinService.scala:14
- FileTooLong: anthropic/JsonFormats.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/JsonFormats.scala
- FileTooLong: openaiscala/JsonFormats.scala openai-core/src/main/scala/io/cequence/openaiscala/JsonFormats.scala
- FileTooLong: impl/AnthropicServiceImpl.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceImpl.scala
- FileTooLong: impl/OpenAIGeminiChatCompletionService.scala google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala
- FileTooLong: impl/OpenAIServiceImpl.scala openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala
- FileTooLong: impl/package.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala
- FileTooLong: domain/NonOpenAIModelId.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/NonOpenAIModelId.scala
- FileTooLong: adapter/OpenAIServiceWrapper.scala openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIServiceWrapper.scala
- FileTooLong: responsesapi/JsonFormats.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/JsonFormats.scala
- FileTooLong: adapter/OpenAIAgentsChatCompletionService.scala openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala
- FileTooLong: adapter/ChatCompletionSettingsConversions.scala openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala
- FileTooLong: impl/OpenAIAnthropicManagedAgentChatCompletionService.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicManagedAgentChatCompletionService.scala
- FileTooLong: adapter/OpenAIResponsesChatCompletionService.scala openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala
- FileTooLong: impl/AnthropicBedrockServiceImpl.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicBedrockServiceImpl.scala
- FileTooLong: tools/JsonFormats.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/tools/JsonFormats.scala
- FileTooLong: service/OpenAIChatCompletionExtra.scala openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala
- FileTooLong: impl/package.scala google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala
- FileTooLong: agents/JsonFormats.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/agents/JsonFormats.scala
- FileTooLong: service/ChatChunks.scala openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala
- FileTooLong: service/AnthropicServiceFactory.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicServiceFactory.scala
- Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:176
- Hotspot: openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala:297
- Hotspot: anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1222
- Hotspot: google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:212
- Hotspot: typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala:106
- Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:531
- Hotspot: openai-core/src/main/scala-3/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala openai-core/src/main/scala-3/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:108
- Hotspot: anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala:442
- Hotspot: openai-core/src/main/scala-2/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala openai-core/src/main/scala-2/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:134
- Hotspot: openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionModelsLatencyBenchmark.scala openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionModelsLatencyBenchmark.scala:120
- Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:778
- Hotspot: google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:123
- Hotspot: openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/TypeSafeOpenAIAdapterScenarios.scala openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/TypeSafeOpenAIAdapterScenarios.scala:121
- Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala:114
- Hotspot: openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletionStreamed.scala openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletionStreamed.scala:70
- Hotspot: openai-core/src/main/scala/io/cequence/openaiscala/domain/response/AssembledChatCompletion.scala openai-core/src/main/scala/io/cequence/openaiscala/domain/response/AssembledChatCompletion.scala:46
- Duplicated block (13 lines × 2) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:1300
- Duplicated block (13 lines × 2) REDACTED:166
- Duplicated block (13 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletionWithFeedback.scala:96
- Duplicated block (13 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:304
- Duplicated block (13 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/adapters/ChatCompletionRouterAdapterWithMappedModelsExample.scala:77
- Duplicated block (13 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicBedrockCreateMessageStreamed.scala:28
- Duplicated block (9 lines × 2) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1061
- Duplicated block (9 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionBatchWithCaching.scala:63
- Duplicated block (9 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateVectorStoreFile.scala:10
- Duplicated block (9 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateChatCompletionWithMultipleNamedImagesAsFileContent.scala:59
- Duplicated block (9 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/managedagents/AnthropicManagedAgentsWithAuthTokenLive.scala:37
- Duplicated block (9 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiCreateChatCompletionWithMultipleNamedFilesAsFileContent.scala:64
- MethodTooLong: ChatChunks.toChatUsage openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:151
- MethodTooLong: ChatChunks.fromResponseEvents openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:176
- MethodTooLong: RetryEngine.run openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala:163
- MethodTooLong: VertexAIChatChunks.protoJson google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/VertexAIChatChunks.scala:25
- MethodTooLong: VertexAIChatChunks.toChatChunks google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/VertexAIChatChunks.scala:28
- Duplicated block (12 lines × 2) REDACTED:181
- Duplicated block (12 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/octoml/OctoMLCreateChatCompletionStreamed.scala:31
- Duplicated block (12 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateMessageWithImage.scala:36
- Duplicated block (12 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/ChatCompletionBatchCachingExperiment.scala:66
- Duplicated block (12 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/octoml/OctoMLCreateChatCompletion.scala:23
- Duplicated block (10 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala:807
- Duplicated block (10 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateImage.scala:19
- Duplicated block (10 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionVisionWithLocalFile.scala:25
- Duplicated block (10 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateChatCompletionWithOpenAIAdapterAndImage.scala:35
- Duplicated block (10 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/fireworksai/FireworksAIDocumentInlining.scala:34
- Duplicated block (15 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionWithLogprobs.scala:21
- Duplicated block (15 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateChatCompletionBatchWithCachingAndOpenAIAdapter.scala:104
- Duplicated block (15 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiCreateChatCompletionBatchWithOpenAIAdapter.scala:52
- Duplicated block (15 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiCreateChatToolCompletionStreamedWithOpenAIAdapter.scala:54
- Duplicated block (15 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlevertexai/GoogleVertexAICreateChatCompletionWithToolsCodeExecution.scala:36
- Duplicated block (15 lines × 3) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:640
- Duplicated block (15 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/adapters/ChatCompletionStreamedRouterExample.scala:146
- Duplicated block (15 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/managedagents/AnthropicDeploymentRunsLive.scala:26
- Duplicated block (15 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/cerebras/CerebrasCreateChatCompletionStreamed.scala:31
- Duplicated block (8 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala:402
- Duplicated block (8 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletionWithFeedback.scala:60
- Duplicated block (8 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/ListThreadMessages.scala:10
- Duplicated block (6 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:76
- Duplicated block (6 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:96
- Duplicated block (6 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/cerebras/CerebrasCreateChatCompletionWithFileContentAndPdf.scala:59
- Sync-over-async blocking openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionJsonCaching.scala:290
- Sync-over-async blocking openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateCompletionStreamed.scala:25
- Sync-over-async blocking openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateRunWithFunctionCall.scala:52
- FixmeComment openai-count-tokens/src/test/scala/io/cequence/openaiscala/service/OpenAICountTokensServiceSpec.scala:318
- FixmeComment openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:584
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:141
- Duplicated block (20 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionBatchSplitFlow.scala:45
- Duplicated block (16 lines × 2) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionErrorInterceptAdapter.scala:45
- Duplicated block (16 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/skills/AnthropicDeleteSkill.scala:22
- Duplicated block (5 lines × 3) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:306
- Duplicated block (5 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiCreateChatCompletionBatchWithCachingAndOpenAIAdapter.scala:123
- Duplicated block (5 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala:377
- Duplicated block (5 lines × 2) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIServiceImpl.scala:457
- Swallowed exception (caught, then discarded) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala:223
- Swallowed exception (caught, then discarded) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:318
- ChatChunks.fromResponseEvents (cyclomatic 82) openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:176
- JsonSchemaMacros.shapeExprOf (cyclomatic 49) openai-core/src/main/scala-3/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:108
- RetryEngine.run (cyclomatic 32) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala:163
- responsesapi.toTracedBlocks (cyclomatic 32) openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/package.scala:16
- ChatCompletionBodyMaker.createBodyParamsForChatCompletion (cyclomatic 30) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala:297
- SchemaQuestions.plan (cyclomatic 30) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala:106
- JsonSchemaReflection.shapeOf (cyclomatic 27) openai-core/src/main/scala-2/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:134
- StreamedChunkMapper.apply (cyclomatic 26) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1222
- TurnState.onEvent (cyclomatic 26) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:796
- OpenAIResponsesChatCompletionService.toResponsesSettings (cyclomatic 26) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:531
- impl.toAnthropicMessages (cyclomatic 22) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:137
- OpenAIAgentsChatCompletionService.toCreate (cyclomatic 22) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:275
- impl.toToolResultChunks (cyclomatic 20) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1026
- impl.toTracedBlocks (cyclomatic 20) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1542
- OpenAIResponsesChatCompletionService.buildResponsesRequest (cyclomatic 20) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:168
- SchemaQuestions.assemble (cyclomatic 20) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala:288
- impl.toAnthropicSettings (cyclomatic 19) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:598
- OpenAIGeminiChatCompletionService.chatChunksFlow (cyclomatic 19) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:212
- TypedTurnMapper.map (cyclomatic 17) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicManagedAgentChatCompletionService.scala:381
- DecisionImage.dimensions (cyclomatic 17) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/domain/DecisionImage.scala:353
- OpenAIAnthropicChatCompletionService.toAnthropicToolRequest (cyclomatic 16) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala:442
- VertexAIChatChunks.toChatChunks (cyclomatic 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/VertexAIChatChunks.scala:28
- impl.toVertexAIContents (cyclomatic 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:123
- JsonSchemaShape.toJsonSchema (cyclomatic 16) openai-core/src/main/scala/io/cequence/openaiscala/service/JsonSchemaShape.scala:114
- OpenAIAgentsChatCompletionService.toInput (cyclomatic 16) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:435
- OpenAIResponsesChatCompletionService.convertMessages (cyclomatic 16) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:443
- ChatChunks.fromResponseEvents (cognitive 64) openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:176
- JsonSchemaMacros.shapeExprOf (cognitive 56) openai-core/src/main/scala-3/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:108
- RetryEngine.run (cognitive 38) openai-core/src/main/scala/io/cequence/openaiscala/RetryEngine.scala:163
- SchemaQuestions.plan (cognitive 34) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala:106
- VertexAIChatChunks.toChatChunks (cognitive 33) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/VertexAIChatChunks.scala:28
- OpenAIAgentsChatCompletionService.toCreate (cognitive 33) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:275
- OpenAIGeminiChatCompletionService.chatChunksFlow (cognitive 32) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:212
- OpenAIResponsesChatCompletionService.toResponsesSettings (cognitive 32) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:531
- ChatCompletionBodyMaker.createBodyParamsForChatCompletion (cognitive 31) openai-client/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceImpl.scala:297
- responsesapi.toTracedBlocks (cognitive 31) openai-core/src/main/scala/io/cequence/openaiscala/domain/responsesapi/package.scala:16
- OpenAIResponsesChatCompletionService.buildResponsesRequest (cognitive 30) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIResponsesChatCompletionService.scala:168
- JsonSchemaReflection.shapeOf (cognitive 29) openai-core/src/main/scala-2/io/cequence/openaiscala/service/JsonSchemaReflectionHelper.scala:134
- JsonFormats.parseSystemInit (cognitive 28) claude-agent-client/src/main/scala/io/cequence/openaiscala/claudeagent/JsonFormats.scala:97
- impl.toAnthropicMessages (cognitive 26) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:137
- impl.toAnthropicSettings (cognitive 25) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:598
- OpenAIVertexAIChatCompletionService.deleteChatCompletionBatch (cognitive 24) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/OpenAIVertexAIChatCompletionService.scala:549
- OpenAIChatCompletionExtra.handleOutputJsonSchema (cognitive 24) openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:778
- OpenAIAnthropicChatCompletionService.toAnthropicToolRequest (cognitive 22) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala:442
- OpenAIAnthropicManagedAgentChatCompletionService.createChatToolCompletionStreamed (cognitive 21) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicManagedAgentChatCompletionService.scala:204
- SchemaQuestions.assemble (cognitive 21) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/SchemaQuestions.scala:288
- OpenAIAnthropicChatCompletionService.streamWithContinuation (cognitive 20) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicChatCompletionService.scala:349
- Anthropic.createBodyParamsForMessageCreation (cognitive 19) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/Anthropic.scala:67
- impl.toAnthropic (cognitive 19) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:274
- impl.toToolResultChunks (cognitive 19) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:1026
- JsonFormats.withChunkedContent (cognitive 19) openai-core/src/main/scala/io/cequence/openaiscala/JsonFormats.scala:180
- TurnState.onEvent (cognitive 19) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:796
- ChatChunks.fromOpenAIChunks (cognitive 18) openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:53
- DecisionImage.dimensions (cognitive 18) typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/domain/DecisionImage.scala:353
- TypedTurnMapper.map (cognitive 17) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/OpenAIAnthropicManagedAgentChatCompletionService.scala:381
- ServerSentEvents.dataOf (cognitive 17) openai-core/src/main/scala/io/cequence/openaiscala/service/ServerSentEvents.scala:146
- OpenAIAgentsChatCompletionService.toInput (cognitive 17) openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala:435
- impl.toVertexAIContents (cognitive 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:123
- impl.toThinkingBudget (cognitive 16) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/package.scala:391
- REDACTED
- REDACTED
- ClassTooLong: OpenAIServiceBatchExtWrapperImpl openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIServiceWrapper.scala:69
- TooManyMethods: ChatCompletionSettingsConversions openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala:18
- REDACTED
- Duplicated block (15–18 lines × 2) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:1130
- Duplicated block (11–16 lines × 2) openai-core/src/main/scala/io/cequence/openaiscala/service/ChatChunks.scala:152
- Duplicated block (12–15 lines × 2) google-vertexai-client/src/main/scala/io/cequence/openaiscala/vertexai/service/impl/OpenAIVertexAIChatCompletionService.scala:106
- Duplicated block (10 lines × 3) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:1058
- Duplicated block (6 lines × 3) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:280
- Duplicated block (57 lines × 2) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicScalaClientException.scala:9
- Near-duplicate member pair (81 shared lines) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:75
- Members sharing a duplicated core (8 members, 50+ identical tokens) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletion.scala:36
- Duplicated block (95–98 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateChatCompletionWithReasoningEffort.scala:49
- Duplicated block (71 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/skills/AnthropicCreateMessageWithPptxSkill.scala:35
- Duplicated block (59–71 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/skills/AnthropicCreateSkill.scala:17
- Duplicated block (43 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicFable51JsonSchemaReasoningAndToolChoiceLive.scala:112
- Duplicated block (38 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:105
- Duplicated block (34 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicFable51JsonSchemaReasoningAndToolChoiceLive.scala:68
- Duplicated block (27 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/skills/AnthropicCreateMessageWithPptxSkill.scala:65
- Duplicated block (27 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/tools/AnthropicCreateMessageWithWebFetch.scala:103
- Duplicated block (26 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletionStreamedWithApproval.scala:111
- Duplicated block (25–26 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/typesafe/DecisionContextLatencyBenchmark.scala:135
- Duplicated block (24 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatCompletionBatchSplitFlow.scala:66
- Duplicated block (17–18 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/ChatCompletionBatchCachingExperiment.scala:112
- Duplicated block (17 lines × 8) openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateChatToolCompletion.scala:44
- Duplicated block (16–17 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/googlegemini/GoogleGeminiGenerateContentCached.scala:75
- Duplicated block (17 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/scenario/Assistants.scala:22
- Duplicated block (21 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/anthropic/AnthropicCreateMessageWithTextBlockAndCitations.scala:49
- Duplicated block (10 lines × 7) openai-examples/src/main/scala/io/cequence/openaiscala/examples/cerebras/CerebrasCreateChatCompletion.scala:30
- Duplicated block (14 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/deepseek/DeepseekCreateChatCompletionStreamed.scala:26
- Duplicated block (9 lines × 3) openai-examples/src/main/scala/io/cequence/openaiscala/examples/responsesapi/CreateChatCompletionWithFileContentAndPdfViaResponsesAPI.scala:41
- Duplicated block (7 lines × 2) openai-examples/src/main/scala/io/cequence/openaiscala/examples/scenario/Assistants.scala:13
- Off the main sequence: core
- Low cohesion: GeminiServiceImpl (LCOM4 4) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/GeminiServiceImpl.scala:51
Minor — 74 finding(s)
- Interpolated log message defeats structured logging typesafe-client/src/main/scala/io/cequence/openaiscala/typesafe/service/impl/DecisionTranslation.scala:278
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/FailoverChain.scala:90
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/InferredJsonSchema.scala:79
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:449
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:460
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:470
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:629
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:712
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:737
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:754
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:824
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:837
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:869
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIChatCompletionExtra.scala:879
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/ProducedReasoning.scala:66
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/ProducedReasoning.scala:70
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:93
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:100
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/ToolApprovalLoop.scala:106
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:110
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:115
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:139
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala:796
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/ChatCompletionSettingsConversions.scala:801
- Interpolated log message defeats structured logging openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/GuardrailsAdapter.scala:402
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:12
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:25
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:31
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:37
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:43
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:49
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:55
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:61
- Disabled test anthropic-client/src/test/scala/io/cequence/openaiscala/anthropic/service/impl/AnthropicServiceSpec.scala:67
- Disabled test openai-client/src/test/scala/io/cequence/openaiscala/service/HandleOpenAIErrorCodesSpec.scala:9
- Orphaned file openai-core/src/main/scala/io/cequence/openaiscala/domain/Batch.scala:1
- Orphaned file openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateRunWithFunctionCall.scala:1
- Orphaned file openai-core/src/main/scala/io/cequence/openaiscala/domain/settings/CreateThreadAndRunSettings.scala:1
- Orphaned file openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateThreadAndRun.scala:1
- Orphaned file openai-core/src/main/scala/io/cequence/openaiscala/domain/response/Assistant.scala:1
- Orphaned file openai-core/src/main/scala/io/cequence/openaiscala/domain/Run.scala:1
- Orphaned file openai-core/src/main/scala/io/cequence/openaiscala/domain/ThreadAndRun.scala:1
- Orphaned file openai-examples/src/main/scala/io/cequence/openaiscala/examples/CreateRun.scala:1
- Fat interface: AnthropicService (16 abstract members) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicService.scala:32
- Fat interface: AnthropicSessionService (17 abstract members) anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/AnthropicSessionService.scala:30
- Fat interface: GeminiService (17 abstract members) google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/GeminiService.scala:26
- Fat interface: OpenAIAgentsService (28 abstract members) openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIAgentsService.scala:31
- Fat interface: OpenAIService (70 abstract members) openai-core/src/main/scala/io/cequence/openaiscala/service/OpenAIService.scala:52
- Duplicated predicate google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:1363
- Duplicated predicate google-gemini-client/src/main/scala/io/cequence/openaiscala/gemini/service/impl/OpenAIGeminiChatCompletionService.scala:1302
- Duplicated predicate anthropic-client/src/main/scala/io/cequence/openaiscala/anthropic/service/impl/package.scala:645
- Duplicated predicate openai-client-stream/src/main/scala/io/cequence/openaiscala/service/impl/OpenAIChatCompletionServiceStreamedExtraImpl.scala:99
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- Diagnostic log message is built whether or not it is wanted openai-core/src/main/scala/io/cequence/openaiscala/service/guardrails/ModelGuardrail.scala:100
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/GuardrailsStreamedAdapter.scala:379
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-b1bcbafdef2c4bf08ffa8d6db16facc9/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-b1bcbafdef2c4bf08ffa8d6db16facc9/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 . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-6534c10c110f46fbacb093f30aadd236 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `openai-core/src/main/scala/io/cequence/openaiscala/service/adapter/OpenAIAgentsChatCompletionService.scala` — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-6534c10c110f46fbacb093f30aadd236 | 0 | artifacts/raw/osv-scanner.json |