Executive summary
e2e-test-quest/uuv is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no access checks on the code's endpoints or handlers and it has packages with a known security hole. It scores 40.3 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 33.1, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package published as malware, worth about 4.0 points. Adding access checks would lift Security and Compliance itself, worth about 6.2 points. Raising Security and Compliance to 70 would lift the score to about 46.6.
Seventy-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifty-five known security holes in the packages the code depends on can be used by attackers, and two automatic updates take new releases before a bad one can be spotted. Pinning each tool to an exact version, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks. The two passwords or keys in the code's history need replacing, with the old ones switched off. The two places where the code runs text as code or as a command need a direct call instead. The 13 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 18,381 lines, about €23,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 33.1 to 70, the lowest score rated Strong, the score would rise from 40.3 to about 46.6.
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,800 to €39,000, for 130 to 411 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 40. 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: 18,381 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 com.e2etesting.uuv.intellijplugin.model | 2 packages.a11y-dashboard.src.server.plugins.database | 3 packages.a11y.src.lib.model.checker | 4 packages.a11y.src.lib.model.reference | 5 packages.a11y.src.lib.query.00-query | 6 packages.assistant.src.Commons | 7 packages.assistant.src.translator.abstract-translator | 8 packages.dictionary.src.lib.accessible-role | 9 packages.dictionary.src.lib.dictionary | 10 packages.mcp-server.src.lib.services.architect.architect_model | 11 packages.mcp-server.src.lib.services.element.abstract-element_service | 12 packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service | 13 packages.mcp-server.src.lib.services.utils | 14 packages.runner-commons.src.cli.runner | 15 com.e2etesting.uuv.intellijplugin | 16 packages.a11y.src.lib.model.rule | 17 packages.a11y.src.lib.query.operators.operator-query | 18 packages.a11y.src.lib.reference.wcag | 19 packages.assistant.src.helper | 20 packages.assistant.src.translator.expect-translator | 21 packages.mcp-server.src.lib.services | 22 packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service | 23 packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service | 24 packages.mcp-server.src.lib.services.image.classifier | 25 packages.mcp-server.src.lib.services.image.classifier.image-classifier_service | 26 packages.runner-commons.src.step-definition-generator.common | 27 packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper | 28 packages.a11y.src.lib.model.result | 29 packages.a11y.src.lib.query.operators.and-query | 30 packages.a11y.src.lib.query.operators.or-query | 31 packages.assistant.src.service.abstract-component-service | 32 packages.mcp-server.src.lib.agents.uuv_agent | 33 packages.mcp-server.src.lib.services.architect.architect_service | 34 packages.runner-commons.src.step-definition-generator.generate-base-step-definitions | 35 packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions | 36 packages.a11y.src.lib.engine.engine | 37 packages.a11y.src.lib.reference.wcag.wcag-checker | 38 packages.assistant.src.service.dialog-service | 39 packages.assistant.src.service.form-completion-service | 40 packages.a11y.src.lib.model.checklist-checker |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.e2etesting.uuv.intellijplugin.model | ||||||||||||||||||||||||||||||||||||||||
| 2 packages.a11y-dashboard.src.server.plugins.database | ||||||||||||||||||||||||||||||||||||||||
| 3 packages.a11y.src.lib.model.checker | ||||||||||||||||||||||||||||||||||||||||
| 4 packages.a11y.src.lib.model.reference | ||||||||||||||||||||||||||||||||||||||||
| 5 packages.a11y.src.lib.query.00-query | ||||||||||||||||||||||||||||||||||||||||
| 6 packages.assistant.src.Commons | ||||||||||||||||||||||||||||||||||||||||
| 7 packages.assistant.src.translator.abstract-translator | ||||||||||||||||||||||||||||||||||||||||
| 8 packages.dictionary.src.lib.accessible-role | ||||||||||||||||||||||||||||||||||||||||
| 9 packages.dictionary.src.lib.dictionary | ||||||||||||||||||||||||||||||||||||||||
| 10 packages.mcp-server.src.lib.services.architect.architect_model | ||||||||||||||||||||||||||||||||||||||||
| 11 packages.mcp-server.src.lib.services.element.abstract-element_service | ||||||||||||||||||||||||||||||||||||||||
| 12 packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service | ||||||||||||||||||||||||||||||||||||||||
| 13 packages.mcp-server.src.lib.services.utils | ||||||||||||||||||||||||||||||||||||||||
| 14 packages.runner-commons.src.cli.runner | ||||||||||||||||||||||||||||||||||||||||
| 15 com.e2etesting.uuv.intellijplugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 packages.a11y.src.lib.model.rule | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 packages.a11y.src.lib.query.operators.operator-query | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 packages.a11y.src.lib.reference.wcag | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 packages.assistant.src.helper | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 packages.assistant.src.translator.expect-translator | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 packages.mcp-server.src.lib.services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 packages.mcp-server.src.lib.services.image.classifier | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 packages.mcp-server.src.lib.services.image.classifier.image-classifier_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 packages.runner-commons.src.step-definition-generator.common | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 packages.a11y.src.lib.model.result | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 packages.a11y.src.lib.query.operators.and-query | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 packages.a11y.src.lib.query.operators.or-query | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 packages.assistant.src.service.abstract-component-service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 packages.mcp-server.src.lib.agents.uuv_agent | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 packages.mcp-server.src.lib.services.architect.architect_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 packages.runner-commons.src.step-definition-generator.generate-base-step-definitions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 packages.a11y.src.lib.engine.engine | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 packages.a11y.src.lib.reference.wcag.wcag-checker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 packages.assistant.src.service.dialog-service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 packages.assistant.src.service.form-completion-service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 packages.a11y.src.lib.model.checklist-checker | 1 | 1 | 1 | 1 |
15→1 com.e2etesting.uuv.intellijplugin uses com.e2etesting.uuv.intellijplugin.model✕
- Connections
- 1 pair of types, where a type in com.e2etesting.uuv.intellijplugin uses a type in com.e2etesting.uuv.intellijplugin.model.
- The types involved
com.e2etesting.uuv.intellijplugin.UUVUtils→com.e2etesting.uuv.intellijplugin.model.UUVTargetScript
- Direction
- com.e2etesting.uuv.intellijplugin uses com.e2etesting.uuv.intellijplugin.model, so a change to com.e2etesting.uuv.intellijplugin.model can break com.e2etesting.uuv.intellijplugin, while a change to com.e2etesting.uuv.intellijplugin can't break com.e2etesting.uuv.intellijplugin.model.
- Position
- Below the diagonal: com.e2etesting.uuv.intellijplugin uses a module listed above it, which is the healthy direction.
16→5 packages.a11y.src.lib.model.rule uses packages.a11y.src.lib.query.00-query✕
- Connections
- 3 pairs of types, where a type in packages.a11y.src.lib.model.rule uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.a11y.src.lib.model.rule.A11yRule→packages.a11y.src.lib.query.00-query.Querypackages.a11y.src.lib.model.rule.AutoCheckA11yRule→packages.a11y.src.lib.query.00-query.Querypackages.a11y.src.lib.model.rule.ManualCheckA11yRule→packages.a11y.src.lib.query.00-query.Query
- Direction
- packages.a11y.src.lib.model.rule uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.a11y.src.lib.model.rule, while a change to packages.a11y.src.lib.model.rule can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.a11y.src.lib.model.rule uses a module listed above it, which is the healthy direction.
17→5 packages.a11y.src.lib.query.operators.operator-query uses packages.a11y.src.lib.query.00-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.query.operators.operator-query uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.a11y.src.lib.query.operators.operator-query.OperatorQuery→packages.a11y.src.lib.query.00-query.Query
- Direction
- packages.a11y.src.lib.query.operators.operator-query uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.a11y.src.lib.query.operators.operator-query, while a change to packages.a11y.src.lib.query.operators.operator-query can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.a11y.src.lib.query.operators.operator-query uses a module listed above it, which is the healthy direction.
18→2 packages.a11y.src.lib.reference.wcag uses packages.a11y-dashboard.src.server.plugins.database✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.reference.wcag uses a type in packages.a11y-dashboard.src.server.plugins.database.
- The types involved
packages.a11y.src.lib.reference.wcag.wcag-helper→packages.a11y-dashboard.src.server.plugins.database.Result
- Direction
- packages.a11y.src.lib.reference.wcag uses packages.a11y-dashboard.src.server.plugins.database, so a change to packages.a11y-dashboard.src.server.plugins.database can break packages.a11y.src.lib.reference.wcag, while a change to packages.a11y.src.lib.reference.wcag can't break packages.a11y-dashboard.src.server.plugins.database.
- Position
- Below the diagonal: packages.a11y.src.lib.reference.wcag uses a module listed above it, which is the healthy direction.
19→6 packages.assistant.src.helper uses packages.assistant.src.Commons✕
- Connections
- 2 pairs of types, where a type in packages.assistant.src.helper uses a type in packages.assistant.src.Commons.
- The types involved
packages.assistant.src.helper.keyboard-navigation-helper→packages.assistant.src.Commons.AdditionalLayerEnumpackages.assistant.src.helper.layer-helper→packages.assistant.src.Commons.AdditionalLayerEnum
- Direction
- packages.assistant.src.helper uses packages.assistant.src.Commons, so a change to packages.assistant.src.Commons can break packages.assistant.src.helper, while a change to packages.assistant.src.helper can't break packages.assistant.src.Commons.
- Position
- Below the diagonal: packages.assistant.src.helper uses a module listed above it, which is the healthy direction.
20→7 packages.assistant.src.translator.expect-translator uses packages.assistant.src.translator.abstract-translator✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.translator.expect-translator uses a type in packages.assistant.src.translator.abstract-translator.
- The types involved
packages.assistant.src.translator.expect-translator.ExpectTranslator→packages.assistant.src.translator.abstract-translator.Translator
- Direction
- packages.assistant.src.translator.expect-translator uses packages.assistant.src.translator.abstract-translator, so a change to packages.assistant.src.translator.abstract-translator can break packages.assistant.src.translator.expect-translator, while a change to packages.assistant.src.translator.expect-translator can't break packages.assistant.src.translator.abstract-translator.
- Position
- Below the diagonal: packages.assistant.src.translator.expect-translator uses a module listed above it, which is the healthy direction.
21→11 packages.mcp-server.src.lib.services uses packages.mcp-server.src.lib.services.element.abstract-element_service✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services uses a type in packages.mcp-server.src.lib.services.element.abstract-element_service.
- The types involved
packages.mcp-server.src.lib.services.expect.service→packages.mcp-server.src.lib.services.element.abstract-element_service.AbstractElementService
- Direction
- packages.mcp-server.src.lib.services uses packages.mcp-server.src.lib.services.element.abstract-element_service, so a change to packages.mcp-server.src.lib.services.element.abstract-element_service can break packages.mcp-server.src.lib.services, while a change to packages.mcp-server.src.lib.services can't break packages.mcp-server.src.lib.services.element.abstract-element_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services uses a module listed above it, which is the healthy direction.
21→13 packages.mcp-server.src.lib.services uses packages.mcp-server.src.lib.services.utils✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services uses a type in packages.mcp-server.src.lib.services.utils.
- The types involved
packages.mcp-server.src.lib.services.utils→packages.mcp-server.src.lib.services.utils.EmbeddingConfig
- Direction
- packages.mcp-server.src.lib.services uses packages.mcp-server.src.lib.services.utils, so a change to packages.mcp-server.src.lib.services.utils can break packages.mcp-server.src.lib.services, while a change to packages.mcp-server.src.lib.services can't break packages.mcp-server.src.lib.services.utils.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services uses a module listed above it, which is the healthy direction.
22→10 packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service uses packages.mcp-server.src.lib.services.architect.architect_model✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service uses a type in packages.mcp-server.src.lib.services.architect.architect_model.
- The types involved
packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service.ArchitectExplorerService→packages.mcp-server.src.lib.services.architect.architect_model.ScenarioResult
- Direction
- packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service uses packages.mcp-server.src.lib.services.architect.architect_model, so a change to packages.mcp-server.src.lib.services.architect.architect_model can break packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service, while a change to packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service can't break packages.mcp-server.src.lib.services.architect.architect_model.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service uses a module listed above it, which is the healthy direction.
23→10 packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service uses packages.mcp-server.src.lib.services.architect.architect_model✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service uses a type in packages.mcp-server.src.lib.services.architect.architect_model.
- The types involved
packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service.ArchitectFormatterService→packages.mcp-server.src.lib.services.architect.architect_model.ScenarioResult
- Direction
- packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service uses packages.mcp-server.src.lib.services.architect.architect_model, so a change to packages.mcp-server.src.lib.services.architect.architect_model can break packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service, while a change to packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service can't break packages.mcp-server.src.lib.services.architect.architect_model.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service uses a module listed above it, which is the healthy direction.
24→12 packages.mcp-server.src.lib.services.image.classifier uses packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service✕
- Connections
- 2 pairs of types, where a type in packages.mcp-server.src.lib.services.image.classifier uses a type in packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.
- The types involved
packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer.service→packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.Relationpackages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer.service→packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.ScoreResult
- Direction
- packages.mcp-server.src.lib.services.image.classifier uses packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service, so a change to packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service can break packages.mcp-server.src.lib.services.image.classifier, while a change to packages.mcp-server.src.lib.services.image.classifier can't break packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.image.classifier uses a module listed above it, which is the healthy direction.
24→13 packages.mcp-server.src.lib.services.image.classifier uses packages.mcp-server.src.lib.services.utils✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.image.classifier uses a type in packages.mcp-server.src.lib.services.utils.
- The types involved
packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer.service→packages.mcp-server.src.lib.services.utils.EmbeddingConfig
- Direction
- packages.mcp-server.src.lib.services.image.classifier uses packages.mcp-server.src.lib.services.utils, so a change to packages.mcp-server.src.lib.services.utils can break packages.mcp-server.src.lib.services.image.classifier, while a change to packages.mcp-server.src.lib.services.image.classifier can't break packages.mcp-server.src.lib.services.utils.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.image.classifier uses a module listed above it, which is the healthy direction.
25→12 packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses a type in packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.
- The types involved
packages.mcp-server.src.lib.services.image.classifier.image-classifier_service.ImageClassifierService→packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.ScoreResult
- Direction
- packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service, so a change to packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service can break packages.mcp-server.src.lib.services.image.classifier.image-classifier_service, while a change to packages.mcp-server.src.lib.services.image.classifier.image-classifier_service can't break packages.mcp-server.src.lib.services.image.classifier.text-similarity-scorer_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses a module listed above it, which is the healthy direction.
25→13 packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses packages.mcp-server.src.lib.services.utils✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses a type in packages.mcp-server.src.lib.services.utils.
- The types involved
packages.mcp-server.src.lib.services.image.classifier.image-classifier_service.ImageClassifierService→packages.mcp-server.src.lib.services.utils.EmbeddingConfig
- Direction
- packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses packages.mcp-server.src.lib.services.utils, so a change to packages.mcp-server.src.lib.services.utils can break packages.mcp-server.src.lib.services.image.classifier.image-classifier_service, while a change to packages.mcp-server.src.lib.services.image.classifier.image-classifier_service can't break packages.mcp-server.src.lib.services.utils.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.image.classifier.image-classifier_service uses a module listed above it, which is the healthy direction.
26→9 packages.runner-commons.src.step-definition-generator.common uses packages.dictionary.src.lib.dictionary✕
- Connections
- 1 pair of types, where a type in packages.runner-commons.src.step-definition-generator.common uses a type in packages.dictionary.src.lib.dictionary.
- The types involved
packages.runner-commons.src.step-definition-generator.common.GenerateFileProcessing→packages.dictionary.src.lib.dictionary.Dictionary
- Direction
- packages.runner-commons.src.step-definition-generator.common uses packages.dictionary.src.lib.dictionary, so a change to packages.dictionary.src.lib.dictionary can break packages.runner-commons.src.step-definition-generator.common, while a change to packages.runner-commons.src.step-definition-generator.common can't break packages.dictionary.src.lib.dictionary.
- Position
- Below the diagonal: packages.runner-commons.src.step-definition-generator.common uses a module listed above it, which is the healthy direction.
27→5 packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper uses packages.a11y.src.lib.query.00-query✕
- Connections
- 1 pair of types, where a type in packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper.UuvPlaywrightReporterHelper→packages.a11y.src.lib.query.00-query.Query
- Direction
- packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper, while a change to packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.runner-playwright.src.reporter.uuv-playwright-reporter-helper uses a module listed above it, which is the healthy direction.
28→4 packages.a11y.src.lib.model.result uses packages.a11y.src.lib.model.reference✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.result uses a type in packages.a11y.src.lib.model.reference.
- The types involved
packages.a11y.src.lib.model.result.A11yResult→packages.a11y.src.lib.model.reference.A11yReference
- Direction
- packages.a11y.src.lib.model.result uses packages.a11y.src.lib.model.reference, so a change to packages.a11y.src.lib.model.reference can break packages.a11y.src.lib.model.result, while a change to packages.a11y.src.lib.model.result can't break packages.a11y.src.lib.model.reference.
- Position
- Below the diagonal: packages.a11y.src.lib.model.result uses a module listed above it, which is the healthy direction.
28→5 packages.a11y.src.lib.model.result uses packages.a11y.src.lib.query.00-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.result uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.a11y.src.lib.model.result.NodeToCheckManually→packages.a11y.src.lib.query.00-query.QueryResult
- Direction
- packages.a11y.src.lib.model.result uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.a11y.src.lib.model.result, while a change to packages.a11y.src.lib.model.result can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.a11y.src.lib.model.result uses a module listed above it, which is the healthy direction.
28→16 packages.a11y.src.lib.model.result uses packages.a11y.src.lib.model.rule✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.result uses a type in packages.a11y.src.lib.model.rule.
- The types involved
packages.a11y.src.lib.model.result.A11yRuleResult→packages.a11y.src.lib.model.rule.A11yRule
- Direction
- packages.a11y.src.lib.model.result uses packages.a11y.src.lib.model.rule, so a change to packages.a11y.src.lib.model.rule can break packages.a11y.src.lib.model.result, while a change to packages.a11y.src.lib.model.result can't break packages.a11y.src.lib.model.rule.
- Position
- Below the diagonal: packages.a11y.src.lib.model.result uses a module listed above it, which is the healthy direction.
29→5 packages.a11y.src.lib.query.operators.and-query uses packages.a11y.src.lib.query.00-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.query.operators.and-query uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.a11y.src.lib.query.operators.and-query.AndQuery→packages.a11y.src.lib.query.00-query.Query
- Direction
- packages.a11y.src.lib.query.operators.and-query uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.a11y.src.lib.query.operators.and-query, while a change to packages.a11y.src.lib.query.operators.and-query can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.a11y.src.lib.query.operators.and-query uses a module listed above it, which is the healthy direction.
29→17 packages.a11y.src.lib.query.operators.and-query uses packages.a11y.src.lib.query.operators.operator-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.query.operators.and-query uses a type in packages.a11y.src.lib.query.operators.operator-query.
- The types involved
packages.a11y.src.lib.query.operators.and-query.AndQuery→packages.a11y.src.lib.query.operators.operator-query.IOperatorQuery
- Direction
- packages.a11y.src.lib.query.operators.and-query uses packages.a11y.src.lib.query.operators.operator-query, so a change to packages.a11y.src.lib.query.operators.operator-query can break packages.a11y.src.lib.query.operators.and-query, while a change to packages.a11y.src.lib.query.operators.and-query can't break packages.a11y.src.lib.query.operators.operator-query.
- Position
- Below the diagonal: packages.a11y.src.lib.query.operators.and-query uses a module listed above it, which is the healthy direction.
30→5 packages.a11y.src.lib.query.operators.or-query uses packages.a11y.src.lib.query.00-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.query.operators.or-query uses a type in packages.a11y.src.lib.query.00-query.
- The types involved
packages.a11y.src.lib.query.operators.or-query.OrQuery→packages.a11y.src.lib.query.00-query.Query
- Direction
- packages.a11y.src.lib.query.operators.or-query uses packages.a11y.src.lib.query.00-query, so a change to packages.a11y.src.lib.query.00-query can break packages.a11y.src.lib.query.operators.or-query, while a change to packages.a11y.src.lib.query.operators.or-query can't break packages.a11y.src.lib.query.00-query.
- Position
- Below the diagonal: packages.a11y.src.lib.query.operators.or-query uses a module listed above it, which is the healthy direction.
30→17 packages.a11y.src.lib.query.operators.or-query uses packages.a11y.src.lib.query.operators.operator-query✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.query.operators.or-query uses a type in packages.a11y.src.lib.query.operators.operator-query.
- The types involved
packages.a11y.src.lib.query.operators.or-query.OrQuery→packages.a11y.src.lib.query.operators.operator-query.IOperatorQuery
- Direction
- packages.a11y.src.lib.query.operators.or-query uses packages.a11y.src.lib.query.operators.operator-query, so a change to packages.a11y.src.lib.query.operators.operator-query can break packages.a11y.src.lib.query.operators.or-query, while a change to packages.a11y.src.lib.query.operators.or-query can't break packages.a11y.src.lib.query.operators.operator-query.
- Position
- Below the diagonal: packages.a11y.src.lib.query.operators.or-query uses a module listed above it, which is the healthy direction.
31→6 packages.assistant.src.service.abstract-component-service uses packages.assistant.src.Commons✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.abstract-component-service uses a type in packages.assistant.src.Commons.
- The types involved
packages.assistant.src.service.abstract-component-service.AbstractComponentService→packages.assistant.src.Commons.AdditionalLayerEnum
- Direction
- packages.assistant.src.service.abstract-component-service uses packages.assistant.src.Commons, so a change to packages.assistant.src.Commons can break packages.assistant.src.service.abstract-component-service, while a change to packages.assistant.src.service.abstract-component-service can't break packages.assistant.src.Commons.
- Position
- Below the diagonal: packages.assistant.src.service.abstract-component-service uses a module listed above it, which is the healthy direction.
31→20 packages.assistant.src.service.abstract-component-service uses packages.assistant.src.translator.expect-translator✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.abstract-component-service uses a type in packages.assistant.src.translator.expect-translator.
- The types involved
packages.assistant.src.service.abstract-component-service.AbstractComponentService→packages.assistant.src.translator.expect-translator.ExpectTranslator
- Direction
- packages.assistant.src.service.abstract-component-service uses packages.assistant.src.translator.expect-translator, so a change to packages.assistant.src.translator.expect-translator can break packages.assistant.src.service.abstract-component-service, while a change to packages.assistant.src.service.abstract-component-service can't break packages.assistant.src.translator.expect-translator.
- Position
- Below the diagonal: packages.assistant.src.service.abstract-component-service uses a module listed above it, which is the healthy direction.
32→25 packages.mcp-server.src.lib.agents.uuv_agent uses packages.mcp-server.src.lib.services.image.classifier.image-classifier_service✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.agents.uuv_agent uses a type in packages.mcp-server.src.lib.services.image.classifier.image-classifier_service.
- The types involved
packages.mcp-server.src.lib.agents.uuv_agent.UuvAgent→packages.mcp-server.src.lib.services.image.classifier.image-classifier_service.ImageClassifierService
- Direction
- packages.mcp-server.src.lib.agents.uuv_agent uses packages.mcp-server.src.lib.services.image.classifier.image-classifier_service, so a change to packages.mcp-server.src.lib.services.image.classifier.image-classifier_service can break packages.mcp-server.src.lib.agents.uuv_agent, while a change to packages.mcp-server.src.lib.agents.uuv_agent can't break packages.mcp-server.src.lib.services.image.classifier.image-classifier_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.agents.uuv_agent uses a module listed above it, which is the healthy direction.
33→22 packages.mcp-server.src.lib.services.architect.architect_service uses packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.architect.architect_service uses a type in packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service.
- The types involved
packages.mcp-server.src.lib.services.architect.architect_service.ArchitectService→packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service.ArchitectExplorerService
- Direction
- packages.mcp-server.src.lib.services.architect.architect_service uses packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service, so a change to packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service can break packages.mcp-server.src.lib.services.architect.architect_service, while a change to packages.mcp-server.src.lib.services.architect.architect_service can't break packages.mcp-server.src.lib.services.architect.explorer.architect-explorer_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.architect.architect_service uses a module listed above it, which is the healthy direction.
33→23 packages.mcp-server.src.lib.services.architect.architect_service uses packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service✕
- Connections
- 1 pair of types, where a type in packages.mcp-server.src.lib.services.architect.architect_service uses a type in packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service.
- The types involved
packages.mcp-server.src.lib.services.architect.architect_service.ArchitectService→packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service.ArchitectFormatterService
- Direction
- packages.mcp-server.src.lib.services.architect.architect_service uses packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service, so a change to packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service can break packages.mcp-server.src.lib.services.architect.architect_service, while a change to packages.mcp-server.src.lib.services.architect.architect_service can't break packages.mcp-server.src.lib.services.architect.formatter.architect-formatter_service.
- Position
- Below the diagonal: packages.mcp-server.src.lib.services.architect.architect_service uses a module listed above it, which is the healthy direction.
34→9 packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses packages.dictionary.src.lib.dictionary✕
- Connections
- 1 pair of types, where a type in packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses a type in packages.dictionary.src.lib.dictionary.
- The types involved
packages.runner-commons.src.step-definition-generator.generate-base-step-definitions.BaseStepDefinition→packages.dictionary.src.lib.dictionary.Dictionary
- Direction
- packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses packages.dictionary.src.lib.dictionary, so a change to packages.dictionary.src.lib.dictionary can break packages.runner-commons.src.step-definition-generator.generate-base-step-definitions, while a change to packages.runner-commons.src.step-definition-generator.generate-base-step-definitions can't break packages.dictionary.src.lib.dictionary.
- Position
- Below the diagonal: packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses a module listed above it, which is the healthy direction.
34→26 packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses packages.runner-commons.src.step-definition-generator.common✕
- Connections
- 1 pair of types, where a type in packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses a type in packages.runner-commons.src.step-definition-generator.common.
- The types involved
packages.runner-commons.src.step-definition-generator.generate-base-step-definitions.BaseStepDefinition→packages.runner-commons.src.step-definition-generator.common.GenerateFileProcessing
- Direction
- packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses packages.runner-commons.src.step-definition-generator.common, so a change to packages.runner-commons.src.step-definition-generator.common can break packages.runner-commons.src.step-definition-generator.generate-base-step-definitions, while a change to packages.runner-commons.src.step-definition-generator.generate-base-step-definitions can't break packages.runner-commons.src.step-definition-generator.common.
- Position
- Below the diagonal: packages.runner-commons.src.step-definition-generator.generate-base-step-definitions uses a module listed above it, which is the healthy direction.
35→9 packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses packages.dictionary.src.lib.dictionary✕
- Connections
- 1 pair of types, where a type in packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses a type in packages.dictionary.src.lib.dictionary.
- The types involved
packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions.BasedRoleStepDefinition→packages.dictionary.src.lib.dictionary.Dictionary
- Direction
- packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses packages.dictionary.src.lib.dictionary, so a change to packages.dictionary.src.lib.dictionary can break packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions, while a change to packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions can't break packages.dictionary.src.lib.dictionary.
- Position
- Below the diagonal: packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses a module listed above it, which is the healthy direction.
35→26 packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses packages.runner-commons.src.step-definition-generator.common✕
- Connections
- 1 pair of types, where a type in packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses a type in packages.runner-commons.src.step-definition-generator.common.
- The types involved
packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions.BasedRoleStepDefinition→packages.runner-commons.src.step-definition-generator.common.GenerateFileProcessing
- Direction
- packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses packages.runner-commons.src.step-definition-generator.common, so a change to packages.runner-commons.src.step-definition-generator.common can break packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions, while a change to packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions can't break packages.runner-commons.src.step-definition-generator.common.
- Position
- Below the diagonal: packages.runner-commons.src.step-definition-generator.generate-based-role-step-definitions uses a module listed above it, which is the healthy direction.
36→4 packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.reference✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.engine.engine uses a type in packages.a11y.src.lib.model.reference.
- The types involved
packages.a11y.src.lib.engine.engine.Engine→packages.a11y.src.lib.model.reference.A11yReference
- Direction
- packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.reference, so a change to packages.a11y.src.lib.model.reference can break packages.a11y.src.lib.engine.engine, while a change to packages.a11y.src.lib.engine.engine can't break packages.a11y.src.lib.model.reference.
- Position
- Below the diagonal: packages.a11y.src.lib.engine.engine uses a module listed above it, which is the healthy direction.
36→16 packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.rule✕
- Connections
- 3 pairs of types, where a type in packages.a11y.src.lib.engine.engine uses a type in packages.a11y.src.lib.model.rule.
- The types involved
packages.a11y.src.lib.engine.engine.Engine→packages.a11y.src.lib.model.rule.A11yRulepackages.a11y.src.lib.engine.engine.Engine→packages.a11y.src.lib.model.rule.AutoCheckA11yRulepackages.a11y.src.lib.engine.engine.Engine→packages.a11y.src.lib.model.rule.ManualCheckA11yRule
- Direction
- packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.rule, so a change to packages.a11y.src.lib.model.rule can break packages.a11y.src.lib.engine.engine, while a change to packages.a11y.src.lib.engine.engine can't break packages.a11y.src.lib.model.rule.
- Position
- Below the diagonal: packages.a11y.src.lib.engine.engine uses a module listed above it, which is the healthy direction.
36→28 packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.result✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.engine.engine uses a type in packages.a11y.src.lib.model.result.
- The types involved
packages.a11y.src.lib.engine.engine.Engine→packages.a11y.src.lib.model.result.A11yRuleResult
- Direction
- packages.a11y.src.lib.engine.engine uses packages.a11y.src.lib.model.result, so a change to packages.a11y.src.lib.model.result can break packages.a11y.src.lib.engine.engine, while a change to packages.a11y.src.lib.engine.engine can't break packages.a11y.src.lib.model.result.
- Position
- Below the diagonal: packages.a11y.src.lib.engine.engine uses a module listed above it, which is the healthy direction.
37→3 packages.a11y.src.lib.reference.wcag.wcag-checker uses packages.a11y.src.lib.model.checker✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.reference.wcag.wcag-checker uses a type in packages.a11y.src.lib.model.checker.
- The types involved
packages.a11y.src.lib.reference.wcag.wcag-checker.WcagChecker→packages.a11y.src.lib.model.checker.A11yChecker
- Direction
- packages.a11y.src.lib.reference.wcag.wcag-checker uses packages.a11y.src.lib.model.checker, so a change to packages.a11y.src.lib.model.checker can break packages.a11y.src.lib.reference.wcag.wcag-checker, while a change to packages.a11y.src.lib.reference.wcag.wcag-checker can't break packages.a11y.src.lib.model.checker.
- Position
- Below the diagonal: packages.a11y.src.lib.reference.wcag.wcag-checker uses a module listed above it, which is the healthy direction.
37→28 packages.a11y.src.lib.reference.wcag.wcag-checker uses packages.a11y.src.lib.model.result✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.reference.wcag.wcag-checker uses a type in packages.a11y.src.lib.model.result.
- The types involved
packages.a11y.src.lib.reference.wcag.wcag-checker.WcagChecker→packages.a11y.src.lib.model.result.A11yResultStatus
- Direction
- packages.a11y.src.lib.reference.wcag.wcag-checker uses packages.a11y.src.lib.model.result, so a change to packages.a11y.src.lib.model.result can break packages.a11y.src.lib.reference.wcag.wcag-checker, while a change to packages.a11y.src.lib.reference.wcag.wcag-checker can't break packages.a11y.src.lib.model.result.
- Position
- Below the diagonal: packages.a11y.src.lib.reference.wcag.wcag-checker uses a module listed above it, which is the healthy direction.
38→6 packages.assistant.src.service.dialog-service uses packages.assistant.src.Commons✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.dialog-service uses a type in packages.assistant.src.Commons.
- The types involved
packages.assistant.src.service.dialog-service.DialogService→packages.assistant.src.Commons.AdditionalLayerEnum
- Direction
- packages.assistant.src.service.dialog-service uses packages.assistant.src.Commons, so a change to packages.assistant.src.Commons can break packages.assistant.src.service.dialog-service, while a change to packages.assistant.src.service.dialog-service can't break packages.assistant.src.Commons.
- Position
- Below the diagonal: packages.assistant.src.service.dialog-service uses a module listed above it, which is the healthy direction.
38→31 packages.assistant.src.service.dialog-service uses packages.assistant.src.service.abstract-component-service✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.dialog-service uses a type in packages.assistant.src.service.abstract-component-service.
- The types involved
packages.assistant.src.service.dialog-service.DialogService→packages.assistant.src.service.abstract-component-service.AbstractComponentService
- Direction
- packages.assistant.src.service.dialog-service uses packages.assistant.src.service.abstract-component-service, so a change to packages.assistant.src.service.abstract-component-service can break packages.assistant.src.service.dialog-service, while a change to packages.assistant.src.service.dialog-service can't break packages.assistant.src.service.abstract-component-service.
- Position
- Below the diagonal: packages.assistant.src.service.dialog-service uses a module listed above it, which is the healthy direction.
39→7 packages.assistant.src.service.form-completion-service uses packages.assistant.src.translator.abstract-translator✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.form-completion-service uses a type in packages.assistant.src.translator.abstract-translator.
- The types involved
packages.assistant.src.service.form-completion-service.FormCompletionService→packages.assistant.src.translator.abstract-translator.Translator
- Direction
- packages.assistant.src.service.form-completion-service uses packages.assistant.src.translator.abstract-translator, so a change to packages.assistant.src.translator.abstract-translator can break packages.assistant.src.service.form-completion-service, while a change to packages.assistant.src.service.form-completion-service can't break packages.assistant.src.translator.abstract-translator.
- Position
- Below the diagonal: packages.assistant.src.service.form-completion-service uses a module listed above it, which is the healthy direction.
39→31 packages.assistant.src.service.form-completion-service uses packages.assistant.src.service.abstract-component-service✕
- Connections
- 1 pair of types, where a type in packages.assistant.src.service.form-completion-service uses a type in packages.assistant.src.service.abstract-component-service.
- The types involved
packages.assistant.src.service.form-completion-service.FormCompletionService→packages.assistant.src.service.abstract-component-service.AbstractComponentService
- Direction
- packages.assistant.src.service.form-completion-service uses packages.assistant.src.service.abstract-component-service, so a change to packages.assistant.src.service.abstract-component-service can break packages.assistant.src.service.form-completion-service, while a change to packages.assistant.src.service.form-completion-service can't break packages.assistant.src.service.abstract-component-service.
- Position
- Below the diagonal: packages.assistant.src.service.form-completion-service uses a module listed above it, which is the healthy direction.
40→3 packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.checker✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.checklist-checker uses a type in packages.a11y.src.lib.model.checker.
- The types involved
packages.a11y.src.lib.model.checklist-checker.A11yChecklistChecker→packages.a11y.src.lib.model.checker.A11yChecker
- Direction
- packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.checker, so a change to packages.a11y.src.lib.model.checker can break packages.a11y.src.lib.model.checklist-checker, while a change to packages.a11y.src.lib.model.checklist-checker can't break packages.a11y.src.lib.model.checker.
- Position
- Below the diagonal: packages.a11y.src.lib.model.checklist-checker uses a module listed above it, which is the healthy direction.
40→4 packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.reference✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.checklist-checker uses a type in packages.a11y.src.lib.model.reference.
- The types involved
packages.a11y.src.lib.model.checklist-checker.A11yChecklistChecker→packages.a11y.src.lib.model.reference.A11yReference
- Direction
- packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.reference, so a change to packages.a11y.src.lib.model.reference can break packages.a11y.src.lib.model.checklist-checker, while a change to packages.a11y.src.lib.model.checklist-checker can't break packages.a11y.src.lib.model.reference.
- Position
- Below the diagonal: packages.a11y.src.lib.model.checklist-checker uses a module listed above it, which is the healthy direction.
40→16 packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.rule✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.checklist-checker uses a type in packages.a11y.src.lib.model.rule.
- The types involved
packages.a11y.src.lib.model.checklist-checker.A11yChecklistChecker→packages.a11y.src.lib.model.rule.A11yRule
- Direction
- packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.model.rule, so a change to packages.a11y.src.lib.model.rule can break packages.a11y.src.lib.model.checklist-checker, while a change to packages.a11y.src.lib.model.checklist-checker can't break packages.a11y.src.lib.model.rule.
- Position
- Below the diagonal: packages.a11y.src.lib.model.checklist-checker uses a module listed above it, which is the healthy direction.
40→36 packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.engine.engine✕
- Connections
- 1 pair of types, where a type in packages.a11y.src.lib.model.checklist-checker uses a type in packages.a11y.src.lib.engine.engine.
- The types involved
packages.a11y.src.lib.model.checklist-checker.A11yChecklistChecker→packages.a11y.src.lib.engine.engine.Engine
- Direction
- packages.a11y.src.lib.model.checklist-checker uses packages.a11y.src.lib.engine.engine, so a change to packages.a11y.src.lib.engine.engine can break packages.a11y.src.lib.model.checklist-checker, while a change to packages.a11y.src.lib.model.checklist-checker can't break packages.a11y.src.lib.engine.engine.
- Position
- Below the diagonal: packages.a11y.src.lib.model.checklist-checker uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 117 | High / Critical |
| A05:2025 — Injection | 80 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A08:2025 — Software or Data Integrity Failures | 1 | Medium |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. | +4.0 pts | Low | Malicious Dependencies |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +6.2 pts | Medium | Access Controls |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.1 pts | Medium | Dependency Hygiene |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +2.9 pts | Medium | Web-Security Posture |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts | 4.8 | Mixed | God Classes: TooManyMethods: UuvPlaywrightReporterHelper |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| packages/assistant/src/helper/informative-nodes-helper.ts | 6.0 | Mixed | Explicit Debt: FixmeComment |
| packages/runner-playwright/src/reporter/uuv-custom-formatter.ts | 6.0 | Mixed | Explicit Debt: FixmeComment |
| packages/a11y/src/lib/query/by-sibling.query.ts | 6.3 | Mixed | Cyclomatic Complexity: BySiblingQuery.computeResult (cyclomatic 19) |
| packages/mcp-server/src/lib/mcp-server-factory.ts | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| packages/a11y/src/lib/engine/engine.ts | 7.0 | Mixed | Cognitive Complexity: Engine.getSelector (cognitive 17) |
| packages/assistant/src/helper/highlight/inspector-dom.js | 7.0 | Mixed | God Classes: FunctionTooLong: inspector-dom.Inspector |
| packages/assistant/src/UuvAssistant.tsx | 7.1 | Mixed | Cyclomatic Complexity: UuvAssistant.UuvAssistant (cyclomatic 34) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 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, 534 of 546 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the jest run in the repository root produced no per-test report (Error: Jest: Failed to parse the TypeScript config file jest.config.ts). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because cache-redirector.jetbrains.com — the registry that answers it — was asked and did not reply (the build stopped because cache-redirector.jetbrains.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add cache-redirector.jetbrains.com to the allowlist and re-run — not to build anything.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, 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 (11 contributor(s) across 3057 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 10 hold 1.9% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/runner-playwright/src/cucumber/step_definitions/playwright/based-role-check-engine.ts`, `packages/runner-playwright/src/cucumber/step_definitions/playwright/index.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 109 commits in the last 90 days, yet 68 of 90 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev` in packages/a11y/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> @uuv/a11y@1.0.0-beta.115 dev / > ts-node watch.ts / sh: 1: ts-node: not found / npm error Lifecycle script `dev` failed with error: / npm error code 127 / npm error path <repo>/packages/a11y / npm error workspace @uuv/a11y@1.0.0-beta.115 / npm error location <repo>/packages/a11y / npm error command failed / npm error command sh -c ts-node watch.ts" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev` in packages/a11y/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> @uuv/a11y@1.0.0-beta.115 dev / > ts-node watch.ts / sh: 1: ts-node: not found / npm error Lifecycle script `dev` failed with error: / npm error code 127 / npm error path <repo>/packages/a11y / npm error workspace @uuv/a11y@1.0.0-beta.115 / npm error location <repo>/packages/a11y / npm error command failed / npm error command sh -c ts-node watch.ts" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
- R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 REDACTED Scanning: REDACTED 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UuvAssistant.UuvAssistant at 34.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UuvAssistant.UuvAssistant (cyclomatic 34), BySiblingQuery.computeResult (cyclomatic 19), generate-step-definitions-documentation.runGenerateDoc (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was BySiblingQuery.computeResult at 30.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with BySiblingQuery.computeResult (cognitive 30), InformativeNodesHelper.findRelevantAccessibilityParent (cognitive 22), UuvAssistant.UuvAssistant::callUnifiedAIForImage (cognitive 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 6 FunctionTooLong finding(s) in God Classes — start with UuvAssistant.tsx, mcp-server-factory.ts, index.tsx. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with UuvAssistant.tsx, uuv-playwright-reporter-helper.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with uuv-playwright-reporter-helper.ts. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
13 production modules (Gradle+Cargo+npm+pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 11 of the 13 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 28 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with uuv-playwright-reporter-helper.ts. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 45.4% — 25 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest in the repository root: not run; jest via `npm ci --ignore-scripts` in packages/a11y/, the 3 run(s) test reliability made; jest via `npm ci --ignore-scripts` in packages/assistant/, the 3 run(s) test reliability made; jest via `npm ci --ignore-scripts` in packages/runner-cypress/, the 3 run(s) test reliability made; jest via `npm ci --ignore-scripts` in packages/runner-playwright/, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 2 line(s) in 1 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 25 Low coverage finding(s) in Code Coverage — start with engine.ts, checklist-checker.ts, accessible-name.query.ts. — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 1 Tests reach code only in some runs finding(s) in Code Coverage — start with runner-cypress.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 230 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root; jest via `npm ci --ignore-scripts` in packages/a11y/ (64 tests); jest via `npm ci --ignore-scripts` in packages/assistant/ (25 tests); jest via `npm ci --ignore-scripts` in packages/runner-cypress/ (20 tests); jest via `npm ci --ignore-scripts` in packages/runner-playwright/ (19 tests)): measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 515 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 REDACTED, 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: packages/assistant/src/UuvAssistant.tsx (2×34=68); packages/mcp-server/src/lib/agents/uuv.agent.ts (2×17=34)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with UuvAssistant.tsx, uuv.agent.ts. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
9 deducted task-comment markers across 15702 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with base-check-engine.ts (2), uuv-cli.spec.ts, mcp-server-factory.ts. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with uuv-custom-formatter.ts, informative-nodes-helper.ts, link-checker.spec.ts. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 52 document(s) read across 14 unit(s).
What to do
- Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (10 contexts). Contexts: a11y, a11y-dashboard, assistant, dictionary, docs, mcp-server, runner-commons, runner-cypress, runner-playwright, vscode-extension.
D24 · Comment Value
7 of 95 judged comments only repeat the code they sit on (7.4 %). 55 comment(s) in another language or script were not judged.
What to do
- Resolve the 7 redundant comment finding(s) in Comment Value — start with prompt-retriever.service.spec.ts (4), bulk.post.ts, index.tsx. — One of this dimension's main actionable groups (7 recommendation-level).
D26 · Project Cohesion
0 of 15 build units (Cargo, Gradle, npm, pub) flagged as possibly oversized/incoherent.
D27 · Navigability
35 % of calls cross a namespace and 3 % go through an interface, but 85 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D29 · Static Analysis (SAST)
80 finding(s): 0 critical, 78 high, 2 medium, 0 low. 67 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `gradlew` (line 74, line 180), `REDACTED` (lines 7–48), `packages/intellij-plugin/src/main/kotlin/com/e2etesting/uuv/intellijplugin/UUVUtils.kt` (line 38, lines 48–49, line 75), `packages/runner-playwright/src/cucumber/step_definitions/playwright/based-role-check-engine.ts` (line 30), `packages/runner-playwright/src/cucumber/step_definitions/playwright/index.ts` (line 27) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 67 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (70 issue-level, 3 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
113 finding(s): 8 critical, 47 high, 50 medium, 8 low.
What to do
- Resolve the 45 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (43), REDACTED (2). — One of this dimension's main actionable groups (45 issue-level).
- Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 1 high, 4 medium, 3 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — packages/a11y-dashboard/src/app.vue:10, packages/assistant/index.html:347, packages/assistant/index.html:371
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — packages/assistant-desktop/src/routes/+page.svelte:273
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/chrome-extension/uuv-devtools-panel.html:1
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — packages/chrome-extension/uuv-devtools-panel.html:1
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. — packages/assistant/index.html:158
- The repo's own CSS styles .uuv-gutter-warning with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — packages/assistant/src/helper/result-display-helper.ts:6
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. — packages/assistant/index.html:329
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- `#service_toggle_submit.stopped` sets color: #fff on background-color: #4caf50 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/assistant-desktop/src/routes/+page.svelte:658
- `*` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/assistant-desktop/src/routes/+page.svelte:349
- `#search button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/assistant-desktop/src/routes/+page.svelte:457
- `#service_toggle_submit` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/assistant-desktop/src/routes/+page.svelte:644
- `.button` moves (`transition: transform 0.3s ease, box-shadow 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/docs/src/pages/index.module.css:120
- `.chevron` moves (`transition: transform 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/assistant-desktop/src/routes/+page.svelte:559
- `.config-body` moves (`transition: max-height 0.3s ease, padding 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/assistant-desktop/src/routes/+page.svelte:571
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
- `@uuv/a11y` ships in a production host and references `@testing-library/dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `@uuv/a11y` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — packages/a11y/REDACTED:43
- `@uuv/cypress` ships in a production host and references `@testing-library/cypress`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `@uuv/cypress` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — packages/runner-cypress/REDACTED:52
- `@uuv/cypress` ships in a production host and references `cypress`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `@uuv/cypress` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — packages/runner-cypress/REDACTED:57
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — new Hono() (packages/mcp-server/src/lib/agents/uuv.agent.ts:35) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — packages/mcp-server/src/lib/agents/uuv.agent.ts:35
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code
- A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. — packages/mcp-server/src/lib/services/element/type-element.service.ts:20
- A placeholder string ("Lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in. — packages/assistant/src/translator/type-translator.ts:147
- A placeholder string (""Lorem ipsum"") is still in shipped code — typical of generated boilerplate that was never filled in. — packages/assistant/src/translator/type-translator.ts:167
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `generateSentenceForDomSelector` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/mcp-server/src/lib/services/element/type-element.service.ts:20
- `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/runner-cypress/src/lib/uuv-cli.ts:20, packages/runner-playwright/src/lib/uuv-cli.ts:20
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
- packages/mcp-server/README.md links to `./01-uuv-assistant.md`, but `packages/mcp-server/01-uuv-assistant.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — packages/mcp-server/README.md:67
What to do
- Reconcile the README with reality: packages/mcp-server/README.md links to `./01-uuv-assistant.md`, but `packages/mcp-server/01-uuv-assistant.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
- Only 1/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/a11y-dashboard`, `packages/assistant`, `packages/assistant-desktop`, `packages/assistant-desktop/src-tauri`, `packages/runner-cypress` and 1 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P8 · Schema migrations
- Sequelize sync() builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Sequelize migrations (`sequelize-cli db:migrate`), so every schema change is a versioned file applied the same way in every environment. — packages/a11y-dashboard/src/server/plugins/database.ts:222
What to do
- Replace Sequelize sync() with Sequelize migrations (`sequelize-cli db:migrate`) so the production schema can evolve safely and reproducibly.
PF3 · Async & latency hygiene
- `fs.readFileSync` in `generateExpectForTable` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/mcp-server/src/lib/services/expect.service.ts:49
- `fs.existsSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runner-cypress/src/lib/runner-cypress.ts:74
- `fs.rmSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runner-cypress/src/lib/runner-cypress.ts:75
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- 24 duplicated blocks under packages/ have copies in at least two of the sibling directories a11y, assistant, dictionary, mcp-server, runner-commons, runner-cypress (+2 more sibling(s) not listed) — 21 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/assistant/.eslintrc.js:1
- packages/assistant/.eslintrc.js:1 · packages/runner-playwright/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 62 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/assistant/.eslintrc.js:1
- packages/a11y/.eslintrc.js:1 · packages/dictionary/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/a11y/.eslintrc.js:1
- packages/a11y/.eslintrc.js:1 · packages/mcp-server/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/a11y/.eslintrc.js:1
- packages/a11y/.eslintrc.js:1 · packages/runner-commons/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/a11y/.eslintrc.js:1
- packages/a11y/.eslintrc.js:1 · packages/vscode-extension/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/a11y/.eslintrc.js:1
- packages/dictionary/.eslintrc.js:1 · packages/mcp-server/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/dictionary/.eslintrc.js:1
- packages/dictionary/.eslintrc.js:1 · packages/runner-commons/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/dictionary/.eslintrc.js:1
- packages/dictionary/.eslintrc.js:1 · packages/vscode-extension/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/dictionary/.eslintrc.js:1
- packages/mcp-server/.eslintrc.js:1 · packages/runner-commons/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mcp-server/.eslintrc.js:1
- packages/mcp-server/.eslintrc.js:1 · packages/vscode-extension/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mcp-server/.eslintrc.js:1
- packages/runner-commons/.eslintrc.js:1 · packages/vscode-extension/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/runner-commons/.eslintrc.js:1
- packages/a11y/.eslintrc.js:1 · packages/assistant/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/a11y/.eslintrc.js:1
- packages/assistant/.eslintrc.js:1 · packages/dictionary/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/assistant/.eslintrc.js:1
- packages/assistant/.eslintrc.js:1 · packages/mcp-server/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/assistant/.eslintrc.js:1
- packages/assistant/.eslintrc.js:1 · packages/runner-commons/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/assistant/.eslintrc.js:1
- packages/assistant/.eslintrc.js:1 · packages/vscode-extension/.eslintrc.js:1 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/assistant/.eslintrc.js:1
- packages/a11y/.eslintrc.js:67 · packages/dictionary/.eslintrc.js:67 · packages/mcp-server/.eslintrc.js:67 · packages/runner-commons/.eslintrc.js:67 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/a11y/.eslintrc.js:67
- packages/a11y-dashboard/src/server/api/apps/[appId].delete.ts:3 · packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:3 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/a11y-dashboard/src/server/api/apps/[appId].delete.ts:3
- packages/a11y/src/lib/engine/engine.ts:108 · packages/assistant/src/translator/abstract-translator.ts:66 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/a11y/src/lib/engine/engine.ts:108
- packages/mcp-server/src/lib/services/image/describer/image-describer.service.ts:54 · packages/mcp-server/src/lib/services/image/describer/image-describer.service.ts:81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/mcp-server/src/lib/services/image/describer/image-describer.service.ts:54
- packages/mcp-server/src/lib/mcp-server-factory.ts:145 · packages/mcp-server/src/lib/mcp-server-factory.ts:222 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/mcp-server/src/lib/mcp-server-factory.ts:145
- packages/runner-commons/src/step-definition-generator/generate-base-step-definitions.ts:17 · packages/runner-commons/src/step-definition-generator/generate-based-role-step-definitions.ts:18 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runner-commons/src/step-definition-generator/generate-base-step-definitions.ts:17
- packages/a11y/src/lib/model/rule.ts:17 · packages/a11y/src/lib/model/rule.ts:44 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/a11y/src/lib/model/rule.ts:17
- packages/mcp-server/src/lib/mcp-server-factory.ts:454 · packages/mcp-server/src/lib/mcp-server-factory.ts:474 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mcp-server/src/lib/mcp-server-factory.ts:454
- packages/assistant/src/component/UuvAssistantSettings.tsx:37 · packages/assistant/src/component/result/UuvAssistantResultHeader.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/assistant/src/component/UuvAssistantSettings.tsx:37
- packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:26 · packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].get.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:26
- packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:172 · packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:190 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:172
- packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].delete.ts:5 · packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results/[resultId].delete.ts:4 — the two spans are one implementation copied and then locally edited — 65 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].delete.ts:5
- packages/assistant/src/translator/type-translator.ts:39 · packages/assistant/src/translator/within-translator.ts:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/assistant/src/translator/type-translator.ts:39
- packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:28 · packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].get.ts:40 · packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results/[resultId].get.ts:16 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:28
- packages/assistant/src/UuvAssistant.tsx:523 · packages/assistant/src/UuvAssistant.tsx:551 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/assistant/src/UuvAssistant.tsx:523
- packages/assistant/src/UuvAssistant.tsx:582 · packages/assistant/src/UuvAssistant.tsx:597 · packages/assistant/src/UuvAssistant.tsx:612 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/assistant/src/UuvAssistant.tsx:582
- packages/dictionary/src/lib/web/en/en-roles.ts:39 · packages/dictionary/src/lib/web/fr/fr-roles.ts:26 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/dictionary/src/lib/web/en/en-roles.ts:39
- packages/a11y-dashboard/src/server/api/apps.post.ts:1 · packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results.get.ts:1 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/a11y-dashboard/src/server/api/apps.post.ts:1
- packages/a11y/src/lib/reference/rgaa/rules/1-image.ts:121 · packages/a11y/src/lib/reference/rgaa/rules/1-image.ts:140 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/a11y/src/lib/reference/rgaa/rules/1-image.ts:121
- packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:208 · packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:225 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:208
- packages/assistant/launcher/uuv-assistant-launcher.ts:22 · packages/runner-commons/src/cli/helper.ts:13 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/assistant/launcher/uuv-assistant-launcher.ts:22
- packages/assistant/src/translator/click-translator.ts:22 · packages/assistant/src/translator/keyboard-navigation-translator.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/assistant/src/translator/click-translator.ts:22
- packages/runner-cypress/postinstall.js:19 · packages/runner-playwright/postinstall.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/runner-cypress/postinstall.js:19
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- packages/a11y/src/lib/query/by-tag.query.ts:3 imports jquery/dist/jquery.min, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/a11y/src/lib/query/by-tag.query.ts:3
- packages/a11y/src/lib/query/compliant-attributes/attribut-specification.ts:3 imports jquery/dist/jquery.min, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/a11y/src/lib/query/compliant-attributes/attribut-specification.ts:3
- packages/assistant/src/service/helper-service.tsx:15 imports antd/lib/notification/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/assistant/src/service/helper-service.tsx:15
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/a11y/src/lib/query/by-sibling.query.ts:35
- findRelevantAccessibilityParent has cyclomatic complexity 16 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/assistant/src/helper/informative-nodes-helper.ts:74
- parseAriaLine has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:185
- buildAndAddScenario has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runner-playwright/src/reporter/uuv-custom-formatter.ts:54
- getMockedDataForAccessibleRole has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/assistant/src/translator/type-translator.ts:126
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/dictionary/src/lib/dictionary.ts:51
R3 · Large Files
- packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts has 692 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:1
- packages/assistant/src/UuvAssistant.tsx has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/assistant/src/UuvAssistant.tsx:1
- packages/assistant-desktop/src/routes/+page.svelte has 631 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/assistant-desktop/src/routes/+page.svelte:1
- packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:1
- packages/dictionary/src/lib/web/fr/fr-roles.ts has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/dictionary/src/lib/web/fr/fr-roles.ts:1
- packages/runner-playwright/src/cucumber/step_definitions/playwright/core-engine.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runner-playwright/src/cucumber/step_definitions/playwright/core-engine.ts:1
- packages/mcp-server/src/lib/mcp-server-factory.ts has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mcp-server/src/lib/mcp-server-factory.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts:15 imports '../../cypress/commands', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts:15
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×39) — packages/assistant/src/UuvAssistant.tsx:1, packages/a11y-dashboard/src/server/plugins/database.ts:1, packages/assistant-desktop/src/routes/+page.svelte:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 142 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling
- The package in `packages/assistant` declares the lint script `lint` (`eslint -c .eslintrc.js`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/assistant` (or the workspace's task runner). — packages/assistant/REDACTED:47
- The package in `packages/dictionary` declares the lint script `lint` (`npx eslint . --ext .js,.ts,.feature --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/dictionary` (or the workspace's task runner). — packages/dictionary/REDACTED:37
- The package in `packages/mcp-server` declares the lint script `lint` (`npx eslint . --ext .js,.ts,.feature --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/mcp-server` (or the workspace's task runner). — packages/mcp-server/REDACTED:47
- The package in `packages/runner-commons` declares the lint script `lint` (`npx eslint . --ext .js,.ts,.feature --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/runner-commons` (or the workspace's task runner). — packages/runner-commons/REDACTED:37
- The package in `packages/runner-cypress` declares the lint script `lint` (`eslint -c .eslintrc.js`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/runner-cypress` (or the workspace's task runner). — packages/runner-cypress/REDACTED:47
- The package in `packages/vscode-extension` declares the lint script `lint` (`eslint src --ext ts`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/vscode-extension` (or the workspace's task runner). — packages/vscode-extension/REDACTED:79
- This repository declares test tooling, and the ✓ above records that declaration — but packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts:15
R7 · Dead Code
- Unreachable from the 42 application, 39 tooling and 65 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (42 application, 39 tooling, 65 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×35) — packages/a11y-dashboard/src/server/plugins/database.ts, packages/a11y-dashboard/src/pages/apps/[[appId]]/usecases/[[usecaseId]]/index.vue, packages/mcp-server/src/lib/agents/uuv-agent.eval.ts, …
- no import path from any entry point (42 application, 39 tooling, 65 test roots considered), but 10 in-repo import(s) from 9 other file(s) do name it (packages/a11y-dashboard/src/components/CardWithCounter.vue, packages/a11y-dashboard/src/components/ResultDetails.vue, packages/a11y-dashboard/src/pages/apps/[[appId]]/index.vue and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/a11y-dashboard/src/models/index.ts
- no import path from any entry point (42 application, 39 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/a11y-dashboard/src/pages/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/a11y-dashboard/src/components/BulkImporter.vue, packages/a11y-dashboard/src/components/CardWithCounter.vue
- no import path from any entry point (42 application, 39 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/a11y-dashboard/src/utils/computeCounter.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/a11y-dashboard/src/utils/filterIssuesByType.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×13) — tests/integration/my-custom-step-definitions.cypress.ts:1, tests/integration/my-custom-step-definitions.playwright.ts:1, packages/assistant/src/UuvAssistant.tsx:9, …
- Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3) — REDACTED:43, REDACTED:50, REDACTED:53
- Declared in packages/a11y/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/a11y/REDACTED:61
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×7) — REDACTED:47, REDACTED:49, REDACTED:50, …
- Declared in packages/assistant-desktop/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/assistant-desktop/REDACTED:20
- Declared in packages/dictionary/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/dictionary/REDACTED:41
- Declared in packages/mcp-server/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3) — packages/mcp-server/REDACTED:67, packages/mcp-server/REDACTED:71, packages/mcp-server/REDACTED:72
- Declared in packages/vscode-extension/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/vscode-extension/REDACTED:89
- Only test files import it (first: packages/runner-cypress/src/cypress/cypress.config.ts:3) — move it to devDependencies. — packages/runner-cypress/REDACTED:51
- Only test files import it (first: packages/runner-cypress/src/cypress/commands.ts:83) — move it to devDependencies. — packages/runner-cypress/REDACTED:56
- Only test files import it (first: packages/runner-cypress/src/cypress/cypress.config.ts:15) — move it to devDependencies. — packages/runner-cypress/REDACTED:58
- Only test files import it (first: packages/runner-cypress/src/cypress/commands.ts:30) — move it to devDependencies. — packages/runner-cypress/REDACTED:59
- Only test files import it (first: packages/runner-cypress/src/cucumber/step_definitions/cypress/_.common.ts:20) — move it to devDependencies. — packages/runner-cypress/REDACTED:60
- Only test files import it (first: packages/runner-cypress/src/cucumber/step_definitions/cypress/a11y-engine.ts:32) — move it to devDependencies. — packages/runner-cypress/REDACTED:63
- Only test files import it (first: packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:19) — move it to devDependencies. — packages/runner-playwright/REDACTED:49
- Only test files import it (first: packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:50) — move it to devDependencies. — packages/runner-playwright/REDACTED:54
- Only test files import it (first: packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:16) — move it to devDependencies. — packages/runner-playwright/REDACTED:55
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/assistant/src/translator/expect-translator.ts → packages/assistant/src/translator/textual-translator.ts → packages/assistant/src/translator/expect-translator.ts — packages/assistant/src/translator/expect-translator.ts:18
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/ag-grid-community@35.3.1/dist/ag-grid-community.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — packages/assistant/index.html:64
- `serve(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/mcp-server/src/lib/agents/uuv.agent.ts:162
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `onDescriptionSelected` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/assistant/src/UuvAssistant.tsx:365
- `generateNominalCase` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/assistant/src/service/architect-service.ts:23
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 72 is called with an argument built by `JSON.stringify(rawPageSnapshot, null, 4)` (line 72), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:72
- `debug` at line 74 is called with an argument built by `JSON.stringify(parsedPageSnapshot, null, 4)` (line 74), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:74
- `debug` at line 84 is called with an argument built by `JSON.stringify(nextStep, null, 4)` (line 84), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:84
- `debug` at line 87 is called with an argument built by `JSON.stringify(nextStep, null, 4)` (line 87), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:87
- `debug` at line 92 is called with an argument built by `JSON.stringify(nextStep.result, null, 4)` (line 92), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:92
- `debug` at line 98 is called with an argument built by `JSON.stringify(actionHistory, null, 2)` (line 98), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:98
- `debug` at line 99 is called with an argument built by `JSON.stringify(progress)` (line 99), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/agents/uuv.agent.ts:99
- `debug` at line 179 is called with an argument built by `JSON.stringify(descriptionResult)` (line 179), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/agents/uuv.agent.ts:179
- `debug` at line 186 is called with an argument built by `JSON.stringify(result)` (line 186), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mcp-server/src/lib/agents/uuv.agent.ts:186
What to do
- Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped
- `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/assistant/src/helper/highlight/tooltip-helper.js:8
- `completeStyle` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — packages/assistant/src/helper/layer-helper.ts:141
- `layer.toString()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/assistant/src/helper/layer-helper.ts:143
- `dialog.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/assistant/src/service/dialog-service.ts:61
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X4 · Structured logging
- `debug` at line 31 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/services/utils.ts:31
- `debug` at line 33 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/services/utils.ts:33
- `warn` at line 98 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/services/utils.ts:98
- `warn` at line 104 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/services/utils.ts:104
- `debug` at line 25 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/services/architect/architect.service.ts:25
- `debug` at line 20 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:20
- `debug` at line 99 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:99
- `error` at line 103 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:103
- `debug` at line 170 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:170
- `debug` at line 179 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:179
- `debug` at line 186 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/mcp-server/src/lib/agents/uuv.agent.ts:186
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 28/31 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.
- ~3.7 `!` null assertions per 1k TypeScript source lines — 60 assertion(s) across the 16163 source line(s) of the 205 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/a11y/src/lib/model/rule.ts (11), packages/dictionary/src/lib/accessible-role.ts (5), packages/mcp-server/src/lib/agents/uuv.agent.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61.5 | Adequate | Acceptable, with room to improve. |
| Architecture | 72.5 | Adequate — gated by AX8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 74.6 | Strong | Strongest area. |
| Readiness | 35.1 | Weak — gated by R5, R8, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 33.1 | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48.0 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60.0 | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 49 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's Dart imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin 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; this repository's TypeScript 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. Dart isolates share no mutable memory, so no two requests write one object at the same instant. 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 (`npm run dev` in packages/a11y/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> @uuv/a11y@1.0.0-beta.115 dev / > ts-node watch.ts / sh: 1: ts-node: not found / npm error Lifecycle script `dev` failed with error: / npm error code 127 / npm error path <repo>/packages/a11y / npm error workspace @uuv/a11y@1.0.0-beta.115 / npm error location <repo>/packages/a11y / npm error command failed / npm error command sh -c ts-node watch.ts" No runtime evidence was gathered. 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D12 Dependency Hygiene — Dependency currency not established — cache-redirector.jetbrains.com did not answer
- 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 does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication. The rest — .dart (136 lines, 0.9% of production source) — is compared by neither card, so duplication there is unmeasured; it is a corner of this repository, not its product.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
- 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
- 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 — no outbound HTTP usage detected — no HTTP client call or construction in the Dart, JVM, JavaScript/TypeScript, Rust source (service entry point: packages/mcp-server/src/lib/agents/uuv.agent.ts:35 (new Hono())
- P9 Domain vs controller coverage — coverage data present for 74 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 162 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative packages/a11y-dashboard/src/app.vue:10
- <img> without a text alternative packages/assistant/index.html:347
- <img> without a text alternative packages/assistant/index.html:371
- Production project references a test package: @uuv/a11y → @testing-library/dom packages/a11y/REDACTED:43
- Production project references a test package: @uuv/cypress → @testing-library/cypress packages/runner-cypress/REDACTED:52
- Production project references a test package: @uuv/cypress → cypress packages/runner-cypress/REDACTED:57
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label packages/assistant-desktop/src/routes/+page.svelte:273
- <html> without a lang packages/chrome-extension/uuv-devtools-panel.html:1
- Document without a <title> packages/chrome-extension/uuv-devtools-panel.html:1
- Clickable role="button" that no keyboard user can reach packages/assistant/index.html:158
- Clickable element isn't keyboard-operable packages/assistant/src/helper/result-display-helper.ts:6
- aria-hidden hides a focusable element packages/assistant/index.html:329
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@badeball/cypress-cucumber-preprocessor' tests/integration/my-custom-step-definitions.cypress.ts:1
- Unlisted import '@playwright/test' tests/integration/my-custom-step-definitions.playwright.ts:1
- Unlisted import '@ant-design/cssinjs' packages/assistant/src/UuvAssistant.tsx:9
- Unlisted import '@codemirror/language' packages/assistant/src/component/result/UuvAssistantResultCodeEditor.tsx:3
- Unlisted import 'chalk' packages/assistant/launcher/uuv-assistant-launcher.ts:17
- Unlisted import '@testing-library/dom' packages/runner-cypress/src/cucumber/step_definitions/cypress/_.common.ts:21
- Unlisted import 'jquery' packages/runner-cypress/src/cucumber/step_definitions/cypress/a11y-engine.ts:26
- Unlisted import 'rxjs' packages/runner-cypress/src/cucumber/step_definitions/cypress/a11y-engine.ts:24
- Unlisted import '@cucumber/gherkin' packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:2
- Unlisted import '@cucumber/gherkin-utils' packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:3
- Unlisted import '@cucumber/messages' packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:4
- Unlisted import 'minimist' packages/runner-playwright/playwright/run-test-app.ts:3
- Unlisted import 'serve-handler' packages/runner-playwright/playwright/run-test-app.ts:2
- Import cycle (2 files) packages/assistant/src/translator/expect-translator.ts:18
Serious — 303 finding(s)
- No test reaches this file packages/assistant/src/UuvAssistant.tsx:1
- No test reaches this file packages/a11y-dashboard/src/server/plugins/database.ts:1
- No test reaches this file packages/assistant-desktop/src/routes/+page.svelte:1
- No test reaches this file packages/assistant/src/component/result/UuvAssistantResultAIAnalysis.tsx:1
- No test reaches this file packages/a11y-dashboard/src/pages/apps/[[appId]]/usecases/[[usecaseId]]/index.vue:1
- No test reaches this file packages/vscode-extension/src/uuv-vscode-listener.ts:1
- No test reaches this file packages/assistant/src/helper/keyboard-navigation-helper.ts:1
- No test reaches this file packages/vscode-extension/src/helper.ts:1
- No test reaches this file packages/assistant/src/component/UuvAssistantArchitect.tsx:1
- No test reaches this file packages/assistant/src/component/sidebar/UuvAssistantSidebar.tsx:1
- No test reaches this file packages/assistant/src/helper/selection-helper.ts:1
- No test reaches this file packages/vscode-extension/src/test-controller.ts:1
- No test reaches this file packages/assistant/src/component/UuvAssistantSettings.tsx:1
- No test reaches this file packages/assistant/src/helper/css-helper.ts:1
- No test reaches this file packages/mcp-server/src/lib/agents/uuv-agent.eval.ts:1
- No test reaches this file packages/a11y-dashboard/src/server/api/bulk.post.ts:1
- No test reaches this file packages/a11y-dashboard/src/models/index.ts:1
- No test reaches this file packages/assistant/src/component/result/UuvAssistantResultToolbar.tsx:1
- No test reaches this file packages/assistant/bundle-script.js:1
- No test reaches this file packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].get.ts:1
- No test reaches this file packages/runner-playwright/postinstall.js:1
- No test reaches this file packages/assistant/launcher/uuv-assistant-launcher.ts:1
- No test reaches this file packages/runner-playwright/src/lib/watch-test-files.ts:1
- No test reaches this file packages/assistant/src/component/result/UuvAssistantResult.tsx:1
- No test reaches this file packages/runner-cypress/postinstall.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low coverage: packages/a11y/src/lib/engine/engine.ts packages/a11y/src/lib/engine/engine.ts:1
- Low coverage: packages/a11y/src/lib/model/checklist-checker.ts packages/a11y/src/lib/model/checklist-checker.ts:1
- Low coverage: packages/a11y/src/lib/query/accessible-name.query.ts packages/a11y/src/lib/query/accessible-name.query.ts:1
- Low coverage: packages/a11y/src/lib/query/by-role.query.ts packages/a11y/src/lib/query/by-role.query.ts:1
- Low coverage: packages/a11y/src/lib/query/by-sibling.query.ts packages/a11y/src/lib/query/by-sibling.query.ts:1
- Low coverage: packages/a11y/src/lib/query/compliant-attributes/attribut-specification.ts packages/a11y/src/lib/query/compliant-attributes/attribut-specification.ts:1
- Low coverage: packages/a11y/src/lib/query/compliant-attributes/compliant-attributes.query.ts packages/a11y/src/lib/query/compliant-attributes/compliant-attributes.query.ts:1
- Low coverage: packages/a11y/src/lib/query/doctype.query.ts packages/a11y/src/lib/query/doctype.query.ts:1
- Low coverage: packages/a11y/src/lib/query/operators/and-query.ts packages/a11y/src/lib/query/operators/and-query.ts:1
- Low coverage: packages/a11y/src/lib/reference/rgaa/rgaa-checker.ts packages/a11y/src/lib/reference/rgaa/rgaa-checker.ts:1
- Low coverage: packages/a11y/src/lib/reference/wcag/wcag-checker.ts packages/a11y/src/lib/reference/wcag/wcag-checker.ts:1
- Low coverage: packages/a11y/src/lib/reference/wcag/wcag-helper.ts packages/a11y/src/lib/reference/wcag/wcag-helper.ts:1
- Low coverage: packages/assistant/src/helper/highlight/highlight-helper.ts packages/assistant/src/helper/highlight/highlight-helper.ts:1
- Low coverage: packages/assistant/src/helper/highlight/inspector-dom.js packages/assistant/src/helper/highlight/inspector-dom.js:1
- Low coverage: packages/assistant/src/helper/highlight/tooltip-helper.js packages/assistant/src/helper/highlight/tooltip-helper.js:1
- Low coverage: packages/assistant/src/helper/informative-nodes-helper.ts packages/assistant/src/helper/informative-nodes-helper.ts:1
- Low coverage: packages/assistant/src/helper/layer-helper.ts packages/assistant/src/helper/layer-helper.ts:1
- Low coverage: packages/assistant/src/helper/result-script-helper.ts packages/assistant/src/helper/result-script-helper.ts:1
- Low coverage: packages/assistant/src/service/abstract-component-service.ts packages/assistant/src/service/abstract-component-service.ts:1
- Low coverage: packages/assistant/src/service/architect-service.ts packages/assistant/src/service/architect-service.ts:1
- Low coverage: packages/assistant/src/service/dialog-service.ts packages/assistant/src/service/dialog-service.ts:1
- Low coverage: packages/assistant/src/service/form-completion-service.ts packages/assistant/src/service/form-completion-service.ts:1
- Low coverage: packages/assistant/src/service/table-and-grid-service.ts packages/assistant/src/service/table-and-grid-service.ts:1
- Low coverage: packages/runner-playwright/src/reporter/uuv-custom-formatter.ts packages/runner-playwright/src/reporter/uuv-custom-formatter.ts:1
- Low coverage: packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Wholesale file copy (61 identical lines × 2 files) packages/a11y/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/a11y/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/a11y/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/a11y/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/dictionary/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/dictionary/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/dictionary/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/mcp-server/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/mcp-server/.eslintrc.js:1
- Wholesale file copy (61 identical lines × 2 files) packages/runner-commons/.eslintrc.js:1
- TodoComment packages/runner-playwright/src/lib/uuv-cli.spec.ts:129
- TodoComment packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:102
- TodoComment packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:362
- TodoComment packages/mcp-server/src/lib/mcp-server-factory.ts:420
- TodoComment packages/mcp-server/src/lib/services/prompt-retriever.service.ts:91
- TodoComment packages/a11y/src/lib/query/form.query.ts:79
- FunctionTooLong: UuvAssistant.UuvAssistant packages/assistant/src/UuvAssistant.tsx:46
- FunctionTooLong: mcp-server-factory.createUUVServer packages/mcp-server/src/lib/mcp-server-factory.ts:57
- FunctionTooLong: index.Home packages/docs/src/pages/index.tsx:91
- FunctionTooLong: generate-step-definitions-documentation.runGenerateDoc packages/runner-commons/src/step-definition-generator/generate-step-definitions-documentation.ts:25
- FunctionTooLong: database.default packages/a11y-dashboard/src/server/plugins/database.ts:3
- FunctionTooLong: inspector-dom.Inspector packages/assistant/src/helper/highlight/inspector-dom.js:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- This package's lint script runs in no CI job packages/assistant/REDACTED:47
- This package's lint script runs in no CI job packages/dictionary/REDACTED:37
- This package's lint script runs in no CI job packages/mcp-server/REDACTED:47
- This package's lint script runs in no CI job packages/runner-commons/REDACTED:37
- This package's lint script runs in no CI job packages/runner-cypress/REDACTED:47
- This package's lint script runs in no CI job packages/vscode-extension/REDACTED:79
- Wholesale file copy (60 identical lines × 2 files) packages/a11y/.eslintrc.js:1
- Wholesale file copy (60 identical lines × 2 files) packages/assistant/.eslintrc.js:1
- Wholesale file copy (60 identical lines × 2 files) packages/assistant/.eslintrc.js:1
- Wholesale file copy (60 identical lines × 2 files) packages/assistant/.eslintrc.js:1
- Wholesale file copy (60 identical lines × 2 files) packages/assistant/.eslintrc.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2 locations) packages/a11y/src/lib/reference/rgaa/rules/1-image.ts:121
- Duplicated block (13 lines × 2 locations) packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:208
- Duplicated block (13 lines × 2 locations) packages/assistant/src/translator/click-translator.ts:22
- Duplicated block (13 lines × 2 locations) packages/runner-cypress/postinstall.js:19
- Untrusted text written into markup unescaped packages/assistant/src/helper/highlight/tooltip-helper.js:8
- Untrusted text written into markup unescaped packages/assistant/src/helper/layer-helper.ts:141
- Untrusted text written into markup unescaped packages/assistant/src/helper/layer-helper.ts:143
- Untrusted text written into markup unescaped packages/assistant/src/service/dialog-service.ts:61
- Focus outline removed in CSS without a :focus replacement packages/assistant-desktop/src/routes/+page.svelte:349
- Focus outline removed in CSS without a :focus replacement packages/assistant-desktop/src/routes/+page.svelte:457
- Focus outline removed in CSS without a :focus replacement packages/assistant-desktop/src/routes/+page.svelte:644
- Animation without a prefers-reduced-motion guard packages/docs/src/pages/index.module.css:120
- Animation without a prefers-reduced-motion guard packages/assistant-desktop/src/routes/+page.svelte:559
- Animation without a prefers-reduced-motion guard packages/assistant-desktop/src/routes/+page.svelte:571
- FixmeComment packages/runner-playwright/src/reporter/uuv-custom-formatter.ts:3
- FixmeComment packages/assistant/src/helper/informative-nodes-helper.ts:57
- FixmeComment packages/a11y/tests/checker/6-link/link-checker.spec.ts:115
- Sync-over-async blocking packages/mcp-server/src/lib/services/expect.service.ts:49
- Sync-over-async blocking packages/runner-cypress/src/lib/runner-cypress.ts:74
- Sync-over-async blocking packages/runner-cypress/src/lib/runner-cypress.ts:75
- Boundary violation [package:third-party-deep-import] packages/a11y/src/lib/query/by-tag.query.ts:3
- Boundary violation [package:third-party-deep-import] packages/a11y/src/lib/query/compliant-attributes/attribut-specification.ts:3
- Boundary violation [package:third-party-deep-import] packages/assistant/src/service/helper-service.tsx:15
- Dead file (~31 LoC) packages/a11y-dashboard/src/pages/apps/[[appId]]/index.vue
- Dead file (~31 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].delete.ts
- Dead file (~31 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results/[resultId].get.ts
- Dead file (~5 LoC) packages/a11y-dashboard/src/middleware/app-details.ts
- Dead file (~5 LoC) packages/a11y-dashboard/src/plugins/vue-masonry.ts
- Dead file (~5 LoC) packages/a11y-dashboard/src/utils/filterIssuesByType.ts
- Hotspot: packages/assistant/src/UuvAssistant.tsx packages/assistant/src/UuvAssistant.tsx:46
- Hotspot: packages/mcp-server/src/lib/agents/uuv.agent.ts packages/mcp-server/src/lib/agents/uuv.agent.ts:28
- REDACTED
- REDACTED
- ClassTooLong: UuvAssistant packages/assistant/src/UuvAssistant.tsx:1
- ClassTooLong: UuvPlaywrightReporterHelper packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:49
- Off the main sequence: @uuv/a11y
- Off the main sequence: @uuv/dictionary
- Fake-async — async method never awaits packages/runner-cypress/src/lib/uuv-cli.ts:20
- Fake-async — async method never awaits packages/runner-playwright/src/lib/uuv-cli.ts:20
- Duplicated block (19 lines × 2 locations) packages/a11y/src/lib/model/rule.ts:17
- Duplicated block (19 lines × 2 locations) packages/mcp-server/src/lib/mcp-server-factory.ts:454
- Duplicated block (17 lines × 2 locations) packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:26
- Duplicated block (17 lines × 2 locations) packages/a11y/src/lib/reference/rgaa/rules/5-table.ts:172
- Duplicated block (15 lines × 3 locations) packages/a11y-dashboard/src/server/api/apps/[appId].get.ts:28
- Duplicated block (15 lines × 3 locations) packages/assistant/src/UuvAssistant.tsx:582
- Duplicated block with local edits (13 matched lines × 2 locations) packages/a11y-dashboard/src/server/api/apps.post.ts:1
- Duplicated block with local edits (13 matched lines × 2 locations) packages/assistant/launcher/uuv-assistant-launcher.ts:22
- Dead file (~43 LoC) packages/a11y-dashboard/src/server/api/apps/[appId].get.ts
- Dead file (~43 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results.post.ts
- Dead file (~36 LoC) packages/a11y-dashboard/src/server/api/apps.get.ts
- Dead file (~36 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases.get.ts
- Dead file (~26 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results.get.ts
- Dead file (~26 LoC) packages/runner-cypress/test.js
- Dead file (~14 LoC) packages/a11y-dashboard/src/components/CardWithCounter.vue
- Dead file (~14 LoC) packages/a11y-dashboard/src/utils/getThemeFromResultCount.ts
- Dead file (~10 LoC) packages/a11y-dashboard/src/components/Breadcrumb.vue
- Dead file (~10 LoC) packages/a11y-dashboard/src/utils/computeCounter.ts
- Dead file (~2 LoC) packages/a11y-dashboard/src/app.vue
- Dead file (~2 LoC) packages/runner-cypress/target-config/command.ts
- Unused dependency 'tslib' packages/a11y/REDACTED:61
- Unused dependency 'tslib' packages/dictionary/REDACTED:41
- Async function without AbortSignal: onDescriptionSelected packages/assistant/src/UuvAssistant.tsx:365
- Async function without AbortSignal: generateNominalCase packages/assistant/src/service/architect-service.ts:23
- Low contrast colour pair in CSS (2.8:1) packages/assistant-desktop/src/routes/+page.svelte:658
- No authorization packages/mcp-server/src/lib/agents/uuv.agent.ts:35
- UuvAssistant.UuvAssistant (cyclomatic 34) packages/assistant/src/UuvAssistant.tsx:46
- BySiblingQuery.computeResult (cyclomatic 19) packages/a11y/src/lib/query/by-sibling.query.ts:32
- generate-step-definitions-documentation.runGenerateDoc (cyclomatic 19) packages/runner-commons/src/step-definition-generator/generate-step-definitions-documentation.ts:25
- UuvAgent.start (cyclomatic 17) packages/mcp-server/src/lib/agents/uuv.agent.ts:28
- InformativeNodesHelper.findRelevantAccessibilityParent (cyclomatic 16) packages/assistant/src/helper/informative-nodes-helper.ts:74
- BySiblingQuery.computeResult (cognitive 30) packages/a11y/src/lib/query/by-sibling.query.ts:32
- InformativeNodesHelper.findRelevantAccessibilityParent (cognitive 22) packages/assistant/src/helper/informative-nodes-helper.ts:74
- UuvAssistant.UuvAssistant::callUnifiedAIForImage (cognitive 21) packages/assistant/src/UuvAssistant.tsx:256
- ArchitectExplorerHelper.parseAriaLine (cognitive 20) packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:185
- UuvCustomFormatter.buildAndAddScenario (cognitive 20) packages/runner-playwright/src/reporter/uuv-custom-formatter.ts:54
- Engine.getSelector (cognitive 17) packages/a11y/src/lib/engine/engine.ts:108
- Translator.getSelector (cognitive 17) packages/assistant/src/translator/abstract-translator.ts:66
- UuvAgent.start (cognitive 16) packages/mcp-server/src/lib/agents/uuv.agent.ts:28
- TooManyMethods: UuvPlaywrightReporterHelper packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:49
- FileTooLong: src/UuvAssistant.tsx packages/assistant/src/UuvAssistant.tsx
- REDACTED
- REDACTED
- Low cohesion: UuvPlaywrightReporterHelper (LCOM4 4) packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:49
- Unfinished stub — throws a "not implemented" error packages/mcp-server/src/lib/services/element/type-element.service.ts:20
- Unfinished stub — throws a "not implemented" exception packages/mcp-server/src/lib/services/element/type-element.service.ts:20
- Schema created by Sequelize sync() (no migration path) packages/a11y-dashboard/src/server/plugins/database.ts:222
- Duplication concentrated across 8 sibling directories (24 clone groups) packages/assistant/.eslintrc.js:1
- Wholesale file copy (62 identical lines × 2 files) packages/assistant/.eslintrc.js:1
- Duplicated block (34 lines × 5 locations) packages/a11y/.eslintrc.js:67
- Duplicated block (31 lines × 2 locations) packages/a11y-dashboard/src/server/api/apps/[appId].delete.ts:3
- Duplicated block (30 lines × 2 locations) packages/a11y/src/lib/engine/engine.ts:108
- Duplicated block (26 lines × 2 locations) packages/mcp-server/src/lib/services/image/describer/image-describer.service.ts:54
- Duplicated block (23 lines × 2 locations) packages/mcp-server/src/lib/mcp-server-factory.ts:145
- Duplicated block with local edits (20 matched lines × 2 locations) packages/runner-commons/src/step-definition-generator/generate-base-step-definitions.ts:17
- Duplicated block (18 lines × 2 locations) packages/assistant/src/component/UuvAssistantSettings.tsx:37
- Duplicated block with local edits (16 matched lines × 2 locations) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].delete.ts:5
- Duplicated block (16 lines × 2 locations) packages/assistant/src/translator/type-translator.ts:39
- Duplicated block (15 lines × 2 locations) packages/assistant/src/UuvAssistant.tsx:523
- Duplicated block with local edits (14 matched lines × 2 locations) packages/dictionary/src/lib/web/en/en-roles.ts:39
- Complex function (anonymous) (cyclomatic 19, cognitive 32) packages/a11y/src/lib/query/by-sibling.query.ts:35
- Complex function findRelevantAccessibilityParent (cyclomatic 16, cognitive 22) packages/assistant/src/helper/informative-nodes-helper.ts:74
- Complex function parseAriaLine (cyclomatic 12, cognitive 23) packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:185
- Complex function buildAndAddScenario (cyclomatic 12, cognitive 20) packages/runner-playwright/src/reporter/uuv-custom-formatter.ts:54
- Complex function getMockedDataForAccessibleRole (cyclomatic 12, cognitive 13) packages/assistant/src/translator/type-translator.ts:126
- Complex function (anonymous) (cyclomatic 11, cognitive 10) packages/dictionary/src/lib/dictionary.ts:51
- packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts: 692 lines of code packages/runner-playwright/src/cucumber/step_definitions/playwright/base-check-engine.ts:1
- packages/assistant/src/UuvAssistant.tsx: 668 lines of code packages/assistant/src/UuvAssistant.tsx:1
- packages/assistant-desktop/src/routes/+page.svelte: 631 lines of code packages/assistant-desktop/src/routes/+page.svelte:1
- packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts: 618 lines of code packages/runner-playwright/src/reporter/uuv-playwright-reporter-helper.ts:1
- packages/dictionary/src/lib/web/fr/fr-roles.ts: 594 lines of code packages/dictionary/src/lib/web/fr/fr-roles.ts:1
- packages/runner-playwright/src/cucumber/step_definitions/playwright/core-engine.ts: 590 lines of code packages/runner-playwright/src/cucumber/step_definitions/playwright/core-engine.ts:1
- packages/mcp-server/src/lib/mcp-server-factory.ts: 472 lines of code packages/mcp-server/src/lib/mcp-server-factory.ts:1
- This test file cannot be loaded packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts:15
- Dependency Freshness
- The declared test suite includes a file that cannot be loaded packages/runner-cypress/src/cucumber/step_definitions/cypress/based-role-check-engine.ts:15
- Dead file (~236 LoC) packages/a11y-dashboard/src/server/plugins/database.ts
- Dead file (~131 LoC) packages/a11y-dashboard/src/pages/apps/[[appId]]/usecases/[[usecaseId]]/index.vue
- Dead file (~93 LoC) packages/mcp-server/src/lib/agents/uuv-agent.eval.ts
- Dead file (~77 LoC) packages/a11y-dashboard/src/server/api/bulk.post.ts
- Dead file (~71 LoC) packages/a11y-dashboard/src/models/index.ts
- Dead file (~55 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId].get.ts
- Dead file (~51 LoC) packages/runner-playwright/src/lib/watch-test-files.ts
- Dead file (~46 LoC) packages/mcp-server/src/lib/services/architect/architect.try.ts
- Dead file (~45 LoC) packages/a11y-dashboard/src/components/BulkImporter.vue
- Dead file (~44 LoC) packages/a11y-dashboard/src/server/api/apps/[appId].delete.ts
- Dead file (~39 LoC) packages/a11y-dashboard/src/pages/index.vue
- Dead file (~25 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases/[usecaseId]/results/[resultId].delete.ts
- Dead file (~23 LoC) packages/a11y-dashboard/src/server/api/apps/[appId]/usecases.post.ts
- Dead file (~21 LoC) packages/runner-commons/src/cli/start-ipc-server.ts
- Dead file (~19 LoC) packages/a11y-dashboard/src/server/api/apps.post.ts
- Dead file (~18 LoC) packages/a11y-dashboard/src/components/ResultDetails.vue
- Dead file (~12 LoC) packages/a11y-dashboard/src/utils/createTooltips.ts
- Dead file (~7 LoC) packages/a11y-dashboard/src/middleware/usecase-details.ts
- Dead file (~6 LoC) packages/a11y-dashboard/src/utils/toFormattedDate.ts
- Dead file (~4 LoC) packages/mcp-server/src/lib/agents/uuv-agent.runner.ts
- Dead file (~3 LoC) packages/a11y-dashboard/src/middleware/app-list.ts
- Unused dependency '@jnxplus/nx-gradle' REDACTED:43
- Unused dependency '@nx/nuxt' REDACTED:50
- Unused dependency '@nxrocks/nx-flutter' REDACTED:53
- Unused dependency '@nuxt/devtools' REDACTED:47
- Unused dependency '@nuxt/kit' REDACTED:49
- Unused dependency '@nuxt/ui-templates' REDACTED:50
- Unused dependency '@swc-node/register' REDACTED:52
- Unused dependency '@vue/test-utils' REDACTED:60
- Unused dependency 'consola' REDACTED:61
- Unused dependency 'vue-tsc' REDACTED:69
- Unused dependency '@tauri-apps/plugin-opener' packages/assistant-desktop/REDACTED:20
- Unused dependency '@langchain/mcp-adapters' packages/mcp-server/REDACTED:67
- Unused dependency '@opentelemetry/context-async-hooks' packages/mcp-server/REDACTED:71
- Unused dependency '@opentelemetry/sdk-node' packages/mcp-server/REDACTED:72
- Unused dependency '@vscode/test-electron' packages/vscode-extension/REDACTED:89
- Third-party script without Subresource Integrity packages/assistant/index.html:64
Minor — 78 finding(s)
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called without args packages/runner-cypress/src/lib/uuv-cli.spec.ts:123
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with targetUrl packages/runner-cypress/src/lib/uuv-cli.spec.ts:162
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with generateHtmlReport option packages/runner-cypress/src/lib/uuv-cli.spec.ts:204
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with generateJunitReport option packages/runner-cypress/src/lib/uuv-cli.spec.ts:243
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with generateA11yReport option packages/runner-cypress/src/lib/uuv-cli.spec.ts:286
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with browser option packages/runner-cypress/src/lib/uuv-cli.spec.ts:325
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with targetTestFile option packages/runner-cypress/src/lib/uuv-cli.spec.ts:365
- Mock-dominated test: should execute e2e run cypress when uuv e2e is called with extraArgs option packages/runner-cypress/src/lib/uuv-cli.spec.ts:406
- Mock-dominated test: runGenerate Base - les attributs sont bien alimentés packages/runner-commons/src/tests/generate-base-spec-definitions.spec.ts:44
- Mock-dominated test: generateWordingFiles - le fichier doit être généré packages/runner-commons/src/tests/generate-base-spec-definitions.spec.ts:71
- Mock-dominated test: runGenerate byRole - les attributs sont bien alimentés packages/runner-commons/src/tests/generate-based-role-spec-definitions.spec.ts:39
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/services/utils.ts:31
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/services/utils.ts:33
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/services/utils.ts:98
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/services/utils.ts:104
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/services/architect/architect.service.ts:25
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:20
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:99
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:103
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:170
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:179
- Interpolated log message defeats structured logging packages/mcp-server/src/lib/agents/uuv.agent.ts:186
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:72
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.helper.ts:74
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:84
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:87
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:92
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/services/architect/explorer/architect-explorer.service.ts:98
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/agents/uuv.agent.ts:99
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/agents/uuv.agent.ts:179
- Diagnostic log message is built whether or not it is wanted packages/mcp-server/src/lib/agents/uuv.agent.ts:186
- redundant comment packages/a11y-dashboard/src/server/api/bulk.post.ts:23
- redundant comment packages/docs/src/components/Button/index.tsx:56
- redundant comment packages/mcp-server/src/lib/services/prompt-retriever.service.spec.ts:21
- redundant comment packages/mcp-server/src/lib/services/prompt-retriever.service.spec.ts:37
- redundant comment packages/mcp-server/src/lib/services/prompt-retriever.service.spec.ts:106
- redundant comment packages/mcp-server/src/lib/services/prompt-retriever.service.spec.ts:114
- redundant comment packages/vscode-extension/src/test-controller.ts:27
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example packages/assistant-desktop/README.md:1
- Documentation: no build, run or usage example packages/runner-commons/README.md:1
- Documentation: no build, run or usage example packages/vscode-extension/README.md:1
- REDACTED
- REDACTED
- REDACTED
- Placeholder literal left in code packages/assistant/src/translator/type-translator.ts:147
- Placeholder literal left in code packages/assistant/src/translator/type-translator.ts:167
- Duplicated predicate packages/assistant/src/translator/abstract-translator.ts:32
- Duplicated predicate packages/a11y/src/lib/engine/engine.ts:124
- No ADRs found packages/runner-playwright/REDACTED:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Tests reach code only in some runs: packages/runner-cypress/src/lib/runner-cypress.ts packages/runner-cypress/src/lib/runner-cypress.ts:110
- No ADRs
- README/code drift packages/mcp-server/README.md:67
- Logging is not universal
- No SAST REDACTED:6
- Test-only dependency '@bahmutov/cypress-esbuild-preprocessor' in production deps packages/runner-cypress/REDACTED:51
- Test-only dependency 'chai-subset' in production deps packages/runner-cypress/REDACTED:56
- Test-only dependency 'cypress-on-fix' in production deps packages/runner-cypress/REDACTED:58
- Test-only dependency 'cypress-real-events' in production deps packages/runner-cypress/REDACTED:59
- Test-only dependency 'dom-accessibility-api' in production deps packages/runner-cypress/REDACTED:60
- Test-only dependency 'lodash' in production deps packages/runner-cypress/REDACTED:63
- Test-only dependency '@cucumber/cucumber' in production deps packages/runner-playwright/REDACTED:49
- Test-only dependency 'axe-core' in production deps packages/runner-playwright/REDACTED:54
- Test-only dependency 'axe-playwright' in production deps packages/runner-playwright/REDACTED:55
- No app-layer HTTPS enforcement detected packages/mcp-server/src/lib/agents/uuv.agent.ts:162
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 3 finding(s)
- doc comments repeat the names packages/a11y/src/lib/model/reference.ts:16
- doc comments repeat the names packages/assistant/src/service/architect-service.ts:20
- doc comments repeat the names packages/runner-commons/src/cli/runner.ts:15
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-82f53cba3cdd466687b868ad8e6e998e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-82f53cba3cdd466687b868ad8e6e998e/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=2069" --report-format json --report-path /tmp/watchdog-gitleaks-82f53cba3cdd466687b868ad8e6e998e/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-82f53cba3cdd466687b868ad8e6e998e/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 80 | 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/** . | 113 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `packages/runner-playwright/src/cucumber/step_definitions/playwright/based-role-check-engine.ts`, `packages/runner-playwright/src/cucumber/step_definitions/playwright/index.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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/** . | 1 | artifacts/raw/trivy-fs.json |