Executive summary
tailcallhq/forgecode falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 48 out of 100 and is rated Weak, and 64 of its 68 critical findings are security problems.
Accessibility, at 30, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 12 points. Automating accessibility checks comes next, worth about 7 points. Raising Accessibility to 70 would lift the score to about 62.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventeen secrets can leak from the build pipeline, and seven known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 116,561 lines, about €110,000 to rebuild.
If Accessibility rose from 30 to 70, the lowest score rated Strong, the score would rise from 48 to about 62.
New since the last survey: 8 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge crates/forge_markdown_stream/src/table.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 4 findings
- Churn × Complexity Hotspots · Hotspot: crates/forge_domain/src/provider.rs crates/forge_domain/src/provider.rs
- Churn × Complexity Hotspots · Hotspot: crates/forge_app/src/dto/anthropic/response.rs crates/forge_app/src/dto/anthropic/response.rs
- Change Coupling · Change coupling: forge_infra.rs ↔ attachment.rs crates/forge_infra/src/forge_infra.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €36,000 to €180,000, for 603 to 1,912 hours of work, about 0.7 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.7 at a score of 48. 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 | Large: 116,561 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 forge_app.dto.anthropic.error | 2 forge_config.config | 3 forge_domain.auth.auth_method | 4 forge_domain.auth.new_types | 5 forge_domain.env | 6 forge_domain.mcp | 7 forge_domain.transformer | 8 forge_app.dto.google.response | 9 forge_domain.conversation | 10 forge_domain.node | 11 forge_domain.tools.definition.name | 12 forge_domain.auth.credentials | 13 forge_domain.event | 14 forge_domain.tools.catalog | 15 forge_domain.tools.call.tool_call | 16 forge_domain.tools.result | 17 forge_repo.conversation.conversation_record | 18 forge_domain.message | 19 forge_domain.model | 20 forge_app.dto.openai.request | 21 forge_domain.context | 22 forge_app.dto.anthropic.request | 23 forge_app.dto.anthropic.response | 24 forge_domain.auth.auth_context | 25 forge_domain.provider | 26 forge_main.info | 27 forge_app.infra | 28 forge_domain.agent | 29 forge_domain.repo | 30 forge_api.api | 31 forge_app.services | 32 forge_app.tool_registry | 33 forge_domain.hook | 34 forge_infra.forge_infra | 35 forge_main.ui | 36 forge_repo.agent_definition | 37 forge_repo.provider.chat | 38 forge_api.forge_api | 39 forge_repo.forge_repo | 40 forge_services.forge_services |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 forge_app.dto.anthropic.error | ||||||||||||||||||||||||||||||||||||||||
| 2 forge_config.config | ||||||||||||||||||||||||||||||||||||||||
| 3 forge_domain.auth.auth_method | ||||||||||||||||||||||||||||||||||||||||
| 4 forge_domain.auth.new_types | ||||||||||||||||||||||||||||||||||||||||
| 5 forge_domain.env | ||||||||||||||||||||||||||||||||||||||||
| 6 forge_domain.mcp | ||||||||||||||||||||||||||||||||||||||||
| 7 forge_domain.transformer | ||||||||||||||||||||||||||||||||||||||||
| 8 forge_app.dto.google.response | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 9 forge_domain.conversation | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 forge_domain.node | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 forge_domain.tools.definition.name | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 forge_domain.auth.credentials | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 forge_domain.event | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 forge_domain.tools.catalog | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 forge_domain.tools.call.tool_call | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 forge_domain.tools.result | 1 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 17 forge_repo.conversation.conversation_record | 1 | 1 | 1 | 1 | 2 | 3 | 1 | 5 | 3 | 1 | ||||||||||||||||||||||||||||||
| 18 forge_domain.message | 2 | 1 | 1 | 1 | 1 | 7 | ||||||||||||||||||||||||||||||||||
| 19 forge_domain.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 forge_app.dto.openai.request | 1 | 2 | 1 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||||
| 21 forge_domain.context | 1 | 2 | 2 | 3 | 6 | 2 | 3 | 1 | 4 | 2 | ||||||||||||||||||||||||||||||
| 22 forge_app.dto.anthropic.request | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 forge_app.dto.anthropic.response | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 forge_domain.auth.auth_context | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 forge_domain.provider | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 forge_main.info | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 27 forge_app.infra | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 28 forge_domain.agent | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 forge_domain.repo | 1 | 2 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 30 forge_api.api | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 31 forge_app.services | 1 | 1 | 2 | 2 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||
| 32 forge_app.tool_registry | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 forge_domain.hook | 4 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 forge_infra.forge_infra | 1 | 1 | 1 | 2 | 1 | 1 | 14 | |||||||||||||||||||||||||||||||||
| 35 forge_main.ui | 1 | 1 | 1 | 3 | 2 | 1 | 1 | 1 | 3 | 4 | 1 | 1 | ||||||||||||||||||||||||||||
| 36 forge_repo.agent_definition | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 forge_repo.provider.chat | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 forge_api.forge_api | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 39 forge_repo.forge_repo | 1 | 2 | 2 | 1 | 2 | 1 | 1 | 1 | 2 | 16 | 9 | 1 | ||||||||||||||||||||||||||||
| 40 forge_services.forge_services | 2 | 1 | 28 |
8→18 forge_app.dto.google.response uses forge_domain.message part of a loop✕
- Connections
- 1 pair of types, where a type in forge_app.dto.google.response uses a type in forge_domain.message.
- The types involved
forge_app.dto.google.response.response$module→forge_domain.message.FinishReason
- Direction
- forge_app.dto.google.response uses forge_domain.message, so a change to forge_domain.message can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_domain.message.
- 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→22 forge_app.dto.google.response uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 1 pair of types, where a type in forge_app.dto.google.response uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_app.dto.google.response.Candidate→forge_app.dto.anthropic.request.Content
- Direction
- forge_app.dto.google.response uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_app.dto.anthropic.request.
- 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→23 forge_app.dto.google.response uses forge_app.dto.anthropic.response part of a loop✕
- Connections
- 2 pairs of types, where a type in forge_app.dto.google.response uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_app.dto.google.response.Model→forge_app.dto.anthropic.response.Modelforge_app.dto.google.response.PingEvent→forge_app.dto.anthropic.response.StringOrF64
- Direction
- forge_app.dto.google.response uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_app.dto.anthropic.response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→17 forge_domain.conversation uses forge_repo.conversation.conversation_record part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.conversation uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.conversation.Conversation→forge_repo.conversation.conversation_record.ConversationRecord
- Direction
- forge_domain.conversation uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.conversation, while a change to forge_domain.conversation can't break forge_repo.conversation.conversation_record.
- 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→21 forge_domain.conversation uses forge_domain.context part of a loop✕
- Connections
- 3 pairs of types, where a type in forge_domain.conversation uses a type in forge_domain.context.
- The types involved
forge_domain.conversation.Conversation→forge_domain.context.Contextforge_domain.conversation.Conversation→forge_domain.context.ContextMessageforge_domain.conversation.Conversation→forge_domain.context.TokenCount
- Direction
- forge_domain.conversation uses forge_domain.context, so a change to forge_domain.context can break forge_domain.conversation, while a change to forge_domain.conversation can't break forge_domain.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→23 forge_domain.conversation uses forge_app.dto.anthropic.response part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.conversation uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_domain.conversation.Conversation→forge_app.dto.anthropic.response.Usage
- Direction
- forge_domain.conversation uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_domain.conversation, while a change to forge_domain.conversation can't break forge_app.dto.anthropic.response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→4 forge_domain.node uses forge_domain.auth.new_types✕
- Connections
- 1 pair of types, where a type in forge_domain.node uses a type in forge_domain.auth.new_types.
- The types involved
forge_domain.node.WorkspaceAuth→forge_domain.auth.new_types.ApiKey
- Direction
- forge_domain.node uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.node, while a change to forge_domain.node can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_domain.node uses a module listed above it, which is the healthy direction.
11→17 forge_domain.tools.definition.name uses forge_repo.conversation.conversation_record part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.definition.name uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.tools.definition.name.ToolName→forge_repo.conversation.conversation_record.ToolNameRecord
- Direction
- forge_domain.tools.definition.name uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.tools.definition.name, while a change to forge_domain.tools.definition.name can't break forge_repo.conversation.conversation_record.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→4 forge_domain.auth.credentials uses forge_domain.auth.new_types✕
- Connections
- 4 pairs of types, where a type in forge_domain.auth.credentials uses a type in forge_domain.auth.new_types.
- The types involved
forge_domain.auth.credentials.AuthCredential→forge_domain.auth.new_types.ApiKeyforge_domain.auth.credentials.AuthDetails→forge_domain.auth.new_types.ApiKeyforge_domain.auth.credentials.OAuthTokens→forge_domain.auth.new_types.AccessTokenforge_domain.auth.credentials.OAuthTokens→forge_domain.auth.new_types.RefreshToken
- Direction
- forge_domain.auth.credentials uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_domain.auth.credentials uses a module listed above it, which is the healthy direction.
12→10 forge_domain.auth.credentials uses forge_domain.node✕
- Connections
- 1 pair of types, where a type in forge_domain.auth.credentials uses a type in forge_domain.node.
- The types involved
forge_domain.auth.credentials.AuthDetails→forge_domain.node.WorkspaceAuth
- Direction
- forge_domain.auth.credentials uses forge_domain.node, so a change to forge_domain.node can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.node.
- Position
- Below the diagonal: forge_domain.auth.credentials uses a module listed above it, which is the healthy direction.
12→25 forge_domain.auth.credentials uses forge_domain.provider part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.auth.credentials uses a type in forge_domain.provider.
- The types involved
forge_domain.auth.credentials.AuthCredential→forge_domain.provider.ProviderId
- Direction
- forge_domain.auth.credentials uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.provider.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→11 forge_domain.event uses forge_domain.tools.definition.name✕
- Connections
- 2 pairs of types, where a type in forge_domain.event uses a type in forge_domain.tools.definition.name.
- The types involved
forge_domain.event.Event→forge_domain.tools.definition.name.NamedToolforge_domain.event.Event→forge_domain.tools.definition.name.ToolName
- Direction
- forge_domain.event uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.event, while a change to forge_domain.event can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_domain.event uses a module listed above it, which is the healthy direction.
13→17 forge_domain.event uses forge_repo.conversation.conversation_record part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.event uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.event.EventValue→forge_repo.conversation.conversation_record.EventValueRecord
- Direction
- forge_domain.event uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.event, while a change to forge_domain.event can't break forge_repo.conversation.conversation_record.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→5 forge_domain.tools.catalog uses forge_domain.env✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.catalog uses a type in forge_domain.env.
- The types involved
forge_domain.tools.catalog.ToolCatalog→forge_domain.env.Environment
- Direction
- forge_domain.tools.catalog uses forge_domain.env, so a change to forge_domain.env can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.env.
- Position
- Below the diagonal: forge_domain.tools.catalog uses a module listed above it, which is the healthy direction.
14→11 forge_domain.tools.catalog uses forge_domain.tools.definition.name✕
- Connections
- 2 pairs of types, where a type in forge_domain.tools.catalog uses a type in forge_domain.tools.definition.name.
- The types involved
forge_domain.tools.catalog.ToolCatalog→forge_domain.tools.definition.name.ToolNameforge_domain.tools.catalog.catalog$module→forge_domain.tools.definition.name.ToolName
- Direction
- forge_domain.tools.catalog uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_domain.tools.catalog uses a module listed above it, which is the healthy direction.
14→15 forge_domain.tools.catalog uses forge_domain.tools.call.tool_call part of a loop✕
- Connections
- 2 pairs of types, where a type in forge_domain.tools.catalog uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_domain.tools.catalog.AgentInput→forge_domain.tools.call.tool_call.ToolCallFullforge_domain.tools.catalog.ToolCatalog→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_domain.tools.catalog uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.tools.call.tool_call.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→22 forge_domain.tools.catalog uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.catalog uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_domain.tools.catalog.ToolCatalog→forge_app.dto.anthropic.request.ToolDefinition
- Direction
- forge_domain.tools.catalog uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_app.dto.anthropic.request.
- 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→11 forge_domain.tools.call.tool_call uses forge_domain.tools.definition.name✕
- Connections
- 3 pairs of types, where a type in forge_domain.tools.call.tool_call uses a type in forge_domain.tools.definition.name.
- The types involved
forge_domain.tools.call.tool_call.ToolCallFull→forge_domain.tools.definition.name.ToolNameforge_domain.tools.call.tool_call.ToolCallPart→forge_domain.tools.definition.name.ToolNameforge_domain.tools.call.tool_call.ToolErrorTracker→forge_domain.tools.definition.name.ToolName
- Direction
- forge_domain.tools.call.tool_call uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.call.tool_call, while a change to forge_domain.tools.call.tool_call can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_domain.tools.call.tool_call uses a module listed above it, which is the healthy direction.
15→14 forge_domain.tools.call.tool_call uses forge_domain.tools.catalog✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.call.tool_call uses a type in forge_domain.tools.catalog.
- The types involved
forge_domain.tools.call.tool_call.ToolCallFull→forge_domain.tools.catalog.ToolCatalog
- Direction
- forge_domain.tools.call.tool_call uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_domain.tools.call.tool_call, while a change to forge_domain.tools.call.tool_call can't break forge_domain.tools.catalog.
- Position
- Below the diagonal: forge_domain.tools.call.tool_call uses a module listed above it, which is the healthy direction.
15→17 forge_domain.tools.call.tool_call uses forge_repo.conversation.conversation_record part of a loop✕
- Connections
- 2 pairs of types, where a type in forge_domain.tools.call.tool_call uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.tools.call.tool_call.ToolCallFull→forge_repo.conversation.conversation_record.ToolCallFullRecordforge_domain.tools.call.tool_call.ToolCallId→forge_repo.conversation.conversation_record.ToolCallIdRecord
- Direction
- forge_domain.tools.call.tool_call uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.tools.call.tool_call, while a change to forge_domain.tools.call.tool_call can't break forge_repo.conversation.conversation_record.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 forge_domain.tools.result uses forge_app.dto.anthropic.error✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.result uses a type in forge_app.dto.anthropic.error.
- The types involved
forge_domain.tools.result.ToolResult→forge_app.dto.anthropic.error.Error
- Direction
- forge_domain.tools.result uses forge_app.dto.anthropic.error, so a change to forge_app.dto.anthropic.error can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_app.dto.anthropic.error.
- Position
- Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
16→9 forge_domain.tools.result uses forge_domain.conversation✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.result uses a type in forge_domain.conversation.
- The types involved
forge_domain.tools.result.ToolOutput→forge_domain.conversation.ConversationId
- Direction
- forge_domain.tools.result uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
16→11 forge_domain.tools.result uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_domain.tools.result uses a type in forge_domain.tools.definition.name.
- The types involved
forge_domain.tools.result.ToolResult→forge_domain.tools.definition.name.ToolName
- Direction
- forge_domain.tools.result uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
16→15 forge_domain.tools.result uses forge_domain.tools.call.tool_call✕
- Connections
- 2 pairs of types, where a type in forge_domain.tools.result uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_domain.tools.result.ToolResult→forge_domain.tools.call.tool_call.ToolCallFullforge_domain.tools.result.ToolResult→forge_domain.tools.call.tool_call.ToolCallId
- Direction
- forge_domain.tools.result uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
16→17 forge_domain.tools.result uses forge_repo.conversation.conversation_record part of a loop✕
- Connections
- 3 pairs of types, where a type in forge_domain.tools.result uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.tools.result.ToolOutput→forge_repo.conversation.conversation_record.ToolOutputRecordforge_domain.tools.result.ToolResult→forge_repo.conversation.conversation_record.ToolResultRecordforge_domain.tools.result.ToolValue→forge_repo.conversation.conversation_record.ToolValueRecord
- Direction
- forge_domain.tools.result uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_repo.conversation.conversation_record.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→5 forge_repo.conversation.conversation_record uses forge_domain.env✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.env.
- The types involved
forge_repo.conversation.conversation_record.ConversationRecord→forge_domain.env.WorkspaceHash
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.env, so a change to forge_domain.env can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.env.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→9 forge_repo.conversation.conversation_record uses forge_domain.conversation✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.conversation.
- The types involved
forge_repo.conversation.conversation_record.ConversationRecord→forge_domain.conversation.Conversation
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→11 forge_repo.conversation.conversation_record uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.tools.definition.name.
- The types involved
forge_repo.conversation.conversation_record.ToolNameRecord→forge_domain.tools.definition.name.ToolName
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→13 forge_repo.conversation.conversation_record uses forge_domain.event✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.event.
- The types involved
forge_repo.conversation.conversation_record.EventValueRecord→forge_domain.event.EventValue
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.event, so a change to forge_domain.event can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.event.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→15 forge_repo.conversation.conversation_record uses forge_domain.tools.call.tool_call✕
- Connections
- 2 pairs of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_repo.conversation.conversation_record.ToolCallFullRecord→forge_domain.tools.call.tool_call.ToolCallFullforge_repo.conversation.conversation_record.ToolCallIdRecord→forge_domain.tools.call.tool_call.ToolCallId
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→16 forge_repo.conversation.conversation_record uses forge_domain.tools.result✕
- Connections
- 3 pairs of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.tools.result.
- The types involved
forge_repo.conversation.conversation_record.ToolOutputRecord→forge_domain.tools.result.ToolOutputforge_repo.conversation.conversation_record.ToolResultRecord→forge_domain.tools.result.ToolResultforge_repo.conversation.conversation_record.ToolValueRecord→forge_domain.tools.result.ToolValue
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
17→19 forge_repo.conversation.conversation_record uses forge_domain.model part of a loop✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.model.
- The types involved
forge_repo.conversation.conversation_record.ModelIdRecord→forge_domain.model.ModelId
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.model, so a change to forge_domain.model can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→21 forge_repo.conversation.conversation_record uses forge_domain.context part of a loop✕
- Connections
- 5 pairs of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_domain.context.
- The types involved
forge_repo.conversation.conversation_record.ContextMessageRecord→forge_domain.context.MessageEntryforge_repo.conversation.conversation_record.ContextMessageValueRecord→forge_domain.context.ContextMessageforge_repo.conversation.conversation_record.ContextRecord→forge_domain.context.Contextforge_repo.conversation.conversation_record.TextMessageRecord→forge_domain.context.TextMessageforge_repo.conversation.conversation_record.TokenCountRecord→forge_domain.context.TokenCount
- Direction
- forge_repo.conversation.conversation_record uses forge_domain.context, so a change to forge_domain.context can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→22 forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 3 pairs of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_repo.conversation.conversation_record.RoleRecord→forge_app.dto.anthropic.request.Roleforge_repo.conversation.conversation_record.ToolChoiceRecord→forge_app.dto.anthropic.request.ToolChoiceforge_repo.conversation.conversation_record.ToolDefinitionRecord→forge_app.dto.anthropic.request.ToolDefinition
- Direction
- forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_app.dto.anthropic.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.response part of a loop✕
- Connections
- 1 pair of types, where a type in forge_repo.conversation.conversation_record uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_repo.conversation.conversation_record.UsageRecord→forge_app.dto.anthropic.response.Usage
- Direction
- forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_app.dto.anthropic.response.
- 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→8 forge_domain.message uses forge_app.dto.google.response✕
- Connections
- 2 pairs of types, where a type in forge_domain.message uses a type in forge_app.dto.google.response.
- The types involved
forge_domain.message.ChatCompletionMessage→forge_app.dto.google.response.Candidateforge_domain.message.ChatCompletionMessage→forge_app.dto.google.response.Response
- Direction
- forge_domain.message uses forge_app.dto.google.response, so a change to forge_app.dto.google.response can break forge_domain.message, while a change to forge_domain.message can't break forge_app.dto.google.response.
- Position
- Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
18→15 forge_domain.message uses forge_domain.tools.call.tool_call✕
- Connections
- 1 pair of types, where a type in forge_domain.message uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_domain.message.ChatCompletionMessageFull→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_domain.message uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
18→17 forge_domain.message uses forge_repo.conversation.conversation_record✕
- Connections
- 1 pair of types, where a type in forge_domain.message uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.message.Usage→forge_repo.conversation.conversation_record.UsageRecord
- Direction
- forge_domain.message uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.message, while a change to forge_domain.message can't break forge_repo.conversation.conversation_record.
- Position
- Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
18→21 forge_domain.message uses forge_domain.context part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.message uses a type in forge_domain.context.
- The types involved
forge_domain.message.Usage→forge_domain.context.TokenCount
- Direction
- forge_domain.message uses forge_domain.context, so a change to forge_domain.context can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→22 forge_domain.message uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 1 pair of types, where a type in forge_domain.message uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_domain.message.ChatCompletionMessage→forge_app.dto.anthropic.request.Content
- Direction
- forge_domain.message uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_domain.message, while a change to forge_domain.message can't break forge_app.dto.anthropic.request.
- 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→23 forge_domain.message uses forge_app.dto.anthropic.response part of a loop✕
- Connections
- 7 pairs of types, where a type in forge_domain.message uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_domain.message.ChatCompletionMessage→forge_app.dto.anthropic.response.ContentBlockforge_domain.message.ChatCompletionMessage→forge_app.dto.anthropic.response.Eventforge_domain.message.ChatCompletionMessage→forge_app.dto.anthropic.response.EventDataforge_domain.message.ChatCompletionMessage→forge_app.dto.anthropic.response.Usageforge_domain.message.ChatCompletionMessageFull→forge_app.dto.anthropic.response.Usageforge_domain.message.FinishReason→forge_app.dto.anthropic.response.StopReasonforge_domain.message.Usage→forge_app.dto.anthropic.response.Usage
- Direction
- forge_domain.message uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_domain.message, while a change to forge_domain.message can't break forge_app.dto.anthropic.response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→17 forge_domain.model uses forge_repo.conversation.conversation_record✕
- Connections
- 1 pair of types, where a type in forge_domain.model uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.model.ModelId→forge_repo.conversation.conversation_record.ModelIdRecord
- Direction
- forge_domain.model uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.model, while a change to forge_domain.model can't break forge_repo.conversation.conversation_record.
- Position
- Below the diagonal: forge_domain.model uses a module listed above it, which is the healthy direction.
20→11 forge_app.dto.openai.request uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_app.dto.openai.request uses a type in forge_domain.tools.definition.name.
- The types involved
forge_app.dto.openai.request.Message→forge_domain.tools.definition.name.ToolName
- Direction
- forge_app.dto.openai.request uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
20→15 forge_app.dto.openai.request uses forge_domain.tools.call.tool_call✕
- Connections
- 2 pairs of types, where a type in forge_app.dto.openai.request uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_app.dto.openai.request.Message→forge_domain.tools.call.tool_call.ToolCallIdforge_app.dto.openai.request.request$module→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_app.dto.openai.request uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
20→16 forge_app.dto.openai.request uses forge_domain.tools.result✕
- Connections
- 1 pair of types, where a type in forge_app.dto.openai.request uses a type in forge_domain.tools.result.
- The types involved
forge_app.dto.openai.request.MessageContent→forge_domain.tools.result.ToolResult
- Direction
- forge_app.dto.openai.request uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
20→19 forge_app.dto.openai.request uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_app.dto.openai.request uses a type in forge_domain.model.
- The types involved
forge_app.dto.openai.request.Request→forge_domain.model.ModelId
- Direction
- forge_app.dto.openai.request uses forge_domain.model, so a change to forge_domain.model can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.model.
- Position
- Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
20→21 forge_app.dto.openai.request uses forge_domain.context part of a loop✕
- Connections
- 2 pairs of types, where a type in forge_app.dto.openai.request uses a type in forge_domain.context.
- The types involved
forge_app.dto.openai.request.Message→forge_domain.context.ContextMessageforge_app.dto.openai.request.Request→forge_domain.context.Context
- Direction
- forge_app.dto.openai.request uses forge_domain.context, so a change to forge_domain.context can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 forge_app.dto.openai.request uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 5 pairs of types, where a type in forge_app.dto.openai.request uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_app.dto.openai.request.Message→forge_app.dto.anthropic.request.Roleforge_app.dto.openai.request.Request→forge_app.dto.anthropic.request.Messageforge_app.dto.openai.request.Request→forge_app.dto.anthropic.request.ToolChoiceforge_app.dto.openai.request.Role→forge_app.dto.anthropic.request.Roleforge_app.dto.openai.request.Tool→forge_app.dto.anthropic.request.ToolDefinition
- Direction
- forge_app.dto.openai.request uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_app.dto.anthropic.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→9 forge_domain.context uses forge_domain.conversation✕
- Connections
- 1 pair of types, where a type in forge_domain.context uses a type in forge_domain.conversation.
- The types involved
forge_domain.context.Context→forge_domain.conversation.ConversationId
- Direction
- forge_domain.context uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→13 forge_domain.context uses forge_domain.event✕
- Connections
- 2 pairs of types, where a type in forge_domain.context uses a type in forge_domain.event.
- The types involved
forge_domain.context.ContextMessage→forge_domain.event.EventValueforge_domain.context.TextMessage→forge_domain.event.EventValue
- Direction
- forge_domain.context uses forge_domain.event, so a change to forge_domain.event can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.event.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→15 forge_domain.context uses forge_domain.tools.call.tool_call✕
- Connections
- 2 pairs of types, where a type in forge_domain.context uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_domain.context.ContextMessage→forge_domain.tools.call.tool_call.ToolCallFullforge_domain.context.TextMessage→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_domain.context uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→16 forge_domain.context uses forge_domain.tools.result✕
- Connections
- 3 pairs of types, where a type in forge_domain.context uses a type in forge_domain.tools.result.
- The types involved
forge_domain.context.Context→forge_domain.tools.result.ToolResultforge_domain.context.ContextMessage→forge_domain.tools.result.ToolResultforge_domain.context.context$module→forge_domain.tools.result.ToolOutput
- Direction
- forge_domain.context uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→17 forge_domain.context uses forge_repo.conversation.conversation_record✕
- Connections
- 6 pairs of types, where a type in forge_domain.context uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.context.Context→forge_repo.conversation.conversation_record.ContextRecordforge_domain.context.ContextMessage→forge_repo.conversation.conversation_record.ContextMessageValueRecordforge_domain.context.MessageEntry→forge_repo.conversation.conversation_record.ContextMessageRecordforge_domain.context.Role→forge_repo.conversation.conversation_record.RoleRecordforge_domain.context.TextMessage→forge_repo.conversation.conversation_record.TextMessageRecordforge_domain.context.TokenCount→forge_repo.conversation.conversation_record.TokenCountRecord
- Direction
- forge_domain.context uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.context, while a change to forge_domain.context can't break forge_repo.conversation.conversation_record.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→18 forge_domain.context uses forge_domain.message✕
- Connections
- 2 pairs of types, where a type in forge_domain.context uses a type in forge_domain.message.
- The types involved
forge_domain.context.Context→forge_domain.message.MessagePhaseforge_domain.context.TextMessage→forge_domain.message.MessagePhase
- Direction
- forge_domain.context uses forge_domain.message, so a change to forge_domain.message can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.message.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→19 forge_domain.context uses forge_domain.model✕
- Connections
- 3 pairs of types, where a type in forge_domain.context uses a type in forge_domain.model.
- The types involved
forge_domain.context.Context→forge_domain.model.ModelIdforge_domain.context.ContextMessage→forge_domain.model.ModelIdforge_domain.context.TextMessage→forge_domain.model.ModelId
- Direction
- forge_domain.context uses forge_domain.model, so a change to forge_domain.model can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.model.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→20 forge_domain.context uses forge_app.dto.openai.request✕
- Connections
- 1 pair of types, where a type in forge_domain.context uses a type in forge_app.dto.openai.request.
- The types involved
forge_domain.context.Context→forge_app.dto.openai.request.ResponseFormat
- Direction
- forge_domain.context uses forge_app.dto.openai.request, so a change to forge_app.dto.openai.request can break forge_domain.context, while a change to forge_domain.context can't break forge_app.dto.openai.request.
- Position
- Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
21→22 forge_domain.context uses forge_app.dto.anthropic.request part of a loop✕
- Connections
- 4 pairs of types, where a type in forge_domain.context uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_domain.context.Context→forge_app.dto.anthropic.request.ToolChoiceforge_domain.context.Context→forge_app.dto.anthropic.request.ToolDefinitionforge_domain.context.ContextMessage→forge_app.dto.anthropic.request.Roleforge_domain.context.TextMessage→forge_app.dto.anthropic.request.Role
- Direction
- forge_domain.context uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_domain.context, while a change to forge_domain.context can't break forge_app.dto.anthropic.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→23 forge_domain.context uses forge_app.dto.anthropic.response part of a loop✕
- Connections
- 2 pairs of types, where a type in forge_domain.context uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_domain.context.Context→forge_app.dto.anthropic.response.Usageforge_domain.context.MessageEntry→forge_app.dto.anthropic.response.Usage
- Direction
- forge_domain.context uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_domain.context, while a change to forge_domain.context can't break forge_app.dto.anthropic.response.
- 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→15 forge_app.dto.anthropic.request uses forge_domain.tools.call.tool_call✕
- Connections
- 1 pair of types, where a type in forge_app.dto.anthropic.request uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_app.dto.anthropic.request.Content→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_app.dto.anthropic.request uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
22→16 forge_app.dto.anthropic.request uses forge_domain.tools.result✕
- Connections
- 1 pair of types, where a type in forge_app.dto.anthropic.request uses a type in forge_domain.tools.result.
- The types involved
forge_app.dto.anthropic.request.Content→forge_domain.tools.result.ToolResult
- Direction
- forge_app.dto.anthropic.request uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
22→21 forge_app.dto.anthropic.request uses forge_domain.context✕
- Connections
- 2 pairs of types, where a type in forge_app.dto.anthropic.request uses a type in forge_domain.context.
- The types involved
forge_app.dto.anthropic.request.Message→forge_domain.context.ContextMessageforge_app.dto.anthropic.request.Request→forge_domain.context.Context
- Direction
- forge_app.dto.anthropic.request uses forge_domain.context, so a change to forge_domain.context can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.context.
- Position
- Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
23→8 forge_app.dto.anthropic.response uses forge_app.dto.google.response✕
- Connections
- 1 pair of types, where a type in forge_app.dto.anthropic.response uses a type in forge_app.dto.google.response.
- The types involved
forge_app.dto.anthropic.response.Usage→forge_app.dto.google.response.UsageMetadata
- Direction
- forge_app.dto.anthropic.response uses forge_app.dto.google.response, so a change to forge_app.dto.google.response can break forge_app.dto.anthropic.response, while a change to forge_app.dto.anthropic.response can't break forge_app.dto.google.response.
- Position
- Below the diagonal: forge_app.dto.anthropic.response uses a module listed above it, which is the healthy direction.
23→22 forge_app.dto.anthropic.response uses forge_app.dto.anthropic.request✕
- Connections
- 1 pair of types, where a type in forge_app.dto.anthropic.response uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_app.dto.anthropic.response.MessageStart→forge_app.dto.anthropic.request.Role
- Direction
- forge_app.dto.anthropic.response uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.anthropic.response, while a change to forge_app.dto.anthropic.response can't break forge_app.dto.anthropic.request.
- Position
- Below the diagonal: forge_app.dto.anthropic.response uses a module listed above it, which is the healthy direction.
24→4 forge_domain.auth.auth_context uses forge_domain.auth.new_types✕
- Connections
- 8 pairs of types, where a type in forge_domain.auth.auth_context uses a type in forge_domain.auth.new_types.
- The types involved
forge_domain.auth.auth_context.ApiKeyRequest→forge_domain.auth.new_types.ApiKeyforge_domain.auth.auth_context.ApiKeyRequest→forge_domain.auth.new_types.URLParamSpecforge_domain.auth.auth_context.ApiKeyResponse→forge_domain.auth.new_types.ApiKeyforge_domain.auth.auth_context.CodeRequest→forge_domain.auth.new_types.PkceVerifierforge_domain.auth.auth_context.CodeRequest→forge_domain.auth.new_types.Stateforge_domain.auth.auth_context.CodeResponse→forge_domain.auth.new_types.AuthorizationCodeforge_domain.auth.auth_context.DeviceCodeRequest→forge_domain.auth.new_types.DeviceCodeforge_domain.auth.auth_context.DeviceCodeRequest→forge_domain.auth.new_types.UserCode
- Direction
- forge_domain.auth.auth_context uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.auth.auth_context, while a change to forge_domain.auth.auth_context can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_domain.auth.auth_context uses a module listed above it, which is the healthy direction.
24→8 forge_domain.auth.auth_context uses forge_app.dto.google.response✕
- Connections
- 1 pair of types, where a type in forge_domain.auth.auth_context uses a type in forge_app.dto.google.response.
- The types involved
forge_domain.auth.auth_context.AuthContext→forge_app.dto.google.response.Response
- Direction
- forge_domain.auth.auth_context uses forge_app.dto.google.response, so a change to forge_app.dto.google.response can break forge_domain.auth.auth_context, while a change to forge_domain.auth.auth_context can't break forge_app.dto.google.response.
- Position
- Below the diagonal: forge_domain.auth.auth_context uses a module listed above it, which is the healthy direction.
24→22 forge_domain.auth.auth_context uses forge_app.dto.anthropic.request✕
- Connections
- 1 pair of types, where a type in forge_domain.auth.auth_context uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_domain.auth.auth_context.AuthContext→forge_app.dto.anthropic.request.Request
- Direction
- forge_domain.auth.auth_context uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_domain.auth.auth_context, while a change to forge_domain.auth.auth_context can't break forge_app.dto.anthropic.request.
- Position
- Below the diagonal: forge_domain.auth.auth_context uses a module listed above it, which is the healthy direction.
25→3 forge_domain.provider uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_domain.provider uses a type in forge_domain.auth.auth_method.
- The types involved
forge_domain.provider.Provider→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_domain.provider uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
25→4 forge_domain.provider uses forge_domain.auth.new_types✕
- Connections
- 2 pairs of types, where a type in forge_domain.provider uses a type in forge_domain.auth.new_types.
- The types involved
forge_domain.provider.Provider→forge_domain.auth.new_types.ApiKeyforge_domain.provider.Provider→forge_domain.auth.new_types.URLParamSpec
- Direction
- forge_domain.provider uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
25→12 forge_domain.provider uses forge_domain.auth.credentials✕
- Connections
- 1 pair of types, where a type in forge_domain.provider uses a type in forge_domain.auth.credentials.
- The types involved
forge_domain.provider.Provider→forge_domain.auth.credentials.AuthCredential
- Direction
- forge_domain.provider uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.credentials.
- Position
- Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
25→23 forge_domain.provider uses forge_app.dto.anthropic.response✕
- Connections
- 1 pair of types, where a type in forge_domain.provider uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_domain.provider.ProviderModels→forge_app.dto.anthropic.response.Model
- Direction
- forge_domain.provider uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_domain.provider, while a change to forge_domain.provider can't break forge_app.dto.anthropic.response.
- Position
- Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
26→2 forge_main.info uses forge_config.config✕
- Connections
- 1 pair of types, where a type in forge_main.info uses a type in forge_config.config.
- The types involved
forge_main.info.Info→forge_config.config.ForgeConfig
- Direction
- forge_main.info uses forge_config.config, so a change to forge_config.config can break forge_main.info, while a change to forge_main.info can't break forge_config.config.
- Position
- Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
26→5 forge_main.info uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_main.info uses a type in forge_domain.env.
- The types involved
forge_main.info.Info→forge_domain.env.Environmentforge_main.info.info$module→forge_domain.env.Environment
- Direction
- forge_main.info uses forge_domain.env, so a change to forge_domain.env can break forge_main.info, while a change to forge_main.info can't break forge_domain.env.
- Position
- Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
26→9 forge_main.info uses forge_domain.conversation✕
- Connections
- 1 pair of types, where a type in forge_main.info uses a type in forge_domain.conversation.
- The types involved
forge_main.info.Info→forge_domain.conversation.Conversation
- Direction
- forge_main.info uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_main.info, while a change to forge_main.info can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
26→21 forge_main.info uses forge_domain.context✕
- Connections
- 1 pair of types, where a type in forge_main.info uses a type in forge_domain.context.
- The types involved
forge_main.info.info$module→forge_domain.context.ContextMessage
- Direction
- forge_main.info uses forge_domain.context, so a change to forge_domain.context can break forge_main.info, while a change to forge_main.info can't break forge_domain.context.
- Position
- Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
26→23 forge_main.info uses forge_app.dto.anthropic.response✕
- Connections
- 2 pairs of types, where a type in forge_main.info uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_main.info.Info→forge_app.dto.anthropic.response.Usageforge_main.info.info$module→forge_app.dto.anthropic.response.Usage
- Direction
- forge_main.info uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_main.info, while a change to forge_main.info can't break forge_app.dto.anthropic.response.
- Position
- Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
27→3 forge_app.infra uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.auth.auth_method.
- The types involved
forge_app.infra.StrategyFactory→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_app.infra uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→4 forge_app.infra uses forge_domain.auth.new_types✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.auth.new_types.
- The types involved
forge_app.infra.StrategyFactory→forge_domain.auth.new_types.URLParamSpec
- Direction
- forge_app.infra uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→5 forge_app.infra uses forge_domain.env✕
- Connections
- 3 pairs of types, where a type in forge_app.infra uses a type in forge_domain.env.
- The types involved
forge_app.infra.EnvironmentInfra→forge_domain.env.ConfigOperationforge_app.infra.EnvironmentInfra→forge_domain.env.Environmentforge_app.infra.McpServerInfra→forge_domain.env.Environment
- Direction
- forge_app.infra uses forge_domain.env, so a change to forge_domain.env can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.env.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→6 forge_app.infra uses forge_domain.mcp✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.mcp.
- The types involved
forge_app.infra.McpServerInfra→forge_domain.mcp.McpServerConfig
- Direction
- forge_app.infra uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→11 forge_app.infra uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.tools.definition.name.
- The types involved
forge_app.infra.McpClientInfra→forge_domain.tools.definition.name.ToolName
- Direction
- forge_app.infra uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→12 forge_app.infra uses forge_domain.auth.credentials✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.auth.credentials.
- The types involved
forge_app.infra.AuthStrategy→forge_domain.auth.credentials.AuthCredential
- Direction
- forge_app.infra uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.credentials.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→24 forge_app.infra uses forge_domain.auth.auth_context✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.auth.auth_context.
- The types involved
forge_app.infra.AuthStrategy→forge_domain.auth.auth_context.AuthContextResponse
- Direction
- forge_app.infra uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.auth_context.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
27→25 forge_app.infra uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_app.infra uses a type in forge_domain.provider.
- The types involved
forge_app.infra.StrategyFactory→forge_domain.provider.ProviderId
- Direction
- forge_app.infra uses forge_domain.provider, so a change to forge_domain.provider can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.provider.
- Position
- Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
28→2 forge_domain.agent uses forge_config.config✕
- Connections
- 1 pair of types, where a type in forge_domain.agent uses a type in forge_config.config.
- The types involved
forge_domain.agent.Agent→forge_config.config.ForgeConfig
- Direction
- forge_domain.agent uses forge_config.config, so a change to forge_config.config can break forge_domain.agent, while a change to forge_domain.agent can't break forge_config.config.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
28→11 forge_domain.agent uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_domain.agent uses a type in forge_domain.tools.definition.name.
- The types involved
forge_domain.agent.Agent→forge_domain.tools.definition.name.ToolName
- Direction
- forge_domain.agent uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
28→17 forge_domain.agent uses forge_repo.conversation.conversation_record✕
- Connections
- 2 pairs of types, where a type in forge_domain.agent uses a type in forge_repo.conversation.conversation_record.
- The types involved
forge_domain.agent.Effort→forge_repo.conversation.conversation_record.EffortRecordforge_domain.agent.ReasoningConfig→forge_repo.conversation.conversation_record.ReasoningConfigRecord
- Direction
- forge_domain.agent uses forge_repo.conversation.conversation_record, so a change to forge_repo.conversation.conversation_record can break forge_domain.agent, while a change to forge_domain.agent can't break forge_repo.conversation.conversation_record.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
28→19 forge_domain.agent uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_domain.agent uses a type in forge_domain.model.
- The types involved
forge_domain.agent.Agent→forge_domain.model.ModelId
- Direction
- forge_domain.agent uses forge_domain.model, so a change to forge_domain.model can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.model.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
28→23 forge_domain.agent uses forge_app.dto.anthropic.response✕
- Connections
- 1 pair of types, where a type in forge_domain.agent uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_domain.agent.Agent→forge_app.dto.anthropic.response.Model
- Direction
- forge_domain.agent uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_domain.agent, while a change to forge_domain.agent can't break forge_app.dto.anthropic.response.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
28→25 forge_domain.agent uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_domain.agent uses a type in forge_domain.provider.
- The types involved
forge_domain.agent.Agent→forge_domain.provider.ProviderId
- Direction
- forge_domain.agent uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.provider.
- Position
- Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
29→4 forge_domain.repo uses forge_domain.auth.new_types✕
- Connections
- 1 pair of types, where a type in forge_domain.repo uses a type in forge_domain.auth.new_types.
- The types involved
forge_domain.repo.WorkspaceIndexRepository→forge_domain.auth.new_types.ApiKey
- Direction
- forge_domain.repo uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
29→9 forge_domain.repo uses forge_domain.conversation✕
- Connections
- 2 pairs of types, where a type in forge_domain.repo uses a type in forge_domain.conversation.
- The types involved
forge_domain.repo.ConversationRepository→forge_domain.conversation.Conversationforge_domain.repo.ConversationRepository→forge_domain.conversation.ConversationId
- Direction
- forge_domain.repo uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
29→12 forge_domain.repo uses forge_domain.auth.credentials✕
- Connections
- 1 pair of types, where a type in forge_domain.repo uses a type in forge_domain.auth.credentials.
- The types involved
forge_domain.repo.ProviderRepository→forge_domain.auth.credentials.AuthCredential
- Direction
- forge_domain.repo uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.auth.credentials.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
29→19 forge_domain.repo uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_domain.repo uses a type in forge_domain.model.
- The types involved
forge_domain.repo.ChatRepository→forge_domain.model.ModelId
- Direction
- forge_domain.repo uses forge_domain.model, so a change to forge_domain.model can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.model.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
29→21 forge_domain.repo uses forge_domain.context✕
- Connections
- 1 pair of types, where a type in forge_domain.repo uses a type in forge_domain.context.
- The types involved
forge_domain.repo.ChatRepository→forge_domain.context.Context
- Direction
- forge_domain.repo uses forge_domain.context, so a change to forge_domain.context can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.context.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
29→25 forge_domain.repo uses forge_domain.provider✕
- Connections
- 2 pairs of types, where a type in forge_domain.repo uses a type in forge_domain.provider.
- The types involved
forge_domain.repo.ChatRepository→forge_domain.provider.Providerforge_domain.repo.ProviderRepository→forge_domain.provider.ProviderId
- Direction
- forge_domain.repo uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.provider.
- Position
- Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
30→3 forge_api.api uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.auth.auth_method.
- The types involved
forge_api.api.API→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_api.api uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_api.api, while a change to forge_api.api can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→5 forge_api.api uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_api.api uses a type in forge_domain.env.
- The types involved
forge_api.api.API→forge_domain.env.ConfigOperationforge_api.api.API→forge_domain.env.Environment
- Direction
- forge_api.api uses forge_domain.env, so a change to forge_domain.env can break forge_api.api, while a change to forge_api.api can't break forge_domain.env.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→6 forge_api.api uses forge_domain.mcp✕
- Connections
- 2 pairs of types, where a type in forge_api.api uses a type in forge_domain.mcp.
- The types involved
forge_api.api.API→forge_domain.mcp.McpConfigforge_api.api.API→forge_domain.mcp.Scope
- Direction
- forge_api.api uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_api.api, while a change to forge_api.api can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→9 forge_api.api uses forge_domain.conversation✕
- Connections
- 2 pairs of types, where a type in forge_api.api uses a type in forge_domain.conversation.
- The types involved
forge_api.api.API→forge_domain.conversation.Conversationforge_api.api.API→forge_domain.conversation.ConversationId
- Direction
- forge_api.api uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_api.api, while a change to forge_api.api can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→10 forge_api.api uses forge_domain.node✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.node.
- The types involved
forge_api.api.API→forge_domain.node.SearchParams
- Direction
- forge_api.api uses forge_domain.node, so a change to forge_domain.node can break forge_api.api, while a change to forge_api.api can't break forge_domain.node.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→13 forge_api.api uses forge_domain.event✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.event.
- The types involved
forge_api.api.API→forge_domain.event.UserPrompt
- Direction
- forge_api.api uses forge_domain.event, so a change to forge_domain.event can break forge_api.api, while a change to forge_api.api can't break forge_domain.event.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→19 forge_api.api uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.model.
- The types involved
forge_api.api.API→forge_domain.model.ModelId
- Direction
- forge_api.api uses forge_domain.model, so a change to forge_domain.model can break forge_api.api, while a change to forge_api.api can't break forge_domain.model.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→24 forge_api.api uses forge_domain.auth.auth_context✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.auth.auth_context.
- The types involved
forge_api.api.API→forge_domain.auth.auth_context.AuthContextResponse
- Direction
- forge_api.api uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_api.api, while a change to forge_api.api can't break forge_domain.auth.auth_context.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→25 forge_api.api uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.provider.
- The types involved
forge_api.api.API→forge_domain.provider.ProviderId
- Direction
- forge_api.api uses forge_domain.provider, so a change to forge_domain.provider can break forge_api.api, while a change to forge_api.api can't break forge_domain.provider.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
30→28 forge_api.api uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_api.api uses a type in forge_domain.agent.
- The types involved
forge_api.api.API→forge_domain.agent.AgentId
- Direction
- forge_api.api uses forge_domain.agent, so a change to forge_domain.agent can break forge_api.api, while a change to forge_api.api can't break forge_domain.agent.
- Position
- Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
31→3 forge_app.services uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.auth.auth_method.
- The types involved
forge_app.services.ProviderAuthService→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_app.services uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→5 forge_app.services uses forge_domain.env✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.env.
- The types involved
forge_app.services.AppConfigService→forge_domain.env.ConfigOperation
- Direction
- forge_app.services uses forge_domain.env, so a change to forge_domain.env can break forge_app.services, while a change to forge_app.services can't break forge_domain.env.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→6 forge_app.services uses forge_domain.mcp✕
- Connections
- 2 pairs of types, where a type in forge_app.services uses a type in forge_domain.mcp.
- The types involved
forge_app.services.McpConfigManager→forge_domain.mcp.McpConfigforge_app.services.McpConfigManager→forge_domain.mcp.Scope
- Direction
- forge_app.services uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_app.services, while a change to forge_app.services can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→9 forge_app.services uses forge_domain.conversation✕
- Connections
- 2 pairs of types, where a type in forge_app.services uses a type in forge_domain.conversation.
- The types involved
forge_app.services.ConversationService→forge_domain.conversation.Conversationforge_app.services.ConversationService→forge_domain.conversation.ConversationId
- Direction
- forge_app.services uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_app.services, while a change to forge_app.services can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→10 forge_app.services uses forge_domain.node✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.node.
- The types involved
forge_app.services.WorkspaceService→forge_domain.node.SearchParams
- Direction
- forge_app.services uses forge_domain.node, so a change to forge_domain.node can break forge_app.services, while a change to forge_app.services can't break forge_domain.node.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→12 forge_app.services uses forge_domain.auth.credentials✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.auth.credentials.
- The types involved
forge_app.services.ProviderService→forge_domain.auth.credentials.AuthCredential
- Direction
- forge_app.services uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.credentials.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→14 forge_app.services uses forge_domain.tools.catalog✕
- Connections
- 3 pairs of types, where a type in forge_app.services uses a type in forge_domain.tools.catalog.
- The types involved
forge_app.services.FsPatchService→forge_domain.tools.catalog.PatchEditforge_app.services.FsSearchService→forge_domain.tools.catalog.FSSearchforge_app.services.TodoWriteOutput→forge_domain.tools.catalog.Todo
- Direction
- forge_app.services uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_app.services, while a change to forge_app.services can't break forge_domain.tools.catalog.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→15 forge_app.services uses forge_domain.tools.call.tool_call✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_app.services.McpService→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_app.services uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.services, while a change to forge_app.services can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→19 forge_app.services uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.model.
- The types involved
forge_app.services.ProviderService→forge_domain.model.ModelId
- Direction
- forge_app.services uses forge_domain.model, so a change to forge_domain.model can break forge_app.services, while a change to forge_app.services can't break forge_domain.model.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→21 forge_app.services uses forge_domain.context✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.context.
- The types involved
forge_app.services.ProviderService→forge_domain.context.Context
- Direction
- forge_app.services uses forge_domain.context, so a change to forge_domain.context can break forge_app.services, while a change to forge_app.services can't break forge_domain.context.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→22 forge_app.services uses forge_app.dto.anthropic.request✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_app.services.ReadOutput→forge_app.dto.anthropic.request.Content
- Direction
- forge_app.services uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.services, while a change to forge_app.services can't break forge_app.dto.anthropic.request.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→24 forge_app.services uses forge_domain.auth.auth_context✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.auth.auth_context.
- The types involved
forge_app.services.ProviderAuthService→forge_domain.auth.auth_context.AuthContextResponse
- Direction
- forge_app.services uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.auth_context.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→25 forge_app.services uses forge_domain.provider✕
- Connections
- 4 pairs of types, where a type in forge_app.services uses a type in forge_domain.provider.
- The types involved
forge_app.services.ProviderAuthService→forge_domain.provider.Providerforge_app.services.ProviderAuthService→forge_domain.provider.ProviderIdforge_app.services.ProviderService→forge_domain.provider.Providerforge_app.services.ProviderService→forge_domain.provider.ProviderId
- Direction
- forge_app.services uses forge_domain.provider, so a change to forge_domain.provider can break forge_app.services, while a change to forge_app.services can't break forge_domain.provider.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→27 forge_app.services uses forge_app.infra✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_app.infra.
- The types involved
forge_app.services.Services→forge_app.infra.EnvironmentInfra
- Direction
- forge_app.services uses forge_app.infra, so a change to forge_app.infra can break forge_app.services, while a change to forge_app.services can't break forge_app.infra.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
31→28 forge_app.services uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_app.services uses a type in forge_domain.agent.
- The types involved
forge_app.services.AgentRegistry→forge_domain.agent.AgentId
- Direction
- forge_app.services uses forge_domain.agent, so a change to forge_domain.agent can break forge_app.services, while a change to forge_app.services can't break forge_domain.agent.
- Position
- Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
32→5 forge_app.tool_registry uses forge_domain.env✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.env.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.env.Environment
- Direction
- forge_app.tool_registry uses forge_domain.env, so a change to forge_domain.env can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.env.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→11 forge_app.tool_registry uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.tools.definition.name.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.tools.definition.name.ToolName
- Direction
- forge_app.tool_registry uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→14 forge_app.tool_registry uses forge_domain.tools.catalog✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.tools.catalog.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.tools.catalog.ToolCatalog
- Direction
- forge_app.tool_registry uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.catalog.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→15 forge_app.tool_registry uses forge_domain.tools.call.tool_call✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_app.tool_registry uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→16 forge_app.tool_registry uses forge_domain.tools.result✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.tools.result.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.tools.result.ToolResult
- Direction
- forge_app.tool_registry uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→22 forge_app.tool_registry uses forge_app.dto.anthropic.request✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_app.dto.anthropic.request.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_app.dto.anthropic.request.ToolDefinition
- Direction
- forge_app.tool_registry uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_app.dto.anthropic.request.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→23 forge_app.tool_registry uses forge_app.dto.anthropic.response✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_app.dto.anthropic.response.Model
- Direction
- forge_app.tool_registry uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_app.dto.anthropic.response.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
32→28 forge_app.tool_registry uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_app.tool_registry uses a type in forge_domain.agent.
- The types involved
forge_app.tool_registry.ToolRegistry→forge_domain.agent.Agent
- Direction
- forge_app.tool_registry uses forge_domain.agent, so a change to forge_domain.agent can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.agent.
- Position
- Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
33→9 forge_domain.hook uses forge_domain.conversation✕
- Connections
- 4 pairs of types, where a type in forge_domain.hook uses a type in forge_domain.conversation.
- The types involved
forge_domain.hook.CombinedHandler→forge_domain.conversation.Conversationforge_domain.hook.EventHandle→forge_domain.conversation.Conversationforge_domain.hook.Hook→forge_domain.conversation.Conversationforge_domain.hook.NoOpHandler→forge_domain.conversation.Conversation
- Direction
- forge_domain.hook uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
33→15 forge_domain.hook uses forge_domain.tools.call.tool_call✕
- Connections
- 2 pairs of types, where a type in forge_domain.hook uses a type in forge_domain.tools.call.tool_call.
- The types involved
forge_domain.hook.ToolcallEndPayload→forge_domain.tools.call.tool_call.ToolCallFullforge_domain.hook.ToolcallStartPayload→forge_domain.tools.call.tool_call.ToolCallFull
- Direction
- forge_domain.hook uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.tools.call.tool_call.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
33→16 forge_domain.hook uses forge_domain.tools.result✕
- Connections
- 1 pair of types, where a type in forge_domain.hook uses a type in forge_domain.tools.result.
- The types involved
forge_domain.hook.ToolcallEndPayload→forge_domain.tools.result.ToolResult
- Direction
- forge_domain.hook uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.tools.result.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
33→18 forge_domain.hook uses forge_domain.message✕
- Connections
- 1 pair of types, where a type in forge_domain.hook uses a type in forge_domain.message.
- The types involved
forge_domain.hook.ResponsePayload→forge_domain.message.ChatCompletionMessageFull
- Direction
- forge_domain.hook uses forge_domain.message, so a change to forge_domain.message can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.message.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
33→19 forge_domain.hook uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_domain.hook uses a type in forge_domain.model.
- The types involved
forge_domain.hook.EventData→forge_domain.model.ModelId
- Direction
- forge_domain.hook uses forge_domain.model, so a change to forge_domain.model can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.model.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
33→28 forge_domain.hook uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_domain.hook uses a type in forge_domain.agent.
- The types involved
forge_domain.hook.EventData→forge_domain.agent.Agent
- Direction
- forge_domain.hook uses forge_domain.agent, so a change to forge_domain.agent can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.agent.
- Position
- Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
34→2 forge_infra.forge_infra uses forge_config.config✕
- Connections
- 1 pair of types, where a type in forge_infra.forge_infra uses a type in forge_config.config.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_config.config.ForgeConfig
- Direction
- forge_infra.forge_infra uses forge_config.config, so a change to forge_config.config can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_config.config.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→3 forge_infra.forge_infra uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_infra.forge_infra uses a type in forge_domain.auth.auth_method.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_infra.forge_infra uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→4 forge_infra.forge_infra uses forge_domain.auth.new_types✕
- Connections
- 1 pair of types, where a type in forge_infra.forge_infra uses a type in forge_domain.auth.new_types.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_domain.auth.new_types.URLParamSpec
- Direction
- forge_infra.forge_infra uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→5 forge_infra.forge_infra uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_infra.forge_infra uses a type in forge_domain.env.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_domain.env.ConfigOperationforge_infra.forge_infra.ForgeInfra→forge_domain.env.Environment
- Direction
- forge_infra.forge_infra uses forge_domain.env, so a change to forge_domain.env can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.env.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→6 forge_infra.forge_infra uses forge_domain.mcp✕
- Connections
- 1 pair of types, where a type in forge_infra.forge_infra uses a type in forge_domain.mcp.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_domain.mcp.McpServerConfig
- Direction
- forge_infra.forge_infra uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→25 forge_infra.forge_infra uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_infra.forge_infra uses a type in forge_domain.provider.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_domain.provider.ProviderId
- Direction
- forge_infra.forge_infra uses forge_domain.provider, so a change to forge_domain.provider can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.provider.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
34→27 forge_infra.forge_infra uses forge_app.infra✕
- Connections
- 14 pairs of types, where a type in forge_infra.forge_infra uses a type in forge_app.infra.
- The types involved
forge_infra.forge_infra.ForgeInfra→forge_app.infra.CommandInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.DirectoryReaderInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.EnvironmentInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.FileDirectoryInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.FileInfoInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.FileReaderInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.FileRemoverInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.FileWriterInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.GrpcInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.HttpInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.McpServerInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.StrategyFactoryforge_infra.forge_infra.ForgeInfra→forge_app.infra.UserInfraforge_infra.forge_infra.ForgeInfra→forge_app.infra.WalkerInfra
- Direction
- forge_infra.forge_infra uses forge_app.infra, so a change to forge_app.infra can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_app.infra.
- Position
- Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
35→2 forge_main.ui uses forge_config.config✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_config.config.
- The types involved
forge_main.ui.UI→forge_config.config.ForgeConfig
- Direction
- forge_main.ui uses forge_config.config, so a change to forge_config.config can break forge_main.ui, while a change to forge_main.ui can't break forge_config.config.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→3 forge_main.ui uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_domain.auth.auth_method.
- The types involved
forge_main.ui.UI→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_main.ui uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→6 forge_main.ui uses forge_domain.mcp✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_domain.mcp.
- The types involved
forge_main.ui.ui$module→forge_domain.mcp.McpServerConfig
- Direction
- forge_main.ui uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→9 forge_main.ui uses forge_domain.conversation✕
- Connections
- 3 pairs of types, where a type in forge_main.ui uses a type in forge_domain.conversation.
- The types involved
forge_main.ui.ConversationDump→forge_domain.conversation.Conversationforge_main.ui.UI→forge_domain.conversation.Conversationforge_main.ui.UI→forge_domain.conversation.ConversationId
- Direction
- forge_main.ui uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→10 forge_main.ui uses forge_domain.node✕
- Connections
- 2 pairs of types, where a type in forge_main.ui uses a type in forge_domain.node.
- The types involved
forge_main.ui.UI→forge_domain.node.SearchParamsforge_main.ui.UI→forge_domain.node.WorkspaceInfo
- Direction
- forge_main.ui uses forge_domain.node, so a change to forge_domain.node can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.node.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→13 forge_main.ui uses forge_domain.event✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_domain.event.
- The types involved
forge_main.ui.UI→forge_domain.event.UserPrompt
- Direction
- forge_main.ui uses forge_domain.event, so a change to forge_domain.event can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.event.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→19 forge_main.ui uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_domain.model.
- The types involved
forge_main.ui.UI→forge_domain.model.ModelId
- Direction
- forge_main.ui uses forge_domain.model, so a change to forge_domain.model can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.model.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→23 forge_main.ui uses forge_app.dto.anthropic.response✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_app.dto.anthropic.response.
- The types involved
forge_main.ui.UI→forge_app.dto.anthropic.response.Event
- Direction
- forge_main.ui uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_main.ui, while a change to forge_main.ui can't break forge_app.dto.anthropic.response.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→24 forge_main.ui uses forge_domain.auth.auth_context✕
- Connections
- 3 pairs of types, where a type in forge_main.ui uses a type in forge_domain.auth.auth_context.
- The types involved
forge_main.ui.UI→forge_domain.auth.auth_context.ApiKeyRequestforge_main.ui.UI→forge_domain.auth.auth_context.CodeRequestforge_main.ui.UI→forge_domain.auth.auth_context.DeviceCodeRequest
- Direction
- forge_main.ui uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.auth.auth_context.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→25 forge_main.ui uses forge_domain.provider✕
- Connections
- 4 pairs of types, where a type in forge_main.ui uses a type in forge_domain.provider.
- The types involved
forge_main.ui.UI→forge_domain.provider.AnyProviderforge_main.ui.UI→forge_domain.provider.Providerforge_main.ui.UI→forge_domain.provider.ProviderIdforge_main.ui.UI→forge_domain.provider.ProviderType
- Direction
- forge_main.ui uses forge_domain.provider, so a change to forge_domain.provider can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.provider.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→26 forge_main.ui uses forge_main.info✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_main.info.
- The types involved
forge_main.ui.UI→forge_main.info.Info
- Direction
- forge_main.ui uses forge_main.info, so a change to forge_main.info can break forge_main.ui, while a change to forge_main.ui can't break forge_main.info.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
35→28 forge_main.ui uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_main.ui uses a type in forge_domain.agent.
- The types involved
forge_main.ui.UI→forge_domain.agent.AgentId
- Direction
- forge_main.ui uses forge_domain.agent, so a change to forge_domain.agent can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.agent.
- Position
- Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
36→11 forge_repo.agent_definition uses forge_domain.tools.definition.name✕
- Connections
- 1 pair of types, where a type in forge_repo.agent_definition uses a type in forge_domain.tools.definition.name.
- The types involved
forge_repo.agent_definition.AgentDefinition→forge_domain.tools.definition.name.ToolName
- Direction
- forge_repo.agent_definition uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.tools.definition.name.
- Position
- Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
36→19 forge_repo.agent_definition uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_repo.agent_definition uses a type in forge_domain.model.
- The types involved
forge_repo.agent_definition.AgentDefinition→forge_domain.model.ModelId
- Direction
- forge_repo.agent_definition uses forge_domain.model, so a change to forge_domain.model can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.model.
- Position
- Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
36→25 forge_repo.agent_definition uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_repo.agent_definition uses a type in forge_domain.provider.
- The types involved
forge_repo.agent_definition.AgentDefinition→forge_domain.provider.ProviderId
- Direction
- forge_repo.agent_definition uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.provider.
- Position
- Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
36→28 forge_repo.agent_definition uses forge_domain.agent✕
- Connections
- 2 pairs of types, where a type in forge_repo.agent_definition uses a type in forge_domain.agent.
- The types involved
forge_repo.agent_definition.AgentDefinition→forge_domain.agent.Agentforge_repo.agent_definition.AgentDefinition→forge_domain.agent.AgentId
- Direction
- forge_repo.agent_definition uses forge_domain.agent, so a change to forge_domain.agent can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.agent.
- Position
- Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
37→19 forge_repo.provider.chat uses forge_domain.model✕
- Connections
- 2 pairs of types, where a type in forge_repo.provider.chat uses a type in forge_domain.model.
- The types involved
forge_repo.provider.chat.ForgeChatRepository→forge_domain.model.ModelIdforge_repo.provider.chat.ProviderRouter→forge_domain.model.ModelId
- Direction
- forge_repo.provider.chat uses forge_domain.model, so a change to forge_domain.model can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.model.
- Position
- Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
37→21 forge_repo.provider.chat uses forge_domain.context✕
- Connections
- 2 pairs of types, where a type in forge_repo.provider.chat uses a type in forge_domain.context.
- The types involved
forge_repo.provider.chat.ForgeChatRepository→forge_domain.context.Contextforge_repo.provider.chat.ProviderRouter→forge_domain.context.Context
- Direction
- forge_repo.provider.chat uses forge_domain.context, so a change to forge_domain.context can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.context.
- Position
- Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
37→25 forge_repo.provider.chat uses forge_domain.provider✕
- Connections
- 2 pairs of types, where a type in forge_repo.provider.chat uses a type in forge_domain.provider.
- The types involved
forge_repo.provider.chat.ForgeChatRepository→forge_domain.provider.Providerforge_repo.provider.chat.ProviderRouter→forge_domain.provider.Provider
- Direction
- forge_repo.provider.chat uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.provider.
- Position
- Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
37→29 forge_repo.provider.chat uses forge_domain.repo✕
- Connections
- 1 pair of types, where a type in forge_repo.provider.chat uses a type in forge_domain.repo.
- The types involved
forge_repo.provider.chat.ForgeChatRepository→forge_domain.repo.ChatRepository
- Direction
- forge_repo.provider.chat uses forge_domain.repo, so a change to forge_domain.repo can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.repo.
- Position
- Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
38→2 forge_api.forge_api uses forge_config.config✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_config.config.
- The types involved
forge_api.forge_api.ForgeAPI→forge_config.config.ForgeConfig
- Direction
- forge_api.forge_api uses forge_config.config, so a change to forge_config.config can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_config.config.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→3 forge_api.forge_api uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.auth.auth_method.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_api.forge_api uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→5 forge_api.forge_api uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_api.forge_api uses a type in forge_domain.env.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.env.ConfigOperationforge_api.forge_api.ForgeAPI→forge_domain.env.Environment
- Direction
- forge_api.forge_api uses forge_domain.env, so a change to forge_domain.env can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.env.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→6 forge_api.forge_api uses forge_domain.mcp✕
- Connections
- 2 pairs of types, where a type in forge_api.forge_api uses a type in forge_domain.mcp.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.mcp.McpConfigforge_api.forge_api.ForgeAPI→forge_domain.mcp.Scope
- Direction
- forge_api.forge_api uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→9 forge_api.forge_api uses forge_domain.conversation✕
- Connections
- 2 pairs of types, where a type in forge_api.forge_api uses a type in forge_domain.conversation.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.conversation.Conversationforge_api.forge_api.ForgeAPI→forge_domain.conversation.ConversationId
- Direction
- forge_api.forge_api uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→10 forge_api.forge_api uses forge_domain.node✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.node.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.node.SearchParams
- Direction
- forge_api.forge_api uses forge_domain.node, so a change to forge_domain.node can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.node.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→13 forge_api.forge_api uses forge_domain.event✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.event.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.event.UserPrompt
- Direction
- forge_api.forge_api uses forge_domain.event, so a change to forge_domain.event can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.event.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→19 forge_api.forge_api uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.model.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.model.ModelId
- Direction
- forge_api.forge_api uses forge_domain.model, so a change to forge_domain.model can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.model.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→24 forge_api.forge_api uses forge_domain.auth.auth_context✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.auth.auth_context.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.auth.auth_context.AuthContextResponse
- Direction
- forge_api.forge_api uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.auth.auth_context.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→25 forge_api.forge_api uses forge_domain.provider✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.provider.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.provider.ProviderId
- Direction
- forge_api.forge_api uses forge_domain.provider, so a change to forge_domain.provider can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.provider.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→28 forge_api.forge_api uses forge_domain.agent✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_domain.agent.
- The types involved
forge_api.forge_api.ForgeAPI→forge_domain.agent.AgentId
- Direction
- forge_api.forge_api uses forge_domain.agent, so a change to forge_domain.agent can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.agent.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
38→30 forge_api.forge_api uses forge_api.api✕
- Connections
- 1 pair of types, where a type in forge_api.forge_api uses a type in forge_api.api.
- The types involved
forge_api.forge_api.ForgeAPI→forge_api.api.API
- Direction
- forge_api.forge_api uses forge_api.api, so a change to forge_api.api can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_api.api.
- Position
- Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
39→3 forge_repo.forge_repo uses forge_domain.auth.auth_method✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_domain.auth.auth_method.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.auth.auth_method.AuthMethod
- Direction
- forge_repo.forge_repo uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.auth_method.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→4 forge_repo.forge_repo uses forge_domain.auth.new_types✕
- Connections
- 2 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_domain.auth.new_types.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.auth.new_types.ApiKeyforge_repo.forge_repo.ForgeRepo→forge_domain.auth.new_types.URLParamSpec
- Direction
- forge_repo.forge_repo uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.new_types.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→5 forge_repo.forge_repo uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_domain.env.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.env.ConfigOperationforge_repo.forge_repo.ForgeRepo→forge_domain.env.Environment
- Direction
- forge_repo.forge_repo uses forge_domain.env, so a change to forge_domain.env can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.env.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→6 forge_repo.forge_repo uses forge_domain.mcp✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_domain.mcp.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.mcp.McpServerConfig
- Direction
- forge_repo.forge_repo uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.mcp.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→9 forge_repo.forge_repo uses forge_domain.conversation✕
- Connections
- 2 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_domain.conversation.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.conversation.Conversationforge_repo.forge_repo.ForgeRepo→forge_domain.conversation.ConversationId
- Direction
- forge_repo.forge_repo uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.conversation.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→12 forge_repo.forge_repo uses forge_domain.auth.credentials✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_domain.auth.credentials.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.auth.credentials.AuthCredential
- Direction
- forge_repo.forge_repo uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.credentials.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→19 forge_repo.forge_repo uses forge_domain.model✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_domain.model.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.model.ModelId
- Direction
- forge_repo.forge_repo uses forge_domain.model, so a change to forge_domain.model can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.model.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→21 forge_repo.forge_repo uses forge_domain.context✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_domain.context.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.context.Context
- Direction
- forge_repo.forge_repo uses forge_domain.context, so a change to forge_domain.context can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.context.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→25 forge_repo.forge_repo uses forge_domain.provider✕
- Connections
- 2 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_domain.provider.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.provider.Providerforge_repo.forge_repo.ForgeRepo→forge_domain.provider.ProviderId
- Direction
- forge_repo.forge_repo uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.provider.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→27 forge_repo.forge_repo uses forge_app.infra✕
- Connections
- 16 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_app.infra.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_app.infra.AgentRepositoryforge_repo.forge_repo.ForgeRepo→forge_app.infra.CommandInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.DirectoryReaderInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.EnvironmentInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.FileDirectoryInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.FileInfoInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.FileReaderInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.FileRemoverInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.FileWriterInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.GrpcInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.HttpInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.KVStoreforge_repo.forge_repo.ForgeRepo→forge_app.infra.McpServerInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.StrategyFactoryforge_repo.forge_repo.ForgeRepo→forge_app.infra.UserInfraforge_repo.forge_repo.ForgeRepo→forge_app.infra.WalkerInfra
- Direction
- forge_repo.forge_repo uses forge_app.infra, so a change to forge_app.infra can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_app.infra.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→29 forge_repo.forge_repo uses forge_domain.repo✕
- Connections
- 9 pairs of types, where a type in forge_repo.forge_repo uses a type in forge_domain.repo.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_domain.repo.ChatRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.ConversationRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.FuzzySearchRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.ProviderRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.SkillRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.SnapshotRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.TextPatchRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.ValidationRepositoryforge_repo.forge_repo.ForgeRepo→forge_domain.repo.WorkspaceIndexRepository
- Direction
- forge_repo.forge_repo uses forge_domain.repo, so a change to forge_domain.repo can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.repo.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
39→37 forge_repo.forge_repo uses forge_repo.provider.chat✕
- Connections
- 1 pair of types, where a type in forge_repo.forge_repo uses a type in forge_repo.provider.chat.
- The types involved
forge_repo.forge_repo.ForgeRepo→forge_repo.provider.chat.ForgeChatRepository
- Direction
- forge_repo.forge_repo uses forge_repo.provider.chat, so a change to forge_repo.provider.chat can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_repo.provider.chat.
- Position
- Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
40→5 forge_services.forge_services uses forge_domain.env✕
- Connections
- 2 pairs of types, where a type in forge_services.forge_services uses a type in forge_domain.env.
- The types involved
forge_services.forge_services.ForgeServices→forge_domain.env.ConfigOperationforge_services.forge_services.ForgeServices→forge_domain.env.Environment
- Direction
- forge_services.forge_services uses forge_domain.env, so a change to forge_domain.env can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_domain.env.
- Position
- Below the diagonal: forge_services.forge_services uses a module listed above it, which is the healthy direction.
40→27 forge_services.forge_services uses forge_app.infra✕
- Connections
- 1 pair of types, where a type in forge_services.forge_services uses a type in forge_app.infra.
- The types involved
forge_services.forge_services.ForgeServices→forge_app.infra.EnvironmentInfra
- Direction
- forge_services.forge_services uses forge_app.infra, so a change to forge_app.infra can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_app.infra.
- Position
- Below the diagonal: forge_services.forge_services uses a module listed above it, which is the healthy direction.
40→31 forge_services.forge_services uses forge_app.services✕
- Connections
- 28 pairs of types, where a type in forge_services.forge_services uses a type in forge_app.services. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
forge_services.forge_services.ForgeServices→forge_app.services.AgentRegistryforge_services.forge_services.ForgeServices→forge_app.services.AppConfigServiceforge_services.forge_services.ForgeServices→forge_app.services.AttachmentServiceforge_services.forge_services.ForgeServices→forge_app.services.AuthServiceforge_services.forge_services.ForgeServices→forge_app.services.CommandLoaderServiceforge_services.forge_services.ForgeServices→forge_app.services.ConversationServiceforge_services.forge_services.ForgeServices→forge_app.services.CustomInstructionsServiceforge_services.forge_services.ForgeServices→forge_app.services.FileDiscoveryServiceforge_services.forge_services.ForgeServices→forge_app.services.FollowUpServiceforge_services.forge_services.ForgeServices→forge_app.services.FsPatchServiceforge_services.forge_services.ForgeServices→forge_app.services.FsReadServiceforge_services.forge_services.ForgeServices→forge_app.services.FsRemoveServiceforge_services.forge_services.ForgeServices→forge_app.services.FsSearchServiceforge_services.forge_services.ForgeServices→forge_app.services.FsUndoServiceforge_services.forge_services.ForgeServices→forge_app.services.FsWriteServiceforge_services.forge_services.ForgeServices→forge_app.services.ImageReadServiceforge_services.forge_services.ForgeServices→forge_app.services.McpConfigManagerforge_services.forge_services.ForgeServices→forge_app.services.McpServiceforge_services.forge_services.ForgeServices→forge_app.services.NetFetchServiceforge_services.forge_services.ForgeServices→forge_app.services.PlanCreateServiceforge_services.forge_services.ForgeServices→forge_app.services.PolicyServiceforge_services.forge_services.ForgeServices→forge_app.services.ProviderAuthServiceforge_services.forge_services.ForgeServices→forge_app.services.ProviderServiceforge_services.forge_services.ForgeServices→forge_app.services.Servicesforge_services.forge_services.ForgeServices→forge_app.services.ShellService
- Direction
- forge_services.forge_services uses forge_app.services, so a change to forge_app.services can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_app.services.
- Position
- Below the diagonal: forge_services.forge_services 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 — Domain Modelling
At a glance — Event Sourcing
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 58 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 38 | High / Critical |
Roadmap
First, address immediate visual and motion safety by ensuring visible focus styles, respecting reduced-motion preferences, and fixing low-contrast colors. Next, integrate automated accessibility checks into your CI pipeline using tools like axe or pa11y to enforce standards on rendered pages, while also correcting basic page structure issues such as missing landmarks and language attributes. Finally, establish a culture of architectural transparency by documenting significant design decisions in a dedicated ADR folder to capture context and consequences for future reference.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +11.7 pts | Medium | Visual & motion safety |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +7.1 pts | Medium | A11y enforcement |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.0 pts | Low | ADR Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +5.1 pts | Medium | Page structure |
| 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. | +2.8 pts | Medium | Architecture documentation |
| Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED (2). | +2.0 pts | Medium | Static Analysis (SAST) |
| Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with table.rs, oauth_callback.rs. | +0.9 pts | Low | Knowledge Freshness |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| crates/forge_app/src/operation.rs | 5.5 | Mixed | Cyclomatic Complexity: ToolOperation::into_tool_output (cyclomatic 51) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/forge_walker/src/walker.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/forge_services/src/tool_services/fs_patch.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/forge_domain/src/context.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/forge_app/src/services.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/forge_app/src/orch.rs | 6.3 | Mixed | Cognitive Complexity: Orchestrator::run (cognitive 28) |
| crates/forge_repo/src/conversation/conversation_record.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/forge_domain/src/tools/catalog.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/forge_app/src/user_prompt.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/forge_main/src/ui.rs | 7.0 | Mixed | Cyclomatic Complexity: UI::handle_subcommands (cyclomatic 83) |
| crates/forge_select/src/preview.rs | 7.0 | Mixed | Cyclomatic Complexity: forge_select::preview::run_select_ui_values (cyclomatic 43) |
| crates/forge_json_repair/src/parser.rs | 7.0 | Mixed | Cyclomatic Complexity: JsonRepairParser::parse_string (cyclomatic 37) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 57 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 57 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, 416 of 444 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`cargo llvm-cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 254 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, 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.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, 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.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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
38 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was UI::handle_subcommands at 83. A further 7 function(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 AppCommand::name at 46 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/forge_domain/src/provider.rs (ProviderId::from_str at 42), crates/forge_app/src/tool_executor.rs (ToolExecutor::call_internal at 17), crates/forge_domain/src/tools/catalog.rs (ToolCatalog::description at 16). 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 UI::handle_subcommands (cyclomatic 83). — 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
69 function(s) exceeded the cognitive complexity threshold of 15; the worst was forge_app::utils::sanitize_gemini_schema at 107.
What to do
- Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with forge_app::utils::sanitize_gemini_schema (cognitive 107), UI::handle_subcommands (cognitive 104), forge_markdown_stream::table::wrap (cognitive 99). — 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 8 together lifts Cognitive Complexity from 5.7 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
31 god class(es) detected.
What to do
- Resolve the 10 FileTooLong finding(s) in God Classes — start with ui.rs, preview.rs, strategy.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 10 MethodTooLong finding(s) in God Classes — start with ui.rs (3), operation.rs, response.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 FunctionTooLong finding(s) in God Classes — start with preview.rs (2), utils.rs, conversation_html.rs. — One of this dimension's main actionable groups (6 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.
What to do
- Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with openai.rs (3), response.rs, github_copilot_reasoning.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with anthropic.rs (3), response.rs, user_prompt.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with response.rs, schema_coercion.rs, template_engine.rs. — 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
25 production modules (Cargo+npm), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 8 module(s) off the main sequence, with abstractness counted on 23 of the 25 (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 8 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Unstable project forge_api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project forge_infra 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 194 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with context.rs. — 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
2686 test methods: 2629 unit, 57 integration, 0 BDD, 0 e2e. The Rust suite contributes 2686 `#[test]` function(s) across 254 file(s) declaring at least one; its unit/integration split is Cargo's own — 15 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
1 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 844 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
12 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/forge_json_repair/src/schema_coercion.rs. Counted over 288 of the 462 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
19 deducted task-comment markers across 116561 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 19 TodoComment finding(s) in Explicit Debt — start with agent_provider_resolver.rs (2), request.rs (2), walker.rs. — One of this dimension's main actionable groups (19 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 25 build units (Cargo, npm) 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)
58 finding(s): 0 critical, 57 high, 1 medium, 0 low. 34 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 5 file(s) — `.forge/skills/write-release-notes/scripts/fetch-release-data.sh` (line 8), `scripts/benchmark.sh` (line 79), `scripts/list-all-porcelain.sh` (line 36), `scripts/test-zsh-utils.sh` (line 162, line 172, line 182, …), `shell-plugin/doctor.zsh` (line 196, lines 219–222, line 297, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 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 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 34 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 (34 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
30 finding(s): 0 critical, 7 high, 22 medium, 1 low.
What to do
- Resolve the 12 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
46 of 288 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/forge_markdown_stream/src/table.rs. Counted over 288 of the 462 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with table.rs, oauth_callback.rs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 44 Orphaned file finding(s) in Knowledge Freshness — start with result.rs (2), event_stream.rs, tool_order.rs. — One of this dimension's main actionable groups (44 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: drop_tool_call.rs↔set_cache.rs 92%; orch.rs↔event.rs 88%; tool_executor.rs↔summary.rs 77%
What to do
- Resolve the 11 Change coupling finding(s) in Change Coupling — start with services.rs (2), drop_tool_call.rs, tool_executor.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with orch.rs, fmt_input.rs, executor.rs. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — 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 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 19 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.agent-conversation a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:16, crates/forge_domain/src/conversation_style.css:256
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
- `Walker` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — crates/forge_app/src/walker.rs:8
What to do
- Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
ES1 · Fold determinism
ES2 · Immutable events
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 24 of 25 project(s) that lack one — worth up to 1.9 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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
P8 · Schema migrations
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/skill.rs:209
- `error!` at line 470 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:470
- `debug!` at line 532 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:532
- `debug!` at line 536 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:536
- `warn!` at line 98 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/database/pool.rs:98
- `debug!` at line 784 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/conversation/conversation_record.rs:784
- `warn!` at line 81 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/http.rs:81
- `warn!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/http.rs:88
- `warn!` at line 118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:118
- `info!` at line 147 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:147
- `debug!` at line 224 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:224
- `warn!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:228
- `info!` at line 237 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:237
- `warn!` at line 240 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:240
- `info!` at line 279 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:279
- `info!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:325
- `info!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:371
- `warn!` at line 375 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:375
- `warn!` at line 611 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:611
- `error!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/app.rs:202
- `error!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/compact.rs:79
- `debug!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:78
- `info!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:90
- `debug!` at line 103 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:103
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 84% | Strong | Solid. |
| Security | 53% | Adequate — gated by D29, D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 90% | Strong | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Accessibility | 30% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2056 lines of test source are present (.rs) 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 .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .ts, 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 (.rs), 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) — 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.
- 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.
- 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 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks. 71 claim(s) of kinds M4 does not check were not checked (path 10, command argument 6, environment variable 55); M4 checks only links and versions.
- 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 Rust source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 449 Rust 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 builds on an HTTP-server crate (`tiny_http` (Cargo.toml)) but serves no HTTP of its own: its production source starts no server (no `HttpServer::new`, `axum::serve`, `Server::bind`, tonic `Server::builder()…serve`, `rocket::build()`, `warp::serve`, `serve_connection` or the like — its examples and tests are not production source), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — 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
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — 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
- 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.
- X5 Nullable reference types — 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 68 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge crates/forge_markdown_stream/src/table.rs:1
- Orphaned knowledge crates/forge_main/src/oauth_callback.rs:1
- Banned license: html2md
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic domain model: Walker crates/forge_app/src/walker.rs:8
Serious — 288 finding(s)
- TodoComment crates/forge_walker/src/walker.rs:136
- TodoComment crates/forge_tracker/src/collect/posthog.rs:97
- TodoComment crates/forge_services/src/policy.rs:69
- TodoComment crates/forge_services/src/tool_services/fs_patch.rs:494
- TodoComment crates/forge_repo/src/provider/bedrock_cache.rs:16
- TodoComment crates/forge_repo/src/conversation/conversation_record.rs:535
- TodoComment crates/forge_main/src/state.rs:6
- TodoComment crates/forge_infra/src/forge_infra.rs:38
- TodoComment crates/forge_domain/src/context.rs:294
- TodoComment crates/forge_domain/src/model.rs:33
- TodoComment crates/forge_domain/src/tools/catalog.rs:1188
- TodoComment crates/forge_app/src/agent_provider_resolver.rs:35
- TodoComment crates/forge_app/src/agent_provider_resolver.rs:62
- TodoComment crates/forge_app/src/compact.rs:46
- TodoComment crates/forge_app/src/services.rs:429
- TodoComment crates/forge_app/src/user_prompt.rs:595
- TodoComment crates/forge_app/src/transformers/trim_context_summary.rs:40
- TodoComment crates/forge_app/src/dto/openai/request.rs:162
- TodoComment crates/forge_app/src/dto/anthropic/request.rs:407
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: drop_tool_call.rs ↔ set_cache.rs crates/forge_app/src/dto/openai/transformers/drop_tool_call.rs:1
- Change coupling: tool_executor.rs ↔ summary.rs crates/forge_app/src/tool_executor.rs:1
- Change coupling: attachment.rs ↔ shell.rs crates/forge_services/src/attachment.rs:1
- Change coupling: services.rs ↔ repo.rs crates/forge_app/src/services.rs:1
- Change coupling: services.rs ↔ lib.rs crates/forge_app/src/services.rs:1
- Change coupling: orch_setup.rs ↔ env.rs crates/forge_app/src/orch_spec/orch_setup.rs:1
- Change coupling: forge_api.rs ↔ app_config.rs crates/forge_api/src/forge_api.rs:1
- Change coupling: prompt.rs ↔ state.rs crates/forge_main/src/prompt.rs:1
- Change coupling: banner.rs ↔ model.rs crates/forge_main/src/banner.rs:1
- Change coupling: env.rs ↔ shell.rs crates/forge_infra/src/env.rs:1
- Change coupling: operation.rs ↔ fs_read.rs crates/forge_app/src/operation.rs:1
- UI::handle_subcommands (cognitive 104) crates/forge_main/src/ui.rs:466
- UI::select_model (cognitive 45) crates/forge_main/src/ui.rs:2904
- UI::on_dump (cognitive 32) crates/forge_main/src/ui.rs:4067
- UI::on_show_models (cognitive 30) crates/forge_main/src/ui.rs:1426
- UI::run_inner (cognitive 29) crates/forge_main/src/ui.rs:358
- UI::on_command (cognitive 27) crates/forge_main/src/ui.rs:2167
- UI::handle_api_key_input (cognitive 27) crates/forge_main/src/ui.rs:3085
- UI::handle_chat_response (cognitive 25) crates/forge_main/src/ui.rs:4140
- UI::on_index (cognitive 21) crates/forge_main/src/ui.rs:4752
- UI::on_show_mcp_servers (cognitive 19) crates/forge_main/src/ui.rs:1730
- FileTooLong: src/ui.rs crates/forge_main/src/ui.rs
- FileTooLong: src/preview.rs crates/forge_select/src/preview.rs
- FileTooLong: auth/strategy.rs crates/forge_infra/src/auth/strategy.rs
- FileTooLong: src/services.rs crates/forge_app/src/services.rs
- FileTooLong: src/parser.rs crates/forge_json_repair/src/parser.rs
- FileTooLong: conversation/conversation_record.rs crates/forge_repo/src/conversation/conversation_record.rs
- FileTooLong: provider/bedrock.rs crates/forge_repo/src/provider/bedrock.rs
- FileTooLong: tools/catalog.rs crates/forge_domain/src/tools/catalog.rs
- FileTooLong: src/context.rs crates/forge_domain/src/context.rs
- FileTooLong: src/utils.rs crates/forge_app/src/utils.rs
- MethodTooLong: ToolOperation.into_tool_output crates/forge_app/src/operation.rs:235
- MethodTooLong: UI.handle_subcommands crates/forge_main/src/ui.rs:466
- MethodTooLong: UI.on_command crates/forge_main/src/ui.rs:2167
- MethodTooLong: ChatCompletionMessage.try_from crates/forge_app/src/dto/openai/response.rs:324
- MethodTooLong: ToolExecutor.call_internal crates/forge_app/src/tool_executor.rs:151
- MethodTooLong: JsonRepairParser.parse_string crates/forge_json_repair/src/parser.rs:348
- MethodTooLong: Orchestrator.run crates/forge_app/src/orch.rs:245
- MethodTooLong: UI.select_model crates/forge_main/src/ui.rs:2904
- MethodTooLong: Renderer.render_event crates/forge_markdown_stream/src/renderer.rs:126
- MethodTooLong: ForgeApp.chat crates/forge_app/src/app.rs:60
- Duplicated block (8 lines × 2) crates/forge_app/src/dto/openai/response.rs:349
- Duplicated block (8 lines × 2) crates/forge_app/src/dto/openai/transformers/github_copilot_reasoning.rs:20
- Duplicated block (8 lines × 2) crates/forge_domain/src/conversation_html.rs:29
- Duplicated block (8 lines × 2) crates/forge_eventsource_stream/src/event_stream.rs:246
- Duplicated block (8 lines × 2) crates/forge_repo/src/provider/openai.rs:73
- Duplicated block (8 lines × 2) crates/forge_repo/src/provider/openai.rs:113
- Duplicated block (8 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:271
- Duplicated block (8 lines × 2) crates/forge_repo/src/provider/openai.rs:331
- Duplicated block (8 lines × 2) crates/forge_main/src/ui.rs:4580
- Off the main sequence: forge_display
- Off the main sequence: forge_json_repair
- Off the main sequence: forge_select
- Off the main sequence: forge_stream
- Off the main sequence: forge_walker
- Off the main sequence: forge_config
- Off the main sequence: forge_fs
- Off the main sequence: forge_eventsource_stream
- Duplicated block (13 lines × 2) crates/forge_app/src/dto/openai/response.rs:384
- Duplicated block (13 lines × 2) crates/forge_app/src/user_prompt.rs:76
- Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:267
- Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:284
- Duplicated block (13 lines × 2) crates/forge_repo/src/provider/bedrock.rs:722
- Duplicated block (13 lines × 2) crates/forge_services/src/tool_services/fs_search.rs:330
- Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:302
- FunctionTooLong: forge_select::preview::draw_preview_ui crates/forge_select/src/preview.rs:876
- FunctionTooLong: forge_select::preview::run_select_ui_values crates/forge_select/src/preview.rs:289
- FunctionTooLong: forge_app::utils::sanitize_gemini_schema crates/forge_app/src/utils.rs:626
- FunctionTooLong: forge_domain::conversation_html::create_conversation_context_section crates/forge_domain/src/conversation_html.rs:288
- FunctionTooLong: forge_services::tool_services::fs_patch::apply_replacement crates/forge_services/src/tool_services/fs_patch.rs:202
- FunctionTooLong: forge_markdown_stream::table::wrap crates/forge_markdown_stream/src/table.rs:135
- forge_markdown_stream::table::wrap (cognitive 99) crates/forge_markdown_stream/src/table.rs:135
- forge_markdown_stream::table::split_word_at_width (cognitive 59) crates/forge_markdown_stream/src/table.rs:304
- forge_markdown_stream::table::render_table (cognitive 25) crates/forge_markdown_stream/src/table.rs:10
- forge_markdown_stream::utils::collapse_ansi_codes (cognitive 22) crates/forge_markdown_stream/src/utils.rs:340
- forge_markdown_stream::utils::parse_atoms (cognitive 16) crates/forge_markdown_stream/src/utils.rs:261
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) crates/forge_app/src/dto/openai/response.rs:360
- Duplicated block (9 lines × 2) crates/forge_json_repair/src/schema_coercion.rs:77
- Duplicated block (9 lines × 2) crates/forge_app/src/template_engine.rs:27
- Duplicated block (9 lines × 2) crates/forge_repo/src/agent.rs:89
- Duplicated block (9 lines × 2) crates/forge_app/src/operation.rs:250
- Duplicated block (7 lines × 2) crates/forge_domain/src/message.rs:44
- Duplicated block (7 lines × 2) crates/forge_domain/src/policies/policy.rs:39
- Duplicated block (7 lines × 2) crates/forge_spinner/src/lib.rs:151
- Duplicated block (7 lines × 2) crates/forge_infra/src/http.rs:273
- Duplicated block (7 lines × 2) crates/forge_app/src/operation.rs:533
- Duplicated block (5 lines × 2) crates/forge_domain/src/tool_order.rs:94
- Duplicated block (5 lines × 2) crates/forge_main/src/ui.rs:2495
- Duplicated block (5 lines × 2) crates/forge_markdown_stream/src/theme.rs:294
- Duplicated block (5 lines × 2) crates/forge_select/src/preview.rs:758
- Duplicated block (5 lines × 2) crates/forge_select/src/preview.rs:791
- UI::handle_subcommands (cyclomatic 83) crates/forge_main/src/ui.rs:466
- UI::on_command (cyclomatic 56) crates/forge_main/src/ui.rs:2167
- UI::select_model (cyclomatic 24) crates/forge_main/src/ui.rs:2904
- UI::handle_chat_response (cyclomatic 20) crates/forge_main/src/ui.rs:4140
- JsonRepairParser::parse_string (cyclomatic 37) crates/forge_json_repair/src/parser.rs:348
- JsonRepairParser::parse_unquoted_string (cyclomatic 25) crates/forge_json_repair/src/parser.rs:694
- JsonRepairParser::parse_number (cyclomatic 18) crates/forge_json_repair/src/parser.rs:595
- JsonRepairParser::parse_object (cyclomatic 17) crates/forge_json_repair/src/parser.rs:195
- forge_app::utils::sanitize_gemini_schema (cognitive 107) crates/forge_app/src/utils.rs:626
- forge_app::utils::enforce_strict_schema (cognitive 28) crates/forge_app/src/utils.rs:448
- forge_app::fmt::todo_fmt::format_todos_diff (cognitive 20) crates/forge_app/src/fmt/todo_fmt.rs:56
- forge_app::dto::anthropic::response::get_context_length (cognitive 16) crates/forge_app/src/dto/anthropic/response.rs:81
- JsonRepairParser::parse_string (cognitive 83) crates/forge_json_repair/src/parser.rs:348
- JsonRepairParser::parse_unquoted_string (cognitive 47) crates/forge_json_repair/src/parser.rs:694
- JsonRepairParser::parse_object (cognitive 33) crates/forge_json_repair/src/parser.rs:195
- JsonRepairParser::parse_number (cognitive 28) crates/forge_json_repair/src/parser.rs:595
- forge_select::preview::run_select_ui_values (cognitive 78) crates/forge_select/src/preview.rs:289
- forge_select::preview::draw_preview_ui (cognitive 57) crates/forge_select/src/preview.rs:876
- forge_select::preview::wrap_ansi_line (cognitive 27) crates/forge_select/src/preview.rs:1194
- forge_select::preview::handle_key_event (cognitive 18) crates/forge_select/src/preview.rs:623
- forge_domain::conversation_html::create_conversation_context_section (cognitive 55) crates/forge_domain/src/conversation_html.rs:288
- forge_domain::conversation_html::create_info_table (cognitive 24) crates/forge_domain/src/conversation_html.rs:136
- forge_domain::compact::summary::extract_tool_info (cognitive 21) crates/forge_domain/src/compact/summary.rs:339
- forge_domain::compact::strategy::find_sequence_preserving_last_n (cognitive 16) crates/forge_domain/src/compact/strategy.rs:81
- Change-coupling hub: orch.rs → agent_executor.rs, compact_config.rs, event.rs, system_context.rs, conversation.rs, template.rs crates/forge_app/src/orch.rs
- Change-coupling hub: fmt_input.rs → operation.rs, tool_executor.rs, summary.rs crates/forge_app/src/fmt/fmt_input.rs
- Change-coupling hub: executor.rs → operation.rs, attachment.rs, shell.rs crates/forge_infra/src/executor.rs
- Change-coupling hub: api.rs → command_generator.rs, services.rs, repo.rs, app_config.rs, conversation.rs crates/forge_api/src/api.rs
- Duplicated block (12 lines × 2) crates/forge_json_repair/src/parser.rs:616
- Duplicated block (12 lines × 2) crates/forge_json_repair/src/schema_coercion.rs:167
- Duplicated block (12 lines × 2) crates/forge_main/src/ui.rs:516
- Duplicated block (12 lines × 2) crates/forge_infra/src/auth/strategy.rs:185
- Duplicated block (10 lines × 2) crates/forge_json_repair/src/parser.rs:598
- Duplicated block (10 lines × 2) crates/forge_repo/src/provider/bedrock.rs:735
- Duplicated block (10 lines × 2) crates/forge_select/src/multi.rs:33
- Duplicated block (10 lines × 2) crates/forge_repo/src/provider/openai_responses/response.rs:206
- Duplicated block (6 lines × 2) crates/forge_infra/src/auth/strategy.rs:464
- Duplicated block (6 lines × 2) crates/forge_main/src/ui.rs:1043
- Duplicated block (6 lines × 2) crates/forge_main/src/ui.rs:1398
- Duplicated block (6 lines × 2) crates/forge_app/src/utils.rs:103
- forge_app::utils::sanitize_gemini_schema (cyclomatic 45) crates/forge_app/src/utils.rs:626
- forge_app::dto::anthropic::response::get_context_length (cyclomatic 17) crates/forge_app/src/dto/anthropic/response.rs:81
- forge_app::utils::enforce_strict_schema (cyclomatic 17) crates/forge_app/src/utils.rs:448
- forge_select::preview::run_select_ui_values (cyclomatic 43) crates/forge_select/src/preview.rs:289
- forge_select::preview::handle_key_event (cyclomatic 35) crates/forge_select/src/preview.rs:623
- forge_select::preview::draw_preview_ui (cyclomatic 28) crates/forge_select/src/preview.rs:876
- forge_markdown_stream::table::wrap (cyclomatic 33) crates/forge_markdown_stream/src/table.rs:135
- forge_markdown_stream::utils::collapse_ansi_codes (cyclomatic 29) crates/forge_markdown_stream/src/utils.rs:340
- forge_markdown_stream::table::split_word_at_width (cyclomatic 17) crates/forge_markdown_stream/src/table.rs:304
- forge_json_repair::schema_coercion::coerce_value_with_schema_object (cognitive 71) crates/forge_json_repair/src/schema_coercion.rs:38
- forge_json_repair::schema_coercion::coerce_array_value (cognitive 25) crates/forge_json_repair/src/schema_coercion.rs:323
- forge_json_repair::schema_coercion::try_coerce_string (cognitive 23) crates/forge_json_repair/src/schema_coercion.rs:243
- REDACTED
- REDACTED
- REDACTED
- Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:16
- Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/conversation_style.css:256
- forge_json_repair::schema_coercion::coerce_value_with_schema_object (cyclomatic 36) crates/forge_json_repair/src/schema_coercion.rs:38
- forge_json_repair::schema_coercion::try_coerce_string (cyclomatic 21) crates/forge_json_repair/src/schema_coercion.rs:243
- ChatCompletionMessage::try_from (cyclomatic 28) crates/forge_app/src/dto/openai/response.rs:324
- ChatCompletionMessage::try_from (cyclomatic 17) crates/forge_app/src/dto/google/response.rs:451
- forge_domain::compact::summary::extract_tool_info (cyclomatic 22) crates/forge_domain/src/compact/summary.rs:339
- forge_domain::conversation_html::create_conversation_context_section (cyclomatic 20) crates/forge_domain/src/conversation_html.rs:288
- ChatCompletionMessage::try_from (cognitive 76) crates/forge_app/src/dto/openai/response.rs:324
- ChatCompletionMessage::try_from (cognitive 35) crates/forge_app/src/dto/google/response.rs:451
- forge_main::zsh::paste::wrap_tokens (cognitive 20) crates/forge_main/src/zsh/paste.rs:141
- forge_main::highlighter::highlight_mentions (cognitive 17) crates/forge_main/src/highlighter.rs:74
- TooManyMethods: UI crates/forge_main/src/ui.rs:105
- TooManyMethods: JsonRepairParser crates/forge_json_repair/src/parser.rs:5
- ClassTooLong: JsonRepairParser crates/forge_json_repair/src/parser.rs:5
- ClassTooLong: ForgeRepo crates/forge_repo/src/forge_repo.rs:41
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2) crates/forge_app/src/operation.rs:463
- Duplicated block (22 lines × 2) crates/forge_json_repair/src/schema_coercion.rs:135
- Duplicated block (15 lines × 2) crates/forge_app/src/utils.rs:19
- Duplicated block (15 lines × 2) crates/forge_json_repair/src/parser.rs:196
- Duplicated block (11 lines × 2) crates/forge_domain/src/conversation_html.rs:181
- Duplicated block (11 lines × 2) crates/forge_main/src/ui.rs:4091
- Duplicated block (10–11 lines × 2) crates/forge_main/src/conversation_selector.rs:72
- Duplicated block (10–11 lines × 2) crates/forge_main/src/ui.rs:1460
- Duplicated block (7 lines × 3) crates/forge_app/src/operation.rs:302
- Duplicated block (7 lines × 3) crates/forge_repo/src/provider/anthropic.rs:46
- Page without a main landmark crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:2
- Accessibility enforcement below the top rung
- ToolOperation::into_tool_output (cyclomatic 51) crates/forge_app/src/operation.rs:235
- Renderer::render_event (cyclomatic 36) crates/forge_markdown_stream/src/renderer.rs:126
- ToolCatalog::to_content (cyclomatic 26) crates/forge_app/src/fmt/fmt_input.rs:9
- forge_fs::binary_detection::is_binary_internal (cyclomatic 19) crates/forge_fs/src/binary_detection.rs:43
- Walker::get_blocking (cyclomatic 19) crates/forge_walker/src/walker.rs:118
- Agent::apply_config (cyclomatic 18) crates/forge_app/src/agent.rs:95
- ContextSummary::from (cyclomatic 17) crates/forge_domain/src/compact/summary.rs:218
- ToolCallFull::try_from_parts (cyclomatic 17) crates/forge_domain/src/tools/call/tool_call.rs:106
- ForgeCommandManager::parse (cyclomatic 17) crates/forge_main/src/model.rs:288
- OpenAIResponsesProvider::get_headers_for_conversation (cyclomatic 17) crates/forge_repo/src/provider/openai_responses/repository.rs:76
- forge_services::tool_services::fs_patch::apply_replacement (cyclomatic 17) crates/forge_services/src/tool_services/fs_patch.rs:202
- Response::into_domain (cyclomatic 16) crates/forge_repo/src/provider/openai_responses/response.rs:156
- DiffFormat::format (cyclomatic 16) crates/forge_display/src/diff.rs:50
- OpenAIProvider::get_headers (cyclomatic 16) crates/forge_repo/src/provider/openai.rs:72
- ForgeProviderRepository::migrate_env_to_file (cyclomatic 16) crates/forge_repo/src/provider/provider_repo.rs:337
- ToolOperation::into_tool_output (cognitive 82) crates/forge_app/src/operation.rs:235
- ContextSummary::from (cognitive 46) crates/forge_domain/src/compact/summary.rs:218
- Response::into_domain (cognitive 43) crates/forge_repo/src/provider/openai_responses/response.rs:156
- DiffFormat::format (cognitive 37) crates/forge_display/src/diff.rs:50
- ForgeProviderAuthService::refresh_provider_credential (cognitive 34) crates/forge_services/src/provider_auth.rs:149
- ToolCallFull::try_from_parts (cognitive 33) crates/forge_domain/src/tools/call/tool_call.rs:106
- Orchestrator::run (cognitive 28) crates/forge_app/src/orch.rs:245
- forge_infra::auth::strategy::poll_for_tokens (cognitive 28) crates/forge_infra/src/auth/strategy.rs:794
- ZshRPrompt::fmt (cognitive 26) crates/forge_main/src/zsh/rprompt.rs:98
- forge_services::tool_services::fs_patch::apply_replacement (cognitive 25) crates/forge_services/src/tool_services/fs_patch.rs:202
- Message::from_domain (cognitive 24) crates/forge_repo/src/provider/bedrock.rs:762
- ForgeCommandManager::parse (cognitive 24) crates/forge_main/src/model.rs:288
- DoomLoopDetector::count_recent_pattern_repetitions (cognitive 22) crates/forge_app/src/hooks/doom_loop.rs:117
- forge_fs::binary_detection::is_binary_internal (cognitive 22) crates/forge_fs/src/binary_detection.rs:43
- ForgeMcpClient::create_connection (cognitive 21) crates/forge_infra/src/mcp_client.rs:95
- ForgeSkillRepository::load_skills_from_dir (cognitive 21) crates/forge_repo/src/skill.rs:119
- ForgeFetch::check_robots_txt (cognitive 21) crates/forge_services/src/tool_services/fetch.rs:31
- Walker::get_blocking (cognitive 21) crates/forge_walker/src/walker.rs:118
- SanitizeToolIds::transform (cognitive 20) crates/forge_repo/src/provider/bedrock_sanitize_ids.rs:29
- forge_tool_macros::derive_description (cognitive 19) crates/forge_tool_macros/src/lib.rs:16
- Request::from (cognitive 18) crates/forge_app/src/dto/google/request.rs:302
- TrimToolCallIds::transform (cognitive 18) crates/forge_app/src/dto/openai/transformers/trim_tool_call_ids.rs:12
- ForgeProviderRepository::migrate_env_to_file (cognitive 18) crates/forge_repo/src/provider/provider_repo.rs:337
- AgentExecutor::execute (cognitive 17) crates/forge_app/src/agent_executor.rs:42
- ContextMessage::to_text (cognitive 17) crates/forge_domain/src/context.rs:113
- ForgeDirectoryReaderService::read_directory_files (cognitive 17) crates/forge_infra/src/fs_read_dir.rs:68
- ForgePrompt::render_prompt_right (cognitive 17) crates/forge_main/src/prompt.rs:116
- ForgeFsSearch::search_content (cognitive 17) crates/forge_services/src/tool_services/fs_search.rs:421
- ForgeHttpInfra::new (cognitive 16) crates/forge_infra/src/http.rs:39
- Info::from (cognitive 16) crates/forge_main/src/info.rs:418
- Renderer::render_event (cognitive 16) crates/forge_markdown_stream/src/renderer.rs:126
- REDACTED
- TooManyFields: ForgeConfig crates/forge_config/src/config.rs:121
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (33 shared lines) crates/forge_repo/src/provider/openai.rs:72
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/forge_repo/src/provider/anthropic.rs:368
- Duplicated block (26–27 lines × 2) crates/forge_markdown_stream/src/table.rs:149
- Duplicated block (24 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:514
- Duplicated block (19–20 lines × 2) crates/forge_infra/src/mcp_client.rs:407
- Duplicated block (17–18 lines × 2) crates/forge_infra/src/auth/strategy.rs:243
- Duplicated block (16–18 lines × 2) crates/forge_main/src/conversation_selector.rs:58
- Duplicated block (14–17 lines × 2) crates/forge_main/src/ui.rs:3163
- Duplicated block (14–16 lines × 2) crates/forge_main/src/conversation_selector.rs:54
- Duplicated block (16 lines × 2) crates/forge_repo/src/provider/openai.rs:83
- Duplicated block (13–16 lines × 2) crates/forge_services/src/provider_auth.rs:37
- Duplicated block (14 lines × 2) crates/forge_services/src/auth.rs:25
- Duplicated block (11 lines × 4) crates/forge_json_repair/src/schema_coercion.rs:135
- Duplicated block (11 lines × 3) crates/forge_main/src/conversation_selector.rs:58
- Duplicated block (6–10 lines × 3) crates/forge_app/src/dto/anthropic/response.rs:362
- Duplicated block (9 lines × 4) crates/forge_repo/src/provider/anthropic.rs:372
- Duplicated block (8–9 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:320
- Duplicated block (7–8 lines × 2) crates/forge_main/src/ui.rs:2174
- Duplicated block (6–7 lines × 2) crates/forge_main/src/ui.rs:1450
- Duplicated block (5 lines × 3) crates/forge_services/src/tool_services/fs_patch.rs:249
- Unstable project forge_api
- Unstable project forge_infra
- Unstable project forge_repo
- Low cohesion: Context (LCOM4 4) crates/forge_domain/src/context.rs:401
Minor — 87 finding(s)
- Orphaned file crates/forge_eventsource_stream/src/event_stream.rs:1
- Orphaned file crates/forge_domain/src/tool_order.rs:1
- Orphaned file crates/forge_app/src/terminal_context.rs:1
- Orphaned file crates/forge_markdown_stream/src/renderer.rs:1
- Orphaned file crates/forge_domain/src/policies/policy.rs:1
- Orphaned file crates/forge_eventsource/src/event_source.rs:1
- Orphaned file crates/forge_domain/src/message_pattern.rs:1
- Orphaned file crates/forge_template/src/element.rs:1
- Orphaned file crates/forge_markdown_stream/src/lib.rs:1
- Orphaned file crates/forge_app/src/transformers/dedupe_role.rs:1
- Orphaned file crates/forge_app/src/transformers/drop_role.rs:1
- Orphaned file crates/forge_app/src/dto/openai/transformers/set_reasoning_effort.rs:1
- Orphaned file crates/forge_domain/src/temperature.rs:1
- Orphaned file crates/forge_domain/src/top_p.rs:1
- Orphaned file crates/forge_domain/src/xml.rs:1
- Orphaned file crates/forge_domain/src/max_tokens.rs:1
- Orphaned file crates/forge_app/src/dto/openai/error.rs:1
- Orphaned file crates/forge_domain/src/top_k.rs:1
- Orphaned file crates/forge_app/src/truncation/truncate_search.rs:1
- Orphaned file crates/forge_fs/src/binary_detection.rs:1
- Orphaned file crates/forge_eventsource_stream/src/utf8_stream.rs:1
- Orphaned file crates/forge_domain/src/tools/result.rs:1
- Orphaned file crates/forge_services/src/range.rs:1
- Orphaned file crates/forge_main/src/sandbox.rs:1
- Orphaned file crates/forge_app/src/dto/openai/transformers/when_model.rs:1
- Interpolated log message defeats structured logging crates/forge_repo/src/skill.rs:209
- Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:470
- Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:532
- Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:536
- Interpolated log message defeats structured logging crates/forge_repo/src/database/pool.rs:98
- Interpolated log message defeats structured logging crates/forge_repo/src/conversation/conversation_record.rs:784
- Interpolated log message defeats structured logging crates/forge_infra/src/http.rs:81
- Interpolated log message defeats structured logging crates/forge_infra/src/http.rs:88
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:118
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:147
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:224
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:228
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:237
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:240
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:279
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:325
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:371
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:375
- Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:611
- Interpolated log message defeats structured logging crates/forge_app/src/app.rs:202
- Interpolated log message defeats structured logging crates/forge_app/src/compact.rs:79
- Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:78
- Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:90
- Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:103
- Silent fallback default on Err crates/forge_app/src/terminal_context.rs:65
- Silent fallback default on Err crates/forge_repo/src/provider/provider_repo.rs:593
- Silent fallback default on Err crates/forge_select/src/preview.rs:755
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Duplicated predicate crates/forge_main/src/completer/input_completer.rs:74
- Duplicated predicate crates/forge_main/src/prompt.rs:190
- Subsumed condition operand crates/forge_main/src/prompt.rs:433
- Subsumed condition operand benchmarks/parse.ts:37
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
Minor — 1 finding(s)
- Outdated: google-cloud-auth
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fc890ca10ed14a228205f76ccc6bcc24/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fc890ca10ed14a228205f76ccc6bcc24/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 58 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 30 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |