Public report of oraios/serena, published 20 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 20 October 2026, 17:39 UTC · Survey ID cd_b1d6f4e8cdc84c249956b9c3e15cc026
oraios/serena
Measured 20 October 2026, 17:11 UTC, at code version abb0a0f
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
CAI scoreAt riskDown 7 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 57,529 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Maturity, 41
Findings by how serious they are
80 critical332 serious96 minor
32 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
20 October 2026, 17:11 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
50of 53 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
500of 508 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
53dimensions across 7 lenses, read from 57,529 lines of product code in 4 projects.
oraios/serena scores 53 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Maturity, which scores 41 and is rated Weak. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to reconcile the README with reality: README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features; The README describes a new REPL-based agent interface, but there is no such feature in the evidence; docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist; docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist; docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist and to record your significant design decisions, and if Maturity rose to 70, the score would rise from 53 to about 62.
80 findings are critical: 65 in Static Analysis (SAST), six in Dependency Vulnerabilities, five in IaC & Container Security and four in Keyboard semantics.
Watchdog couldn't measure 31 dimensions in this code, among them Dependency Hygiene, Internal API Consistency and Navigability, so they are left out of the score. The product code is 57,529 lines, which would take an estimated 0.7 person-years, around €95,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Visual & motion safety · Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 12 findings
These 12 critical or serious findings were in the previous survey, on 4 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: PYSEC-2026-2132 REDACTED
Rebuild cost: about €95,000 · Estimate
Cost to rebuild
€32,000 to €160,000, for 528 to 1,675 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 57,529 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Reconcile the README with reality: README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features; The README describes a new REPL-based agent interface, but there is no such feature in the evidence; docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist; docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist; docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist.
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €95,000 to build again, about 0.7 person-years of work. Its weakest lens is Maturity, at 41 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Reconcile the README with reality: README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features; The README describes a new REPL-based agent interface, but there is no such feature in the evidence; docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist; docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist; docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
235 modules, with 466 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 195 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
serena.language_backend uses serena.util.file_proxy, so a change to serena.util.file_proxy can break serena.language_backend, while a change to serena.language_backend can't break serena.util.file_proxy.
Position
Below the diagonal: serena.language_backend uses a module listed above it, which is the healthy direction.
solidlsp.dependency_provider uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.dependency_provider, while a change to solidlsp.dependency_provider can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.dependency_provider uses a module listed above it, which is the healthy direction.
solidlsp.ls_types uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.ls_types, while a change to solidlsp.ls_types can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.ls_types uses a module listed above it, which is the healthy direction.
solidlsp.lsp_protocol_handler.server uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.lsp_protocol_handler.server, while a change to solidlsp.lsp_protocol_handler.server can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.lsp_protocol_handler.server uses a module listed above it, which is the healthy direction.
serena.config.serena_config uses solidlsp.ls_config, so a change to solidlsp.ls_config can break serena.config.serena_config, while a change to serena.config.serena_config can't break solidlsp.ls_config.
Position
Below the diagonal: serena.config.serena_config uses a module listed above it, which is the healthy direction.
serena.config.serena_config uses serena.language_backend, so a change to serena.language_backend can break serena.config.serena_config, while a change to serena.config.serena_config can't break serena.language_backend.
Position
Below the diagonal: serena.config.serena_config uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
solidlsp.ls uses solidlsp.lsp_protocol_handler.server, so a change to solidlsp.lsp_protocol_handler.server can break solidlsp.ls, while a change to solidlsp.ls can't break solidlsp.lsp_protocol_handler.server.
Position
Below the diagonal: solidlsp.ls uses a module listed above it, which is the healthy direction.
serena.ls_manager uses solidlsp.ls_config, so a change to solidlsp.ls_config can break serena.ls_manager, while a change to serena.ls_manager can't break solidlsp.ls_config.
Position
Below the diagonal: serena.ls_manager uses a module listed above it, which is the healthy direction.
serena.ls_manager uses serena.config.serena_config, so a change to serena.config.serena_config can break serena.ls_manager, while a change to serena.ls_manager can't break serena.config.serena_config.
Position
Below the diagonal: serena.ls_manager uses a module listed above it, which is the healthy direction.
serena.ls_manager uses solidlsp.ls, so a change to solidlsp.ls can break serena.ls_manager, while a change to serena.ls_manager can't break solidlsp.ls.
Position
Below the diagonal: serena.ls_manager uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.ada_language_server uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.ada_language_server, while a change to solidlsp.language_servers.ada_language_server can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.ada_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.ada_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.ada_language_server, while a change to solidlsp.language_servers.ada_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.ada_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.ada_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.ada_language_server, while a change to solidlsp.language_servers.ada_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.ada_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.ada_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.ada_language_server, while a change to solidlsp.language_servers.ada_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.ada_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.ada_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.ada_language_server, while a change to solidlsp.language_servers.ada_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.ada_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clangd_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.clangd_language_server, while a change to solidlsp.language_servers.clangd_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.clangd_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clangd_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.clangd_language_server, while a change to solidlsp.language_servers.clangd_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.clangd_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clangd_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.clangd_language_server, while a change to solidlsp.language_servers.clangd_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.clangd_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clangd_language_server uses solidlsp.lsp_protocol_handler.server, so a change to solidlsp.lsp_protocol_handler.server can break solidlsp.language_servers.clangd_language_server, while a change to solidlsp.language_servers.clangd_language_server can't break solidlsp.lsp_protocol_handler.server.
Position
Below the diagonal: solidlsp.language_servers.clangd_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clangd_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.clangd_language_server, while a change to solidlsp.language_servers.clangd_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.clangd_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clojure_lsp uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.clojure_lsp, while a change to solidlsp.language_servers.clojure_lsp can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.clojure_lsp uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clojure_lsp uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.clojure_lsp, while a change to solidlsp.language_servers.clojure_lsp can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.clojure_lsp uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clojure_lsp uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.clojure_lsp, while a change to solidlsp.language_servers.clojure_lsp can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.clojure_lsp uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clojure_lsp uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.clojure_lsp, while a change to solidlsp.language_servers.clojure_lsp can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.clojure_lsp uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.clojure_lsp uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.clojure_lsp, while a change to solidlsp.language_servers.clojure_lsp can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.clojure_lsp uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.csharp_language_server uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.csharp_language_server, while a change to solidlsp.language_servers.csharp_language_server can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.csharp_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.csharp_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.csharp_language_server, while a change to solidlsp.language_servers.csharp_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.csharp_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.csharp_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.csharp_language_server, while a change to solidlsp.language_servers.csharp_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.csharp_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.csharp_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.csharp_language_server, while a change to solidlsp.language_servers.csharp_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.csharp_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.csharp_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.csharp_language_server, while a change to solidlsp.language_servers.csharp_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.csharp_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.cue_language_server uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.cue_language_server, while a change to solidlsp.language_servers.cue_language_server can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.cue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.cue_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.cue_language_server, while a change to solidlsp.language_servers.cue_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.cue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.cue_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.cue_language_server, while a change to solidlsp.language_servers.cue_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.cue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.cue_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.cue_language_server, while a change to solidlsp.language_servers.cue_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.cue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.cue_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.cue_language_server, while a change to solidlsp.language_servers.cue_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.cue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.devsense_php_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.devsense_php_language_server, while a change to solidlsp.language_servers.devsense_php_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.devsense_php_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.devsense_php_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.devsense_php_language_server, while a change to solidlsp.language_servers.devsense_php_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.devsense_php_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.devsense_php_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.devsense_php_language_server, while a change to solidlsp.language_servers.devsense_php_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.devsense_php_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.devsense_php_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.devsense_php_language_server, while a change to solidlsp.language_servers.devsense_php_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.devsense_php_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.emmylua_ls uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.emmylua_ls, while a change to solidlsp.language_servers.emmylua_ls can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.emmylua_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.emmylua_ls uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.emmylua_ls, while a change to solidlsp.language_servers.emmylua_ls can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.emmylua_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.emmylua_ls uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.emmylua_ls, while a change to solidlsp.language_servers.emmylua_ls can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.emmylua_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.emmylua_ls uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.emmylua_ls, while a change to solidlsp.language_servers.emmylua_ls can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.emmylua_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.erlang_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.erlang_language_server, while a change to solidlsp.language_servers.erlang_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.erlang_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.erlang_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.erlang_language_server, while a change to solidlsp.language_servers.erlang_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.erlang_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.erlang_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.erlang_language_server, while a change to solidlsp.language_servers.erlang_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.erlang_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.erlang_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.erlang_language_server, while a change to solidlsp.language_servers.erlang_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.erlang_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.fortran_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.fortran_language_server, while a change to solidlsp.language_servers.fortran_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.fortran_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.fortran_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.fortran_language_server, while a change to solidlsp.language_servers.fortran_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.fortran_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.fortran_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.fortran_language_server, while a change to solidlsp.language_servers.fortran_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.fortran_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.fortran_language_server uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.fortran_language_server, while a change to solidlsp.language_servers.fortran_language_server can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.fortran_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.fortran_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.fortran_language_server, while a change to solidlsp.language_servers.fortran_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.fortran_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.intelephense uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.intelephense, while a change to solidlsp.language_servers.intelephense can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.intelephense uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.intelephense uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.language_servers.intelephense, while a change to solidlsp.language_servers.intelephense can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.language_servers.intelephense uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.intelephense uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.intelephense, while a change to solidlsp.language_servers.intelephense can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.intelephense uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.intelephense uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.intelephense, while a change to solidlsp.language_servers.intelephense can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.intelephense uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.intelephense uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.intelephense, while a change to solidlsp.language_servers.intelephense can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.intelephense uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.kotlin_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.kotlin_language_server, while a change to solidlsp.language_servers.kotlin_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.kotlin_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.kotlin_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.kotlin_language_server, while a change to solidlsp.language_servers.kotlin_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.kotlin_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.kotlin_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.kotlin_language_server, while a change to solidlsp.language_servers.kotlin_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.kotlin_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.kotlin_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.kotlin_language_server, while a change to solidlsp.language_servers.kotlin_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.kotlin_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.marksman uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.marksman, while a change to solidlsp.language_servers.marksman can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.marksman uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.marksman uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.marksman, while a change to solidlsp.language_servers.marksman can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.marksman uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.marksman uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.marksman, while a change to solidlsp.language_servers.marksman can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.marksman uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.marksman uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.marksman, while a change to solidlsp.language_servers.marksman can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.marksman uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.marksman uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.marksman, while a change to solidlsp.language_servers.marksman can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.marksman uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.nixd_ls uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.nixd_ls, while a change to solidlsp.language_servers.nixd_ls can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.nixd_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.nixd_ls uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.nixd_ls, while a change to solidlsp.language_servers.nixd_ls can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.nixd_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.nixd_ls uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.nixd_ls, while a change to solidlsp.language_servers.nixd_ls can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.nixd_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.nixd_ls uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.nixd_ls, while a change to solidlsp.language_servers.nixd_ls can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.nixd_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.nixd_ls uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.nixd_ls, while a change to solidlsp.language_servers.nixd_ls can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.nixd_ls uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.phpantom uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.phpantom, while a change to solidlsp.language_servers.phpantom can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.phpantom uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.phpantom uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.language_servers.phpantom, while a change to solidlsp.language_servers.phpantom can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.language_servers.phpantom uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.phpantom uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.phpantom, while a change to solidlsp.language_servers.phpantom can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.phpantom uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.phpantom uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.phpantom, while a change to solidlsp.language_servers.phpantom can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.phpantom uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.phpantom uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.phpantom, while a change to solidlsp.language_servers.phpantom can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.phpantom uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.typescript_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.typescript_language_server, while a change to solidlsp.language_servers.typescript_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.typescript_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vbnet_language_server uses solidlsp.language_servers.common, so a change to solidlsp.language_servers.common can break solidlsp.language_servers.vbnet_language_server, while a change to solidlsp.language_servers.vbnet_language_server can't break solidlsp.language_servers.common.
Position
Below the diagonal: solidlsp.language_servers.vbnet_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vbnet_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.vbnet_language_server, while a change to solidlsp.language_servers.vbnet_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.vbnet_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vbnet_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.vbnet_language_server, while a change to solidlsp.language_servers.vbnet_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.vbnet_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vbnet_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.vbnet_language_server, while a change to solidlsp.language_servers.vbnet_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.vbnet_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vbnet_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.vbnet_language_server, while a change to solidlsp.language_servers.vbnet_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.vbnet_language_server uses a module listed above it, which is the healthy direction.
serena.project uses serena.util.file_proxy, so a change to serena.util.file_proxy can break serena.project, while a change to serena.project can't break serena.util.file_proxy.
Position
Below the diagonal: serena.project uses a module listed above it, which is the healthy direction.
serena.project uses solidlsp.ls_config, so a change to solidlsp.ls_config can break serena.project, while a change to serena.project can't break solidlsp.ls_config.
Position
Below the diagonal: serena.project uses a module listed above it, which is the healthy direction.
serena.project uses serena.language_backend, so a change to serena.language_backend can break serena.project, while a change to serena.project can't break serena.language_backend.
Position
Below the diagonal: serena.project uses a module listed above it, which is the healthy direction.
serena.project uses serena.config.serena_config, so a change to serena.config.serena_config can break serena.project, while a change to serena.project can't break serena.config.serena_config.
Position
Below the diagonal: serena.project uses a module listed above it, which is the healthy direction.
serena.project uses serena.ls_manager, so a change to serena.ls_manager can break serena.project, while a change to serena.project can't break serena.ls_manager.
Position
Below the diagonal: serena.project uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.angular_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.angular_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.angular_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.angular_language_server uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.angular_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in solidlsp.language_servers.angular_language_server uses a type in solidlsp.language_servers.typescript_language_server.
solidlsp.language_servers.angular_language_server uses solidlsp.language_servers.typescript_language_server, so a change to solidlsp.language_servers.typescript_language_server can break solidlsp.language_servers.angular_language_server, while a change to solidlsp.language_servers.angular_language_server can't break solidlsp.language_servers.typescript_language_server.
Position
Below the diagonal: solidlsp.language_servers.angular_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.astro_language_server uses solidlsp.language_servers.typescript_language_server, so a change to solidlsp.language_servers.typescript_language_server can break solidlsp.language_servers.astro_language_server, while a change to solidlsp.language_servers.astro_language_server can't break solidlsp.language_servers.typescript_language_server.
Position
Below the diagonal: solidlsp.language_servers.astro_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.svelte_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.svelte_language_server, while a change to solidlsp.language_servers.svelte_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.svelte_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.svelte_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.svelte_language_server, while a change to solidlsp.language_servers.svelte_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.svelte_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.svelte_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.svelte_language_server, while a change to solidlsp.language_servers.svelte_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.svelte_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.svelte_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.svelte_language_server, while a change to solidlsp.language_servers.svelte_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.svelte_language_server uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in solidlsp.language_servers.svelte_language_server uses a type in solidlsp.language_servers.typescript_language_server.
solidlsp.language_servers.svelte_language_server uses solidlsp.language_servers.typescript_language_server, so a change to solidlsp.language_servers.typescript_language_server can break solidlsp.language_servers.svelte_language_server, while a change to solidlsp.language_servers.svelte_language_server can't break solidlsp.language_servers.typescript_language_server.
Position
Below the diagonal: solidlsp.language_servers.svelte_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.ls_config, so a change to solidlsp.ls_config can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.ls_config.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.settings, so a change to solidlsp.settings can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.settings.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.dependency_provider, so a change to solidlsp.dependency_provider can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.dependency_provider.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.ls_types, so a change to solidlsp.ls_types can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.ls_types.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.ls, so a change to solidlsp.ls can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.ls.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
solidlsp.language_servers.vue_language_server uses solidlsp.language_servers.typescript_language_server, so a change to solidlsp.language_servers.typescript_language_server can break solidlsp.language_servers.vue_language_server, while a change to solidlsp.language_servers.vue_language_server can't break solidlsp.language_servers.typescript_language_server.
Position
Below the diagonal: solidlsp.language_servers.vue_language_server uses a module listed above it, which is the healthy direction.
serena.repl.facade uses serena.config.serena_config, so a change to serena.config.serena_config can break serena.repl.facade, while a change to serena.repl.facade can't break serena.config.serena_config.
Position
Below the diagonal: serena.repl.facade uses a module listed above it, which is the healthy direction.
serena.repl.facade uses serena.project, so a change to serena.project can break serena.repl.facade, while a change to serena.repl.facade can't break serena.project.
Position
Below the diagonal: serena.repl.facade uses a module listed above it, which is the healthy direction.
serena.symbol uses solidlsp.lsp_protocol_handler.lsp_types, so a change to solidlsp.lsp_protocol_handler.lsp_types can break serena.symbol, while a change to serena.symbol can't break solidlsp.lsp_protocol_handler.lsp_types.
Position
Below the diagonal: serena.symbol uses a module listed above it, which is the healthy direction.
serena.symbol uses solidlsp.ls_types, so a change to solidlsp.ls_types can break serena.symbol, while a change to serena.symbol can't break solidlsp.ls_types.
Position
Below the diagonal: serena.symbol uses a module listed above it, which is the healthy direction.
serena.tools.tools_base uses serena.project, so a change to serena.project can break serena.tools.tools_base, while a change to serena.tools.tools_base can't break serena.project.
Position
Below the diagonal: serena.tools.tools_base uses a module listed above it, which is the healthy direction.
serena.agent uses solidlsp.ls_config, so a change to solidlsp.ls_config can break serena.agent, while a change to serena.agent can't break solidlsp.ls_config.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.agent uses serena.language_backend, so a change to serena.language_backend can break serena.agent, while a change to serena.agent can't break serena.language_backend.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.agent uses serena.config.serena_config, so a change to serena.config.serena_config can break serena.agent, while a change to serena.agent can't break serena.config.serena_config.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.agent uses serena.ls_manager, so a change to serena.ls_manager can break serena.agent, while a change to serena.agent can't break serena.ls_manager.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.agent uses serena.repl.facade, so a change to serena.repl.facade can break serena.agent, while a change to serena.agent can't break serena.repl.facade.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.agent uses serena.tools.tools_base, so a change to serena.tools.tools_base can break serena.agent, while a change to serena.agent can't break serena.tools.tools_base.
Position
Below the diagonal: serena.agent uses a module listed above it, which is the healthy direction.
serena.code_editor uses solidlsp.ls_types, so a change to solidlsp.ls_types can break serena.code_editor, while a change to serena.code_editor can't break solidlsp.ls_types.
Position
Below the diagonal: serena.code_editor uses a module listed above it, which is the healthy direction.
serena.code_editor uses solidlsp.ls, so a change to solidlsp.ls can break serena.code_editor, while a change to serena.code_editor can't break solidlsp.ls.
Position
Below the diagonal: serena.code_editor uses a module listed above it, which is the healthy direction.
serena.code_editor uses serena.project, so a change to serena.project can break serena.code_editor, while a change to serena.code_editor can't break serena.project.
Position
Below the diagonal: serena.code_editor uses a module listed above it, which is the healthy direction.
serena.code_editor uses serena.symbol, so a change to serena.symbol can break serena.code_editor, while a change to serena.code_editor can't break serena.symbol.
Position
Below the diagonal: serena.code_editor uses a module listed above it, which is the healthy direction.
serena.repl.api.lsp_api uses serena.repl.representable, so a change to serena.repl.representable can break serena.repl.api.lsp_api, while a change to serena.repl.api.lsp_api can't break serena.repl.representable.
Position
Below the diagonal: serena.repl.api.lsp_api uses a module listed above it, which is the healthy direction.
serena.repl.api.lsp_api uses serena.repl.facade, so a change to serena.repl.facade can break serena.repl.api.lsp_api, while a change to serena.repl.api.lsp_api can't break serena.repl.facade.
Position
Below the diagonal: serena.repl.api.lsp_api uses a module listed above it, which is the healthy direction.
serena.repl.api.lsp_api uses serena.symbol, so a change to serena.symbol can break serena.repl.api.lsp_api, while a change to serena.repl.api.lsp_api can't break serena.symbol.
Position
Below the diagonal: serena.repl.api.lsp_api uses a module listed above it, which is the healthy direction.
serena.repl.api.lsp_api uses serena.code_editor, so a change to serena.code_editor can break serena.repl.api.lsp_api, while a change to serena.repl.api.lsp_api can't break serena.code_editor.
Position
Below the diagonal: serena.repl.api.lsp_api uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
102
High / Critical
A03:2025 — Software Supply Chain Failures
22
High / Critical
A02:2025 — Security Misconfiguration
9
High / Critical
Roadmap
First, reconcile the README and internal documentation with the actual codebase to eliminate false claims about missing features and fix broken links. Second, establish a dedicated folder for Architecture Decision Records to formally capture significant design choices and their consequences. Third, ensure all custom controls are fully keyboard-operable with proper roles and handlers, and provide anchors with valid hrefs. Finally, add a clear Testing section to the root README explaining how to run the test suite.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Reconcile the README with reality: README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features; The README describes a new REPL-based agent interface, but there is no such feature in the evidence; docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist; docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist; docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist.
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.
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.
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.
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 80
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.
Serious — 332
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.
Minor — 96
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 32
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 50 of 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 53 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 500 of 508 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 1 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .py (56,384 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 22 task marker(s) (TODO/FIXME/HACK/XXX) across 14 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D22 Internal API Consistency — evaluation did not complete — Internal API Consistency not included (check did not complete) — excluded from the score.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/serena/language_backend.py, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (compose.yaml). compose up failed (exit 17 — an image could not be built) — serena Pulling serena Warning Get "https://registry-1.docker.io/v2/": Forbidden failed to solve: target stage "production" could not be found; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
31 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LanguageServerId.get_source_fn_matcher at 83. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being LanguageServerId.get_ls_class at 80 — they are counted neither in the figure above nor in this dimension's score.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with LanguageServerId.get_source_fn_matcher (cyclomatic 83). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 65 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with MemoryReferenceAnalyzer.validate_referential_integrity (cognitive 75), RubyLsp._setup_runtime_dependencies (cognitive 70). — 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 2 together lifts Cognitive Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 19 FileTooLong finding(s) in God Classes — start with REDACTED, dashboard.js, cli.py. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with REDACTED, dashboard.js, REDACTED. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with dashboard.js (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
124 duplicated block group(s) detected. A further 7 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 80 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with astro_language_server.py (2), ccls_language_server.py, crystal_language_server.py. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ruby_lsp.py (2), astro_language_server.py, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), angular_language_server.py, csharp_language_server.py. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
4 production modules (Gradle+Maven+Python+sbt), 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; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 4 (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 it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with al_language_server.py, facade.py, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2007 test methods: 2001 unit, 6 integration, 0 BDD, 0 e2e. The Rust suite contributes 1 `#[test]` function(s) across 1 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 2006 test function(s) across 243 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: src/solidlsp/ls_config.py (18×83=1494); REDACTED (43×16=688); src/serena/config/serena_config.py (23×29=667) Repeated repair below the complexity floor: REDACTED (6 of 8 changes were fixes); src/solidlsp/language_servers/vue_language_server.py (4 of 7 changes were fixes); src/solidlsp/language_servers/nixd_ls.py (4 of 6 changes were fixes)
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with ls_config.py, REDACTED, serena_config.py. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED, vue_language_server.py, nixd_ls.py. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.7 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
23 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/serena/repl/api/lsp_api.py. Counted over 162 of the 202 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted debt markers + 0 dead symbols across 0 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .py (100% of production source) was not read, and carries at least 22 uncounted task marker(s) in 14 file(s).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The project's READMEs cover usage (02-usage) with a detailed JetBrains plugin guide, client-setup instructions, the project workflow, memories/onboarding, configuration, and security documentation. The architecture/design docs are separate and extensive (39 markdown files). A single clipped section is unavoidable given the scanner budget; the visible content is clear and complete for its scope. A strong C/C++ setup guide for Serena's clangd/ccls language servers, covering the essentials of a compile_commands.json file and its requirements (standard flags, include paths), plus configuration options like customizing the .serena/compile_commands_dir. The document is well-structured with an outline that lists every section present in the visible text. (14 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
What to do
Improve Documentation Quality — currently 8.9/10. — The project's READMEs cover usage (02-usage) with a detailed JetBrains plugin guide, client-setup instructions, the project workflow, memories/onboarding, configuration, and security documentation. The architecture/design docs are separate and extensive (39 markdown files). A single clipped section is unavoidable given the scanner budget; the visible content is clear and complete for its scope. A strong C/C++ setup guide for Serena's clangd/ccls language servers, covering the essentials of a compile_commands.json file and its requirements (standard flags, include paths), plus configuration options like customizing the .serena/compile_commands_dir. The document is well-structured with an outline that lists every section present in the visible text. (14 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
102 finding(s): 0 critical, 65 high, 23 medium, 14 low. 51 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 51 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (51 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
4 of 162 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/solidlsp/language_servers/msl_lsp_server.py. Counted over 162 of the 202 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with project.py. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 9 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 34 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/serena/resources/dashboard/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
The repo's own CSS styles .collapsible-header with `cursor: pointer`, so this <h2> 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. (×4) — src/serena/resources/dashboard/index.html:131, src/serena/resources/dashboard/index.html:141, src/serena/resources/dashboard/index.html:151, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.menu-dropdown a.active` sets color: white on background-color: #eaa45d — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/serena/resources/dashboard/dashboard.css:359
`.memory-rename-input` 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. — src/serena/resources/dashboard/dashboard.css:1719
`.toggle-icon` moves (`transition: transform 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. — src/serena/resources/dashboard/dashboard.css:545
`.execution-spinner` moves (`animation: spin 0.7s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/serena/resources/dashboard/dashboard.css:816
`.bar` moves (`transition: width 0.5s 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. — src/serena/resources/dashboard/dashboard.css:975
`.btn` moves (`transition: background-color 0.2s ease, transform 0.05s 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. — src/serena/resources/dashboard/dashboard.css:1035
`.combobox-caret` moves (`transition: transform 0.15s ease, color 0.15s 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. — src/serena/resources/dashboard/dashboard.css:1419
`.spinner` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/serena/resources/dashboard/dashboard.css:1605
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 15 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
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.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features — searched for: `code querying`, `symbol-level editing`, `semantic refactoring`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:1
The README describes a new REPL-based agent interface, but there is no such feature in the evidence — searched for: `REPL-based agent interface`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:1
docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/index.md:2
docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:16
docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:60
docs/01-about/020_programming-languages.md links to `../03-special-guides/unreal_engine_setup_guide_for_serena`, but `docs/03-special-guides/unreal_engine_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:61
docs/01-about/020_programming-languages.md links to `../03-special-guides/godot_gdscript_setup_guide_for_serena`, but `docs/03-special-guides/godot_gdscript_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:82
docs/01-about/020_programming-languages.md links to `../03-special-guides/groovy_setup_guide_for_serena`, but `docs/03-special-guides/groovy_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:89
docs/01-about/020_programming-languages.md links to `../03-special-guides/scala_setup_guide_for_serena`, but `docs/03-special-guides/scala_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:168
docs/01-about/020_programming-languages.md names `hardhat.config.js`, but no file or folder `hardhat.config.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:174
docs/01-about/020_programming-languages.md names TypeScript 7, but the manifest declares `typescript` ~5.5.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:186
docs/01-about/020_programming-languages.md links to `../02-usage/025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/020_programming-languages.md:234
docs/01-about/070_privacy.md links to `contexts`, but `docs/01-about/contexts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-about/070_privacy.md:14
docs/02-usage/010_installation.md links to `language-servers`, but `docs/02-usage/language-servers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/010_installation.md:14
docs/02-usage/010_installation.md links to `025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/010_installation.md:32
docs/02-usage/010_installation.md links to `050_configuration`, but `docs/02-usage/050_configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/010_installation.md:34
docs/02-usage/010_installation.md links to `060_dashboard`, but `docs/02-usage/060_dashboard` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/010_installation.md:43
docs/02-usage/020_running.md links to `install-serena`, but `docs/02-usage/install-serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:9
docs/02-usage/020_running.md links to `025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:30
docs/02-usage/020_running.md links to `040_workflow`, but `docs/02-usage/040_workflow` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:77
docs/02-usage/020_running.md links to `contexts`, but `docs/02-usage/contexts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:101
docs/02-usage/020_running.md links to `modes`, but `docs/02-usage/modes` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:102
docs/02-usage/020_running.md links to `010_installation`, but `docs/02-usage/010_installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/020_running.md:194
docs/02-usage/025_jetbrains_plugin.md links to `configure-jetbrains`, but `docs/02-usage/configure-jetbrains` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:23
docs/02-usage/025_jetbrains_plugin.md links to `jetbrains-workflow`, but `docs/02-usage/jetbrains-workflow` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:24
docs/02-usage/025_jetbrains_plugin.md links to `../01-about/035_tools`, but `docs/01-about/035_tools` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:59
docs/02-usage/025_jetbrains_plugin.md links to `global-config`, but `docs/02-usage/global-config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:129
docs/02-usage/025_jetbrains_plugin.md links to `project-creation-indexing`, but `docs/02-usage/project-creation-indexing` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:130
docs/02-usage/025_jetbrains_plugin.md links to `project-activation`, but `docs/02-usage/project-activation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:130
docs/02-usage/025_jetbrains_plugin.md links to `050_configuration`, but `docs/02-usage/050_configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/025_jetbrains_plugin.md:182
docs/02-usage/030_clients.md links to `start-mcp-server`, but `docs/02-usage/start-mcp-server` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:14
docs/02-usage/030_clients.md links to `streamable-http`, but `docs/02-usage/streamable-http` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:15
docs/02-usage/030_clients.md links to `mcp-args`, but `docs/02-usage/mcp-args` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:20
docs/02-usage/030_clients.md links to `050_configuration`, but `docs/02-usage/050_configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:21
docs/02-usage/030_clients.md documents the environment variable `MCP_TIMEOUT`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:126
docs/02-usage/030_clients.md names `claude_desktop_config.json`, but no file or folder `claude_desktop_config.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/030_clients.md:595
docs/02-usage/040_workflow.md links to `060_dashboard`, but `docs/02-usage/060_dashboard` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/040_workflow.md:51
docs/02-usage/040_workflow.md links to `per-project-language-backend`, but `docs/02-usage/per-project-language-backend` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/040_workflow.md:53
docs/02-usage/040_workflow.md links to `global-config`, but `docs/02-usage/global-config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/040_workflow.md:67
docs/02-usage/040_workflow.md links to `contexts`, but `docs/02-usage/contexts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-usage/040_workflow.md:104
What to do
Reconcile the README with reality: README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features; The README describes a new REPL-based agent interface, but there is no such feature in the evidence; docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist; docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist; docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://cdn.jsdelivr.net/npm/chart.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. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — src/serena/resources/dashboard/index.html:16
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.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 103 is called with an argument built by `list(global_ignored_paths)` (line 103), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/serena/project.py:103
`debug` at line 285 is called with an argument built by `"…".join(cmd)` (line 285), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/solidlsp/language_servers/vbnet_language_server.py:285
`debug` at line 147 is called with an argument built by `list(gopls_settings.keys())` (line 147), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/solidlsp/language_servers/gopls.py:147
`debug` at line 368 is called with an argument built by `"…".join(cmd)` (line 368), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/solidlsp/language_servers/csharp_language_server.py:368
`debug` at line 340 is called with an argument built by `list(init_response["…"].keys())` (line 340), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/solidlsp/language_servers/ansible_language_server.py:340
What to do
In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — serena Pulling serena Warning Get "https://registry-1.docker.io/v2/": Forbidden failed to solve: target stage "production" could not be found; runtime evidence skipped 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~40035 lines of test source are present (.py, .ts) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 1 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .py — the .NET project files present are an immaterial minority — so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — Internal API Consistency not included (check did not complete)
D23 Boundary Type-Coupling — At only 57k LoC across a single project there is no scale to justify any boundaries. No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.py), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
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 dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (62 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — SQLAlchemy is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Python runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×4
Clickable element isn't keyboard-operable src/serena/resources/dashboard/index.html:131— The repo's own CSS styles .collapsible-header with `cursor: pointer`, so this <h2> 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.
Clickable element isn't keyboard-operable src/serena/resources/dashboard/index.html:141— The repo's own CSS styles .collapsible-header with `cursor: pointer`, so this <h2> 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.
Clickable element isn't keyboard-operable src/serena/resources/dashboard/index.html:151— The repo's own CSS styles .collapsible-header with `cursor: pointer`, so this <h2> 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.
Clickable element isn't keyboard-operable src/serena/resources/dashboard/index.html:161— The repo's own CSS styles .collapsible-header with `cursor: pointer`, so this <h2> 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 1942 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1442 over it, 3.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dashboard/dashboard.js src/serena/resources/dashboard/dashboard.js— FileTooLong — 1635 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 89% of them inside a single declaration: Dashboard (291-2529). The bar is 500 significant lines; this is 1135 over it, 3.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: serena/cli.py src/serena/cli.py— FileTooLong — 1242 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 742 over it, 2.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 977 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 477 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 452 over it, 1.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config/serena_config.py src/serena/config/serena_config.py— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: serena/symbol.py src/serena/symbol.py— FileTooLong — 857 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 357 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: solidlsp/ls_config.py src/solidlsp/ls_config.py— FileTooLong — 763 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 263 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 219 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/vue_language_server.py src/solidlsp/language_servers/vue_language_server.py— FileTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 161 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 143 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/rust_analyzer.py src/solidlsp/language_servers/rust_analyzer.py— FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 98 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: util/text_utils.py src/serena/util/text_utils.py— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 93 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/angular_language_server.py src/solidlsp/language_servers/angular_language_server.py— FileTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 85 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: solidlsp/ls_process.py src/solidlsp/ls_process.py— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/al_language_server.py src/solidlsp/language_servers/al_language_server.py— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/astro_language_server.py src/solidlsp/language_servers/astro_language_server.py— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 24 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: language_servers/svelte_language_server.py src/solidlsp/language_servers/svelte_language_server.py— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Hotspot: src/solidlsp/ls_config.py src/solidlsp/ls_config.py:452— src/solidlsp/ls_config.py changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in LanguageServerId.get_source_fn_matcher at line 452. 1 of those changes was a fix/bug commit, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/ls_config.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:552— REDACTED changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SerenaAgent.__init__ at line 552. 4 of those changes were fix/bug commits, and the other 39 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/serena/config/serena_config.py src/serena/config/serena_config.py:1054— src/serena/config/serena_config.py changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in SerenaConfig.from_config_file at line 1054. 4 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/serena/config/serena_config.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/serena/repl/facade.py src/serena/repl/facade.py:188— src/serena/repl/facade.py changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ReferencedType.describe at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/serena/repl/facade.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:544— REDACTED changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SerenaDashboardAPI._compute_config_overview at line 544. 3 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/solidlsp/ls_process.py src/solidlsp/ls_process.py:599— src/solidlsp/ls_process.py changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in StdioLanguageServer._read_ls_process_stdout at line 599. 6 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/ls_process.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/serena/resources/dashboard/dashboard.js src/serena/resources/dashboard/dashboard.js:684— src/serena/resources/dashboard/dashboard.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Dashboard.displayConfig at line 684. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/serena/resources/dashboard/dashboard.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/serena/ls_manager.py src/serena/ls_manager.py:306— src/serena/ls_manager.py changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in LanguageServerFileChangeNotifier.poll_and_notify at line 306. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/serena/ls_manager.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/solidlsp/language_servers/ruby_lsp.py src/solidlsp/language_servers/ruby_lsp.py:105— src/solidlsp/language_servers/ruby_lsp.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in RubyLsp._setup_runtime_dependencies at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/language_servers/ruby_lsp.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:114— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ElixirTools._setup_runtime_dependencies at line 114. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyMethods: SolidLanguageServer REDACTED:352— TooManyMethods — 108 methods. The bar is 30 methods; this is 78 over it, 3.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Dashboard src/serena/resources/dashboard/dashboard.js:291— TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SerenaAgent REDACTED:551— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LanguageServerRequest src/solidlsp/ls_request.py:11— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AngularLanguageServer src/solidlsp/language_servers/angular_language_server.py:215— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TypeScriptLanguageServer src/solidlsp/language_servers/typescript_language_server.py:106— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VueLanguageServer src/solidlsp/language_servers/vue_language_server.py:153— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JetBrainsPluginClient src/serena/jetbrains/jetbrains_plugin_client.py:178— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/astro_language_server.py:320— src/solidlsp/language_servers/astro_language_server.py:320-329 | src/solidlsp/language_servers/svelte_language_server.py:330-339 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/astro_language_server.py:358— src/solidlsp/language_servers/astro_language_server.py:358-367 | src/solidlsp/language_servers/svelte_language_server.py:376-385 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/ccls_language_server.py:138— src/solidlsp/language_servers/ccls_language_server.py:138-147 | REDACTED:364-373 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/crystal_language_server.py:139— src/solidlsp/language_servers/crystal_language_server.py:139-148 | src/solidlsp/language_servers/sourcekit_lsp.py:326-335 — before extracting anything, compare `src/solidlsp/language_servers/crystal_language_server.py` and `src/solidlsp/language_servers/sourcekit_lsp.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:762— src/solidlsp/language_servers/csharp_language_server.py:762-776 | src/solidlsp/language_servers/vbnet_language_server.py:538-547 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/ruby_lsp.py:434— src/solidlsp/language_servers/ruby_lsp.py:434-443 | src/solidlsp/language_servers/solargraph.py:324-333 — before extracting anything, compare `src/solidlsp/language_servers/ruby_lsp.py` and `src/solidlsp/language_servers/solargraph.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/solidlsp/language_servers/some_sass_language_server.py:208— src/solidlsp/language_servers/some_sass_language_server.py:208-217 | src/solidlsp/language_servers/vscode_html_language_server.py:146-155 — before extracting anything, compare `src/solidlsp/language_servers/some_sass_language_server.py` and `src/solidlsp/language_servers/vscode_html_language_server.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×6
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:545— `.toggle-icon` moves (`transition: transform 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.
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:816— `.execution-spinner` moves (`animation: spin 0.7s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:975— `.bar` moves (`transition: width 0.5s 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.
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:1035— `.btn` moves (`transition: background-color 0.2s ease, transform 0.05s 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.
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:1419— `.combobox-caret` moves (`transition: transform 0.15s ease, color 0.15s 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.
Animation without a prefers-reduced-motion guard src/serena/resources/dashboard/dashboard.css:1605— `.spinner` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Duplicated block (11 lines × 2) src/solidlsp/language_servers/astro_language_server.py:262— src/solidlsp/language_servers/astro_language_server.py:262-272 | src/solidlsp/language_servers/svelte_language_server.py:261-271 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/astro_language_server.py:262` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) REDACTED:986— REDACTED:986-996 | REDACTED:1008-1018 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:986` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/solidlsp/language_servers/hlsl_language_server.py:154— src/solidlsp/language_servers/hlsl_language_server.py:154-164 | src/solidlsp/language_servers/systemverilog_server.py:137-147 — before extracting anything, compare `src/solidlsp/language_servers/hlsl_language_server.py` and `src/solidlsp/language_servers/systemverilog_server.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) src/solidlsp/language_servers/ruby_lsp.py:224— src/solidlsp/language_servers/ruby_lsp.py:224-234 | src/solidlsp/language_servers/solargraph.py:145-155 — before extracting anything, compare `src/solidlsp/language_servers/ruby_lsp.py` and `src/solidlsp/language_servers/solargraph.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) src/solidlsp/language_servers/ruby_lsp.py:388— src/solidlsp/language_servers/ruby_lsp.py:388-398 | src/solidlsp/language_servers/solargraph.py:306-316 — before extracting anything, compare `src/solidlsp/language_servers/ruby_lsp.py` and `src/solidlsp/language_servers/solargraph.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) src/solidlsp/language_servers/vue_language_server.py:342— src/solidlsp/language_servers/vue_language_server.py:342-352 | src/solidlsp/language_servers/vue_language_server.py:399-409 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) REDACTED:369— REDACTED:369-373 | REDACTED:381-385 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) REDACTED:1385— REDACTED:1385-1389 | REDACTED:1399-1403 — 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.
Duplicated block (5 lines × 2) src/solidlsp/language_servers/angular_language_server.py:607— src/solidlsp/language_servers/angular_language_server.py:607-611 | src/solidlsp/language_servers/vscode_html_language_server.py:152-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/angular_language_server.py:602` calls `angular_project_loading_finish`, `info`, `set` and `src/solidlsp/language_servers/vscode_html_language_server.py:150` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:559— src/solidlsp/language_servers/csharp_language_server.py:559-564 | src/solidlsp/language_servers/vbnet_language_server.py:383-387 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/csharp_language_server.py:570` calls `set` and `src/solidlsp/language_servers/vbnet_language_server.py:389` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/solidlsp/language_servers/ruby_lsp.py:177— src/solidlsp/language_servers/ruby_lsp.py:177-181 | src/solidlsp/language_servers/solargraph.py:83-87 — before extracting anything, compare `src/solidlsp/language_servers/ruby_lsp.py` and `src/solidlsp/language_servers/solargraph.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/solidlsp/language_servers/typescript_language_server.py:592— src/solidlsp/language_servers/typescript_language_server.py:592-596 | src/solidlsp/language_servers/typescript_language_server.py:601-605 — 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Repeated repair: REDACTED REDACTED:173— REDACTED changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is DependencyProvider._create_artifact at line 173), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Kotlin LS not being downloadable/usable”; “fix(kotlin): redirect idea.system.path to prevent stale /tmp dirs (#1130)”; “fix(kotlin): remove the leaked fallback storage directory on release (#2113)”; “fix(kotlin): update managed Kotlin LSP to 263.4702.0”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/solidlsp/language_servers/vue_language_server.py src/solidlsp/language_servers/vue_language_server.py:357— src/solidlsp/language_servers/vue_language_server.py changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is VueLanguageServer.request_file_references at line 357), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(typescript): pin tsserver for untrusted projects (#2143)”; “Fix Vue companion discovery to respect project ignore patterns (#2125)”; “fix(lsp): use typescriptreact/javascriptreact languageIds for .tsx/.jsx in Angular, Vue and Svelte (#2066)”; “Fix document symbol caching for language servers that post-process symbols”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/language_servers/vue_language_server.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/solidlsp/language_servers/nixd_ls.py src/solidlsp/language_servers/nixd_ls.py:76— src/solidlsp/language_servers/nixd_ls.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is DependencyProvider._install_nixd_with_nix at line 76), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(nix): retry transient hover responses (#1040) (#1921)”; “fix(nix): use schema-valid default nixd options (#1957)”; “Fix document symbol caching for language servers that post-process symbols”; “fix(nix): use published diagnostics for nixd”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/language_servers/nixd_ls.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/solidlsp/language_servers/dart_language_server.py src/solidlsp/language_servers/dart_language_server.py:94— src/solidlsp/language_servers/dart_language_server.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is DartLanguageServer._setup_runtime_dependencies at line 94), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(dart): omit rootUri/rootPath (#2045) (#2051)”; “fix(dart): wait for analyzer readiness signal before returning from start()”; “fix(dart): handle analyzer status notifications (#1863)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/solidlsp/language_servers/dart_language_server.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/serena/analytics.py src/serena/analytics.py:107— src/serena/analytics.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is RegisteredTokenCountEstimator._create_estimator at line 107), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Merge pull request #2083 from anxkhn/fix/tiktoken-literal-usage-counting”; “Fix: Update model used by Anthropic token estimator”; “fix: do not load the anthropic package on import”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 10:47:26 +02:00' --until='2026-10-20 10:47:26 +02:00' --full-history --no-merges -- src/serena/analytics.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (14 lines × 2) scripts/demo_progressive_tool_shortening.py:68— scripts/demo_progressive_tool_shortening.py:68-81 | scripts/demo_progressive_tool_shortening.py:136-149 — 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.
Duplicated block (14 lines × 2) src/solidlsp/language_servers/ada_language_server.py:202— src/solidlsp/language_servers/ada_language_server.py:202-215 | REDACTED:300-313 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) src/solidlsp/language_servers/angular_language_server.py:138— src/solidlsp/language_servers/angular_language_server.py:138-151 | src/solidlsp/language_servers/angular_language_server.py:285-298 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:277— REDACTED:277-290 | src/solidlsp/language_servers/ty_server.py:123-136 — before extracting anything, compare `REDACTED` and `src/solidlsp/language_servers/ty_server.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:276` calls `_install_mutation_retry` and `src/solidlsp/language_servers/ty_server.py:122` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) src/serena/util/file_system.py:74— src/serena/util/file_system.py:74-87 | src/serena/util/yaml.py:245-259 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/interprompt/multilang_prompt.py:274— src/interprompt/multilang_prompt.py:274-281 | src/interprompt/multilang_prompt.py:302-309 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/solidlsp/language_servers/dart_language_server.py:235— src/solidlsp/language_servers/dart_language_server.py:235-242 | src/solidlsp/language_servers/pyright_server.py:233-243 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/solidlsp/language_servers/fsharp_language_server.py:362— src/solidlsp/language_servers/fsharp_language_server.py:362-369 | src/solidlsp/language_servers/fsharp_language_server.py:373-380 — 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.
Duplicated block (8 lines × 2) REDACTED:204— REDACTED:204-211 | src/solidlsp/language_servers/rust_analyzer.py:759-769 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:202` calls `_download_dependencies` and `src/solidlsp/language_servers/rust_analyzer.py:757` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) REDACTED:608— REDACTED:608-618 | src/solidlsp/language_servers/svelte_language_server.py:594-601 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Low cohesion: ALLanguageServer (LCOM4 6) src/solidlsp/language_servers/al_language_server.py:59— ALLanguageServer's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Facade (LCOM4 5) src/serena/repl/facade.py:562— Facade's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: EclipseJDTLS (LCOM4 5) REDACTED:102— EclipseJDTLS's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NixLanguageServer (LCOM4 4) src/solidlsp/language_servers/nixd_ls.py:32— NixLanguageServer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RubyLsp (LCOM4 4) src/solidlsp/language_servers/ruby_lsp.py:33— RubyLsp's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (12 lines × 2) scripts/demo_progressive_tool_shortening.py:87— scripts/demo_progressive_tool_shortening.py:87-98 | scripts/demo_progressive_tool_shortening.py:155-166 — 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.
Duplicated block (12 lines × 2) src/solidlsp/language_servers/clojure_lsp.py:267— src/solidlsp/language_servers/clojure_lsp.py:267-278 | src/solidlsp/language_servers/marksman.py:132-143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/clojure_lsp.py:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) REDACTED:285— REDACTED:285-296 | src/solidlsp/language_servers/solargraph.py:309-320 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) src/solidlsp/language_servers/omnisharp.py:207— src/solidlsp/language_servers/omnisharp.py:207-218 | src/solidlsp/language_servers/omnisharp.py:224-235 — 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.
Duplicated block (13 lines × 2) src/solidlsp/language_servers/bash_language_server.py:239— src/solidlsp/language_servers/bash_language_server.py:239-251 | src/solidlsp/language_servers/typescript_language_server.py:449-474 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/typescript_language_server.py:476` calls `configuration_handler`, `get` and `src/solidlsp/language_servers/bash_language_server.py:253` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/solidlsp/language_servers/vue_language_server.py:76— src/solidlsp/language_servers/vue_language_server.py:76-88 | src/solidlsp/language_servers/vue_language_server.py:241-253 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/solidlsp/language_servers/fsharp_language_server.py:52— src/solidlsp/language_servers/fsharp_language_server.py:52-65 | src/solidlsp/language_servers/vts_language_server.py:54-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–9 lines × 2) src/serena/config/context_mode.py:133— src/serena/config/context_mode.py:133-141 | src/serena/config/context_mode.py:252-259 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–9 lines × 2) src/solidlsp/language_servers/devsense_php_language_server.py:193— src/solidlsp/language_servers/devsense_php_language_server.py:193-200 | src/solidlsp/language_servers/wolfram_language_server.py:77-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–9 lines × 2) src/solidlsp/language_servers/some_sass_language_server.py:220— src/solidlsp/language_servers/some_sass_language_server.py:220-227 | src/solidlsp/language_servers/vscode_html_language_server.py:158-166 — before extracting anything, compare `src/solidlsp/language_servers/some_sass_language_server.py` and `src/solidlsp/language_servers/vscode_html_language_server.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) REDACTED:266— REDACTED:266-274 | src/solidlsp/language_servers/ty_server.py:114-122 — before extracting anything, compare `REDACTED` and `src/solidlsp/language_servers/ty_server.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:276` calls `_install_mutation_retry` and `src/solidlsp/language_servers/ty_server.py:123` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) src/interprompt/util/class_decorators.py:7— src/interprompt/util/class_decorators.py:7-15 | src/serena/util/class_decorators.py:9-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) src/solidlsp/language_servers/angular_language_server.py:447— src/solidlsp/language_servers/angular_language_server.py:447-455 | src/solidlsp/language_servers/vue_language_server.py:738-746 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/serena/cli.py:424— src/serena/cli.py:424-430 | src/serena/cli.py:558-564 — 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.
Duplicated block (7 lines × 2) REDACTED:92— REDACTED:92-98 | REDACTED:663-669 — 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.
Duplicated block (7 lines × 2) src/serena/util/text_utils.py:463— src/serena/util/text_utils.py:463-469 | src/serena/util/text_utils.py:579-585 — 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.
Duplicated block (6 lines × 2) REDACTED:621— REDACTED:621-626 | src/solidlsp/language_servers/matlab_language_server.py:444-449 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) REDACTED:337— REDACTED:337-342 | src/solidlsp/ls_utils.py:644-651 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/serena/language_backend.py:187— src/serena/language_backend.py:187-192 | src/solidlsp/ls_config.py:1085-1090 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
MethodTooLong: Dashboard.constructor src/serena/resources/dashboard/dashboard.js:292— MethodTooLong — constructor runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dashboard.displayConfig src/serena/resources/dashboard/dashboard.js:684— MethodTooLong — displayConfig runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (21 lines × 2) scripts/demo_find_defining_symbol.py:25— scripts/demo_find_defining_symbol.py:25-45 | scripts/demo_find_implementing_symbol.py:23-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scripts/demo_find_defining_symbol.py:21` calls `Path` and `scripts/demo_find_implementing_symbol.py:19` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) src/solidlsp/language_servers/fortran_language_server.py:292— src/solidlsp/language_servers/fortran_language_server.py:292-312 | src/solidlsp/language_servers/powershell_language_server.py:400-420 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/powershell_language_server.py:399` calls `_get_published_diagnostics_uri` and `src/solidlsp/language_servers/fortran_language_server.py:291` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) src/solidlsp/language_servers/astro_language_server.py:538— src/solidlsp/language_servers/astro_language_server.py:538-555 | src/solidlsp/language_servers/svelte_language_server.py:581-598 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/svelte_language_server.py:603` calls `_wrap_notify_send_for_ts_js_mirror` and `src/solidlsp/language_servers/astro_language_server.py:558` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) src/solidlsp/language_servers/angular_language_server.py:186— src/solidlsp/language_servers/angular_language_server.py:186-203 | src/solidlsp/language_servers/vue_language_server.py:123-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 3) src/solidlsp/language_servers/csharp_language_server.py:672— src/solidlsp/language_servers/csharp_language_server.py:672-682 | src/solidlsp/language_servers/fsharp_language_server.py:407-417 | src/solidlsp/language_servers/vbnet_language_server.py:467-477 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) REDACTED:349— REDACTED:349-359 | REDACTED:595-605 | src/solidlsp/language_servers/typescript_language_server.py:529-539 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:349` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) src/solidlsp/language_servers/cue_language_server.py:233— src/solidlsp/language_servers/cue_language_server.py:233-243 | src/solidlsp/language_servers/luau_lsp.py:345-354 — before extracting anything, compare `src/solidlsp/language_servers/cue_language_server.py` and `src/solidlsp/language_servers/luau_lsp.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) src/solidlsp/language_servers/emmylua_ls.py:204— src/solidlsp/language_servers/emmylua_ls.py:204-214 | src/solidlsp/language_servers/nextflow_language_server.py:272-281 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 4) src/solidlsp/language_servers/emmylua_ls.py:202— src/solidlsp/language_servers/emmylua_ls.py:202-210 | src/solidlsp/language_servers/nextflow_language_server.py:270-278 | src/solidlsp/language_servers/nixd_ls.py:431-439 | src/solidlsp/language_servers/vts_language_server.py:211-219 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/vts_language_server.py:224` calls `debug` and `src/solidlsp/language_servers/nixd_ls.py:443` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) src/solidlsp/language_servers/basedpyright_server.py:44— src/solidlsp/language_servers/basedpyright_server.py:44-52 | src/solidlsp/language_servers/fatou_language_server.py:35-43 | src/solidlsp/language_servers/pyright_server.py:48-56 | src/solidlsp/language_servers/ty_server.py:43-51 — before extracting anything, compare `src/solidlsp/language_servers/basedpyright_server.py` and `src/solidlsp/language_servers/pyright_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/basedpyright_server.py:40` calls `Event` and `src/solidlsp/language_servers/ty_server.py:40` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) src/solidlsp/language_servers/cue_language_server.py:234— src/solidlsp/language_servers/cue_language_server.py:234-243 | src/solidlsp/language_servers/luau_lsp.py:346-354 | src/solidlsp/language_servers/nixd_ls.py:428-436 — before extracting anything, compare `src/solidlsp/language_servers/cue_language_server.py` and `src/solidlsp/language_servers/luau_lsp.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/cue_language_server.py:246` calls `_create_initialize_params` and `src/solidlsp/language_servers/nixd_ls.py:439` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) REDACTED:288— REDACTED:288-296 | src/solidlsp/language_servers/solargraph.py:312-320 | src/solidlsp/language_servers/wolfram_language_server.py:70-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 7) REDACTED:381— REDACTED:381-388 | src/solidlsp/language_servers/clojure_lsp.py:382-389 | src/solidlsp/language_servers/dart_language_server.py:215-222 | REDACTED:291-298 | src/solidlsp/language_servers/jedi_server.py:156-163 | src/solidlsp/language_servers/rust_analyzer.py:747-754 | src/solidlsp/language_servers/solargraph.py:315-322 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/dart_language_server.py:212` calls `info` and `src/solidlsp/language_servers/rust_analyzer.py:744` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 7) REDACTED:88— REDACTED:88-95 | src/solidlsp/language_servers/gopls.py:66-73 | src/solidlsp/language_servers/gopls.py:77-84 | src/solidlsp/language_servers/perl_language_server.py:46-53 | src/solidlsp/language_servers/rust_analyzer.py:58-65 | src/solidlsp/language_servers/zls.py:39-46 | src/solidlsp/language_servers/zls.py:50-57 — there are 7 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 5) REDACTED:370— REDACTED:370-377 | REDACTED:394-401 | REDACTED:406-413 | REDACTED:418-425 | REDACTED:438-445 — all 5 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.
Duplicated block (8 lines × 5) src/solidlsp/language_servers/emmylua_ls.py:203— src/solidlsp/language_servers/emmylua_ls.py:203-210 | src/solidlsp/language_servers/erlang_language_server.py:244-251 | src/solidlsp/language_servers/nextflow_language_server.py:271-278 | src/solidlsp/language_servers/nixd_ls.py:432-439 | src/solidlsp/language_servers/vts_language_server.py:212-219 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/erlang_language_server.py:242` calls `on_notification` and `src/solidlsp/language_servers/emmylua_ls.py:202` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) src/solidlsp/language_servers/csharp_language_server.py:670— src/solidlsp/language_servers/csharp_language_server.py:670-675 | REDACTED:619-624 | src/solidlsp/language_servers/vbnet_language_server.py:465-470 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) src/solidlsp/language_servers/fatou_language_server.py:95— src/solidlsp/language_servers/fatou_language_server.py:95-100 | REDACTED:616-621 | REDACTED:622-627 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:628` calls `on_notification` and `src/solidlsp/language_servers/fatou_language_server.py:102` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark src/serena/resources/dashboard/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (2.1:1) src/serena/resources/dashboard/dashboard.css:359— `.menu-dropdown a.active` sets color: white on background-color: #eaa45d — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement src/serena/resources/dashboard/dashboard.css:1719— `.memory-rename-input` 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 15 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
LanguageServerId.get_source_fn_matcher (cyclomatic 83) src/solidlsp/ls_config.py:452— LanguageServerId.get_source_fn_matcher has cyclomatic complexity 83 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RubyLsp._setup_runtime_dependencies (cyclomatic 39) src/solidlsp/language_servers/ruby_lsp.py:105— RubyLsp._setup_runtime_dependencies has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dashboard.displayConfig (cyclomatic 35) src/serena/resources/dashboard/dashboard.js:684— Dashboard.displayConfig has cyclomatic complexity 35 (threshold 15). Of this number, 30 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoryReferenceAnalyzer.validate_referential_integrity (cyclomatic 30) src/serena/memories/memory_reference_analysis.py:523— MemoryReferenceAnalyzer.validate_referential_integrity has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SerenaConfig.from_config_file (cyclomatic 29) src/serena/config/serena_config.py:1054— SerenaConfig.from_config_file has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
msl_lsp_server._find_symbol_at_position (cyclomatic 26) src/solidlsp/language_servers/msl_lsp_server.py:213— msl_lsp_server._find_symbol_at_position has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Solargraph._setup_runtime_dependencies (cyclomatic 24) src/solidlsp/language_servers/solargraph.py:70— Solargraph._setup_runtime_dependencies has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GlobMatcher._translate_glob_to_regex (cyclomatic 23) src/serena/util/text_utils.py:254— GlobMatcher._translate_glob_to_regex has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SolidLanguageServer.request_referencing_symbols (cyclomatic 23) REDACTED:2501— SolidLanguageServer.request_referencing_symbols has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReferentialIntegrityReport.format (cyclomatic 21) src/serena/memories/memory_reference_analysis.py:377— ReferentialIntegrityReport.format has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ALLanguageServer.request_full_symbol_tree (cyclomatic 21) src/solidlsp/language_servers/al_language_server.py:716— ALLanguageServer.request_full_symbol_tree has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PascalLanguageServer._atomic_install (cyclomatic 21) REDACTED:534— PascalLanguageServer._atomic_install has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SolidLanguageServer.request_completions (cyclomatic 21) REDACTED:1876— SolidLanguageServer.request_completions has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
autogen_docs.make_rst (cyclomatic 20) docs/autogen_docs.py:53— autogen_docs.make_rst has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProjectConfig._from_dict (cyclomatic 20) src/serena/config/serena_config.py:584— ProjectConfig._from_dict has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ReferencedType.describe (cyclomatic 19) src/serena/repl/facade.py:188— ReferencedType.describe has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
yaml.normalise_yaml_comments (cyclomatic 19) src/serena/util/yaml.py:92— yaml.normalise_yaml_comments has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SerenaDashboardAPI._compute_config_overview (cyclomatic 18) REDACTED:544— SerenaDashboardAPI._compute_config_overview has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
memory_reference_analysis.compute_name_similarity (cyclomatic 18) src/serena/memories/memory_reference_analysis.py:104— memory_reference_analysis.compute_name_similarity has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ElixirTools._setup_runtime_dependencies (cyclomatic 18) REDACTED:114— ElixirTools._setup_runtime_dependencies has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TypeScriptLanguageServer._find_representative_source_file (cyclomatic 18) src/solidlsp/language_servers/typescript_language_server.py:578— TypeScriptLanguageServer._find_representative_source_file has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TCPLanguageServer._read_loop (cyclomatic 18) src/solidlsp/ls_process.py:797— TCPLanguageServer._read_loop has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dashboard.constructor (cyclomatic 18) src/serena/resources/dashboard/dashboard.js:292— Dashboard.constructor has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 528, 429, 447, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LanguageServerFileChangeNotifier.poll_and_notify (cyclomatic 17) src/serena/ls_manager.py:306— LanguageServerFileChangeNotifier.poll_and_notify has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SerenaAgent.__init__ (cyclomatic 16) REDACTED:552— SerenaAgent.__init__ has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AngularLanguageServer._find_representative_source_file (cyclomatic 16) src/solidlsp/language_servers/angular_language_server.py:675— AngularLanguageServer._find_representative_source_file has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OmniSharp._setup_runtime_dependencies (cyclomatic 16) src/solidlsp/language_servers/omnisharp.py:146— OmniSharp._setup_runtime_dependencies has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dashboard.updateChartsTheme (cyclomatic 16) src/serena/resources/dashboard/dashboard.js:1780— Dashboard.updateChartsTheme has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoryReferenceAnalyzer.validate_referential_integrity (cognitive 75) src/serena/memories/memory_reference_analysis.py:523— MemoryReferenceAnalyzer.validate_referential_integrity has cognitive complexity 75 (threshold 15). Drivers by points: if/else 21 (61 pts), loops 5 (10 pts), boolean chains 4 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RubyLsp._setup_runtime_dependencies (cognitive 70) src/solidlsp/language_servers/ruby_lsp.py:105— RubyLsp._setup_runtime_dependencies has cognitive complexity 70 (threshold 15). Drivers by points: if/else 18 (33 pts), ternaries 8 (18 pts), boolean chains 9, error handling 4 (7 pts), loops 1 (3 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yaml.normalise_yaml_comments (cognitive 58) src/serena/util/yaml.py:92— yaml.normalise_yaml_comments has cognitive complexity 58 (threshold 15). Drivers by points: if/else 9 (48 pts), loops 2 (5 pts), boolean chains 4, match/switch 1 (nesting depth added 42). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
displayConfig (cognitive 56) src/serena/resources/dashboard/dashboard.js:684— displayConfig has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (26 pts), ternaries 10 (19 pts), boolean chains 10, error handling 1 (nesting depth added 18). Of this number, 44 points are the body's own statements and 12 belong to 14 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Solargraph._setup_runtime_dependencies (cognitive 50) src/solidlsp/language_servers/solargraph.py:70— Solargraph._setup_runtime_dependencies has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (27 pts), ternaries 3 (10 pts), error handling 4 (7 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ALLanguageServer.request_full_symbol_tree (cognitive 46) src/solidlsp/language_servers/al_language_server.py:716— ALLanguageServer.request_full_symbol_tree has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 5 (8 pts), error handling 2 (6 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeScriptLanguageServer._find_representative_source_file (cognitive 46) src/solidlsp/language_servers/typescript_language_server.py:578— TypeScriptLanguageServer._find_representative_source_file has cognitive complexity 46 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 6 (16 pts), boolean chains 3 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguageServerId.get_source_fn_matcher (cognitive 43) src/solidlsp/ls_config.py:452— LanguageServerId.get_source_fn_matcher has cognitive complexity 43 (threshold 15). Drivers by points: loops 15 (42 pts), match/switch 1 (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SerenaConfig.from_config_file (cognitive 42) src/serena/config/serena_config.py:1054— SerenaConfig.from_config_file has cognitive complexity 42 (threshold 15). Drivers by points: if/else 20 (29 pts), error handling 4 (8 pts), boolean chains 3, loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReferentialIntegrityReport.format (cognitive 42) src/serena/memories/memory_reference_analysis.py:377— ReferentialIntegrityReport.format has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 5 (17 pts), if/else 11 (15 pts), loops 4 (9 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlobMatcher._translate_glob_to_regex (cognitive 42) src/serena/util/text_utils.py:254— GlobMatcher._translate_glob_to_regex has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SolidLanguageServer.request_referencing_symbols (cognitive 42) REDACTED:2501— SolidLanguageServer.request_referencing_symbols has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (30 pts), boolean chains 6, loops 2 (5 pts), ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
msl_lsp_server._find_symbol_at_position (cognitive 39) src/solidlsp/language_servers/msl_lsp_server.py:213— msl_lsp_server._find_symbol_at_position has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 8 (10 pts), ternaries 2 (6 pts), boolean chains 5 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SerenaDashboardTrayManager._alive_check_loop (cognitive 38) REDACTED:1172— SerenaDashboardTrayManager._alive_check_loop has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (18 pts), error handling 3 (10 pts), loops 4 (10 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuiLogViewer._process_queue (cognitive 36) src/serena/gui_log_viewer.py:149— GuiLogViewer._process_queue has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (13 pts), error handling 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PascalLanguageServer._atomic_install (cognitive 35) REDACTED:534— PascalLanguageServer._atomic_install has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (21 pts), error handling 5 (12 pts), boolean chains 1, ternaries 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
autogen_docs.make_rst (cognitive 33) docs/autogen_docs.py:53— autogen_docs.make_rst has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 7, loops 3 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Project.gather_project_files (cognitive 33) src/serena/project.py:475— Project.gather_project_files has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 2 (8 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TCPLanguageServer._read_loop (cognitive 33) src/solidlsp/ls_process.py:797— TCPLanguageServer._read_loop has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (19 pts), error handling 5 (10 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolSet.apply (cognitive 32) REDACTED:150— ToolSet.apply has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DependencyProvider._find_matlab_installation (cognitive 30) src/solidlsp/language_servers/matlab_language_server.py:240— DependencyProvider._find_matlab_installation has cognitive complexity 30 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 5 (14 pts), boolean chains 1 (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ReferencedType.describe (cognitive 28) src/serena/repl/facade.py:188— ReferencedType.describe has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 4 (12 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HaskellLanguageServer._ensure_hls_installed (cognitive 27) src/solidlsp/language_servers/haskell_language_server.py:29— HaskellLanguageServer._ensure_hls_installed has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (7 pts), error handling 2 (6 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguageServerFileChangeNotifier.poll_and_notify (cognitive 25) src/serena/ls_manager.py:306— LanguageServerFileChangeNotifier.poll_and_notify has cognitive complexity 25 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 7 (10 pts), loops 4 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguageServerSymbolRetriever.request_info_for_symbol_batch (cognitive 25) src/serena/symbol.py:634— LanguageServerSymbolRetriever.request_info_for_symbol_batch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
file_system.scan_directory (cognitive 25) src/serena/util/file_system.py:112— file_system.scan_directory has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 3 (6 pts), loops 1, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AngularLanguageServer._find_representative_source_file (cognitive 25) src/solidlsp/language_servers/angular_language_server.py:675— AngularLanguageServer._find_representative_source_file has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PascalLanguageServer._setup_runtime_dependencies (cognitive 24) REDACTED:633— PascalLanguageServer._setup_runtime_dependencies has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitignoreParser._parse_gitignore_content (cognitive 23) src/serena/util/file_system.py:377— GitignoreParser._parse_gitignore_content has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
msl_lsp_server._get_all_mrc_files (cognitive 23) src/solidlsp/language_servers/msl_lsp_server.py:168— msl_lsp_server._get_all_mrc_files has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 4 (7 pts), error handling 2 (5 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OmniSharp._setup_runtime_dependencies (cognitive 23) src/solidlsp/language_servers/omnisharp.py:146— OmniSharp._setup_runtime_dependencies has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectConfig._from_dict (cognitive 22) src/serena/config/serena_config.py:584— ProjectConfig._from_dict has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (7 pts), error handling 2 (3 pts), ternaries 3, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MemoryReferenceAnalyzer.auto_prefix_bare_references (cognitive 22) src/serena/memories/memory_reference_analysis.py:688— MemoryReferenceAnalyzer.auto_prefix_bare_references has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElixirTools._setup_runtime_dependencies (cognitive 22) REDACTED:114— ElixirTools._setup_runtime_dependencies has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 6, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileCollection.filter_glob (cognitive 21) src/serena/util/file_proxy.py:73— FileCollection.filter_glob has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitignoreParser.should_ignore (cognitive 21) src/serena/util/file_system.py:464— GitignoreParser.should_ignore has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (5 pts), ternaries 2 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DependencyProvider._ensure_rust_analyzer_installed (cognitive 21) src/solidlsp/language_servers/rust_analyzer.py:92— DependencyProvider._ensure_rust_analyzer_installed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolidLanguageServer.request_completions (cognitive 21) REDACTED:1876— SolidLanguageServer.request_completions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 7, loops 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StdioLanguageServer._read_ls_process_stdout (cognitive 21) src/solidlsp/ls_process.py:599— StdioLanguageServer._read_ls_process_stdout has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 4 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SerenaAgent.__init__ (cognitive 20) REDACTED:552— SerenaAgent.__init__ has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 3, boolean chains 2, error handling 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SerenaDashboardAPI._compute_config_overview (cognitive 20) REDACTED:544— SerenaDashboardAPI._compute_config_overview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (7 pts), error handling 2 (4 pts), loops 4, ternaries 4, boolean chains 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
JetBrainsPluginClient._make_request (cognitive 20) src/serena/jetbrains/jetbrains_plugin_client.py:307— JetBrainsPluginClient._make_request has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 5, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
memory_reference_analysis.compute_name_similarity (cognitive 20) src/serena/memories/memory_reference_analysis.py:104— memory_reference_analysis.compute_name_similarity has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AngularLanguageServer._find_angular_core_install (cognitive 20) src/solidlsp/language_servers/angular_language_server.py:498— AngularLanguageServer._find_angular_core_install has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 3 (7 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectConfig._load_yaml_dict (cognitive 19) src/serena/config/serena_config.py:528— ProjectConfig._load_yaml_dict has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiagnosticsDiff.__init__ (cognitive 19) src/serena/lsp/lsp_diagnostics.py:152— DiagnosticsDiff.__init__ has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), error handling 2 (5 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClojureLSP._collect_source_paths (cognitive 19) src/solidlsp/language_servers/clojure_lsp.py:148— ClojureLSP._collect_source_paths has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dashboard.updateChartsTheme (cognitive 19) src/serena/resources/dashboard/dashboard.js:1780— Dashboard.updateChartsTheme has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutofixReport.format (cognitive 18) src/serena/memories/memory_reference_analysis.py:469— AutofixReport.format has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (5 pts), ternaries 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yaml.transfer_yaml_comments_by_index (cognitive 18) src/serena/util/yaml.py:279— yaml.transfer_yaml_comments_by_index has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroovyLanguageServer._setup_runtime_dependencies (cognitive 18) REDACTED:111— GroovyLanguageServer._setup_runtime_dependencies has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LuaLanguageServer._download_lua_ls (cognitive 18) src/solidlsp/language_servers/lua_ls.py:120— LuaLanguageServer._download_lua_ls has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PascalLanguageServer._extract_archive (cognitive 18) REDACTED:473— PascalLanguageServer._extract_archive has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wolfram_language_server._find_wolfram_kernel (cognitive 18) src/solidlsp/language_servers/wolfram_language_server.py:93— wolfram_language_server._find_wolfram_kernel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlatformUtils.get_dotnet_version (cognitive 18) src/solidlsp/ls_utils.py:848— PlatformUtils.get_dotnet_version has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (3 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dashboard.constructor (cognitive 18) src/serena/resources/dashboard/dashboard.js:292— Dashboard.constructor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 1 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 10 function literals inside it that branch (lines 528, 429, 447, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TopLevelCommands.start_mcp_server (cognitive 17) src/serena/cli.py:394— TopLevelCommands.start_mcp_server has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ToolUseCounter.update (cognitive 17) REDACTED:244— ToolUseCounter.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SolidLanguageServer.is_ignored_path (cognitive 17) REDACTED:1315— SolidLanguageServer.is_ignored_path has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bump_version.bump_repo_version (cognitive 16) scripts/bump_version.py:119— bump_version.bump_repo_version has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LanguageServerCodeEditor._workspace_edit_to_edit_operations (cognitive 16) src/serena/code_editor.py:376— LanguageServerCodeEditor._workspace_edit_to_edit_operations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReferencedType.get_referenced_classes (cognitive 16) src/serena/repl/facade.py:131— ReferencedType.get_referenced_classes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguageServerSymbolRetriever.get_symbol_diagnostics_by_location (cognitive 16) src/serena/symbol.py:1079— LanguageServerSymbolRetriever.get_symbol_diagnostics_by_location has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskExecutor._process_task_queue (cognitive 16) src/serena/task_executor.py:126— TaskExecutor._process_task_queue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Tool.apply_ex (cognitive 16) src/serena/tools/tools_base.py:301— Tool.apply_ex has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 4 (5 pts), ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlobMatcher._expand_braces (cognitive 16) src/serena/util/text_utils.py:227— GlobMatcher._expand_braces has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
msl_lsp_server._get_workspace_roots (cognitive 16) src/solidlsp/language_servers/msl_lsp_server.py:130— msl_lsp_server._get_workspace_roots has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
msl_lsp_server.references (cognitive 16) src/solidlsp/language_servers/msl_lsp_server.py:352— msl_lsp_server.references has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (7 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolidLanguageServer.request_text_document_diagnostics (cognitive 16) REDACTED:978— SolidLanguageServer.request_text_document_diagnostics has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolidLanguageServer.request_containing_symbol (cognitive 16) REDACTED:2666— SolidLanguageServer.request_containing_symbol has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ClassTooLong: Dashboard src/serena/resources/dashboard/dashboard.js:291— ClassTooLong — 1449 significant lines (blank, comment-only and punctuation-only lines excluded), 81 methods. The bar is 400 significant lines; this is 1049 over it, 3.62× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: project.py ↔ memory_tools.py src/serena/project.py:1— `src/serena/project.py` and `src/serena/tools/memory_tools.py` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `eb43c5be` Rename MemoriesManager -> MemoryManager; `b8a5eef5` Change regex multi-line handling; `461b7ebd` Memory management: * Add renaming with auto-updated references * … — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (10 members, 10 shared lines) · ×1
Near-duplicate member family (10 members, 10 shared lines) src/solidlsp/language_servers/gopls.py:300— src/solidlsp/language_servers/gopls.py:300-328 | src/solidlsp/language_servers/intelephense.py:155-202 | src/solidlsp/language_servers/lua_ls.py:297-326 | src/solidlsp/language_servers/luau_lsp.py:328-375 | REDACTED:150-178 | REDACTED:214-246 | src/solidlsp/language_servers/powershell_language_server.py:331-388 | src/solidlsp/language_servers/terraform_ls.py:245-273 | src/solidlsp/language_servers/texlab_language_server.py:160-187 | src/solidlsp/language_servers/zls.py:173-226 — These 10 members are variants of one another: a block of 10 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 22 shared lines) · ×1
Near-duplicate member family (5 members, 22 shared lines) src/solidlsp/language_servers/crystal_language_server.py:122— src/solidlsp/language_servers/crystal_language_server.py:122-153 | src/solidlsp/language_servers/lean4_language_server.py:130-157 | src/solidlsp/language_servers/marksman.py:227-261 | src/solidlsp/language_servers/qml_language_server.py:102-129 | src/solidlsp/language_servers/sourcekit_lsp.py:309-341 — These 5 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 9 shared lines) · ×1
Near-duplicate member family (5 members, 9 shared lines) REDACTED:342— REDACTED:342-419 | src/solidlsp/language_servers/dart_language_server.py:193-242 | REDACTED:281-319 | src/solidlsp/language_servers/jedi_server.py:141-181 | src/solidlsp/language_servers/solargraph.py:291-350 — These 5 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 17 shared lines) · ×1
Near-duplicate member family (4 members, 17 shared lines) src/solidlsp/language_servers/matlab_language_server.py:400— src/solidlsp/language_servers/matlab_language_server.py:400-487 | REDACTED:885-945 | src/solidlsp/language_servers/powershell_language_server.py:331-388 | src/solidlsp/language_servers/vue_language_server.py:750-831 — These 4 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 30 shared lines) · ×1
Near-duplicate member family (3 members, 30 shared lines) REDACTED:294— REDACTED:294-392 | REDACTED:552-667 | src/solidlsp/language_servers/typescript_language_server.py:449-575 — These 3 members are variants of one another: a block of 30 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 11 shared lines) · ×1
Near-duplicate member family (3 members, 11 shared lines) src/solidlsp/language_servers/cue_language_server.py:220— src/solidlsp/language_servers/cue_language_server.py:220-260 | REDACTED:1368-1442 | src/solidlsp/language_servers/fortran_language_server.py:241-281 — These 3 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (121 shared lines) src/solidlsp/language_servers/csharp_language_server.py:551— src/solidlsp/language_servers/csharp_language_server.py:551-729 | src/solidlsp/language_servers/vbnet_language_server.py:376-519 — These two members are variants of one another: 121 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Duplicated block (64–70 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:660— src/solidlsp/language_servers/csharp_language_server.py:660-729 | src/solidlsp/language_servers/vbnet_language_server.py:456-519 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (28–34 lines × 2) REDACTED:571— REDACTED:571-598 | src/solidlsp/language_servers/typescript_language_server.py:499-532 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (31–33 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:574— src/solidlsp/language_servers/csharp_language_server.py:574-606 | src/solidlsp/language_servers/vbnet_language_server.py:390-420 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/csharp_language_server.py:570` calls `set` and `src/solidlsp/language_servers/vbnet_language_server.py:387` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (30 lines × 2) src/serena/language_backend.py:205— src/serena/language_backend.py:205-234 | src/solidlsp/ls_config.py:1103-1132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21–28 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:625— src/solidlsp/language_servers/csharp_language_server.py:625-652 | src/solidlsp/language_servers/vbnet_language_server.py:432-452 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) src/solidlsp/language_servers/ruby_lsp.py:275— src/solidlsp/language_servers/ruby_lsp.py:275-300 | src/solidlsp/language_servers/solargraph.py:204-229 — before extracting anything, compare `src/solidlsp/language_servers/ruby_lsp.py` and `src/solidlsp/language_servers/solargraph.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24–25 lines × 2) src/solidlsp/language_servers/basedpyright_server.py:124— src/solidlsp/language_servers/basedpyright_server.py:124-147 | src/solidlsp/language_servers/pyright_server.py:156-180 — before extracting anything, compare `src/solidlsp/language_servers/basedpyright_server.py` and `src/solidlsp/language_servers/pyright_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 2) src/solidlsp/language_servers/matlab_language_server.py:469— src/solidlsp/language_servers/matlab_language_server.py:469-487 | REDACTED:928-945 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17–18 lines × 2) src/solidlsp/language_servers/astro_language_server.py:221— src/solidlsp/language_servers/astro_language_server.py:221-237 | src/solidlsp/language_servers/svelte_language_server.py:219-236 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/astro_language_server.py:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–18 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:285— src/solidlsp/language_servers/csharp_language_server.py:285-302 | src/solidlsp/language_servers/vbnet_language_server.py:204-219 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15–18 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:353— src/solidlsp/language_servers/csharp_language_server.py:353-370 | src/solidlsp/language_servers/vbnet_language_server.py:273-287 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (17 lines × 8) src/solidlsp/language_servers/gopls.py:300— src/solidlsp/language_servers/gopls.py:300-316 | src/solidlsp/language_servers/intelephense.py:155-171 | src/solidlsp/language_servers/lua_ls.py:297-313 | REDACTED:150-166 | REDACTED:214-230 | src/solidlsp/language_servers/terraform_ls.py:245-261 | src/solidlsp/language_servers/texlab_language_server.py:160-176 | src/solidlsp/language_servers/zls.py:173-189 — before extracting anything, compare `src/solidlsp/language_servers/gopls.py` and `src/solidlsp/language_servers/intelephense.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–17 lines × 5) src/solidlsp/language_servers/crystal_language_server.py:122— src/solidlsp/language_servers/crystal_language_server.py:122-136 | src/solidlsp/language_servers/lean4_language_server.py:130-144 | src/solidlsp/language_servers/marksman.py:227-243 | src/solidlsp/language_servers/qml_language_server.py:102-116 | src/solidlsp/language_servers/sourcekit_lsp.py:309-323 — before extracting anything, compare `src/solidlsp/language_servers/crystal_language_server.py` and `src/solidlsp/language_servers/lean4_language_server.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/lean4_language_server.py:145` calls `on_notification` and `src/solidlsp/language_servers/crystal_language_server.py:138` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–17 lines × 3) src/solidlsp/language_servers/ansible_language_server.py:212— src/solidlsp/language_servers/ansible_language_server.py:212-228 | src/solidlsp/language_servers/json_language_server.py:80-95 | src/solidlsp/language_servers/yaml_language_server.py:92-108 — before extracting anything, compare `src/solidlsp/language_servers/ansible_language_server.py` and `src/solidlsp/language_servers/json_language_server.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 91 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/ansible_language_server.py:212` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–17 lines × 3) REDACTED:336— REDACTED:336-347 | REDACTED:582-593 | src/solidlsp/language_servers/typescript_language_server.py:511-527 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (13–17 lines × 2) src/solidlsp/language_servers/astro_language_server.py:573— src/solidlsp/language_servers/astro_language_server.py:573-585 | src/solidlsp/language_servers/svelte_language_server.py:617-633 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/solidlsp/language_servers/json_language_server.py:131— src/solidlsp/language_servers/json_language_server.py:131-146 | REDACTED:241-256 | src/solidlsp/language_servers/yaml_language_server.py:155-170 — before extracting anything, compare `src/solidlsp/language_servers/json_language_server.py` and `REDACTED` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–16 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:252— src/solidlsp/language_servers/csharp_language_server.py:252-267 | src/solidlsp/language_servers/vbnet_language_server.py:182-195 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/csharp_language_server.py:247` calls `names`, `name`, `Add` and `src/solidlsp/language_servers/vbnet_language_server.py:181` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 3) src/solidlsp/language_servers/ada_language_server.py:187— src/solidlsp/language_servers/ada_language_server.py:187-201 | src/solidlsp/language_servers/devsense_php_language_server.py:181-195 | src/solidlsp/language_servers/emmylua_ls.py:191-205 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/ada_language_server.py:202` calls `on_notification` and `src/solidlsp/language_servers/devsense_php_language_server.py:197` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14–15 lines × 2) src/solidlsp/language_servers/hlsl_language_server.py:233— src/solidlsp/language_servers/hlsl_language_server.py:233-246 | src/solidlsp/language_servers/systemverilog_server.py:201-215 — before extracting anything, compare `src/solidlsp/language_servers/hlsl_language_server.py` and `src/solidlsp/language_servers/systemverilog_server.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–15 lines × 2) REDACTED:600— REDACTED:600-614 | src/solidlsp/language_servers/typescript_language_server.py:534-543 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:600` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/typescript_language_server.py:544` calls `on_notification` and `REDACTED:615` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 9) src/solidlsp/language_servers/deno_language_server.py:138— src/solidlsp/language_servers/deno_language_server.py:138-150 | src/solidlsp/language_servers/elm_language_server.py:189-202 | src/solidlsp/language_servers/gopls.py:313-326 | src/solidlsp/language_servers/julia_server.py:189-201 | src/solidlsp/language_servers/lua_ls.py:310-323 | src/solidlsp/language_servers/luau_lsp.py:351-364 | src/solidlsp/language_servers/terraform_ls.py:258-271 | src/solidlsp/language_servers/texlab_language_server.py:173-185 | src/solidlsp/language_servers/zls.py:186-199 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 9 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/deno_language_server.py:134` calls `on_notification` and `src/solidlsp/language_servers/luau_lsp.py:349` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 3) src/solidlsp/language_servers/fortran_language_server.py:269— src/solidlsp/language_servers/fortran_language_server.py:269-281 | src/solidlsp/language_servers/matlab_language_server.py:468-481 | REDACTED:927-939 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:920` calls `debug` and `src/solidlsp/language_servers/fortran_language_server.py:264` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 2) src/solidlsp/language_servers/csharp_language_server.py:323— src/solidlsp/language_servers/csharp_language_server.py:323-336 | src/solidlsp/language_servers/vbnet_language_server.py:223-235 — before extracting anything, compare `src/solidlsp/language_servers/csharp_language_server.py` and `src/solidlsp/language_servers/vbnet_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–14 lines × 2) src/solidlsp/language_servers/matlab_language_server.py:403— src/solidlsp/language_servers/matlab_language_server.py:403-413 | src/solidlsp/language_servers/typescript_language_server.py:463-476 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10–13 lines × 3) src/solidlsp/language_servers/ada_language_server.py:202— src/solidlsp/language_servers/ada_language_server.py:202-211 | src/solidlsp/language_servers/cue_language_server.py:241-253 | REDACTED:300-309 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 3) src/solidlsp/language_servers/r_language_server.py:124— src/solidlsp/language_servers/r_language_server.py:124-136 | src/solidlsp/language_servers/regal_server.py:99-110 | src/solidlsp/language_servers/typescript_language_server.py:547-558 — before extracting anything, compare `src/solidlsp/language_servers/r_language_server.py` and `src/solidlsp/language_servers/regal_server.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–13 lines × 2) src/solidlsp/language_servers/some_sass_language_server.py:125— src/solidlsp/language_servers/some_sass_language_server.py:125-134 | src/solidlsp/language_servers/vscode_html_language_server.py:77-89 — before extracting anything, compare `src/solidlsp/language_servers/some_sass_language_server.py` and `src/solidlsp/language_servers/vscode_html_language_server.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/vscode_html_language_server.py:76` calls `get` and `src/solidlsp/language_servers/some_sass_language_server.py:123` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–13 lines × 2) src/solidlsp/language_servers/terraform_ls.py:193— src/solidlsp/language_servers/terraform_ls.py:193-205 | src/solidlsp/language_servers/texlab_language_server.py:110-120 — before extracting anything, compare `src/solidlsp/language_servers/terraform_ls.py` and `src/solidlsp/language_servers/texlab_language_server.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/terraform_ls.py:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9–12 lines × 7) src/solidlsp/language_servers/basedpyright_server.py:165— src/solidlsp/language_servers/basedpyright_server.py:165-176 | src/solidlsp/language_servers/dart_language_server.py:221-229 | src/solidlsp/language_servers/deno_language_server.py:133-142 | src/solidlsp/language_servers/erlang_language_server.py:241-249 | REDACTED:624-633 | src/solidlsp/language_servers/pyright_server.py:208-218 | src/solidlsp/language_servers/solidity_language_server.py:303-311 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:622` calls `on_request` and `src/solidlsp/language_servers/basedpyright_server.py:164` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–12 lines × 6) src/solidlsp/language_servers/fortran_language_server.py:256— src/solidlsp/language_servers/fortran_language_server.py:256-267 | src/solidlsp/language_servers/hlsl_language_server.py:229-238 | src/solidlsp/language_servers/lean4_language_server.py:145-154 | src/solidlsp/language_servers/ocaml_lsp_server.py:403-413 | src/solidlsp/language_servers/rust_analyzer.py:757-764 | src/solidlsp/language_servers/systemverilog_server.py:197-207 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/lean4_language_server.py:142` calls `on_notification` and `src/solidlsp/language_servers/fortran_language_server.py:253` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) src/solidlsp/language_servers/json_language_server.py:139— src/solidlsp/language_servers/json_language_server.py:139-150 | REDACTED:249-260 | src/solidlsp/language_servers/wolfram_language_server.py:71-82 | src/solidlsp/language_servers/yaml_language_server.py:163-174 — before extracting anything, compare `src/solidlsp/language_servers/json_language_server.py` and `REDACTED` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–11 lines × 4) src/solidlsp/language_servers/matlab_language_server.py:431— src/solidlsp/language_servers/matlab_language_server.py:431-441 | REDACTED:891-899 | src/solidlsp/language_servers/powershell_language_server.py:346-354 | src/solidlsp/language_servers/vue_language_server.py:764-771 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/powershell_language_server.py:356` calls `do_nothing` and `src/solidlsp/language_servers/matlab_language_server.py:443` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 3) src/solidlsp/language_servers/clojure_lsp.py:391— src/solidlsp/language_servers/clojure_lsp.py:391-401 | REDACTED:1410-1419 | src/solidlsp/language_servers/jedi_server.py:165-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8–10 lines × 8) src/solidlsp/language_servers/basedpyright_server.py:173— src/solidlsp/language_servers/basedpyright_server.py:173-181 | src/solidlsp/language_servers/intelephense.py:169-176 | src/solidlsp/language_servers/perl_language_server.py:194-202 | REDACTED:164-171 | REDACTED:228-236 | src/solidlsp/language_servers/powershell_language_server.py:363-370 | src/solidlsp/language_servers/pyright_server.py:215-224 | src/solidlsp/language_servers/ty_server.py:118-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 8 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/perl_language_server.py:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ty_server.py:116` calls `on_request` and `src/solidlsp/language_servers/basedpyright_server.py:171` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 5) src/solidlsp/language_servers/haskell_language_server.py:352— src/solidlsp/language_servers/haskell_language_server.py:352-361 | src/solidlsp/language_servers/hlsl_language_server.py:231-239 | src/solidlsp/language_servers/lean4_language_server.py:147-155 | src/solidlsp/language_servers/ocaml_lsp_server.py:405-414 | src/solidlsp/language_servers/systemverilog_server.py:199-208 — before extracting anything, compare `src/solidlsp/language_servers/hlsl_language_server.py` and `src/solidlsp/language_servers/lean4_language_server.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/haskell_language_server.py:349` calls `on_request` and `src/solidlsp/language_servers/lean4_language_server.py:145` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) src/solidlsp/language_servers/matlab_language_server.py:451— src/solidlsp/language_servers/matlab_language_server.py:451-460 | REDACTED:914-923 | REDACTED:259-268 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (9–10 lines × 2) src/solidlsp/language_servers/bash_language_server.py:270— src/solidlsp/language_servers/bash_language_server.py:270-279 | src/solidlsp/language_servers/vue_language_server.py:805-813 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 43) src/solidlsp/language_servers/ada_language_server.py:201— src/solidlsp/language_servers/ada_language_server.py:201-209 | src/solidlsp/language_servers/ansible_language_server.py:329-337 | src/solidlsp/language_servers/basedpyright_server.py:172-181 | src/solidlsp/language_servers/bash_language_server.py:267-275 | REDACTED:390-398 | src/solidlsp/language_servers/clojure_lsp.py:391-400 | src/solidlsp/language_servers/crystal_language_server.py:135-143 | src/solidlsp/language_servers/cue_language_server.py:240-249 | src/solidlsp/language_servers/deno_language_server.py:138-146 | REDACTED:1410-1418 | src/solidlsp/language_servers/elm_language_server.py:189-197 | src/solidlsp/language_servers/fortran_language_server.py:255-264 | src/solidlsp/language_servers/gopls.py:313-321 | REDACTED:299-307 | src/solidlsp/language_servers/hlsl_language_server.py:228-236 | src/solidlsp/language_servers/intelephense.py:168-176 | src/solidlsp/language_servers/jedi_server.py:165-173 | src/solidlsp/language_servers/json_language_server.py:146-154 | src/solidlsp/language_servers/julia_server.py:189-198 | REDACTED:629-637 | src/solidlsp/language_servers/lean4_language_server.py:144-152 | src/solidlsp/language_servers/lua_ls.py:310-318 | src/solidlsp/language_servers/luau_lsp.py:351-359 | src/solidlsp/language_servers/marksman.py:242-250 | src/solidlsp/language_servers/matlab_language_server.py:448-456 | src/solidlsp/language_servers/ocaml_lsp_server.py:402-410 | REDACTED:911-919 | src/solidlsp/language_servers/perl_language_server.py:193-201 | REDACTED:163-171 | REDACTED:227-236 | src/solidlsp/language_servers/powershell_language_server.py:362-370 | src/solidlsp/language_servers/pyright_server.py:214-224 | src/solidlsp/language_servers/qml_language_server.py:115-123 | src/solidlsp/language_servers/rust_analyzer.py:756-764 | src/solidlsp/language_servers/sourcekit_lsp.py:322-330 | src/solidlsp/language_servers/systemverilog_server.py:196-204 | REDACTED:256-264 | src/solidlsp/language_servers/terraform_ls.py:258-266 | src/solidlsp/language_servers/texlab_language_server.py:173-181 | src/solidlsp/language_servers/ty_server.py:117-126 | src/solidlsp/language_servers/vue_language_server.py:802-810 | src/solidlsp/language_servers/yaml_language_server.py:170-178 | src/solidlsp/language_servers/zls.py:186-194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 43 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ada_language_server.py:199` calls `on_notification` and `src/solidlsp/language_servers/crystal_language_server.py:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 42) src/solidlsp/language_servers/ada_language_server.py:200— src/solidlsp/language_servers/ada_language_server.py:200-208 | src/solidlsp/language_servers/al_language_server.py:553-564 | src/solidlsp/language_servers/ansible_language_server.py:328-336 | src/solidlsp/language_servers/basedpyright_server.py:171-180 | REDACTED:389-397 | src/solidlsp/language_servers/clojure_lsp.py:390-399 | src/solidlsp/language_servers/crystal_language_server.py:134-142 | src/solidlsp/language_servers/cue_language_server.py:239-248 | src/solidlsp/language_servers/deno_language_server.py:136-145 | REDACTED:1409-1417 | src/solidlsp/language_servers/fortran_language_server.py:254-262 | src/solidlsp/language_servers/gopls.py:312-320 | REDACTED:298-306 | REDACTED:364-372 | src/solidlsp/language_servers/hlsl_language_server.py:227-235 | src/solidlsp/language_servers/intelephense.py:167-175 | src/solidlsp/language_servers/jedi_server.py:164-172 | src/solidlsp/language_servers/json_language_server.py:145-153 | src/solidlsp/language_servers/julia_server.py:188-196 | REDACTED:628-636 | src/solidlsp/language_servers/lean4_language_server.py:143-151 | src/solidlsp/language_servers/lua_ls.py:309-317 | src/solidlsp/language_servers/luau_lsp.py:350-358 | src/solidlsp/language_servers/marksman.py:241-249 | src/solidlsp/language_servers/ocaml_lsp_server.py:401-409 | REDACTED:910-918 | src/solidlsp/language_servers/perl_language_server.py:192-200 | REDACTED:162-170 | REDACTED:226-235 | src/solidlsp/language_servers/powershell_language_server.py:361-369 | src/solidlsp/language_servers/pyright_server.py:213-223 | src/solidlsp/language_servers/qml_language_server.py:114-122 | src/solidlsp/language_servers/rust_analyzer.py:755-763 | src/solidlsp/language_servers/solargraph.py:322-330 | src/solidlsp/language_servers/sourcekit_lsp.py:321-329 | src/solidlsp/language_servers/systemverilog_server.py:195-203 | REDACTED:255-263 | src/solidlsp/language_servers/terraform_ls.py:257-265 | src/solidlsp/language_servers/texlab_language_server.py:172-180 | src/solidlsp/language_servers/vue_language_server.py:801-809 | src/solidlsp/language_servers/yaml_language_server.py:169-177 | src/solidlsp/language_servers/zls.py:185-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 42 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ada_language_server.py:199` calls `on_notification` and `src/solidlsp/language_servers/crystal_language_server.py:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 41) src/solidlsp/language_servers/ada_language_server.py:200— src/solidlsp/language_servers/ada_language_server.py:200-208 | src/solidlsp/language_servers/al_language_server.py:553-564 | src/solidlsp/language_servers/ansible_language_server.py:328-336 | src/solidlsp/language_servers/basedpyright_server.py:171-180 | REDACTED:389-397 | src/solidlsp/language_servers/clojure_lsp.py:390-399 | src/solidlsp/language_servers/crystal_language_server.py:134-142 | src/solidlsp/language_servers/cue_language_server.py:239-248 | src/solidlsp/language_servers/deno_language_server.py:136-145 | REDACTED:1409-1417 | src/solidlsp/language_servers/elm_language_server.py:188-196 | src/solidlsp/language_servers/fortran_language_server.py:254-262 | src/solidlsp/language_servers/gopls.py:312-320 | REDACTED:298-306 | src/solidlsp/language_servers/hlsl_language_server.py:227-235 | src/solidlsp/language_servers/intelephense.py:167-175 | src/solidlsp/language_servers/jedi_server.py:164-172 | src/solidlsp/language_servers/json_language_server.py:145-153 | src/solidlsp/language_servers/julia_server.py:188-196 | REDACTED:628-636 | src/solidlsp/language_servers/lean4_language_server.py:143-151 | src/solidlsp/language_servers/lua_ls.py:309-317 | src/solidlsp/language_servers/luau_lsp.py:350-358 | src/solidlsp/language_servers/marksman.py:241-249 | src/solidlsp/language_servers/ocaml_lsp_server.py:401-409 | REDACTED:910-918 | src/solidlsp/language_servers/perl_language_server.py:192-200 | REDACTED:162-170 | REDACTED:226-235 | src/solidlsp/language_servers/powershell_language_server.py:361-369 | src/solidlsp/language_servers/pyright_server.py:213-223 | src/solidlsp/language_servers/qml_language_server.py:114-122 | src/solidlsp/language_servers/rust_analyzer.py:755-763 | src/solidlsp/language_servers/sourcekit_lsp.py:321-329 | src/solidlsp/language_servers/systemverilog_server.py:195-203 | REDACTED:255-263 | src/solidlsp/language_servers/terraform_ls.py:257-265 | src/solidlsp/language_servers/texlab_language_server.py:172-180 | src/solidlsp/language_servers/vue_language_server.py:801-809 | src/solidlsp/language_servers/yaml_language_server.py:169-177 | src/solidlsp/language_servers/zls.py:185-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 41 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ada_language_server.py:199` calls `on_notification` and `src/solidlsp/language_servers/crystal_language_server.py:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–9 lines × 30) src/solidlsp/language_servers/ansible_language_server.py:328— src/solidlsp/language_servers/ansible_language_server.py:328-334 | src/solidlsp/language_servers/crystal_language_server.py:134-140 | src/solidlsp/language_servers/cue_language_server.py:239-246 | REDACTED:1409-1415 | src/solidlsp/language_servers/fortran_language_server.py:254-261 | src/solidlsp/language_servers/gopls.py:312-318 | REDACTED:298-304 | REDACTED:364-370 | src/solidlsp/language_servers/hlsl_language_server.py:227-233 | src/solidlsp/language_servers/intelephense.py:167-173 | src/solidlsp/language_servers/json_language_server.py:145-151 | src/solidlsp/language_servers/julia_server.py:188-195 | src/solidlsp/language_servers/lua_ls.py:309-315 | src/solidlsp/language_servers/luau_lsp.py:350-356 | src/solidlsp/language_servers/marksman.py:241-247 | src/solidlsp/language_servers/perl_language_server.py:192-198 | REDACTED:162-168 | REDACTED:226-232 | src/solidlsp/language_servers/qml_language_server.py:114-120 | src/solidlsp/language_servers/r_language_server.py:124-132 | src/solidlsp/language_servers/regal_server.py:99-107 | src/solidlsp/language_servers/solargraph.py:322-328 | src/solidlsp/language_servers/sourcekit_lsp.py:321-327 | src/solidlsp/language_servers/systemverilog_server.py:195-201 | REDACTED:255-261 | src/solidlsp/language_servers/terraform_ls.py:257-263 | src/solidlsp/language_servers/texlab_language_server.py:172-178 | src/solidlsp/language_servers/typescript_language_server.py:547-555 | src/solidlsp/language_servers/yaml_language_server.py:169-175 | src/solidlsp/language_servers/zls.py:185-191 — before extracting anything, compare `src/solidlsp/language_servers/ansible_language_server.py` and `src/solidlsp/language_servers/crystal_language_server.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/r_language_server.py:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:295` calls `on_notification` and `src/solidlsp/language_servers/ansible_language_server.py:326` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 18) src/solidlsp/language_servers/ansible_language_server.py:329— src/solidlsp/language_servers/ansible_language_server.py:329-337 | src/solidlsp/language_servers/basedpyright_server.py:172-181 | src/solidlsp/language_servers/bash_language_server.py:267-275 | src/solidlsp/language_servers/intelephense.py:168-176 | src/solidlsp/language_servers/json_language_server.py:146-154 | src/solidlsp/language_servers/marksman.py:242-250 | src/solidlsp/language_servers/matlab_language_server.py:448-456 | src/solidlsp/language_servers/msl_language_server.py:82-90 | REDACTED:911-919 | src/solidlsp/language_servers/perl_language_server.py:193-201 | REDACTED:163-171 | REDACTED:227-236 | src/solidlsp/language_servers/powershell_language_server.py:362-370 | src/solidlsp/language_servers/pyright_server.py:214-224 | REDACTED:256-264 | src/solidlsp/language_servers/ty_server.py:117-126 | src/solidlsp/language_servers/vue_language_server.py:802-810 | src/solidlsp/language_servers/yaml_language_server.py:170-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 18 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/bash_language_server.py:266` calls `on_request` and `src/solidlsp/language_servers/ansible_language_server.py:328` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 16) src/solidlsp/language_servers/crystal_language_server.py:131— src/solidlsp/language_servers/crystal_language_server.py:131-139 | src/solidlsp/language_servers/devsense_php_language_server.py:190-198 | src/solidlsp/language_servers/fortran_language_server.py:250-259 | src/solidlsp/language_servers/gopls.py:309-317 | src/solidlsp/language_servers/intelephense.py:164-172 | src/solidlsp/language_servers/lua_ls.py:306-314 | src/solidlsp/language_servers/marksman.py:238-246 | REDACTED:159-167 | REDACTED:223-231 | src/solidlsp/language_servers/qml_language_server.py:111-119 | src/solidlsp/language_servers/r_language_server.py:120-129 | src/solidlsp/language_servers/regal_server.py:96-104 | src/solidlsp/language_servers/sourcekit_lsp.py:318-326 | src/solidlsp/language_servers/terraform_ls.py:254-262 | src/solidlsp/language_servers/texlab_language_server.py:169-177 | src/solidlsp/language_servers/zls.py:182-190 — before extracting anything, compare `src/solidlsp/language_servers/crystal_language_server.py` and `src/solidlsp/language_servers/fortran_language_server.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/crystal_language_server.py:142` calls `info` and `src/solidlsp/language_servers/devsense_php_language_server.py:200` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 15) src/solidlsp/language_servers/crystal_language_server.py:131— src/solidlsp/language_servers/crystal_language_server.py:131-139 | src/solidlsp/language_servers/devsense_php_language_server.py:190-198 | src/solidlsp/language_servers/emmylua_ls.py:200-208 | src/solidlsp/language_servers/fortran_language_server.py:250-259 | src/solidlsp/language_servers/gopls.py:309-317 | src/solidlsp/language_servers/intelephense.py:164-172 | src/solidlsp/language_servers/lua_ls.py:306-314 | src/solidlsp/language_servers/marksman.py:238-246 | REDACTED:159-167 | REDACTED:223-231 | src/solidlsp/language_servers/qml_language_server.py:111-119 | src/solidlsp/language_servers/sourcekit_lsp.py:318-326 | src/solidlsp/language_servers/terraform_ls.py:254-262 | src/solidlsp/language_servers/texlab_language_server.py:169-177 | src/solidlsp/language_servers/zls.py:182-190 — before extracting anything, compare `src/solidlsp/language_servers/crystal_language_server.py` and `src/solidlsp/language_servers/fortran_language_server.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/crystal_language_server.py:142` calls `info` and `src/solidlsp/language_servers/devsense_php_language_server.py:200` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 9) REDACTED:1399— REDACTED:1399-1407 | src/solidlsp/language_servers/gopls.py:305-313 | src/solidlsp/language_servers/intelephense.py:160-168 | src/solidlsp/language_servers/lua_ls.py:302-310 | REDACTED:155-163 | REDACTED:219-227 | src/solidlsp/language_servers/terraform_ls.py:250-258 | src/solidlsp/language_servers/texlab_language_server.py:165-173 | src/solidlsp/language_servers/zls.py:178-186 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 9 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:1408` calls `on_request`, `on_notification` and `src/solidlsp/language_servers/gopls.py:314` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 32) src/solidlsp/language_servers/ansible_language_server.py:327— src/solidlsp/language_servers/ansible_language_server.py:327-334 | src/solidlsp/language_servers/crystal_language_server.py:133-140 | src/solidlsp/language_servers/cue_language_server.py:238-246 | src/solidlsp/language_servers/devsense_php_language_server.py:192-199 | REDACTED:1408-1415 | src/solidlsp/language_servers/fortran_language_server.py:253-261 | src/solidlsp/language_servers/gopls.py:311-318 | REDACTED:297-304 | REDACTED:363-370 | src/solidlsp/language_servers/hlsl_language_server.py:226-233 | src/solidlsp/language_servers/intelephense.py:166-173 | src/solidlsp/language_servers/json_language_server.py:144-151 | src/solidlsp/language_servers/julia_server.py:187-195 | src/solidlsp/language_servers/lua_ls.py:308-315 | src/solidlsp/language_servers/luau_lsp.py:349-356 | src/solidlsp/language_servers/marksman.py:240-247 | src/solidlsp/language_servers/perl_language_server.py:191-198 | REDACTED:161-168 | REDACTED:225-232 | src/solidlsp/language_servers/qml_language_server.py:113-120 | src/solidlsp/language_servers/r_language_server.py:123-131 | src/solidlsp/language_servers/regal_server.py:98-105 | src/solidlsp/language_servers/solargraph.py:321-328 | src/solidlsp/language_servers/sourcekit_lsp.py:320-327 | src/solidlsp/language_servers/systemverilog_server.py:194-201 | REDACTED:254-261 | src/solidlsp/language_servers/terraform_ls.py:256-263 | src/solidlsp/language_servers/texlab_language_server.py:171-178 | src/solidlsp/language_servers/typescript_language_server.py:546-553 | src/solidlsp/language_servers/wolfram_language_server.py:76-84 | src/solidlsp/language_servers/yaml_language_server.py:168-175 | src/solidlsp/language_servers/zls.py:184-191 — before extracting anything, compare `src/solidlsp/language_servers/ansible_language_server.py` and `src/solidlsp/language_servers/crystal_language_server.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ansible_language_server.py:323` calls `window_log_message`, `info`, `on_request` and `src/solidlsp/language_servers/crystal_language_server.py:131` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 17) src/solidlsp/language_servers/ada_language_server.py:199— src/solidlsp/language_servers/ada_language_server.py:199-207 | src/solidlsp/language_servers/al_language_server.py:552-562 | src/solidlsp/language_servers/basedpyright_server.py:170-178 | REDACTED:388-395 | src/solidlsp/language_servers/clojure_lsp.py:389-397 | src/solidlsp/language_servers/dart_language_server.py:223-230 | src/solidlsp/language_servers/deno_language_server.py:135-143 | src/solidlsp/language_servers/jedi_server.py:163-170 | REDACTED:627-634 | src/solidlsp/language_servers/lean4_language_server.py:142-149 | src/solidlsp/language_servers/ocaml_lsp_server.py:400-407 | REDACTED:909-916 | src/solidlsp/language_servers/powershell_language_server.py:360-367 | src/solidlsp/language_servers/pyright_server.py:212-221 | src/solidlsp/language_servers/rust_analyzer.py:754-761 | src/solidlsp/language_servers/solidity_language_server.py:305-313 | src/solidlsp/language_servers/vue_language_server.py:800-807 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 17 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/basedpyright_server.py:182` calls `info` and `src/solidlsp/language_servers/deno_language_server.py:148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 11) src/solidlsp/language_servers/ansible_language_server.py:326— src/solidlsp/language_servers/ansible_language_server.py:326-333 | src/solidlsp/language_servers/cue_language_server.py:237-244 | src/solidlsp/language_servers/fatou_language_server.py:96-103 | REDACTED:362-369 | src/solidlsp/language_servers/hlsl_language_server.py:225-232 | src/solidlsp/language_servers/luau_lsp.py:348-355 | src/solidlsp/language_servers/nextflow_language_server.py:269-276 | src/solidlsp/language_servers/nixd_ls.py:430-437 | src/solidlsp/language_servers/perl_language_server.py:190-197 | src/solidlsp/language_servers/typescript_language_server.py:545-552 | src/solidlsp/language_servers/vts_language_server.py:210-217 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 11 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ansible_language_server.py:323` calls `window_log_message`, `info` and `src/solidlsp/language_servers/luau_lsp.py:346` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 6) REDACTED:289— REDACTED:289-296 | src/solidlsp/language_servers/json_language_server.py:139-146 | src/solidlsp/language_servers/solargraph.py:313-320 | REDACTED:249-256 | src/solidlsp/language_servers/wolfram_language_server.py:71-78 | src/solidlsp/language_servers/yaml_language_server.py:163-170 — before extracting anything, compare `REDACTED` and `src/solidlsp/language_servers/json_language_server.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:297` calls `on_request`, `on_notification` and `src/solidlsp/language_servers/json_language_server.py:147` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) src/solidlsp/language_servers/ada_language_server.py:195— src/solidlsp/language_servers/ada_language_server.py:195-202 | src/solidlsp/language_servers/erlang_language_server.py:238-245 | REDACTED:905-912 | src/solidlsp/language_servers/powershell_language_server.py:356-363 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/erlang_language_server.py:246` calls `on_notification` and `src/solidlsp/language_servers/ada_language_server.py:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 3) src/solidlsp/language_servers/astro_language_server.py:391— src/solidlsp/language_servers/astro_language_server.py:391-397 | src/solidlsp/language_servers/svelte_language_server.py:408-414 | src/solidlsp/language_servers/vue_language_server.py:723-730 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 45) src/solidlsp/language_servers/ada_language_server.py:200— src/solidlsp/language_servers/ada_language_server.py:200-207 | src/solidlsp/language_servers/al_language_server.py:553-562 | src/solidlsp/language_servers/ansible_language_server.py:328-334 | src/solidlsp/language_servers/basedpyright_server.py:171-178 | REDACTED:389-395 | src/solidlsp/language_servers/clojure_lsp.py:390-397 | src/solidlsp/language_servers/crystal_language_server.py:134-140 | src/solidlsp/language_servers/cue_language_server.py:239-246 | src/solidlsp/language_servers/deno_language_server.py:136-143 | REDACTED:1409-1415 | src/solidlsp/language_servers/fortran_language_server.py:254-261 | src/solidlsp/language_servers/gopls.py:312-318 | REDACTED:298-304 | REDACTED:364-370 | src/solidlsp/language_servers/hlsl_language_server.py:227-233 | src/solidlsp/language_servers/intelephense.py:167-173 | src/solidlsp/language_servers/jedi_server.py:164-170 | src/solidlsp/language_servers/json_language_server.py:145-151 | src/solidlsp/language_servers/julia_server.py:188-195 | REDACTED:628-634 | src/solidlsp/language_servers/lean4_language_server.py:143-149 | src/solidlsp/language_servers/lua_ls.py:309-315 | src/solidlsp/language_servers/luau_lsp.py:350-356 | src/solidlsp/language_servers/marksman.py:241-247 | src/solidlsp/language_servers/ocaml_lsp_server.py:401-407 | REDACTED:910-916 | src/solidlsp/language_servers/perl_language_server.py:192-198 | REDACTED:162-168 | REDACTED:226-232 | src/solidlsp/language_servers/powershell_language_server.py:361-367 | src/solidlsp/language_servers/pyright_server.py:213-221 | src/solidlsp/language_servers/qml_language_server.py:114-120 | src/solidlsp/language_servers/r_language_server.py:124-132 | src/solidlsp/language_servers/regal_server.py:99-107 | src/solidlsp/language_servers/rust_analyzer.py:755-761 | src/solidlsp/language_servers/solargraph.py:322-328 | src/solidlsp/language_servers/sourcekit_lsp.py:321-327 | src/solidlsp/language_servers/systemverilog_server.py:195-201 | REDACTED:255-261 | src/solidlsp/language_servers/terraform_ls.py:257-263 | src/solidlsp/language_servers/texlab_language_server.py:172-178 | src/solidlsp/language_servers/typescript_language_server.py:547-555 | src/solidlsp/language_servers/vue_language_server.py:801-807 | src/solidlsp/language_servers/yaml_language_server.py:169-175 | src/solidlsp/language_servers/zls.py:185-191 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 45 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/solidlsp/language_servers/r_language_server.py:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/solidlsp/language_servers/ada_language_server.py:199` calls `on_notification` and `src/solidlsp/language_servers/crystal_language_server.py:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 11) src/solidlsp/language_servers/ansible_language_server.py:327— src/solidlsp/language_servers/ansible_language_server.py:327-333 | src/solidlsp/language_servers/cue_language_server.py:238-244 | REDACTED:1408-1414 | src/solidlsp/language_servers/fatou_language_server.py:97-103 | REDACTED:297-303 | REDACTED:363-369 | src/solidlsp/language_servers/hlsl_language_server.py:226-232 | src/solidlsp/language_servers/luau_lsp.py:349-355 | src/solidlsp/language_servers/perl_language_server.py:191-197 | src/solidlsp/language_servers/solargraph.py:321-327 | src/solidlsp/language_servers/typescript_language_server.py:546-552 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 11 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:295` calls `on_notification` and `src/solidlsp/language_servers/ansible_language_server.py:326` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 12) src/solidlsp/language_servers/basedpyright_server.py:162— src/solidlsp/language_servers/basedpyright_server.py:162-168 | REDACTED:384-389 | src/solidlsp/language_servers/clojure_lsp.py:385-390 | src/solidlsp/language_servers/dart_language_server.py:218-223 | REDACTED:1405-1410 | REDACTED:294-299 | src/solidlsp/language_servers/jedi_server.py:159-164 | REDACTED:265-270 | src/solidlsp/language_servers/pyright_server.py:205-210 | src/solidlsp/language_servers/rust_analyzer.py:750-755 | src/solidlsp/language_servers/solargraph.py:318-323 | src/solidlsp/language_servers/ty_server.py:113-118 — before extracting anything, compare `src/solidlsp/language_servers/basedpyright_server.py` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:263` calls `on_request` and `src/solidlsp/language_servers/basedpyright_server.py:160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 8) src/solidlsp/language_servers/basedpyright_server.py:164— src/solidlsp/language_servers/basedpyright_server.py:164-170 | REDACTED:386-391 | src/solidlsp/language_servers/clojure_lsp.py:387-392 | src/solidlsp/language_servers/dart_language_server.py:220-225 | src/solidlsp/language_servers/jedi_server.py:161-166 | src/solidlsp/language_servers/omnisharp.py:385-390 | src/solidlsp/language_servers/pyright_server.py:207-212 | src/solidlsp/language_servers/rust_analyzer.py:752-757 — before extracting anything, compare `src/solidlsp/language_servers/basedpyright_server.py` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/solidlsp/language_servers/basedpyright_server.py:171` calls `on_notification` and `REDACTED:393` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 5) src/solidlsp/language_servers/astro_language_server.py:549— src/solidlsp/language_servers/astro_language_server.py:549-554 | src/solidlsp/language_servers/csharp_language_server.py:671-676 | src/solidlsp/language_servers/fsharp_language_server.py:406-411 | src/solidlsp/language_servers/svelte_language_server.py:592-597 | src/solidlsp/language_servers/vbnet_language_server.py:466-471 — before extracting anything, compare `src/solidlsp/language_servers/astro_language_server.py` and `src/solidlsp/language_servers/svelte_language_server.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) src/solidlsp/language_servers/angular_language_server.py:207— src/solidlsp/language_servers/angular_language_server.py:207-212 | src/solidlsp/language_servers/astro_language_server.py:160-165 | src/solidlsp/language_servers/svelte_language_server.py:150-155 | src/solidlsp/language_servers/vue_language_server.py:145-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
Third-party script without Subresource Integrity src/serena/resources/dashboard/index.html:16— `https://cdn.jsdelivr.net/npm/chart.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. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup.
README/code drift README.md:1— README claims Serena is an IDE with semantic retrieval/editing/refactoring tools but the repository contains only a single project (TestProject) and no code-querying or editing features — searched for: `code querying`, `symbol-level editing`, `semantic refactoring`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift README.md:1— The README describes a new REPL-based agent interface, but there is no such feature in the evidence — searched for: `REPL-based agent interface`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift docs/index.md:2— docs/index.md links to `01-about/000_intro.html`, but `docs/01-about/000_intro.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:16— docs/01-about/020_programming-languages.md links to `025_features`, but `docs/01-about/025_features` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:60— docs/01-about/020_programming-languages.md links to `../03-special-guides/cpp_setup`, but `docs/03-special-guides/cpp_setup` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:61— docs/01-about/020_programming-languages.md links to `../03-special-guides/unreal_engine_setup_guide_for_serena`, but `docs/03-special-guides/unreal_engine_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:82— docs/01-about/020_programming-languages.md links to `../03-special-guides/godot_gdscript_setup_guide_for_serena`, but `docs/03-special-guides/godot_gdscript_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:89— docs/01-about/020_programming-languages.md links to `../03-special-guides/groovy_setup_guide_for_serena`, but `docs/03-special-guides/groovy_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:168— docs/01-about/020_programming-languages.md links to `../03-special-guides/scala_setup_guide_for_serena`, but `docs/03-special-guides/scala_setup_guide_for_serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:174— docs/01-about/020_programming-languages.md names `hardhat.config.js`, but no file or folder `hardhat.config.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:186— docs/01-about/020_programming-languages.md names TypeScript 7, but the manifest declares `typescript` ~5.5.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/020_programming-languages.md:234— docs/01-about/020_programming-languages.md links to `../02-usage/025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-about/070_privacy.md:14— docs/01-about/070_privacy.md links to `contexts`, but `docs/01-about/contexts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/010_installation.md:14— docs/02-usage/010_installation.md links to `language-servers`, but `docs/02-usage/language-servers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/010_installation.md:32— docs/02-usage/010_installation.md links to `025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/010_installation.md:34— docs/02-usage/010_installation.md links to `050_configuration`, but `docs/02-usage/050_configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/010_installation.md:43— docs/02-usage/010_installation.md links to `060_dashboard`, but `docs/02-usage/060_dashboard` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:9— docs/02-usage/020_running.md links to `install-serena`, but `docs/02-usage/install-serena` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:30— docs/02-usage/020_running.md links to `025_jetbrains_plugin`, but `docs/02-usage/025_jetbrains_plugin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:77— docs/02-usage/020_running.md links to `040_workflow`, but `docs/02-usage/040_workflow` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:101— docs/02-usage/020_running.md links to `contexts`, but `docs/02-usage/contexts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:102— docs/02-usage/020_running.md links to `modes`, but `docs/02-usage/modes` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/020_running.md:194— docs/02-usage/020_running.md links to `010_installation`, but `docs/02-usage/010_installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/025_jetbrains_plugin.md:23— docs/02-usage/025_jetbrains_plugin.md links to `configure-jetbrains`, but `docs/02-usage/configure-jetbrains` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-usage/025_jetbrains_plugin.md:24— docs/02-usage/025_jetbrains_plugin.md links to `jetbrains-workflow`, but `docs/02-usage/jetbrains-workflow` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate src/solidlsp/language_servers/csharp_language_server.py:617— `"enable" in section or "show" in section or "suppress" in section or "navigate" in section` appears character-identically in 2 files — src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/ruby_lsp.py:295— `"gem 'rails'" in content or 'gem "rails"' in content` appears character-identically in 2 files — src/solidlsp/language_servers/ruby_lsp.py, src/solidlsp/language_servers/solargraph.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:897— `"initialized" in message_text.lower() or "ready" in message_text.lower()` appears character-identically in 2 files — REDACTED, src/solidlsp/language_servers/vue_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/csharp_language_server.py:634— `"location" in section or "behavior" in section` appears character-identically in 2 files — src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/astro_language_server.py:325— `"node_modules" not in relative and not relative.startswith(".")` appears character-identically in 2 files — src/solidlsp/language_servers/astro_language_server.py, src/solidlsp/language_servers/svelte_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/astro_language_server.py:614— `_is_ts_file(relative_file_path) and self._ts_server is not None` appears character-identically in 2 files — src/solidlsp/language_servers/astro_language_server.py, src/solidlsp/language_servers/svelte_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/ruby_lsp.py:214— `bundle_full_path and os.path.exists(bundle_full_path)` appears character-identically in 2 files — src/solidlsp/language_servers/ruby_lsp.py, src/solidlsp/language_servers/solargraph.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/serena/language_backend.py:219— `distribution.name or "unknown distribution"` appears character-identically in 2 files — src/serena/language_backend.py, src/solidlsp/ls_config.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/csharp_language_server.py:180— `filename.endswith((".sln", ".slnx")) and sln_file is None` appears character-identically in 2 files — src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/ccls_language_server.py:76— `is_unreal_engine_project(self.repository_root_path) and dirname in UE_IGNORED_DIRNAMES` appears character-identically in 2 files — src/solidlsp/language_servers/ccls_language_server.py, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/al_language_server.py:1074— `isinstance(contents, dict) and "value" in contents` appears character-identically in 3 files — src/solidlsp/language_servers/al_language_server.py, src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/julia_server.py:72— `os.path.isfile(location) and os.access(location, os.X_OK)` appears character-identically in 2 files — src/solidlsp/language_servers/julia_server.py, src/solidlsp/language_servers/wolfram_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/ocaml_lsp_server.py:388— `params.get("type") == "ServiceReady" and params.get("message") == "ServiceReady"` appears character-identically in 2 files — src/solidlsp/language_servers/ocaml_lsp_server.py, src/solidlsp/language_servers/rust_analyzer.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:368— `params["type"] == "ServiceReady" and params["message"] == "ServiceReady"` appears character-identically in 3 files — REDACTED, src/solidlsp/language_servers/clojure_lsp.py, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/haskell_language_server.py:61— `path and os.path.isfile(path) and os.access(path, os.X_OK)` appears character-identically in 2 files — src/solidlsp/language_servers/haskell_language_server.py, src/solidlsp/language_servers/rust_analyzer.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/csharp_language_server.py:640— `section == "tab_width" or section == "indent_size"` appears character-identically in 2 files — src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/astro_language_server.py:444— `self._ts_server is None or not self._ts_server_started` appears character-identically in 2 files — src/solidlsp/language_servers/astro_language_server.py, src/solidlsp/language_servers/vue_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/al_language_server.py:1039— `start and "line" in start and "character" in start` appears character-identically in 3 files — src/solidlsp/language_servers/al_language_server.py, src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/typescript_language_server.py:293— `super().is_ignored_dirname(dirname) or dirname in [ "node_modules", "dist", "build", ]` appears character-identically in 2 files — src/solidlsp/language_servers/typescript_language_server.py, src/solidlsp/language_servers/vts_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/fatou_language_server.py:47— `super().is_ignored_dirname(dirname) or dirname in [".julia", "build", "dist"]` appears character-identically in 2 files — src/solidlsp/language_servers/fatou_language_server.py, src/solidlsp/language_servers/julia_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/emmylua_ls.py:137— `super().is_ignored_dirname(dirname) or dirname in [".luarocks", "lua_modules", "node_modules", "build", "dist", ".cache"]` appears character-identically in 2 files — src/solidlsp/language_servers/emmylua_ls.py, src/solidlsp/language_servers/lua_ls.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/csharp_language_server.py:242— `super().is_ignored_dirname(dirname) or dirname in ["bin", "obj", "packages", ".vs"]` appears character-identically in 2 files — src/solidlsp/language_servers/csharp_language_server.py, src/solidlsp/language_servers/vbnet_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/some_sass_language_server.py:118— `super().is_ignored_dirname(dirname) or dirname in ["node_modules", "dist", "build", "coverage"]` appears character-identically in 2 files — src/solidlsp/language_servers/some_sass_language_server.py, src/solidlsp/language_servers/vscode_html_language_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/basedpyright_server.py:56— `super().is_ignored_dirname(dirname) or dirname in ["venv", "__pycache__"]` appears character-identically in 5 files — src/solidlsp/language_servers/basedpyright_server.py, src/solidlsp/language_servers/jedi_server.py, REDACTED, src/solidlsp/language_servers/pyright_server.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/solidlsp/language_servers/ruby_lsp.py:73— `super().is_ignored_dirname(dirname) or dirname in ruby_ignored_dirs` appears character-identically in 2 files — src/solidlsp/language_servers/ruby_lsp.py, src/solidlsp/language_servers/solargraph.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×5
Diagnostic log message is built whether or not it is wanted src/serena/project.py:103— `debug` at line 103 is called with an argument built by `list(global_ignored_paths)` (line 103), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted src/solidlsp/language_servers/vbnet_language_server.py:285— `debug` at line 285 is called with an argument built by `"…".join(cmd)` (line 285), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted src/solidlsp/language_servers/gopls.py:147— `debug` at line 147 is called with an argument built by `list(gopls_settings.keys())` (line 147), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted src/solidlsp/language_servers/csharp_language_server.py:368— `debug` at line 368 is called with an argument built by `"…".join(cmd)` (line 368), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted src/solidlsp/language_servers/ansible_language_server.py:340— `debug` at line 340 is called with an argument built by `list(init_response["…"].keys())` (line 340), whose cost grows with the collection it walks. Python 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 `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Orphaned file src/solidlsp/language_servers/msl_lsp_server.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/solidlsp/util/metals_db_utils.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/solidlsp/language_servers/crystal_language_server.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/solidlsp/language_servers/msl_language_server.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 23 significant file(s) lose their only recent owner: src/serena/repl/api/lsp_api.py, src/serena/repl/facade.py, src/serena/repl/api/jb_api.py, src/solidlsp/ls_request.py, REDACTED, src/serena/gui_log_viewer.py, src/serena/lsp/lsp_diagnostics.py, src/serena/language_backend.py (+15 more). Pair on, review, or document these before any departure.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 162 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 162 of the 202 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/solidlsp/language_servers/msl_lsp_server.py, src/solidlsp/util/metals_db_utils.py, src/solidlsp/language_servers/crystal_language_server.py, src/solidlsp/language_servers/msl_language_server.py. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — 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.
Hand-rolled JSON/XML parsing via regex docs/autogen_docs.py:264— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Silent fallback default in catch src/serena/repl/facade.py:83— `get_annotated_classes` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
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.
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.
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.
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.
Run 01a15a4c-4470-71d8-9d40-039731f404f7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 80 · Warnings: 332 · Recommendations: 96 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 20-10-2026 @ 17:11 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.