Executive summary
mufeedvh/code2prompt falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 64 out of 100 and is rated Adequate, and 15 of its 16 critical findings are security problems.
Production Readiness, at 57, is the weakest lens and counts most in the score. The best first step for the work it takes is rebalancing the test suite towards unit tests, worth about 3 points. Adding automated security scanning would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 68.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code. Adding the tests the test command is meant to run would take care of the test command with no tests behind it.
The product code is 9,678 lines, about €16,000 to rebuild.
If Production Readiness rose from 57 to 70, the lowest score rated Strong, the score would rise from 64 to about 68.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,300 to €26,000, for 88 to 278 hours of work, about 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.9 at a score of 64. 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: 9,678 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 code2prompt.model.commands | 2 code2prompt.model.statistics.types | 3 code2prompt.model.template.picker | 4 code2prompt.model.template.variable | 5 code2prompt_core.entity_map | 6 code2prompt_core.selection | 7 code2prompt.widgets.template.picker | 8 code2prompt.widgets.template.variable | 9 code2prompt_core.analysis | 10 code2prompt_core.file_processor | 11 code2prompt_core.template | 12 code2prompt_core.tokenizer | 13 code2prompt.model.template.editor | 14 code2prompt.token_map | 15 code2prompt_core.configuration | 16 code2prompt_core.file_processor.csv | 17 code2prompt.config_loader | 18 code2prompt.widgets.template.editor | 19 code2prompt_core.path | 20 code2prompt_core.session | 21 code2prompt.model.prompt_output | 22 code2prompt.model.settings | 23 code2prompt.model.statistics | 24 code2prompt.model.template | 25 code2prompt_python.python | 26 code2prompt.model | 27 code2prompt.view.formatters | 28 code2prompt_core.sort | 29 code2prompt.args | 30 code2prompt.tui | 31 code2prompt.utils | 32 code2prompt.widgets.file_selection | 33 code2prompt.widgets.output | 34 code2prompt.widgets.settings | 35 code2prompt.widgets.statistics_by_extension | 36 code2prompt.widgets.statistics_overview | 37 code2prompt.widgets.statistics_token_map | 38 code2prompt.widgets.template | 39 code2prompt.config | 40 code2prompt.main |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 code2prompt.model.commands | ||||||||||||||||||||||||||||||||||||||||
| 2 code2prompt.model.statistics.types | ||||||||||||||||||||||||||||||||||||||||
| 3 code2prompt.model.template.picker | ||||||||||||||||||||||||||||||||||||||||
| 4 code2prompt.model.template.variable | ||||||||||||||||||||||||||||||||||||||||
| 5 code2prompt_core.entity_map | ||||||||||||||||||||||||||||||||||||||||
| 6 code2prompt_core.selection | ||||||||||||||||||||||||||||||||||||||||
| 7 code2prompt.widgets.template.picker | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 code2prompt.widgets.template.variable | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 code2prompt_core.analysis | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 code2prompt_core.file_processor | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 code2prompt_core.template | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 code2prompt_core.tokenizer | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 code2prompt.model.template.editor | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 code2prompt.token_map | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 code2prompt_core.configuration | 2 | 2 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 16 code2prompt_core.file_processor.csv | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 code2prompt.config_loader | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 code2prompt.widgets.template.editor | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 code2prompt_core.path | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 code2prompt_core.session | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 21 code2prompt.model.prompt_output | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 code2prompt.model.settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 code2prompt.model.statistics | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 code2prompt.model.template | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 code2prompt_python.python | 3 | 2 | 1 | 2 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 26 code2prompt.model | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 code2prompt.view.formatters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 code2prompt_core.sort | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 code2prompt.args | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 code2prompt.tui | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 code2prompt.utils | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 code2prompt.widgets.file_selection | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 code2prompt.widgets.output | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 code2prompt.widgets.settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 code2prompt.widgets.statistics_by_extension | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 code2prompt.widgets.statistics_overview | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 code2prompt.widgets.statistics_token_map | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 code2prompt.widgets.template | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 code2prompt.config | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 code2prompt.main | 1 | 2 | 1 |
7→3 code2prompt.widgets.template.picker uses code2prompt.model.template.picker✕
- Connections
- 2 pairs of types, where a type in code2prompt.widgets.template.picker uses a type in code2prompt.model.template.picker.
- The types involved
code2prompt.widgets.template.picker.TemplatePickerWidget→code2prompt.model.template.picker.ActiveListcode2prompt.widgets.template.picker.TemplatePickerWidget→code2prompt.model.template.picker.PickerState
- Direction
- code2prompt.widgets.template.picker uses code2prompt.model.template.picker, so a change to code2prompt.model.template.picker can break code2prompt.widgets.template.picker, while a change to code2prompt.widgets.template.picker can't break code2prompt.model.template.picker.
- Position
- Below the diagonal: code2prompt.widgets.template.picker uses a module listed above it, which is the healthy direction.
8→4 code2prompt.widgets.template.variable uses code2prompt.model.template.variable✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template.variable uses a type in code2prompt.model.template.variable.
- The types involved
code2prompt.widgets.template.variable.TemplateVariableWidget→code2prompt.model.template.variable.VariableState
- Direction
- code2prompt.widgets.template.variable uses code2prompt.model.template.variable, so a change to code2prompt.model.template.variable can break code2prompt.widgets.template.variable, while a change to code2prompt.widgets.template.variable can't break code2prompt.model.template.variable.
- Position
- Below the diagonal: code2prompt.widgets.template.variable uses a module listed above it, which is the healthy direction.
9→25 code2prompt_core.analysis uses code2prompt_python.python part of a loop✕
- Connections
- 1 pair of types, where a type in code2prompt_core.analysis uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.analysis.TokenMapOptions→code2prompt_python.python.PyTokenMapOptions
- Direction
- code2prompt_core.analysis uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.analysis, while a change to code2prompt_core.analysis can't break code2prompt_python.python.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 code2prompt_core.file_processor uses code2prompt_python.python part of a loop✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.file_processor uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.file_processor.FileProcessorsConfig→code2prompt_python.python.PyFileProcessorsConfigcode2prompt_core.file_processor.IpynbProcessorConfig→code2prompt_python.python.PyIpynbProcessorConfig
- Direction
- code2prompt_core.file_processor uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.file_processor, while a change to code2prompt_core.file_processor can't break code2prompt_python.python.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→25 code2prompt_core.template uses code2prompt_python.python part of a loop✕
- Connections
- 1 pair of types, where a type in code2prompt_core.template uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.template.OutputFormat→code2prompt_python.python.PyOutputFormat
- Direction
- code2prompt_core.template uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.template, while a change to code2prompt_core.template can't break code2prompt_python.python.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 code2prompt_core.tokenizer uses code2prompt_python.python part of a loop✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.tokenizer uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.tokenizer.TokenFormat→code2prompt_python.python.PyTokenFormatcode2prompt_core.tokenizer.TokenizerType→code2prompt_python.python.PyTokenizerType
- Direction
- code2prompt_core.tokenizer uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.tokenizer, while a change to code2prompt_core.tokenizer can't break code2prompt_python.python.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→11 code2prompt.model.template.editor uses code2prompt_core.template✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template.editor uses a type in code2prompt_core.template.
- The types involved
code2prompt.model.template.editor.EditorState→code2prompt_core.template.OutputFormat
- Direction
- code2prompt.model.template.editor uses code2prompt_core.template, so a change to code2prompt_core.template can break code2prompt.model.template.editor, while a change to code2prompt.model.template.editor can't break code2prompt_core.template.
- Position
- Below the diagonal: code2prompt.model.template.editor uses a module listed above it, which is the healthy direction.
14→9 code2prompt.token_map uses code2prompt_core.analysis✕
- Connections
- 1 pair of types, where a type in code2prompt.token_map uses a type in code2prompt_core.analysis.
- The types involved
code2prompt.token_map.token_map$module→code2prompt_core.analysis.TokenMapEntry
- Direction
- code2prompt.token_map uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt.token_map, while a change to code2prompt.token_map can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt.token_map uses a module listed above it, which is the healthy direction.
14→12 code2prompt.token_map uses code2prompt_core.tokenizer✕
- Connections
- 1 pair of types, where a type in code2prompt.token_map uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt.token_map.token_map$module→code2prompt_core.tokenizer.TokenFormat
- Direction
- code2prompt.token_map uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt.token_map, while a change to code2prompt.token_map can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt.token_map uses a module listed above it, which is the healthy direction.
15→10 code2prompt_core.configuration uses code2prompt_core.file_processor✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.configuration uses a type in code2prompt_core.file_processor.
- The types involved
code2prompt_core.configuration.Code2PromptConfig→code2prompt_core.file_processor.FileProcessorsConfigcode2prompt_core.configuration.TomlConfig→code2prompt_core.file_processor.FileProcessorsConfig
- Direction
- code2prompt_core.configuration uses code2prompt_core.file_processor, so a change to code2prompt_core.file_processor can break code2prompt_core.configuration, while a change to code2prompt_core.configuration can't break code2prompt_core.file_processor.
- Position
- Below the diagonal: code2prompt_core.configuration uses a module listed above it, which is the healthy direction.
15→11 code2prompt_core.configuration uses code2prompt_core.template✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.configuration uses a type in code2prompt_core.template.
- The types involved
code2prompt_core.configuration.Code2PromptConfig→code2prompt_core.template.OutputFormatcode2prompt_core.configuration.TomlConfig→code2prompt_core.template.OutputFormat
- Direction
- code2prompt_core.configuration uses code2prompt_core.template, so a change to code2prompt_core.template can break code2prompt_core.configuration, while a change to code2prompt_core.configuration can't break code2prompt_core.template.
- Position
- Below the diagonal: code2prompt_core.configuration uses a module listed above it, which is the healthy direction.
15→12 code2prompt_core.configuration uses code2prompt_core.tokenizer✕
- Connections
- 4 pairs of types, where a type in code2prompt_core.configuration uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt_core.configuration.Code2PromptConfig→code2prompt_core.tokenizer.TokenFormatcode2prompt_core.configuration.Code2PromptConfig→code2prompt_core.tokenizer.TokenizerTypecode2prompt_core.configuration.TomlConfig→code2prompt_core.tokenizer.TokenFormatcode2prompt_core.configuration.TomlConfig→code2prompt_core.tokenizer.TokenizerType
- Direction
- code2prompt_core.configuration uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt_core.configuration, while a change to code2prompt_core.configuration can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt_core.configuration uses a module listed above it, which is the healthy direction.
15→25 code2prompt_core.configuration uses code2prompt_python.python part of a loop✕
- Connections
- 1 pair of types, where a type in code2prompt_core.configuration uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.configuration.Code2PromptConfig→code2prompt_python.python.PyCode2PromptConfig
- Direction
- code2prompt_core.configuration uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.configuration, while a change to code2prompt_core.configuration can't break code2prompt_python.python.
- 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→28 code2prompt_core.configuration uses code2prompt_core.sort part of a loop✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.configuration uses a type in code2prompt_core.sort.
- The types involved
code2prompt_core.configuration.Code2PromptConfig→code2prompt_core.sort.FileSortMethodcode2prompt_core.configuration.TomlConfig→code2prompt_core.sort.FileSortMethod
- Direction
- code2prompt_core.configuration uses code2prompt_core.sort, so a change to code2prompt_core.sort can break code2prompt_core.configuration, while a change to code2prompt_core.configuration can't break code2prompt_core.sort.
- 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→10 code2prompt_core.file_processor.csv uses code2prompt_core.file_processor✕
- Connections
- 1 pair of types, where a type in code2prompt_core.file_processor.csv uses a type in code2prompt_core.file_processor.
- The types involved
code2prompt_core.file_processor.csv.CsvProcessor→code2prompt_core.file_processor.FileProcessor
- Direction
- code2prompt_core.file_processor.csv uses code2prompt_core.file_processor, so a change to code2prompt_core.file_processor can break code2prompt_core.file_processor.csv, while a change to code2prompt_core.file_processor.csv can't break code2prompt_core.file_processor.
- Position
- Below the diagonal: code2prompt_core.file_processor.csv uses a module listed above it, which is the healthy direction.
17→15 code2prompt.config_loader uses code2prompt_core.configuration✕
- Connections
- 2 pairs of types, where a type in code2prompt.config_loader uses a type in code2prompt_core.configuration.
- The types involved
code2prompt.config_loader.ConfigSource→code2prompt_core.configuration.TomlConfigcode2prompt.config_loader.config_loader$module→code2prompt_core.configuration.OutputDestination
- Direction
- code2prompt.config_loader uses code2prompt_core.configuration, so a change to code2prompt_core.configuration can break code2prompt.config_loader, while a change to code2prompt.config_loader can't break code2prompt_core.configuration.
- Position
- Below the diagonal: code2prompt.config_loader uses a module listed above it, which is the healthy direction.
18→13 code2prompt.widgets.template.editor uses code2prompt.model.template.editor✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template.editor uses a type in code2prompt.model.template.editor.
- The types involved
code2prompt.widgets.template.editor.TemplateEditorWidget→code2prompt.model.template.editor.EditorState
- Direction
- code2prompt.widgets.template.editor uses code2prompt.model.template.editor, so a change to code2prompt.model.template.editor can break code2prompt.widgets.template.editor, while a change to code2prompt.widgets.template.editor can't break code2prompt.model.template.editor.
- Position
- Below the diagonal: code2prompt.widgets.template.editor uses a module listed above it, which is the healthy direction.
19→5 code2prompt_core.path uses code2prompt_core.entity_map✕
- Connections
- 1 pair of types, where a type in code2prompt_core.path uses a type in code2prompt_core.entity_map.
- The types involved
code2prompt_core.path.FileEntry→code2prompt_core.entity_map.EntitySummary
- Direction
- code2prompt_core.path uses code2prompt_core.entity_map, so a change to code2prompt_core.entity_map can break code2prompt_core.path, while a change to code2prompt_core.path can't break code2prompt_core.entity_map.
- Position
- Below the diagonal: code2prompt_core.path uses a module listed above it, which is the healthy direction.
19→6 code2prompt_core.path uses code2prompt_core.selection✕
- Connections
- 1 pair of types, where a type in code2prompt_core.path uses a type in code2prompt_core.selection.
- The types involved
code2prompt_core.path.path$module→code2prompt_core.selection.SelectionEngine
- Direction
- code2prompt_core.path uses code2prompt_core.selection, so a change to code2prompt_core.selection can break code2prompt_core.path, while a change to code2prompt_core.path can't break code2prompt_core.selection.
- Position
- Below the diagonal: code2prompt_core.path uses a module listed above it, which is the healthy direction.
19→9 code2prompt_core.path uses code2prompt_core.analysis✕
- Connections
- 1 pair of types, where a type in code2prompt_core.path uses a type in code2prompt_core.analysis.
- The types involved
code2prompt_core.path.FileEntry→code2prompt_core.analysis.EntryMetadata
- Direction
- code2prompt_core.path uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt_core.path, while a change to code2prompt_core.path can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt_core.path uses a module listed above it, which is the healthy direction.
19→15 code2prompt_core.path uses code2prompt_core.configuration✕
- Connections
- 1 pair of types, where a type in code2prompt_core.path uses a type in code2prompt_core.configuration.
- The types involved
code2prompt_core.path.path$module→code2prompt_core.configuration.Code2PromptConfig
- Direction
- code2prompt_core.path uses code2prompt_core.configuration, so a change to code2prompt_core.configuration can break code2prompt_core.path, while a change to code2prompt_core.path can't break code2prompt_core.configuration.
- Position
- Below the diagonal: code2prompt_core.path uses a module listed above it, which is the healthy direction.
20→5 code2prompt_core.session uses code2prompt_core.entity_map✕
- Connections
- 2 pairs of types, where a type in code2prompt_core.session uses a type in code2prompt_core.entity_map.
- The types involved
code2prompt_core.session.Code2PromptSession→code2prompt_core.entity_map.FileCodeMapcode2prompt_core.session.TemplateContext→code2prompt_core.entity_map.FileCodeMap
- Direction
- code2prompt_core.session uses code2prompt_core.entity_map, so a change to code2prompt_core.entity_map can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.entity_map.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
20→6 code2prompt_core.session uses code2prompt_core.selection✕
- Connections
- 1 pair of types, where a type in code2prompt_core.session uses a type in code2prompt_core.selection.
- The types involved
code2prompt_core.session.Code2PromptSession→code2prompt_core.selection.SelectionEngine
- Direction
- code2prompt_core.session uses code2prompt_core.selection, so a change to code2prompt_core.selection can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.selection.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
20→9 code2prompt_core.session uses code2prompt_core.analysis✕
- Connections
- 1 pair of types, where a type in code2prompt_core.session uses a type in code2prompt_core.analysis.
- The types involved
code2prompt_core.session.Code2PromptSession→code2prompt_core.analysis.CodebaseAnalysis
- Direction
- code2prompt_core.session uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
20→12 code2prompt_core.session uses code2prompt_core.tokenizer✕
- Connections
- 1 pair of types, where a type in code2prompt_core.session uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt_core.session.Code2PromptSession→code2prompt_core.tokenizer.TokenizerType
- Direction
- code2prompt_core.session uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
20→15 code2prompt_core.session uses code2prompt_core.configuration✕
- Connections
- 1 pair of types, where a type in code2prompt_core.session uses a type in code2prompt_core.configuration.
- The types involved
code2prompt_core.session.Code2PromptSession→code2prompt_core.configuration.Code2PromptConfig
- Direction
- code2prompt_core.session uses code2prompt_core.configuration, so a change to code2prompt_core.configuration can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.configuration.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
20→19 code2prompt_core.session uses code2prompt_core.path✕
- Connections
- 1 pair of types, where a type in code2prompt_core.session uses a type in code2prompt_core.path.
- The types involved
code2prompt_core.session.SessionData→code2prompt_core.path.FileEntry
- Direction
- code2prompt_core.session uses code2prompt_core.path, so a change to code2prompt_core.path can break code2prompt_core.session, while a change to code2prompt_core.session can't break code2prompt_core.path.
- Position
- Below the diagonal: code2prompt_core.session uses a module listed above it, which is the healthy direction.
21→9 code2prompt.model.prompt_output uses code2prompt_core.analysis✕
- Connections
- 1 pair of types, where a type in code2prompt.model.prompt_output uses a type in code2prompt_core.analysis.
- The types involved
code2prompt.model.prompt_output.AnalysisResults→code2prompt_core.analysis.TokenMapEntry
- Direction
- code2prompt.model.prompt_output uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt.model.prompt_output, while a change to code2prompt.model.prompt_output can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt.model.prompt_output uses a module listed above it, which is the healthy direction.
21→20 code2prompt.model.prompt_output uses code2prompt_core.session✕
- Connections
- 2 pairs of types, where a type in code2prompt.model.prompt_output uses a type in code2prompt_core.session.
- The types involved
code2prompt.model.prompt_output.AnalysisResults→code2prompt_core.session.RenderedPromptcode2prompt.model.prompt_output.PromptOutputState→code2prompt_core.session.RenderedPrompt
- Direction
- code2prompt.model.prompt_output uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.model.prompt_output, while a change to code2prompt.model.prompt_output can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.model.prompt_output uses a module listed above it, which is the healthy direction.
22→20 code2prompt.model.settings uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.model.settings uses a type in code2prompt_core.session.
- The types involved
code2prompt.model.settings.SettingsState→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.model.settings uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.model.settings, while a change to code2prompt.model.settings can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.model.settings uses a module listed above it, which is the healthy direction.
23→2 code2prompt.model.statistics uses code2prompt.model.statistics.types✕
- Connections
- 1 pair of types, where a type in code2prompt.model.statistics uses a type in code2prompt.model.statistics.types.
- The types involved
code2prompt.model.statistics.StatisticsState→code2prompt.model.statistics.types.StatisticsView
- Direction
- code2prompt.model.statistics uses code2prompt.model.statistics.types, so a change to code2prompt.model.statistics.types can break code2prompt.model.statistics, while a change to code2prompt.model.statistics can't break code2prompt.model.statistics.types.
- Position
- Below the diagonal: code2prompt.model.statistics uses a module listed above it, which is the healthy direction.
23→9 code2prompt.model.statistics uses code2prompt_core.analysis✕
- Connections
- 2 pairs of types, where a type in code2prompt.model.statistics uses a type in code2prompt_core.analysis.
- The types involved
code2prompt.model.statistics.StatisticsState→code2prompt_core.analysis.CodebaseAnalysiscode2prompt.model.statistics.StatisticsState→code2prompt_core.analysis.TokenMapEntry
- Direction
- code2prompt.model.statistics uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt.model.statistics, while a change to code2prompt.model.statistics can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt.model.statistics uses a module listed above it, which is the healthy direction.
23→20 code2prompt.model.statistics uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.model.statistics uses a type in code2prompt_core.session.
- The types involved
code2prompt.model.statistics.StatisticsState→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.model.statistics uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.model.statistics, while a change to code2prompt.model.statistics can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.model.statistics uses a module listed above it, which is the healthy direction.
24→3 code2prompt.model.template uses code2prompt.model.template.picker✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template uses a type in code2prompt.model.template.picker.
- The types involved
code2prompt.model.template.TemplateState→code2prompt.model.template.picker.PickerState
- Direction
- code2prompt.model.template uses code2prompt.model.template.picker, so a change to code2prompt.model.template.picker can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt.model.template.picker.
- Position
- Below the diagonal: code2prompt.model.template uses a module listed above it, which is the healthy direction.
24→4 code2prompt.model.template uses code2prompt.model.template.variable✕
- Connections
- 2 pairs of types, where a type in code2prompt.model.template uses a type in code2prompt.model.template.variable.
- The types involved
code2prompt.model.template.TemplateState→code2prompt.model.template.variable.VariableInfocode2prompt.model.template.TemplateState→code2prompt.model.template.variable.VariableState
- Direction
- code2prompt.model.template uses code2prompt.model.template.variable, so a change to code2prompt.model.template.variable can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt.model.template.variable.
- Position
- Below the diagonal: code2prompt.model.template uses a module listed above it, which is the healthy direction.
24→11 code2prompt.model.template uses code2prompt_core.template✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template uses a type in code2prompt_core.template.
- The types involved
code2prompt.model.template.TemplateState→code2prompt_core.template.OutputFormat
- Direction
- code2prompt.model.template uses code2prompt_core.template, so a change to code2prompt_core.template can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt_core.template.
- Position
- Below the diagonal: code2prompt.model.template uses a module listed above it, which is the healthy direction.
24→13 code2prompt.model.template uses code2prompt.model.template.editor✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template uses a type in code2prompt.model.template.editor.
- The types involved
code2prompt.model.template.TemplateState→code2prompt.model.template.editor.EditorState
- Direction
- code2prompt.model.template uses code2prompt.model.template.editor, so a change to code2prompt.model.template.editor can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt.model.template.editor.
- Position
- Below the diagonal: code2prompt.model.template uses a module listed above it, which is the healthy direction.
24→20 code2prompt.model.template uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template uses a type in code2prompt_core.session.
- The types involved
code2prompt.model.template.TemplateState→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.model.template uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.model.template uses a module listed above it, which is the healthy direction.
24→26 code2prompt.model.template uses code2prompt.model part of a loop✕
- Connections
- 1 pair of types, where a type in code2prompt.model.template uses a type in code2prompt.model.
- The types involved
code2prompt.model.template.TemplateState→code2prompt.model.Model
- Direction
- code2prompt.model.template uses code2prompt.model, so a change to code2prompt.model can break code2prompt.model.template, while a change to code2prompt.model.template can't break code2prompt.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→9 code2prompt_python.python uses code2prompt_core.analysis✕
- Connections
- 3 pairs of types, where a type in code2prompt_python.python uses a type in code2prompt_core.analysis.
- The types involved
code2prompt_python.python.PyEntryMetadata→code2prompt_core.analysis.EntryMetadatacode2prompt_python.python.PyExtensionStat→code2prompt_core.analysis.ExtensionStatcode2prompt_python.python.PyTokenMapEntry→code2prompt_core.analysis.TokenMapEntry
- Direction
- code2prompt_python.python uses code2prompt_core.analysis, so a change to code2prompt_core.analysis can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.analysis.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→10 code2prompt_python.python uses code2prompt_core.file_processor✕
- Connections
- 2 pairs of types, where a type in code2prompt_python.python uses a type in code2prompt_core.file_processor.
- The types involved
code2prompt_python.python.PyFileProcessorsConfig→code2prompt_core.file_processor.FileProcessorsConfigcode2prompt_python.python.PyIpynbProcessorConfig→code2prompt_core.file_processor.IpynbProcessorConfig
- Direction
- code2prompt_python.python uses code2prompt_core.file_processor, so a change to code2prompt_core.file_processor can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.file_processor.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→11 code2prompt_python.python uses code2prompt_core.template✕
- Connections
- 1 pair of types, where a type in code2prompt_python.python uses a type in code2prompt_core.template.
- The types involved
code2prompt_python.python.PyOutputFormat→code2prompt_core.template.OutputFormat
- Direction
- code2prompt_python.python uses code2prompt_core.template, so a change to code2prompt_core.template can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.template.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→12 code2prompt_python.python uses code2prompt_core.tokenizer✕
- Connections
- 2 pairs of types, where a type in code2prompt_python.python uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt_python.python.PyTokenFormat→code2prompt_core.tokenizer.TokenFormatcode2prompt_python.python.PyTokenizerType→code2prompt_core.tokenizer.TokenizerType
- Direction
- code2prompt_python.python uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→15 code2prompt_python.python uses code2prompt_core.configuration✕
- Connections
- 1 pair of types, where a type in code2prompt_python.python uses a type in code2prompt_core.configuration.
- The types involved
code2prompt_python.python.PyCode2PromptConfig→code2prompt_core.configuration.Code2PromptConfig
- Direction
- code2prompt_python.python uses code2prompt_core.configuration, so a change to code2prompt_core.configuration can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.configuration.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→19 code2prompt_python.python uses code2prompt_core.path✕
- Connections
- 2 pairs of types, where a type in code2prompt_python.python uses a type in code2prompt_core.path.
- The types involved
code2prompt_python.python.PyCodebaseAnalysis→code2prompt_core.path.FileEntrycode2prompt_python.python.PyFileEntry→code2prompt_core.path.FileEntry
- Direction
- code2prompt_python.python uses code2prompt_core.path, so a change to code2prompt_core.path can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.path.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→20 code2prompt_python.python uses code2prompt_core.session✕
- Connections
- 3 pairs of types, where a type in code2prompt_python.python uses a type in code2prompt_core.session.
- The types involved
code2prompt_python.python.PyCode2PromptSession→code2prompt_core.session.Code2PromptSessioncode2prompt_python.python.PyRenderedPrompt→code2prompt_core.session.RenderedPromptcode2prompt_python.python.PySessionData→code2prompt_core.session.SessionData
- Direction
- code2prompt_python.python uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt_python.python uses a module listed above it, which is the healthy direction.
25→28 code2prompt_python.python uses code2prompt_core.sort part of a loop✕
- Connections
- 1 pair of types, where a type in code2prompt_python.python uses a type in code2prompt_core.sort.
- The types involved
code2prompt_python.python.PyFileSortMethod→code2prompt_core.sort.FileSortMethod
- Direction
- code2prompt_python.python uses code2prompt_core.sort, so a change to code2prompt_core.sort can break code2prompt_python.python, while a change to code2prompt_python.python can't break code2prompt_core.sort.
- 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→20 code2prompt.model uses code2prompt_core.session✕
- Connections
- 2 pairs of types, where a type in code2prompt.model uses a type in code2prompt_core.session.
- The types involved
code2prompt.model.DisplayFileNode→code2prompt_core.session.Code2PromptSessioncode2prompt.model.Model→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.model uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.model, while a change to code2prompt.model can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.model uses a module listed above it, which is the healthy direction.
26→21 code2prompt.model uses code2prompt.model.prompt_output✕
- Connections
- 1 pair of types, where a type in code2prompt.model uses a type in code2prompt.model.prompt_output.
- The types involved
code2prompt.model.Model→code2prompt.model.prompt_output.PromptOutputState
- Direction
- code2prompt.model uses code2prompt.model.prompt_output, so a change to code2prompt.model.prompt_output can break code2prompt.model, while a change to code2prompt.model can't break code2prompt.model.prompt_output.
- Position
- Below the diagonal: code2prompt.model uses a module listed above it, which is the healthy direction.
26→22 code2prompt.model uses code2prompt.model.settings✕
- Connections
- 2 pairs of types, where a type in code2prompt.model uses a type in code2prompt.model.settings.
- The types involved
code2prompt.model.Model→code2prompt.model.settings.SettingsGroupcode2prompt.model.Model→code2prompt.model.settings.SettingsState
- Direction
- code2prompt.model uses code2prompt.model.settings, so a change to code2prompt.model.settings can break code2prompt.model, while a change to code2prompt.model can't break code2prompt.model.settings.
- Position
- Below the diagonal: code2prompt.model uses a module listed above it, which is the healthy direction.
26→23 code2prompt.model uses code2prompt.model.statistics✕
- Connections
- 1 pair of types, where a type in code2prompt.model uses a type in code2prompt.model.statistics.
- The types involved
code2prompt.model.Model→code2prompt.model.statistics.StatisticsState
- Direction
- code2prompt.model uses code2prompt.model.statistics, so a change to code2prompt.model.statistics can break code2prompt.model, while a change to code2prompt.model can't break code2prompt.model.statistics.
- Position
- Below the diagonal: code2prompt.model uses a module listed above it, which is the healthy direction.
26→24 code2prompt.model uses code2prompt.model.template✕
- Connections
- 1 pair of types, where a type in code2prompt.model uses a type in code2prompt.model.template.
- The types involved
code2prompt.model.Model→code2prompt.model.template.TemplateState
- Direction
- code2prompt.model uses code2prompt.model.template, so a change to code2prompt.model.template can break code2prompt.model, while a change to code2prompt.model can't break code2prompt.model.template.
- Position
- Below the diagonal: code2prompt.model uses a module listed above it, which is the healthy direction.
27→20 code2prompt.view.formatters uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.view.formatters uses a type in code2prompt_core.session.
- The types involved
code2prompt.view.formatters.formatters$module→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.view.formatters uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.view.formatters, while a change to code2prompt.view.formatters can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.view.formatters uses a module listed above it, which is the healthy direction.
27→22 code2prompt.view.formatters uses code2prompt.model.settings✕
- Connections
- 1 pair of types, where a type in code2prompt.view.formatters uses a type in code2prompt.model.settings.
- The types involved
code2prompt.view.formatters.formatters$module→code2prompt.model.settings.SettingsGroup
- Direction
- code2prompt.view.formatters uses code2prompt.model.settings, so a change to code2prompt.model.settings can break code2prompt.view.formatters, while a change to code2prompt.view.formatters can't break code2prompt.model.settings.
- Position
- Below the diagonal: code2prompt.view.formatters uses a module listed above it, which is the healthy direction.
28→25 code2prompt_core.sort uses code2prompt_python.python✕
- Connections
- 1 pair of types, where a type in code2prompt_core.sort uses a type in code2prompt_python.python.
- The types involved
code2prompt_core.sort.FileSortMethod→code2prompt_python.python.PyFileSortMethod
- Direction
- code2prompt_core.sort uses code2prompt_python.python, so a change to code2prompt_python.python can break code2prompt_core.sort, while a change to code2prompt_core.sort can't break code2prompt_python.python.
- Position
- Below the diagonal: code2prompt_core.sort uses a module listed above it, which is the healthy direction.
29→11 code2prompt.args uses code2prompt_core.template✕
- Connections
- 1 pair of types, where a type in code2prompt.args uses a type in code2prompt_core.template.
- The types involved
code2prompt.args.Cli→code2prompt_core.template.OutputFormat
- Direction
- code2prompt.args uses code2prompt_core.template, so a change to code2prompt_core.template can break code2prompt.args, while a change to code2prompt.args can't break code2prompt_core.template.
- Position
- Below the diagonal: code2prompt.args uses a module listed above it, which is the healthy direction.
29→12 code2prompt.args uses code2prompt_core.tokenizer✕
- Connections
- 2 pairs of types, where a type in code2prompt.args uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt.args.Cli→code2prompt_core.tokenizer.TokenFormatcode2prompt.args.Cli→code2prompt_core.tokenizer.TokenizerType
- Direction
- code2prompt.args uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt.args, while a change to code2prompt.args can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt.args uses a module listed above it, which is the healthy direction.
29→28 code2prompt.args uses code2prompt_core.sort✕
- Connections
- 1 pair of types, where a type in code2prompt.args uses a type in code2prompt_core.sort.
- The types involved
code2prompt.args.Cli→code2prompt_core.sort.FileSortMethod
- Direction
- code2prompt.args uses code2prompt_core.sort, so a change to code2prompt_core.sort can break code2prompt.args, while a change to code2prompt.args can't break code2prompt_core.sort.
- Position
- Below the diagonal: code2prompt.args uses a module listed above it, which is the healthy direction.
30→1 code2prompt.tui uses code2prompt.model.commands✕
- Connections
- 1 pair of types, where a type in code2prompt.tui uses a type in code2prompt.model.commands.
- The types involved
code2prompt.tui.TuiApp→code2prompt.model.commands.Cmd
- Direction
- code2prompt.tui uses code2prompt.model.commands, so a change to code2prompt.model.commands can break code2prompt.tui, while a change to code2prompt.tui can't break code2prompt.model.commands.
- Position
- Below the diagonal: code2prompt.tui uses a module listed above it, which is the healthy direction.
30→20 code2prompt.tui uses code2prompt_core.session✕
- Connections
- 2 pairs of types, where a type in code2prompt.tui uses a type in code2prompt_core.session.
- The types involved
code2prompt.tui.TuiApp→code2prompt_core.session.Code2PromptSessioncode2prompt.tui.tui$module→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.tui uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.tui, while a change to code2prompt.tui can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.tui uses a module listed above it, which is the healthy direction.
30→26 code2prompt.tui uses code2prompt.model✕
- Connections
- 2 pairs of types, where a type in code2prompt.tui uses a type in code2prompt.model.
- The types involved
code2prompt.tui.TuiApp→code2prompt.model.Messagecode2prompt.tui.TuiApp→code2prompt.model.Model
- Direction
- code2prompt.tui uses code2prompt.model, so a change to code2prompt.model can break code2prompt.tui, while a change to code2prompt.tui can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.tui uses a module listed above it, which is the healthy direction.
31→12 code2prompt.utils uses code2prompt_core.tokenizer✕
- Connections
- 1 pair of types, where a type in code2prompt.utils uses a type in code2prompt_core.tokenizer.
- The types involved
code2prompt.utils.utils$module→code2prompt_core.tokenizer.TokenFormat
- Direction
- code2prompt.utils uses code2prompt_core.tokenizer, so a change to code2prompt_core.tokenizer can break code2prompt.utils, while a change to code2prompt.utils can't break code2prompt_core.tokenizer.
- Position
- Below the diagonal: code2prompt.utils uses a module listed above it, which is the healthy direction.
31→20 code2prompt.utils uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.utils uses a type in code2prompt_core.session.
- The types involved
code2prompt.utils.utils$module→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.utils uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.utils, while a change to code2prompt.utils can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.utils uses a module listed above it, which is the healthy direction.
31→26 code2prompt.utils uses code2prompt.model✕
- Connections
- 2 pairs of types, where a type in code2prompt.utils uses a type in code2prompt.model.
- The types involved
code2prompt.utils.DisplayNodeWithSelection→code2prompt.model.DisplayFileNodecode2prompt.utils.utils$module→code2prompt.model.DisplayFileNode
- Direction
- code2prompt.utils uses code2prompt.model, so a change to code2prompt.model can break code2prompt.utils, while a change to code2prompt.utils can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.utils uses a module listed above it, which is the healthy direction.
32→26 code2prompt.widgets.file_selection uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.file_selection uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.file_selection.FileSelectionWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.file_selection uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.file_selection, while a change to code2prompt.widgets.file_selection can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.file_selection uses a module listed above it, which is the healthy direction.
33→26 code2prompt.widgets.output uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.output uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.output.OutputWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.output uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.output, while a change to code2prompt.widgets.output can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.output uses a module listed above it, which is the healthy direction.
34→26 code2prompt.widgets.settings uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.settings uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.settings.SettingsWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.settings uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.settings, while a change to code2prompt.widgets.settings can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.settings uses a module listed above it, which is the healthy direction.
35→26 code2prompt.widgets.statistics_by_extension uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.statistics_by_extension uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.statistics_by_extension.StatisticsByExtensionWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.statistics_by_extension uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.statistics_by_extension, while a change to code2prompt.widgets.statistics_by_extension can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.statistics_by_extension uses a module listed above it, which is the healthy direction.
36→26 code2prompt.widgets.statistics_overview uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.statistics_overview uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.statistics_overview.StatisticsOverviewWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.statistics_overview uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.statistics_overview, while a change to code2prompt.widgets.statistics_overview can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.statistics_overview uses a module listed above it, which is the healthy direction.
37→26 code2prompt.widgets.statistics_token_map uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.statistics_token_map uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.statistics_token_map.StatisticsTokenMapWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.statistics_token_map uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.statistics_token_map, while a change to code2prompt.widgets.statistics_token_map can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.statistics_token_map uses a module listed above it, which is the healthy direction.
38→7 code2prompt.widgets.template uses code2prompt.widgets.template.picker✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template uses a type in code2prompt.widgets.template.picker.
- The types involved
code2prompt.widgets.template.TemplateWidget→code2prompt.widgets.template.picker.TemplatePickerWidget
- Direction
- code2prompt.widgets.template uses code2prompt.widgets.template.picker, so a change to code2prompt.widgets.template.picker can break code2prompt.widgets.template, while a change to code2prompt.widgets.template can't break code2prompt.widgets.template.picker.
- Position
- Below the diagonal: code2prompt.widgets.template uses a module listed above it, which is the healthy direction.
38→8 code2prompt.widgets.template uses code2prompt.widgets.template.variable✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template uses a type in code2prompt.widgets.template.variable.
- The types involved
code2prompt.widgets.template.TemplateWidget→code2prompt.widgets.template.variable.TemplateVariableWidget
- Direction
- code2prompt.widgets.template uses code2prompt.widgets.template.variable, so a change to code2prompt.widgets.template.variable can break code2prompt.widgets.template, while a change to code2prompt.widgets.template can't break code2prompt.widgets.template.variable.
- Position
- Below the diagonal: code2prompt.widgets.template uses a module listed above it, which is the healthy direction.
38→18 code2prompt.widgets.template uses code2prompt.widgets.template.editor✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template uses a type in code2prompt.widgets.template.editor.
- The types involved
code2prompt.widgets.template.TemplateWidget→code2prompt.widgets.template.editor.TemplateEditorWidget
- Direction
- code2prompt.widgets.template uses code2prompt.widgets.template.editor, so a change to code2prompt.widgets.template.editor can break code2prompt.widgets.template, while a change to code2prompt.widgets.template can't break code2prompt.widgets.template.editor.
- Position
- Below the diagonal: code2prompt.widgets.template uses a module listed above it, which is the healthy direction.
38→24 code2prompt.widgets.template uses code2prompt.model.template✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template uses a type in code2prompt.model.template.
- The types involved
code2prompt.widgets.template.TemplateWidget→code2prompt.model.template.TemplateState
- Direction
- code2prompt.widgets.template uses code2prompt.model.template, so a change to code2prompt.model.template can break code2prompt.widgets.template, while a change to code2prompt.widgets.template can't break code2prompt.model.template.
- Position
- Below the diagonal: code2prompt.widgets.template uses a module listed above it, which is the healthy direction.
38→26 code2prompt.widgets.template uses code2prompt.model✕
- Connections
- 1 pair of types, where a type in code2prompt.widgets.template uses a type in code2prompt.model.
- The types involved
code2prompt.widgets.template.TemplateWidget→code2prompt.model.Model
- Direction
- code2prompt.widgets.template uses code2prompt.model, so a change to code2prompt.model can break code2prompt.widgets.template, while a change to code2prompt.widgets.template can't break code2prompt.model.
- Position
- Below the diagonal: code2prompt.widgets.template uses a module listed above it, which is the healthy direction.
39→17 code2prompt.config uses code2prompt.config_loader✕
- Connections
- 1 pair of types, where a type in code2prompt.config uses a type in code2prompt.config_loader.
- The types involved
code2prompt.config.config$module→code2prompt.config_loader.ConfigSource
- Direction
- code2prompt.config uses code2prompt.config_loader, so a change to code2prompt.config_loader can break code2prompt.config, while a change to code2prompt.config can't break code2prompt.config_loader.
- Position
- Below the diagonal: code2prompt.config uses a module listed above it, which is the healthy direction.
39→20 code2prompt.config uses code2prompt_core.session✕
- Connections
- 1 pair of types, where a type in code2prompt.config uses a type in code2prompt_core.session.
- The types involved
code2prompt.config.config$module→code2prompt_core.session.Code2PromptSession
- Direction
- code2prompt.config uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.config, while a change to code2prompt.config can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.config uses a module listed above it, which is the healthy direction.
39→29 code2prompt.config uses code2prompt.args✕
- Connections
- 1 pair of types, where a type in code2prompt.config uses a type in code2prompt.args.
- The types involved
code2prompt.config.config$module→code2prompt.args.Cli
- Direction
- code2prompt.config uses code2prompt.args, so a change to code2prompt.args can break code2prompt.config, while a change to code2prompt.config can't break code2prompt.args.
- Position
- Below the diagonal: code2prompt.config uses a module listed above it, which is the healthy direction.
40→15 code2prompt.main uses code2prompt_core.configuration✕
- Connections
- 1 pair of types, where a type in code2prompt.main uses a type in code2prompt_core.configuration.
- The types involved
code2prompt.main.main$module→code2prompt_core.configuration.OutputDestination
- Direction
- code2prompt.main uses code2prompt_core.configuration, so a change to code2prompt_core.configuration can break code2prompt.main, while a change to code2prompt.main can't break code2prompt_core.configuration.
- Position
- Below the diagonal: code2prompt.main uses a module listed above it, which is the healthy direction.
40→20 code2prompt.main uses code2prompt_core.session✕
- Connections
- 2 pairs of types, where a type in code2prompt.main uses a type in code2prompt_core.session.
- The types involved
code2prompt.main.main$module→code2prompt_core.session.Code2PromptSessioncode2prompt.main.main$module→code2prompt_core.session.RenderedPrompt
- Direction
- code2prompt.main uses code2prompt_core.session, so a change to code2prompt_core.session can break code2prompt.main, while a change to code2prompt.main can't break code2prompt_core.session.
- Position
- Below the diagonal: code2prompt.main uses a module listed above it, which is the healthy direction.
40→29 code2prompt.main uses code2prompt.args✕
- Connections
- 1 pair of types, where a type in code2prompt.main uses a type in code2prompt.args.
- The types involved
code2prompt.main.main$module→code2prompt.args.Cli
- Direction
- code2prompt.main uses code2prompt.args, so a change to code2prompt.args can break code2prompt.main, while a change to code2prompt.main can't break code2prompt.args.
- Position
- Below the diagonal: code2prompt.main uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | Medium |
Roadmap
First, integrate automated security scanning into the CI pipeline to block regressions and enforce strict null checking in TypeScript to prevent runtime errors. Next, address the inverted test pyramid to improve test distribution and ensure every release requires manual approval or is published as a draft to prevent bad builds from reaching users. Finally, maintain a changelog to clearly document what ships in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +2.9 pts | Low | Test Distribution |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.4 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.8 pts | Medium | Security & performance tooling |
| The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`). | +3.1 pts | Medium | Nullable reference types |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.5 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.5 pts | Medium | Release Hygiene |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.2 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.6 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| crates/code2prompt/src/model/settings.rs | 7.0 | Mixed | Cyclomatic Complexity: SettingsState::update_setting_by_key (cyclomatic 23) |
| crates/code2prompt/src/model/mod.rs | 7.0 | Mixed | Cyclomatic Complexity: Model::update (cyclomatic 79) |
| crates/code2prompt/src/widgets/statistics_by_extension.rs | 7.1 | Mixed | God Classes: MethodTooLong: StatisticsByExtensionWidget.render |
| crates/code2prompt-core/src/git.rs | 7.1 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
| crates/code2prompt/src/tui.rs | 7.2 | Mixed | Cyclomatic Complexity: TuiApp::handle_key_event (cyclomatic 27) |
| crates/code2prompt/src/config.rs | 7.2 | Mixed | Cyclomatic Complexity: code2prompt::config::build_session (cyclomatic 25) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/code2prompt-python/src/python.rs | 7.4 | Mixed | God Classes: FileTooLong: src/python.rs |
| crates/code2prompt/src/utils.rs | 7.8 | Mixed | Cognitive Complexity: code2prompt::utils::collect_visible_nodes_recursive (cognitive 37) |
| crates/code2prompt/src/widgets/template/picker.rs | 7.8 | Mixed | Cognitive Complexity: TemplatePickerWidget::render (cognitive 30) |
| crates/code2prompt-core/src/file_processor/ipynb.rs | 7.8 | Mixed | Cognitive Complexity: JupyterNotebookProcessor::process (cognitive 23) |
| crates/code2prompt-core/src/analysis.rs | 7.8 | Mixed | Cognitive Complexity: code2prompt_core::analysis::select_nodes_to_display (cognitive 20) |
| crates/code2prompt/src/widgets/file_selection.rs | 7.8 | Mixed | Cognitive Complexity: FileSelectionWidget::render (cognitive 19) |
| crates/code2prompt/src/config_loader.rs | 7.8 | Mixed | Cognitive Complexity: code2prompt::config_loader::load_config (cognitive 17) |
| crates/code2prompt/src/widgets/statistics_overview.rs | 7.8 | Mixed | God Classes: MethodTooLong: StatisticsOverviewWidget.render |
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. 54 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 54 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, 79 of 102 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
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in website/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (36 contributor(s) across 705 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 35 hold 0.5% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- 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 this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- 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.
- 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Model::update at 79. 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 TuiApp::convert_crossterm_key at 21 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/code2prompt/src/widgets/statistics_token_map.rs (StatisticsTokenMapWidget::render at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Model::update (cyclomatic 79). — Refactoring it lifts Cyclomatic Complexity from 7.9 to about 8.9/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was Model::update at 121.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Model::update (cognitive 121). — Refactoring it lifts Cognitive Complexity from 3.9 to about 5.5/10.
- 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
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with mod.rs, statistics_by_extension.rs, statistics_overview.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with formatters.rs, config.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with python.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
21 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 python.rs (2), config.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with git.rs (2), picker.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with git.rs, statistics_by_extension.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.
D5 · Coupling
3 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 18 classes have LCOM4 above 3.
D9 · Test Distribution
168 test methods: 26 unit, 142 integration, 0 BDD, 0 e2e. The Rust suite contributes 148 `#[test]` function(s) across 18 file(s) declaring at least one; its unit/integration split is Cargo's own — 16 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. The Python suite contributes 20 test function(s) across 6 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D12 · Dependency Hygiene
8 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 436 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/code2prompt/src/main.rs (6×15=90)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 9678 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. 128 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
0 of 4 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 15 high, 1 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 0 high, 6 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 42 of the 54 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: settings.rs↔tui.rs 67%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with settings.rs. — One of this dimension's main actionable groups (1 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
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
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 4 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README_ES.md links to `src/default_template.hbs`, but `src/default_template.hbs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README_ES.md:29
What to do
- Reconcile the README with reality: README_ES.md links to `src/default_template.hbs`, but `src/default_template.hbs` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/code2prompt-python`, `website`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- 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
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6613 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads 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
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
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
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by D2, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4162 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — No tests discovered
- 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; JavaScript, Python, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in website/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- 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
- 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 JavaScript/TypeScript, 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.
- S1 Web-Security Posture — No web surface: 54 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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.
- 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
- 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: website/
- REDACTED
- REDACTED
- REDACTED
Serious — 66 finding(s)
- code2prompt::utils::collect_visible_nodes_recursive (cognitive 37) crates/code2prompt/src/utils.rs:153
- code2prompt::config::build_session (cognitive 35) crates/code2prompt/src/config.rs:25
- code2prompt::emit_cli_results (cognitive 21) crates/code2prompt/src/main.rs:142
- code2prompt::token_map::format_token_map_for_tui (cognitive 21) crates/code2prompt/src/token_map.rs:67
- code2prompt::config_loader::load_config (cognitive 17) crates/code2prompt/src/config_loader.rs:19
- code2prompt::utils::ensure_path_exists_in_tree (cognitive 17) crates/code2prompt/src/utils.rs:399
- MethodTooLong: Model.update crates/code2prompt/src/model/mod.rs:249
- MethodTooLong: StatisticsByExtensionWidget.render crates/code2prompt/src/widgets/statistics_by_extension.rs:27
- MethodTooLong: StatisticsOverviewWidget.render crates/code2prompt/src/widgets/statistics_overview.rs:21
- MethodTooLong: FileSelectionWidget.render crates/code2prompt/src/widgets/file_selection.rs:26
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) crates/code2prompt-python/src/python.rs:341
- Duplicated block (9 lines × 2) crates/code2prompt-python/src/python.rs:351
- Duplicated block (9 lines × 2) crates/code2prompt/src/config.rs:141
- Duplicated block (8 lines × 2) crates/code2prompt-core/src/git.rs:47
- Duplicated block (8 lines × 2) crates/code2prompt-core/src/git.rs:51
- Duplicated block (8 lines × 2) crates/code2prompt/src/widgets/template/picker.rs:58
- TuiApp::handle_key_event (cyclomatic 27) crates/code2prompt/src/tui.rs:203
- TuiApp::handle_template_keys (cyclomatic 27) crates/code2prompt/src/tui.rs:336
- code2prompt_core::path::discover_files (cognitive 29) crates/code2prompt-core/src/path.rs:98
- code2prompt_core::analysis::select_nodes_to_display (cognitive 20) crates/code2prompt-core/src/analysis.rs:314
- TuiApp::handle_template_keys (cognitive 27) crates/code2prompt/src/tui.rs:336
- TuiApp::run (cognitive 23) crates/code2prompt/src/tui.rs:64
- JupyterNotebookProcessor::process (cognitive 23) crates/code2prompt-core/src/file_processor/ipynb.rs:87
- JupyterNotebookProcessor::append_outputs (cognitive 20) crates/code2prompt-core/src/file_processor/ipynb.rs:39
- FunctionTooLong: code2prompt::view::formatters::format_settings_groups crates/code2prompt/src/view/formatters.rs:14
- FunctionTooLong: code2prompt::config::build_session crates/code2prompt/src/config.rs:25
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) crates/code2prompt-core/src/git.rs:109
- Duplicated block (18 lines × 2) crates/code2prompt/src/widgets/statistics_by_extension.rs:43
- Duplicated block (11 lines × 2) crates/code2prompt/src/model/mod.rs:206
- Duplicated block (11 lines × 2) crates/code2prompt/src/model/mod.rs:360
- Duplicated block (5 lines × 2) crates/code2prompt/src/widgets/statistics_by_extension.rs:227
- Duplicated block (5 lines × 2) crates/code2prompt/src/widgets/statistics_overview.rs:44
- Model::update (cyclomatic 79) crates/code2prompt/src/model/mod.rs:249
- code2prompt::config::build_session (cyclomatic 25) crates/code2prompt/src/config.rs:25
- SettingsState::update_setting_by_key (cyclomatic 23) crates/code2prompt/src/model/settings.rs:75
- Hotspot: crates/code2prompt/src/main.rs crates/code2prompt/src/main.rs:142
- Model::update (cognitive 121) crates/code2prompt/src/model/mod.rs:249
- TemplatePickerWidget::render (cognitive 30) crates/code2prompt/src/widgets/template/picker.rs:20
- FileSelectionWidget::render (cognitive 19) crates/code2prompt/src/widgets/file_selection.rs:26
- TemplateVariableWidget::render (cognitive 19) crates/code2prompt/src/widgets/template/variable.rs:20
- SettingsWidget::render (cognitive 17) crates/code2prompt/src/widgets/settings.rs:26
- REDACTED
- FileTooLong: src/python.rs crates/code2prompt-python/src/python.rs
- REDACTED
- Change coupling: settings.rs ↔ tui.rs crates/code2prompt/src/model/settings.rs:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (25 corresponding lines) crates/code2prompt-core/src/git.rs:104
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/code2prompt/src/model/mod.rs:91
- Duplicated block (12–13 lines × 2) crates/code2prompt/src/config_loader.rs:22
- Duplicated block (11 lines × 3) crates/code2prompt-core/src/git.rs:105
- Duplicated block (10 lines × 2) crates/code2prompt-core/src/analysis.rs:251
- Duplicated block (7–8 lines × 3) crates/code2prompt/src/widgets/template/editor.rs:37
- Duplicated block (4–7 lines × 4) crates/code2prompt/src/model/mod.rs:123
- Duplicated block (6 lines × 2) crates/code2prompt/src/model/mod.rs:447
- Duplicated block (13 lines × 2) crates/code2prompt/src/widgets/statistics_by_extension.rs:29
- Duplicated block (12 lines × 2) crates/code2prompt/src/model/mod.rs:454
- Duplicated block (8 lines × 3) crates/code2prompt/src/widgets/statistics_by_extension.rs:47
- Off the main sequence: code2prompt_core
- Coverage not measured — JavaScript/TypeScript suite
Minor — 12 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- README/code drift README_ES.md:29
- Logging is not universal
- No SAST
- No changelog
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 8 finding(s)
- Outdated: arboard
- Outdated: clap
- Outdated: encoding_rs
- Outdated: ratatui-textarea
- Outdated: serde_json
- Outdated: tiktoken-rs
- Outdated: tokio
- Outdated: toml
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-52f221d118c045e3b2e5afeb3b5a3834/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-52f221d118c045e3b2e5afeb3b5a3834/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 . | 16 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 6 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |