Executive summary
sigoden/aichat falls short of our standard for a preview release, in part because it has controls that only work with a mouse. It scores 36 out of 100 and is rated Weak, and 11 of its 25 critical findings are security problems in the build pipeline and in the packages it uses.
Accessibility, at 26, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Adding access checks comes next, worth about 6 points. Raising Accessibility to 65 would lift the score to about 44.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five controls can't be used without a mouse, and five buttons or links have no name a screen reader can say. Pinning each tool to an exact version, making the controls work with a keyboard and naming the buttons and links would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole. The three form fields without a label need a label.
The product code is 15,282 lines, about €13,000 to rebuild.
If Accessibility rose from 26 to 65, the lowest score rated Strong, the score would rise from 36 to about 44.
New since the last survey: 10 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
Fixed since the last survey: 5 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 228 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,282 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: which parts of the code depend on which
| uses → | 1 cli | 2 client.access_token | 3 rag.serde_vectors | 4 rag.splitter.language | 5 render | 6 render.markdown | 7 repl.highlighter | 8 repl.prompt | 9 utils | 10 utils.abort_signal | 11 utils.clipboard | 12 utils.clipboard.internal | 13 utils.command | 14 utils.spinner | 15 client.azure_openai | 16 client.bedrock | 17 client.claude | 18 client.cohere | 19 client.gemini | 20 client.openai_compatible | 21 client.vertexai | 22 config.role | 23 rag | 24 client.openai | 25 config.session | 26 rag.splitter | 27 client | 28 config | 29 config.agent | 30 function | 31 client.stream | 32 client.common | 33 render.stream | 34 client.model | 35 serve | 36 client.message | 37 config.input | 38 aichat | 39 repl | 40 repl.completer |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cli | ||||||||||||||||||||||||||||||||||||||||
| 2 client.access_token | ||||||||||||||||||||||||||||||||||||||||
| 3 rag.serde_vectors | ||||||||||||||||||||||||||||||||||||||||
| 4 rag.splitter.language | ||||||||||||||||||||||||||||||||||||||||
| 5 render | ||||||||||||||||||||||||||||||||||||||||
| 6 render.markdown | ||||||||||||||||||||||||||||||||||||||||
| 7 repl.highlighter | ||||||||||||||||||||||||||||||||||||||||
| 8 repl.prompt | ||||||||||||||||||||||||||||||||||||||||
| 9 utils | ||||||||||||||||||||||||||||||||||||||||
| 10 utils.abort_signal | ||||||||||||||||||||||||||||||||||||||||
| 11 utils.clipboard | ||||||||||||||||||||||||||||||||||||||||
| 12 utils.clipboard.internal | ||||||||||||||||||||||||||||||||||||||||
| 13 utils.command | ||||||||||||||||||||||||||||||||||||||||
| 14 utils.spinner | ||||||||||||||||||||||||||||||||||||||||
| 15 client.azure_openai | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 client.bedrock | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 client.claude | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 18 client.cohere | 1 | 1 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 19 client.gemini | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 client.openai_compatible | 1 | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 client.vertexai | 1 | 1 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 config.role | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 rag | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 client.openai | 1 | 1 | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||
| 25 config.session | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 rag.splitter | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 client | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 8 | 30 | 10 | ||||||||||||||||||||||||||||
| 28 config | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 29 config.agent | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 30 function | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 client.stream | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 client.common | 2 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 33 render.stream | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 client.model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 serve | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 client.message | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 config.input | 2 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 38 aichat | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 repl | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 repl.completer | 1 |
15→27 client.azure_openai uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.azure_openai uses a type in client.
- The types involved
aichat.client.azure_openai.azure_openai$module→aichat.client.AzureOpenAIClient
- Direction
- client.azure_openai uses client, so a change to client can break client.azure_openai, while a change to client.azure_openai can't break client.
- 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→32 client.azure_openai uses client.common part of a loop✕
- Connections
- 4 pairs of types, where a type in client.azure_openai uses a type in client.common.
- The types involved
aichat.client.azure_openai.AzureOpenAIConfig→aichat.client.common.ExtraConfigaichat.client.azure_openai.AzureOpenAIConfig→aichat.client.common.RequestPatchaichat.client.azure_openai.azure_openai$module→aichat.client.common.ChatCompletionsDataaichat.client.azure_openai.azure_openai$module→aichat.client.common.EmbeddingsData
- Direction
- client.azure_openai uses client.common, so a change to client.common can break client.azure_openai, while a change to client.azure_openai can't break client.common.
- 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→34 client.azure_openai uses client.model part of a loop✕
- Connections
- 1 pair of types, where a type in client.azure_openai uses a type in client.model.
- The types involved
aichat.client.azure_openai.AzureOpenAIConfig→aichat.client.model.ModelData
- Direction
- client.azure_openai uses client.model, so a change to client.model can break client.azure_openai, while a change to client.azure_openai can't break client.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.
16→31 client.bedrock uses client.stream part of a loop✕
- Connections
- 1 pair of types, where a type in client.bedrock uses a type in client.stream.
- The types involved
aichat.client.bedrock.bedrock$module→aichat.client.stream.SseHandler
- Direction
- client.bedrock uses client.stream, so a change to client.stream can break client.bedrock, while a change to client.bedrock can't break client.stream.
- 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→32 client.bedrock uses client.common part of a loop✕
- Connections
- 3 pairs of types, where a type in client.bedrock uses a type in client.common.
- The types involved
aichat.client.bedrock.BedrockConfig→aichat.client.common.ExtraConfigaichat.client.bedrock.BedrockConfig→aichat.client.common.RequestPatchaichat.client.bedrock.bedrock$module→aichat.client.common.ChatCompletionsData
- Direction
- client.bedrock uses client.common, so a change to client.common can break client.bedrock, while a change to client.bedrock can't break client.common.
- 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→34 client.bedrock uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.bedrock uses a type in client.model.
- The types involved
aichat.client.bedrock.BedrockConfig→aichat.client.model.ModelDataaichat.client.bedrock.bedrock$module→aichat.client.model.Model
- Direction
- client.bedrock uses client.model, so a change to client.model can break client.bedrock, while a change to client.bedrock can't break client.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→27 client.claude uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.claude uses a type in client.
- The types involved
aichat.client.claude.claude$module→aichat.client.ClaudeClient
- Direction
- client.claude uses client, so a change to client can break client.claude, while a change to client.claude can't break client.
- 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→31 client.claude uses client.stream part of a loop✕
- Connections
- 1 pair of types, where a type in client.claude uses a type in client.stream.
- The types involved
aichat.client.claude.claude$module→aichat.client.stream.SseHandler
- Direction
- client.claude uses client.stream, so a change to client.stream can break client.claude, while a change to client.claude can't break client.stream.
- 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→32 client.claude uses client.common part of a loop✕
- Connections
- 3 pairs of types, where a type in client.claude uses a type in client.common.
- The types involved
aichat.client.claude.ClaudeConfig→aichat.client.common.ExtraConfigaichat.client.claude.ClaudeConfig→aichat.client.common.RequestPatchaichat.client.claude.claude$module→aichat.client.common.ChatCompletionsData
- Direction
- client.claude uses client.common, so a change to client.common can break client.claude, while a change to client.claude can't break client.common.
- 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→34 client.claude uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.claude uses a type in client.model.
- The types involved
aichat.client.claude.ClaudeConfig→aichat.client.model.ModelDataaichat.client.claude.claude$module→aichat.client.model.Model
- Direction
- client.claude uses client.model, so a change to client.model can break client.claude, while a change to client.claude can't break client.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.
18→27 client.cohere uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.cohere uses a type in client.
- The types involved
aichat.client.cohere.cohere$module→aichat.client.CohereClient
- Direction
- client.cohere uses client, so a change to client can break client.cohere, while a change to client.cohere can't break client.
- 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→31 client.cohere uses client.stream part of a loop✕
- Connections
- 1 pair of types, where a type in client.cohere uses a type in client.stream.
- The types involved
aichat.client.cohere.cohere$module→aichat.client.stream.SseHandler
- Direction
- client.cohere uses client.stream, so a change to client.stream can break client.cohere, while a change to client.cohere can't break client.stream.
- 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→32 client.cohere uses client.common part of a loop✕
- Connections
- 5 pairs of types, where a type in client.cohere uses a type in client.common.
- The types involved
aichat.client.cohere.CohereConfig→aichat.client.common.ExtraConfigaichat.client.cohere.CohereConfig→aichat.client.common.RequestPatchaichat.client.cohere.cohere$module→aichat.client.common.ChatCompletionsDataaichat.client.cohere.cohere$module→aichat.client.common.EmbeddingsDataaichat.client.cohere.cohere$module→aichat.client.common.RerankData
- Direction
- client.cohere uses client.common, so a change to client.common can break client.cohere, while a change to client.cohere can't break client.common.
- 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→34 client.cohere uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.cohere uses a type in client.model.
- The types involved
aichat.client.cohere.CohereConfig→aichat.client.model.ModelDataaichat.client.cohere.cohere$module→aichat.client.model.Model
- Direction
- client.cohere uses client.model, so a change to client.model can break client.cohere, while a change to client.cohere can't break client.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.
19→27 client.gemini uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.gemini uses a type in client.
- The types involved
aichat.client.gemini.gemini$module→aichat.client.GeminiClient
- Direction
- client.gemini uses client, so a change to client can break client.gemini, while a change to client.gemini can't break client.
- 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→32 client.gemini uses client.common part of a loop✕
- Connections
- 4 pairs of types, where a type in client.gemini uses a type in client.common.
- The types involved
aichat.client.gemini.GeminiConfig→aichat.client.common.ExtraConfigaichat.client.gemini.GeminiConfig→aichat.client.common.RequestPatchaichat.client.gemini.gemini$module→aichat.client.common.ChatCompletionsDataaichat.client.gemini.gemini$module→aichat.client.common.EmbeddingsData
- Direction
- client.gemini uses client.common, so a change to client.common can break client.gemini, while a change to client.gemini can't break client.common.
- 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→34 client.gemini uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.gemini uses a type in client.model.
- The types involved
aichat.client.gemini.GeminiConfig→aichat.client.model.ModelDataaichat.client.gemini.gemini$module→aichat.client.model.Model
- Direction
- client.gemini uses client.model, so a change to client.model can break client.gemini, while a change to client.gemini can't break client.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.
20→27 client.openai_compatible uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.openai_compatible uses a type in client.
- The types involved
aichat.client.openai_compatible.openai_compatible$module→aichat.client.OpenAICompatibleClient
- Direction
- client.openai_compatible uses client, so a change to client can break client.openai_compatible, while a change to client.openai_compatible can't break client.
- 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→32 client.openai_compatible uses client.common part of a loop✕
- Connections
- 5 pairs of types, where a type in client.openai_compatible uses a type in client.common.
- The types involved
aichat.client.openai_compatible.OpenAICompatibleConfig→aichat.client.common.ExtraConfigaichat.client.openai_compatible.OpenAICompatibleConfig→aichat.client.common.RequestPatchaichat.client.openai_compatible.openai_compatible$module→aichat.client.common.ChatCompletionsDataaichat.client.openai_compatible.openai_compatible$module→aichat.client.common.EmbeddingsDataaichat.client.openai_compatible.openai_compatible$module→aichat.client.common.RerankData
- Direction
- client.openai_compatible uses client.common, so a change to client.common can break client.openai_compatible, while a change to client.openai_compatible can't break client.common.
- 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→34 client.openai_compatible uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.openai_compatible uses a type in client.model.
- The types involved
aichat.client.openai_compatible.OpenAICompatibleConfig→aichat.client.model.ModelDataaichat.client.openai_compatible.openai_compatible$module→aichat.client.model.Model
- Direction
- client.openai_compatible uses client.model, so a change to client.model can break client.openai_compatible, while a change to client.openai_compatible can't break client.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.
21→27 client.vertexai uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.vertexai uses a type in client.
- The types involved
aichat.client.vertexai.vertexai$module→aichat.client.VertexAIClient
- Direction
- client.vertexai uses client, so a change to client can break client.vertexai, while a change to client.vertexai can't break client.
- 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→31 client.vertexai uses client.stream part of a loop✕
- Connections
- 1 pair of types, where a type in client.vertexai uses a type in client.stream.
- The types involved
aichat.client.vertexai.vertexai$module→aichat.client.stream.SseHandler
- Direction
- client.vertexai uses client.stream, so a change to client.stream can break client.vertexai, while a change to client.vertexai can't break client.stream.
- 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→32 client.vertexai uses client.common part of a loop✕
- Connections
- 5 pairs of types, where a type in client.vertexai uses a type in client.common.
- The types involved
aichat.client.vertexai.VertexAIConfig→aichat.client.common.ExtraConfigaichat.client.vertexai.VertexAIConfig→aichat.client.common.RequestPatchaichat.client.vertexai.vertexai$module→aichat.client.common.ChatCompletionsDataaichat.client.vertexai.vertexai$module→aichat.client.common.Clientaichat.client.vertexai.vertexai$module→aichat.client.common.EmbeddingsData
- Direction
- client.vertexai uses client.common, so a change to client.common can break client.vertexai, while a change to client.vertexai can't break client.common.
- 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→34 client.vertexai uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.vertexai uses a type in client.model.
- The types involved
aichat.client.vertexai.VertexAIConfig→aichat.client.model.ModelDataaichat.client.vertexai.vertexai$module→aichat.client.model.Model
- Direction
- client.vertexai uses client.model, so a change to client.model can break client.vertexai, while a change to client.vertexai can't break client.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.
22→34 config.role uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in config.role uses a type in client.model.
- The types involved
aichat.config.role.Role→aichat.client.model.Modelaichat.config.role.RoleLike→aichat.client.model.Model
- Direction
- config.role uses client.model, so a change to client.model can break config.role, while a change to config.role can't break client.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.
22→36 config.role uses client.message part of a loop✕
- Connections
- 1 pair of types, where a type in config.role uses a type in client.message.
- The types involved
aichat.config.role.Role→aichat.client.message.Message
- Direction
- config.role uses client.message, so a change to client.message can break config.role, while a change to config.role can't break client.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.
22→37 config.role uses config.input part of a loop✕
- Connections
- 1 pair of types, where a type in config.role uses a type in config.input.
- The types involved
aichat.config.role.Role→aichat.config.input.Input
- Direction
- config.role uses config.input, so a change to config.input can break config.role, while a change to config.role can't break config.input.
- 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.
23→14 rag uses utils.spinner✕
- Connections
- 2 pairs of types, where a type in rag uses a type in utils.spinner.
- The types involved
aichat.rag.Rag→aichat.utils.spinner.Spinneraichat.rag.rag$module→aichat.utils.spinner.Spinner
- Direction
- rag uses utils.spinner, so a change to utils.spinner can break rag, while a change to rag can't break utils.spinner.
- Position
- Below the diagonal: rag uses a module listed above it, which is the healthy direction.
23→32 rag uses client.common part of a loop✕
- Connections
- 1 pair of types, where a type in rag uses a type in client.common.
- The types involved
aichat.rag.Rag→aichat.client.common.EmbeddingsData
- Direction
- rag uses client.common, so a change to client.common can break rag, while a change to rag can't break client.common.
- 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.
23→34 rag uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in rag uses a type in client.model.
- The types involved
aichat.rag.Rag→aichat.client.model.Modelaichat.rag.rag$module→aichat.client.model.Model
- Direction
- rag uses client.model, so a change to client.model can break rag, while a change to rag can't break client.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.
24→19 client.openai uses client.gemini✕
- Connections
- 1 pair of types, where a type in client.openai uses a type in client.gemini.
- The types involved
aichat.client.openai.EmbeddingsResBody→aichat.client.gemini.EmbeddingsResBodyEmbedding
- Direction
- client.openai uses client.gemini, so a change to client.gemini can break client.openai, while a change to client.openai can't break client.gemini.
- Position
- Below the diagonal: client.openai uses a module listed above it, which is the healthy direction.
24→27 client.openai uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.openai uses a type in client.
- The types involved
aichat.client.openai.openai$module→aichat.client.OpenAIClient
- Direction
- client.openai uses client, so a change to client can break client.openai, while a change to client.openai can't break client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→31 client.openai uses client.stream part of a loop✕
- Connections
- 1 pair of types, where a type in client.openai uses a type in client.stream.
- The types involved
aichat.client.openai.openai$module→aichat.client.stream.SseHandler
- Direction
- client.openai uses client.stream, so a change to client.stream can break client.openai, while a change to client.openai can't break client.stream.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→32 client.openai uses client.common part of a loop✕
- Connections
- 4 pairs of types, where a type in client.openai uses a type in client.common.
- The types involved
aichat.client.openai.OpenAIConfig→aichat.client.common.ExtraConfigaichat.client.openai.OpenAIConfig→aichat.client.common.RequestPatchaichat.client.openai.openai$module→aichat.client.common.ChatCompletionsDataaichat.client.openai.openai$module→aichat.client.common.EmbeddingsData
- Direction
- client.openai uses client.common, so a change to client.common can break client.openai, while a change to client.openai can't break client.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→34 client.openai uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.openai uses a type in client.model.
- The types involved
aichat.client.openai.OpenAIConfig→aichat.client.model.ModelDataaichat.client.openai.openai$module→aichat.client.model.Model
- Direction
- client.openai uses client.model, so a change to client.model can break client.openai, while a change to client.openai can't break client.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.
25→6 config.session uses render.markdown✕
- Connections
- 1 pair of types, where a type in config.session uses a type in render.markdown.
- The types involved
aichat.config.session.Session→aichat.render.markdown.MarkdownRender
- Direction
- config.session uses render.markdown, so a change to render.markdown can break config.session, while a change to config.session can't break render.markdown.
- Position
- Below the diagonal: config.session uses a module listed above it, which is the healthy direction.
25→22 config.session uses config.role✕
- Connections
- 2 pairs of types, where a type in config.session uses a type in config.role.
- The types involved
aichat.config.session.Session→aichat.config.role.Roleaichat.config.session.Session→aichat.config.role.RoleLike
- Direction
- config.session uses config.role, so a change to config.role can break config.session, while a change to config.session can't break config.role.
- Position
- Below the diagonal: config.session uses a module listed above it, which is the healthy direction.
25→28 config.session uses config part of a loop✕
- Connections
- 1 pair of types, where a type in config.session uses a type in config.
- The types involved
aichat.config.session.Session→aichat.config.Config
- Direction
- config.session uses config, so a change to config can break config.session, while a change to config.session can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→29 config.session uses config.agent part of a loop✕
- Connections
- 1 pair of types, where a type in config.session uses a type in config.agent.
- The types involved
aichat.config.session.Session→aichat.config.agent.Agent
- Direction
- config.session uses config.agent, so a change to config.agent can break config.session, while a change to config.session can't break config.agent.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 config.session uses client.model part of a loop✕
- Connections
- 1 pair of types, where a type in config.session uses a type in client.model.
- The types involved
aichat.config.session.Session→aichat.client.model.Model
- Direction
- config.session uses client.model, so a change to client.model can break config.session, while a change to config.session can't break client.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.
25→36 config.session uses client.message part of a loop✕
- Connections
- 1 pair of types, where a type in config.session uses a type in client.message.
- The types involved
aichat.config.session.Session→aichat.client.message.Message
- Direction
- config.session uses client.message, so a change to client.message can break config.session, while a change to config.session can't break client.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.
25→37 config.session uses config.input part of a loop✕
- Connections
- 1 pair of types, where a type in config.session uses a type in config.input.
- The types involved
aichat.config.session.Session→aichat.config.input.Input
- Direction
- config.session uses config.input, so a change to config.input can break config.session, while a change to config.session can't break config.input.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→23 rag.splitter uses rag✕
- Connections
- 1 pair of types, where a type in rag.splitter uses a type in rag.
- The types involved
aichat.rag.splitter.RecursiveCharacterTextSplitter→aichat.rag.RagDocument
- Direction
- rag.splitter uses rag, so a change to rag can break rag.splitter, while a change to rag.splitter can't break rag.
- Position
- Below the diagonal: rag.splitter uses a module listed above it, which is the healthy direction.
27→15 client uses client.azure_openai✕
- Connections
- 1 pair of types, where a type in client uses a type in client.azure_openai.
- The types involved
aichat.client.AzureOpenAIClient→aichat.client.azure_openai.AzureOpenAIConfig
- Direction
- client uses client.azure_openai, so a change to client.azure_openai can break client, while a change to client can't break client.azure_openai.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→16 client uses client.bedrock✕
- Connections
- 1 pair of types, where a type in client uses a type in client.bedrock.
- The types involved
aichat.client.BedrockClient→aichat.client.bedrock.BedrockConfig
- Direction
- client uses client.bedrock, so a change to client.bedrock can break client, while a change to client can't break client.bedrock.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→17 client uses client.claude✕
- Connections
- 1 pair of types, where a type in client uses a type in client.claude.
- The types involved
aichat.client.ClaudeClient→aichat.client.claude.ClaudeConfig
- Direction
- client uses client.claude, so a change to client.claude can break client, while a change to client can't break client.claude.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→18 client uses client.cohere✕
- Connections
- 1 pair of types, where a type in client uses a type in client.cohere.
- The types involved
aichat.client.CohereClient→aichat.client.cohere.CohereConfig
- Direction
- client uses client.cohere, so a change to client.cohere can break client, while a change to client can't break client.cohere.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→19 client uses client.gemini✕
- Connections
- 1 pair of types, where a type in client uses a type in client.gemini.
- The types involved
aichat.client.GeminiClient→aichat.client.gemini.GeminiConfig
- Direction
- client uses client.gemini, so a change to client.gemini can break client, while a change to client can't break client.gemini.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→20 client uses client.openai_compatible✕
- Connections
- 1 pair of types, where a type in client uses a type in client.openai_compatible.
- The types involved
aichat.client.OpenAICompatibleClient→aichat.client.openai_compatible.OpenAICompatibleConfig
- Direction
- client uses client.openai_compatible, so a change to client.openai_compatible can break client, while a change to client can't break client.openai_compatible.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→21 client uses client.vertexai✕
- Connections
- 1 pair of types, where a type in client uses a type in client.vertexai.
- The types involved
aichat.client.VertexAIClient→aichat.client.vertexai.VertexAIConfig
- Direction
- client uses client.vertexai, so a change to client.vertexai can break client, while a change to client can't break client.vertexai.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→24 client uses client.openai✕
- Connections
- 1 pair of types, where a type in client uses a type in client.openai.
- The types involved
aichat.client.OpenAIClient→aichat.client.openai.OpenAIConfig
- Direction
- client uses client.openai, so a change to client.openai can break client, while a change to client can't break client.openai.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
27→28 client uses config part of a loop✕
- Connections
- 1 pair of types, where a type in client uses a type in config.
- The types involved
aichat.client.client$module→aichat.config.Config
- Direction
- client uses config, so a change to config can break client, while a change to client can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→31 client uses client.stream part of a loop✕
- Connections
- 8 pairs of types, where a type in client uses a type in client.stream.
- The types involved
aichat.client.AzureOpenAIClient→aichat.client.stream.SseHandleraichat.client.BedrockClient→aichat.client.stream.SseHandleraichat.client.ClaudeClient→aichat.client.stream.SseHandleraichat.client.CohereClient→aichat.client.stream.SseHandleraichat.client.GeminiClient→aichat.client.stream.SseHandleraichat.client.OpenAIClient→aichat.client.stream.SseHandleraichat.client.OpenAICompatibleClient→aichat.client.stream.SseHandleraichat.client.VertexAIClient→aichat.client.stream.SseHandler
- Direction
- client uses client.stream, so a change to client.stream can break client, while a change to client can't break client.stream.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→32 client uses client.common part of a loop✕
- Connections
- 30 pairs of types, where a type in client uses a type in client.common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
aichat.client.AzureOpenAIClient→aichat.client.common.ChatCompletionsDataaichat.client.AzureOpenAIClient→aichat.client.common.Clientaichat.client.AzureOpenAIClient→aichat.client.common.EmbeddingsDataaichat.client.AzureOpenAIClient→aichat.client.common.RerankDataaichat.client.BedrockClient→aichat.client.common.ChatCompletionsDataaichat.client.BedrockClient→aichat.client.common.Clientaichat.client.BedrockClient→aichat.client.common.EmbeddingsDataaichat.client.ClaudeClient→aichat.client.common.ChatCompletionsDataaichat.client.ClaudeClient→aichat.client.common.Clientaichat.client.ClaudeClient→aichat.client.common.EmbeddingsDataaichat.client.ClaudeClient→aichat.client.common.RerankDataaichat.client.CohereClient→aichat.client.common.ChatCompletionsDataaichat.client.CohereClient→aichat.client.common.Clientaichat.client.CohereClient→aichat.client.common.EmbeddingsDataaichat.client.CohereClient→aichat.client.common.RerankDataaichat.client.GeminiClient→aichat.client.common.ChatCompletionsDataaichat.client.GeminiClient→aichat.client.common.Clientaichat.client.GeminiClient→aichat.client.common.EmbeddingsDataaichat.client.GeminiClient→aichat.client.common.RerankDataaichat.client.OpenAIClient→aichat.client.common.ChatCompletionsDataaichat.client.OpenAIClient→aichat.client.common.Clientaichat.client.OpenAIClient→aichat.client.common.EmbeddingsDataaichat.client.OpenAIClient→aichat.client.common.RerankDataaichat.client.OpenAICompatibleClient→aichat.client.common.ChatCompletionsDataaichat.client.OpenAICompatibleClient→aichat.client.common.Client
- Direction
- client uses client.common, so a change to client.common can break client, while a change to client can't break client.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→34 client uses client.model part of a loop✕
- Connections
- 10 pairs of types, where a type in client uses a type in client.model.
- The types involved
aichat.client.AzureOpenAIClient→aichat.client.model.Modelaichat.client.BedrockClient→aichat.client.model.Modelaichat.client.ClaudeClient→aichat.client.model.Modelaichat.client.CohereClient→aichat.client.model.Modelaichat.client.GeminiClient→aichat.client.model.Modelaichat.client.OpenAIClient→aichat.client.model.Modelaichat.client.OpenAICompatibleClient→aichat.client.model.Modelaichat.client.VertexAIClient→aichat.client.model.Modelaichat.client.client$module→aichat.client.model.Modelaichat.client.client$module→aichat.client.model.ModelType
- Direction
- client uses client.model, so a change to client.model can break client, while a change to client can't break client.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.
28→22 config uses config.role✕
- Connections
- 1 pair of types, where a type in config uses a type in config.role.
- The types involved
aichat.config.Config→aichat.config.role.Role
- Direction
- config uses config.role, so a change to config.role can break config, while a change to config can't break config.role.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→23 config uses rag✕
- Connections
- 1 pair of types, where a type in config uses a type in rag.
- The types involved
aichat.config.Config→aichat.rag.Rag
- Direction
- config uses rag, so a change to rag can break config, while a change to config can't break rag.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→25 config uses config.session✕
- Connections
- 1 pair of types, where a type in config uses a type in config.session.
- The types involved
aichat.config.Config→aichat.config.session.Session
- Direction
- config uses config.session, so a change to config.session can break config, while a change to config can't break config.session.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→27 config uses client✕
- Connections
- 1 pair of types, where a type in config uses a type in client.
- The types involved
aichat.config.Config→aichat.client.ClientConfig
- Direction
- config uses client, so a change to client can break config, while a change to config can't break client.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→29 config uses config.agent part of a loop✕
- Connections
- 1 pair of types, where a type in config uses a type in config.agent.
- The types involved
aichat.config.Config→aichat.config.agent.Agent
- Direction
- config uses config.agent, so a change to config.agent can break config, while a change to config can't break config.agent.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→30 config uses function part of a loop✕
- Connections
- 2 pairs of types, where a type in config uses a type in function.
- The types involved
aichat.config.Config→aichat.function.FunctionDeclarationaichat.config.Config→aichat.function.Functions
- Direction
- config uses function, so a change to function can break config, while a change to config can't break function.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→34 config uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in config uses a type in client.model.
- The types involved
aichat.config.Config→aichat.client.model.Modelaichat.config.ModelsOverride→aichat.client.model.ProviderModels
- Direction
- config uses client.model, so a change to client.model can break config, while a change to config can't break client.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.
28→37 config uses config.input part of a loop✕
- Connections
- 2 pairs of types, where a type in config uses a type in config.input.
- The types involved
aichat.config.Config→aichat.config.input.Inputaichat.config.LastMessage→aichat.config.input.Input
- Direction
- config uses config.input, so a change to config.input can break config, while a change to config can't break config.input.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→22 config.agent uses config.role✕
- Connections
- 2 pairs of types, where a type in config.agent uses a type in config.role.
- The types involved
aichat.config.agent.Agent→aichat.config.role.Roleaichat.config.agent.Agent→aichat.config.role.RoleLike
- Direction
- config.agent uses config.role, so a change to config.role can break config.agent, while a change to config.agent can't break config.role.
- Position
- Below the diagonal: config.agent uses a module listed above it, which is the healthy direction.
29→23 config.agent uses rag✕
- Connections
- 1 pair of types, where a type in config.agent uses a type in rag.
- The types involved
aichat.config.agent.Agent→aichat.rag.Rag
- Direction
- config.agent uses rag, so a change to rag can break config.agent, while a change to config.agent can't break rag.
- Position
- Below the diagonal: config.agent uses a module listed above it, which is the healthy direction.
29→28 config.agent uses config✕
- Connections
- 1 pair of types, where a type in config.agent uses a type in config.
- The types involved
aichat.config.agent.AgentConfig→aichat.config.Config
- Direction
- config.agent uses config, so a change to config can break config.agent, while a change to config.agent can't break config.
- Position
- Below the diagonal: config.agent uses a module listed above it, which is the healthy direction.
29→30 config.agent uses function part of a loop✕
- Connections
- 2 pairs of types, where a type in config.agent uses a type in function.
- The types involved
aichat.config.agent.Agent→aichat.function.Functionsaichat.config.agent.AgentDefinition→aichat.function.Functions
- Direction
- config.agent uses function, so a change to function can break config.agent, while a change to config.agent can't break function.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→34 config.agent uses client.model part of a loop✕
- Connections
- 1 pair of types, where a type in config.agent uses a type in client.model.
- The types involved
aichat.config.agent.Agent→aichat.client.model.Model
- Direction
- config.agent uses client.model, so a change to client.model can break config.agent, while a change to config.agent can't break client.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.
30→29 function uses config.agent✕
- Connections
- 1 pair of types, where a type in function uses a type in config.agent.
- The types involved
aichat.function.ToolCall→aichat.config.agent.Agent
- Direction
- function uses config.agent, so a change to config.agent can break function, while a change to function can't break config.agent.
- Position
- Below the diagonal: function uses a module listed above it, which is the healthy direction.
31→30 client.stream uses function✕
- Connections
- 1 pair of types, where a type in client.stream uses a type in function.
- The types involved
aichat.client.stream.SseHandler→aichat.function.ToolCall
- Direction
- client.stream uses function, so a change to function can break client.stream, while a change to client.stream can't break function.
- Position
- Below the diagonal: client.stream uses a module listed above it, which is the healthy direction.
32→30 client.common uses function✕
- Connections
- 2 pairs of types, where a type in client.common uses a type in function.
- The types involved
aichat.client.common.ChatCompletionsData→aichat.function.FunctionDeclarationaichat.client.common.ChatCompletionsOutput→aichat.function.ToolCall
- Direction
- client.common uses function, so a change to function can break client.common, while a change to client.common can't break function.
- Position
- Below the diagonal: client.common uses a module listed above it, which is the healthy direction.
32→31 client.common uses client.stream✕
- Connections
- 1 pair of types, where a type in client.common uses a type in client.stream.
- The types involved
aichat.client.common.Client→aichat.client.stream.SseHandler
- Direction
- client.common uses client.stream, so a change to client.stream can break client.common, while a change to client.common can't break client.stream.
- Position
- Below the diagonal: client.common uses a module listed above it, which is the healthy direction.
32→34 client.common uses client.model part of a loop✕
- Connections
- 2 pairs of types, where a type in client.common uses a type in client.model.
- The types involved
aichat.client.common.Client→aichat.client.model.Modelaichat.client.common.common$module→aichat.client.model.Model
- Direction
- client.common uses client.model, so a change to client.model can break client.common, while a change to client.common can't break client.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.
32→36 client.common uses client.message part of a loop✕
- Connections
- 1 pair of types, where a type in client.common uses a type in client.message.
- The types involved
aichat.client.common.ChatCompletionsData→aichat.client.message.Message
- Direction
- client.common uses client.message, so a change to client.message can break client.common, while a change to client.common can't break client.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.
32→37 client.common uses config.input part of a loop✕
- Connections
- 2 pairs of types, where a type in client.common uses a type in config.input.
- The types involved
aichat.client.common.Client→aichat.config.input.Inputaichat.client.common.common$module→aichat.config.input.Input
- Direction
- client.common uses config.input, so a change to config.input can break client.common, while a change to client.common can't break config.input.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→6 render.stream uses render.markdown✕
- Connections
- 1 pair of types, where a type in render.stream uses a type in render.markdown.
- The types involved
aichat.render.stream.stream$module→aichat.render.markdown.MarkdownRender
- Direction
- render.stream uses render.markdown, so a change to render.markdown can break render.stream, while a change to render.stream can't break render.markdown.
- Position
- Below the diagonal: render.stream uses a module listed above it, which is the healthy direction.
33→31 render.stream uses client.stream✕
- Connections
- 1 pair of types, where a type in render.stream uses a type in client.stream.
- The types involved
aichat.render.stream.stream$module→aichat.client.stream.SseEvent
- Direction
- render.stream uses client.stream, so a change to client.stream can break render.stream, while a change to render.stream can't break client.stream.
- Position
- Below the diagonal: render.stream uses a module listed above it, which is the healthy direction.
34→28 client.model uses config✕
- Connections
- 1 pair of types, where a type in client.model uses a type in config.
- The types involved
aichat.client.model.Model→aichat.config.Config
- Direction
- client.model uses config, so a change to config can break client.model, while a change to client.model can't break config.
- Position
- Below the diagonal: client.model uses a module listed above it, which is the healthy direction.
34→32 client.model uses client.common✕
- Connections
- 1 pair of types, where a type in client.model uses a type in client.common.
- The types involved
aichat.client.model.ModelType→aichat.client.common.RequestPatch
- Direction
- client.model uses client.common, so a change to client.common can break client.model, while a change to client.model can't break client.common.
- Position
- Below the diagonal: client.model uses a module listed above it, which is the healthy direction.
35→22 serve uses config.role✕
- Connections
- 1 pair of types, where a type in serve uses a type in config.role.
- The types involved
aichat.serve.Server→aichat.config.role.Role
- Direction
- serve uses config.role, so a change to config.role can break serve, while a change to serve can't break config.role.
- Position
- Below the diagonal: serve uses a module listed above it, which is the healthy direction.
35→28 serve uses config✕
- Connections
- 1 pair of types, where a type in serve uses a type in config.
- The types involved
aichat.serve.Server→aichat.config.Config
- Direction
- serve uses config, so a change to config can break serve, while a change to serve can't break config.
- Position
- Below the diagonal: serve uses a module listed above it, which is the healthy direction.
35→32 serve uses client.common✕
- Connections
- 1 pair of types, where a type in serve uses a type in client.common.
- The types involved
aichat.serve.serve$module→aichat.client.common.ChatCompletionsOutput
- Direction
- serve uses client.common, so a change to client.common can break serve, while a change to serve can't break client.common.
- Position
- Below the diagonal: serve uses a module listed above it, which is the healthy direction.
36→30 client.message uses function✕
- Connections
- 1 pair of types, where a type in client.message uses a type in function.
- The types involved
aichat.client.message.MessageContentToolCalls→aichat.function.ToolResult
- Direction
- client.message uses function, so a change to function can break client.message, while a change to client.message can't break function.
- Position
- Below the diagonal: client.message uses a module listed above it, which is the healthy direction.
36→34 client.message uses client.model✕
- Connections
- 1 pair of types, where a type in client.message uses a type in client.model.
- The types involved
aichat.client.message.message$module→aichat.client.model.Model
- Direction
- client.message uses client.model, so a change to client.model can break client.message, while a change to client.message can't break client.model.
- Position
- Below the diagonal: client.message uses a module listed above it, which is the healthy direction.
37→22 config.input uses config.role✕
- Connections
- 2 pairs of types, where a type in config.input uses a type in config.role.
- The types involved
aichat.config.input.Input→aichat.config.role.Roleaichat.config.input.input$module→aichat.config.role.Role
- Direction
- config.input uses config.role, so a change to config.role can break config.input, while a change to config.input can't break config.role.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
37→25 config.input uses config.session✕
- Connections
- 1 pair of types, where a type in config.input uses a type in config.session.
- The types involved
aichat.config.input.Input→aichat.config.session.Session
- Direction
- config.input uses config.session, so a change to config.session can break config.input, while a change to config.input can't break config.session.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
37→28 config.input uses config✕
- Connections
- 1 pair of types, where a type in config.input uses a type in config.
- The types involved
aichat.config.input.input$module→aichat.config.Config
- Direction
- config.input uses config, so a change to config can break config.input, while a change to config.input can't break config.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
37→30 config.input uses function✕
- Connections
- 1 pair of types, where a type in config.input uses a type in function.
- The types involved
aichat.config.input.Input→aichat.function.ToolResult
- Direction
- config.input uses function, so a change to function can break config.input, while a change to config.input can't break function.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
37→34 config.input uses client.model✕
- Connections
- 1 pair of types, where a type in config.input uses a type in client.model.
- The types involved
aichat.config.input.Input→aichat.client.model.Model
- Direction
- config.input uses client.model, so a change to client.model can break config.input, while a change to config.input can't break client.model.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
37→36 config.input uses client.message✕
- Connections
- 2 pairs of types, where a type in config.input uses a type in client.message.
- The types involved
aichat.config.input.Input→aichat.client.message.MessageContentaichat.config.input.Input→aichat.client.message.MessageContentToolCalls
- Direction
- config.input uses client.message, so a change to client.message can break config.input, while a change to config.input can't break client.message.
- Position
- Below the diagonal: config.input uses a module listed above it, which is the healthy direction.
38→1 aichat uses cli✕
- Connections
- 1 pair of types, where a type in aichat uses a type in cli.
- The types involved
aichat.aichat$module→aichat.cli.Cli
- Direction
- aichat uses cli, so a change to cli can break aichat, while a change to aichat can't break cli.
- Position
- Below the diagonal: aichat uses a module listed above it, which is the healthy direction.
38→13 aichat uses utils.command✕
- Connections
- 1 pair of types, where a type in aichat uses a type in utils.command.
- The types involved
aichat.aichat$module→aichat.utils.command.Shell
- Direction
- aichat uses utils.command, so a change to utils.command can break aichat, while a change to aichat can't break utils.command.
- Position
- Below the diagonal: aichat uses a module listed above it, which is the healthy direction.
38→37 aichat uses config.input✕
- Connections
- 1 pair of types, where a type in aichat uses a type in config.input.
- The types involved
aichat.aichat$module→aichat.config.input.Input
- Direction
- aichat uses config.input, so a change to config.input can break aichat, while a change to aichat can't break config.input.
- Position
- Below the diagonal: aichat uses a module listed above it, which is the healthy direction.
39→8 repl uses repl.prompt✕
- Connections
- 1 pair of types, where a type in repl uses a type in repl.prompt.
- The types involved
aichat.repl.Repl→aichat.repl.prompt.ReplPrompt
- Direction
- repl uses repl.prompt, so a change to repl.prompt can break repl, while a change to repl can't break repl.prompt.
- Position
- Below the diagonal: repl uses a module listed above it, which is the healthy direction.
39→28 repl uses config✕
- Connections
- 2 pairs of types, where a type in repl uses a type in config.
- The types involved
aichat.repl.ReplCommand→aichat.config.AssertStateaichat.repl.ReplCommand→aichat.config.StateFlags
- Direction
- repl uses config, so a change to config can break repl, while a change to repl can't break config.
- Position
- Below the diagonal: repl uses a module listed above it, which is the healthy direction.
39→37 repl uses config.input✕
- Connections
- 1 pair of types, where a type in repl uses a type in config.input.
- The types involved
aichat.repl.repl$module→aichat.config.input.Input
- Direction
- repl uses config.input, so a change to config.input can break repl, while a change to repl can't break config.input.
- Position
- Below the diagonal: repl uses a module listed above it, which is the healthy direction.
40→39 repl.completer uses repl✕
- Connections
- 1 pair of types, where a type in repl.completer uses a type in repl.
- The types involved
aichat.repl.completer.ReplCompleter→aichat.repl.ReplCommand
- Direction
- repl.completer uses repl, so a change to repl can break repl.completer, while a change to repl.completer can't break repl.
- Position
- Below the diagonal: repl.completer 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 30 | High / Critical |
| A05:2025 — Injection | 11 | High / Critical |
Roadmap
First, secure the application by implementing a global authentication guard with explicit role-based permissions and default-deny access controls. Next, address accessibility and visual safety by ensuring visible focus styles, respecting reduced motion preferences, and correcting low-contrast colors. Then, resolve the missing architectural decision record and clean up orphaned files to improve knowledge freshness. Finally, harden web security by pinning third-party scripts with integrity hashes or restricting their origins via content security policies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.1 pts | Low | ADR Quality |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +5.9 pts | Medium | Access Controls |
| 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. | +4.5 pts | Medium | Visual & motion safety |
| Resolve the 32 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (3), stream.rs (2), bedrock.rs. | +4.0 pts | Medium | Knowledge Freshness |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +3.8 pts | Medium | Web-Security Posture |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.8 pts | Medium | Keyboard semantics |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.3 pts | Medium | Architecture documentation |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +2.5 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/client/claude.rs | 4.8 | Mixed | Cyclomatic Complexity: aichat::client::claude::claude_build_chat_completions_body (cyclomatic 16) |
| src/client/mod.rs | 4.8 | Mixed | Cyclomatic Complexity: aichat::client::create_client_config (cyclomatic 18) |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/config/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: Config::load_envs (cyclomatic 45) |
| src/client/bedrock.rs | 7.0 | Near-clean | Cyclomatic Complexity: aichat::client::bedrock::chat_completions_streaming (cyclomatic 20) |
| src/serve.rs | 7.0 | Near-clean | Cyclomatic Complexity: aichat::serve::parse_messages (cyclomatic 20) |
| src/repl/mod.rs | 7.1 | Near-clean | Cyclomatic Complexity: aichat::repl::run_repl_command (cyclomatic 78) |
| src/rag/mod.rs | 7.1 | Near-clean | Cyclomatic Complexity: Rag::sync_documents (cyclomatic 31) |
| src/utils/request.rs | 7.2 | Near-clean | Cyclomatic Complexity: aichat::utils::request::fetch_with_loaders (cyclomatic 22) |
| src/client/openai.rs | 7.2 | Near-clean | Cyclomatic Complexity: aichat::client::openai::openai_chat_completions_streaming (cyclomatic 18) |
| src/config/session.rs | 7.2 | Near-clean | Cognitive Complexity: Session::exit (cognitive 25) |
| src/client/vertexai.rs | 7.2 | Near-clean | Cognitive Complexity: aichat::client::vertexai::gemini_chat_completions_streaming (cognitive 18) |
| src/main.rs | 7.4 | Near-clean | Cyclomatic Complexity: aichat::run (cyclomatic 32) |
| src/utils/path.rs | 7.4 | Near-clean | Cyclomatic Complexity: aichat::utils::path::parse_glob (cyclomatic 16) |
| src/rag/splitter/mod.rs | 7.4 | Near-clean | Cognitive Complexity: RecursiveCharacterTextSplitter::merge_splits (cognitive 20) |
| src/render/stream.rs | 7.8 | Near-clean | Cyclomatic Complexity: aichat::render::stream::markdown_stream_inner (cyclomatic 16) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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. 50 of 50 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 — 50 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 219 of 273 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (35 contributor(s) across 989 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 34 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (Cargo.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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: 2 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
18 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was aichat::repl::run_repl_command at 78. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Config::update at 17 — they are counted neither in the figure above nor in this dimension's score. 2 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: src/rag/splitter/mod.rs (aichat::rag::splitter::get_separators at 17), src/rag/splitter/language.rs (Language::separators 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 18 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with aichat::repl::run_repl_command (cyclomatic 78), REDACTED.setupApp (cyclomatic 77), Config::load_envs (cyclomatic 45). — 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 18 together lifts Cyclomatic Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
55 method(s) exceeded the cognitive complexity threshold of 15; the worst was aichat::repl::run_repl_command at 119.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with aichat::repl::run_repl_command (cognitive 119), REDACTED.setupApp (cognitive 98), aichat::client::bedrock::chat_completions_streaming (cognitive 66). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 2.0 to about 3.8/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
18 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with mod.rs (3), serve.rs, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with REDACTED, mod.rs, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with mod.rs (2), serve.rs. — One of this dimension's main actionable groups (3 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
18 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 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), vertexai.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with bedrock.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with bedrock.rs, claude.rs. — One of this dimension's main actionable groups (2 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.
D6 · Cohesion (LCOM4)
6 of 32 classes have LCOM4 above 3.
What to do
- Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (6). — One of this dimension's main actionable groups (6 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
22 test methods: 22 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 22 `#[test]` function(s) across 9 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 9 test files): measured (0 flaky).
D12 · Dependency Hygiene
36 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 463 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. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
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.
D17 · Explicit Debt
0 deducted task-comment markers across 15282 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 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
1 of 1 build units (Cargo) 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)
11 finding(s): 0 critical, 9 high, 2 medium, 0 low. 9 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 2 high, 18 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
D34 · Knowledge Freshness
35 of 35 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/config/mod.rs. Counted over 35 of the 48 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 32 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (3), stream.rs (2), bedrock.rs. — One of this dimension's main actionable groups (32 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), serve.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: claude.rs↔openai.rs 60%; claude.rs↔cohere.rs 55%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with claude.rs (2). — One of this dimension's main actionable groups (2 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 — start with REDACTED. — 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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — REDACTED:506, REDACTED:766
- This <div> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label. (×2) — REDACTED:588, REDACTED:595
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×3) — REDACTED:606, REDACTED:665, REDACTED:758
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — REDACTED:659
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
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>. (×2) — REDACTED:2, REDACTED: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.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×5) — REDACTED:588, REDACTED:595, REDACTED:606, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.spinner` moves (`animation: spinner-rotation 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — REDACTED:327, REDACTED:487
- `.chat-header select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — REDACTED:91, REDACTED:170
- `.input-panel-inner textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — REDACTED:246, REDACTED:338
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 automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 2 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 test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (.serve_connection_with_upgrades) (src/serve.rs:129) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/serve.rs:129
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
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
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `//unpkg.com/@highlightjs/cdn-assets@11.10.0/highlight.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 10 such include(s) across the repository's markup. — REDACTED:15
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection_with_upgrades(` (src/serve.rs:129).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection_with_upgrades(` (src/serve.rs:129).
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
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
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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 | 85% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 76% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 43% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate | Acceptable, with room to improve. |
| Security | 30% | Weak — gated by D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 26% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 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.
- 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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.
- 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 — ~0 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
- 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
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 25 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> REDACTED:588
- Click handler on a non-interactive <div> REDACTED:595
- Click handler on a non-interactive <div> REDACTED:606
- Click handler on a non-interactive <div> REDACTED:665
- Click handler on a non-interactive <div> REDACTED:758
- Custom control with no accessible name on <div> REDACTED:606
- Custom control with no accessible name on <div> REDACTED:665
- Custom control with no accessible name on <div> REDACTED:758
- <textarea> without a programmatic label REDACTED:506
- <textarea> without a programmatic label REDACTED:766
- Custom control named only by title on <div> REDACTED:588
- Custom control named only by title on <div> REDACTED:595
- REDACTED
- REDACTED
- <select> without a programmatic label REDACTED:659
- Banned license: ansi_colours
Serious — 154 finding(s)
- aichat::repl::run_repl_command (cognitive 119) src/repl/mod.rs:374
- aichat::client::bedrock::chat_completions_streaming (cognitive 66) src/client/bedrock.rs:192
- aichat::serve::parse_messages (cognitive 51) src/serve.rs:816
- aichat::render::stream::markdown_stream_inner (cognitive 43) src/render/stream.rs:67
- aichat::run (cognitive 40) src/main.rs:63
- aichat::client::openai::openai_chat_completions_streaming (cognitive 35) src/client/openai.rs:100
- aichat::repl::split_args_text (cognitive 35) src/repl/mod.rs:799
- aichat::utils::path::parse_glob (cognitive 32) src/utils/path.rs:89
- aichat::client::claude::claude_chat_completions_streaming (cognitive 30) src/client/claude.rs:75
- aichat::utils::request::crawl_website (cognitive 30) src/utils/request.rs:213
- aichat::client::claude::claude_extract_chat_completions (cognitive 26) src/client/claude.rs:300
- aichat::utils::request::fetch_with_loaders (cognitive 25) src/utils/request.rs:70
- aichat::client::bedrock::extract_chat_completions (cognitive 23) src/client/bedrock.rs:480
- aichat::client::cohere::chat_completions_streaming (cognitive 23) src/client/cohere.rs:123
- aichat::config::role::parse_structure_prompt (cognitive 20) src/config/role.rs:303
- aichat::utils::render_prompt::parse_template (cognitive 20) src/utils/render_prompt.rs:16
- aichat::shell_execute (cognitive 19) src/main.rs:241
- aichat::client::claude::claude_build_chat_completions_body (cognitive 19) src/client/claude.rs:156
- aichat::utils::command::detect_shell (cognitive 19) src/utils/command.rs:35
- aichat::client::bedrock::build_chat_completions_body (cognitive 18) src/client/bedrock.rs:321
- aichat::client::vertexai::gemini_chat_completions_streaming (cognitive 18) src/client/vertexai.rs:197
- aichat::client::create_client_config (cognitive 17) src/client/mod.rs:15
- aichat::client::common::set_client_models_config (cognitive 17) src/client/common.rs:542
- aichat::client::vertexai::gemini_build_chat_completions_body (cognitive 17) src/client/vertexai.rs:309
- aichat::client::openai::openai_build_chat_completions_body (cognitive 16) src/client/openai.rs:226
- aichat::repl::run_repl_command (cyclomatic 78) src/repl/mod.rs:374
- aichat::run (cyclomatic 32) src/main.rs:63
- aichat::repl::split_args_text (cyclomatic 22) src/repl/mod.rs:799
- aichat::utils::request::fetch_with_loaders (cyclomatic 22) src/utils/request.rs:70
- aichat::client::bedrock::chat_completions_streaming (cyclomatic 20) src/client/bedrock.rs:192
- aichat::serve::parse_messages (cyclomatic 20) src/serve.rs:816
- aichat::client::create_client_config (cyclomatic 18) src/client/mod.rs:15
- aichat::client::openai::openai_chat_completions_streaming (cyclomatic 18) src/client/openai.rs:100
- aichat::client::claude::claude_build_chat_completions_body (cyclomatic 16) src/client/claude.rs:156
- aichat::render::stream::markdown_stream_inner (cyclomatic 16) src/render/stream.rs:67
- aichat::utils::path::parse_glob (cyclomatic 16) src/utils/path.rs:89
- Config::load_envs (cognitive 53) src/config/mod.rs:2248
- Config::repl_complete (cognitive 30) src/config/mod.rs:1738
- Config::select_functions (cognitive 29) src/config/mod.rs:1652
- Config::use_session (cognitive 23) src/config/mod.rs:1073
- Config::delete (cognitive 21) src/config/mod.rs:697
- Config::generate_prompt_context (cognitive 19) src/config/mod.rs:1966
- Low cohesion: OpenAIClient (LCOM4 4) src/client/mod.rs:15
- Low cohesion: OpenAICompatibleClient (LCOM4 4) src/client/mod.rs:15
- Low cohesion: GeminiClient (LCOM4 4) src/client/mod.rs:15
- Low cohesion: ClaudeClient (LCOM4 4) src/client/mod.rs:15
- Low cohesion: CohereClient (LCOM4 4) src/client/mod.rs:15
- Low cohesion: AzureOpenAIClient (LCOM4 4) src/client/mod.rs:15
- FileTooLong: config/mod.rs src/config/mod.rs
- FileTooLong: rag/mod.rs src/rag/mod.rs
- FileTooLong: src/serve.rs src/serve.rs
- FileTooLong: repl/mod.rs src/repl/mod.rs
- FileTooLong: REDACTED REDACTED
- FunctionTooLong: REDACTED.setupApp REDACTED:849
- FunctionTooLong: aichat::repl::run_repl_command src/repl/mod.rs:374
- FunctionTooLong: REDACTED.setupApp REDACTED:570
- FunctionTooLong: aichat::client::bedrock::build_chat_completions_body src/client/bedrock.rs:321
- FunctionTooLong: aichat::client::claude::claude_build_chat_completions_body src/client/claude.rs:156
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement REDACTED:91
- Focus outline removed in CSS without a :focus replacement REDACTED:246
- Focus outline removed in CSS without a :focus replacement REDACTED:170
- Focus outline removed in CSS without a :focus replacement REDACTED:338
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Config::load_envs (cyclomatic 45) src/config/mod.rs:2248
- Config::repl_complete (cyclomatic 30) src/config/mod.rs:1738
- Config::generate_prompt_context (cyclomatic 16) src/config/mod.rs:1966
- Session::exit (cognitive 25) src/config/session.rs:386
- Session::add_message (cognitive 22) src/config/session.rs:469
- Session::render (cognitive 18) src/config/session.rs:178
- RecursiveCharacterTextSplitter::merge_splits (cognitive 20) src/rag/splitter/mod.rs:204
- RecursiveCharacterTextSplitter::split_text_impl (cognitive 19) src/rag/splitter/mod.rs:152
- RecursiveCharacterTextSplitter::create_documents (cognitive 18) src/rag/splitter/mod.rs:89
- MethodTooLong: Server.chat_completions src/serve.rs:261
- MethodTooLong: Rag.sync_documents src/rag/mod.rs:313
- MethodTooLong: Config.repl_complete src/config/mod.rs:1738
- Duplicated block (9 lines × 2) src/client/vertexai.rs:97
- Duplicated block (9 lines × 2) src/config/mod.rs:2136
- Duplicated block (9 lines × 2) src/config/mod.rs:1236
- Page without a main landmark REDACTED:2
- Page without a main landmark REDACTED:2
- Animation without a prefers-reduced-motion guard REDACTED:327
- Animation without a prefers-reduced-motion guard REDACTED:487
- Server::chat_completions (cognitive 38) src/serve.rs:261
- Server::handle (cognitive 16) src/serve.rs:142
- Agent::init (cognitive 27) src/config/agent.rs:33
- Agent::init_agent_variables (cognitive 24) src/config/agent.rs:121
- REDACTED
- REDACTED
- ClassTooLong: Config src/config/mod.rs:101
- ClassTooLong: Rag src/rag/mod.rs:21
- TooManyMethods: Config src/config/mod.rs:101
- TooManyMethods: Session src/config/session.rs:20
- Change coupling: claude.rs ↔ openai.rs src/client/claude.rs:1
- Change coupling: claude.rs ↔ cohere.rs src/client/claude.rs:1
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/client/bedrock.rs:179
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/client/bedrock.rs:302
- Duplicated block (14 lines × 2) src/client/bedrock.rs:328
- Duplicated block (14 lines × 2) src/client/claude.rs:276
- Duplicated block (10–11 lines × 2) src/client/bedrock.rs:234
- Duplicated block (10–11 lines × 2) src/client/claude.rs:95
- Accessibility enforcement below the top rung
- No authorization src/serve.rs:129
- REDACTED.setupApp (cyclomatic 77) REDACTED:849
- REDACTED.setupApp (cyclomatic 43) REDACTED:570
- Rag::sync_documents (cyclomatic 31) src/rag/mod.rs:313
- Server::chat_completions (cyclomatic 19) src/serve.rs:261
- REDACTED.setupApp (cognitive 98) REDACTED:849
- Rag::sync_documents (cognitive 57) src/rag/mod.rs:313
- REDACTED.setupApp (cognitive 55) REDACTED:570
- JsonStreamParser::process (cognitive 27) src/client/stream.rs:185
- REDACTED.parseStructurePrompt (cognitive 23) REDACTED:1418
- MessageContent::render_input (cognitive 19) src/client/message.rs:89
- Input::from_files (cognitive 19) src/config/input.rs:57
- Role::new (cognitive 18) src/config/role.rs:60
- REDACTED.fetchChatCompletions (cognitive 18) REDACTED:894
- REDACTED.fetchChatCompletions (cognitive 18) REDACTED:1331
- Model::retrieve_model (cognitive 17) src/client/model.rs:48
- MarkdownRender::check_line (cognitive 17) src/render/markdown.rs:99
- Cli::text (cognitive 16) src/cli.rs:90
- TooManyFields: Config src/config/mod.rs:101
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (29 lines × 2) src/client/bedrock.rs:62
- Duplicated block (21 lines × 2) src/client/bedrock.rs:415
- Duplicated block (16–17 lines × 2) src/client/cohere.rs:226
- Duplicated block (12–13 lines × 2) src/client/bedrock.rs:231
- Duplicated block (12 lines × 2) src/client/openai.rs:113
- Duplicated block (10–11 lines × 4) src/client/bedrock.rs:230
- Duplicated block (8–10 lines × 5) src/client/bedrock.rs:303
- Duplicated block (7–9 lines × 5) src/client/bedrock.rs:180
- Duplicated block (5 lines × 2) src/client/vertexai.rs:45
- Duplicated block (11 lines × 2) src/utils/request.rs:319
- Duplicated block (6 lines × 3) src/serve.rs:262
- Third-party script without Subresource Integrity REDACTED:15
Minor — 58 finding(s)
- Orphaned file src/repl/mod.rs:1
- Orphaned file src/client/bedrock.rs:1
- Orphaned file src/config/session.rs:1
- Orphaned file src/client/common.rs:1
- Orphaned file src/client/vertexai.rs:1
- Orphaned file src/config/agent.rs:1
- Orphaned file src/config/input.rs:1
- Orphaned file src/rag/splitter/mod.rs:1
- Orphaned file src/utils/request.rs:1
- Orphaned file src/client/openai.rs:1
- Orphaned file src/client/model.rs:1
- Orphaned file src/client/claude.rs:1
- Orphaned file src/render/markdown.rs:1
- Orphaned file src/main.rs:1
- Orphaned file src/config/role.rs:1
- Orphaned file src/function.rs:1
- Orphaned file src/client/macros.rs:1
- Orphaned file src/client/stream.rs:1
- Orphaned file src/utils/path.rs:1
- Orphaned file src/client/cohere.rs:1
- Orphaned file src/client/message.rs:1
- Orphaned file src/utils/command.rs:1
- Orphaned file src/utils/mod.rs:1
- Orphaned file src/render/stream.rs:1
- Orphaned file src/rag/splitter/language.rs:1
- Silent fallback default on Err src/config/mod.rs:1473
- Silent fallback default on Err src/config/session.rs:522
- Silent fallback default on Err src/config/agent.rs:525
- Silent fallback default on Err src/config/agent.rs:545
- Silent fallback default on Err src/utils/path.rs:65
- Most significant orphaned file src/config/mod.rs:1
- Most significant orphaned file src/rag/mod.rs:1
- Most significant orphaned file src/serve.rs:1
- Duplicated predicate src/client/bedrock.rs:341
- Duplicated predicate src/client/bedrock.rs:517
- No ADRs found
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Hand-rolled JSON/XML parsing via regex src/utils/mod.rs:39
Minor — 36 finding(s)
- Outdated: anyhow
- Outdated: arboard
- Outdated: async-recursion
- Outdated: async-trait
- Outdated: bitflags
- Outdated: bm25
- Outdated: bytes
- Outdated: chrono
- Outdated: clap
- Outdated: duct
- Outdated: futures-util
- Outdated: hnsw_rs
- Outdated: http
- Outdated: http-body-util
- Outdated: hyper
- Outdated: hyper-util
- Outdated: indexmap
- Outdated: is-terminal
- Outdated: json-patch
- Outdated: log
- Outdated: nu-ansi-term
- Outdated: os_info
- Outdated: rayon
- Outdated: rust-embed
- Outdated: serde
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-7431856fc6c14673b7520ab11d6b98c6/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-7431856fc6c14673b7520ab11d6b98c6/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 20 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |