Public report of devoxx/DevoxxGenieIDEAPlugin, published 17 November 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.11.4). Assert 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, 17 November 2026, 06:38 UTC · Survey ID cd_97d241e426694c74afe3cced1b4b0fdf
devoxx/DevoxxGenieIDEAPlugin
Measured 17 November 2026, 06:38 UTC, at code version af3e772
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt risk
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: 72,471 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Code Health, 41.7
Findings by how serious they are
34 critical520 serious149 minor
15 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 06:38 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer 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. We work 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 ▸
70of 70 dimensions measured by tools.
697of 703 findings point to an exact file and line, so you can open each one in the code. The other 6 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 72,471 lines of product code in 2 projects.
devoxx/DevoxxGenieIDEAPlugin is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 49.7 out of 100, which the At risk rating leaves unchanged.
Code Health, at 41.7, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 5.2 points. Adding type checking would lift Code Health itself, worth about 3.6 points. Raising Code Health to 70 would lift the score to about 55.2.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline, and three passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version, limiting each secret to its own step and replacing each exposed password or key would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The page that doesn't say its language needs its language set.
The product code is 72,471 lines, about €130,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.
If Code Health rose from 41.7 to 70, the lowest score rated Strong, the score would rise from 49.7 to about 55.2.
Code composition: what the lines of code are
Product code 53%Tests 47%
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€42,000 to €210,000, for 708 to 2,246 hours of work, about 0.9 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 50. 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: 72,471 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 5.2 points · Low effort · Secret Scanning
2
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 3.6 points · Medium effort · Type Safety
3
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.
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 €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Code Health, at 41.7 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5.2 points for low effort, because it clears the 3 Secret Scanning findings. 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.
182 modules, with 335 dependencies between them. 2 loops run through 34 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 142 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.
chatmodel.catalog uses model.enumarations, so a change to model.enumarations can break chatmodel.catalog, while a change to chatmodel.catalog can't break model.enumarations.
Position
Below the diagonal: chatmodel.catalog uses a module listed above it, which is the healthy direction.
chatmodel.cloud.router uses model.enumarations, so a change to model.enumarations can break chatmodel.cloud.router, while a change to chatmodel.cloud.router can't break model.enumarations.
Position
Below the diagonal: chatmodel.cloud.router uses a module listed above it, which is the healthy direction.
chatmodel.cloud.router uses chatmodel.catalog, so a change to chatmodel.catalog can break chatmodel.cloud.router, while a change to chatmodel.cloud.router can't break chatmodel.catalog.
Position
Below the diagonal: chatmodel.cloud.router uses a module listed above it, which is the healthy direction.
14→38 chatmodel.cloud.router uses chatmodelpart of a loop✕
Connections
1 pair of types, where a type in chatmodel.cloud.router uses a type in chatmodel.
chatmodel.cloud.router uses chatmodel, so a change to chatmodel can break chatmodel.cloud.router, while a change to chatmodel.cloud.router can't break chatmodel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.listener uses model.conversation, so a change to model.conversation can break ui.listener, while a change to ui.listener can't break model.conversation.
Position
Below the diagonal: ui.listener uses a module listed above it, which is the healthy direction.
ui.panel.conversation uses model.conversation, so a change to model.conversation can break ui.panel.conversation, while a change to ui.panel.conversation can't break model.conversation.
Position
Below the diagonal: ui.panel.conversation uses a module listed above it, which is the healthy direction.
ui.panel.conversation uses model.activity, so a change to model.activity can break ui.panel.conversation, while a change to ui.panel.conversation can't break model.activity.
Position
Below the diagonal: ui.panel.conversation uses a module listed above it, which is the healthy direction.
ui.panel.conversation uses ui.compose, so a change to ui.compose can break ui.panel.conversation, while a change to ui.panel.conversation can't break ui.compose.
Position
Below the diagonal: ui.panel.conversation uses a module listed above it, which is the healthy direction.
ui.panel.conversation uses model.request, so a change to model.request can break ui.panel.conversation, while a change to ui.panel.conversation can't break model.request.
Position
Below the diagonal: ui.panel.conversation uses a module listed above it, which is the healthy direction.
ui.panel.conversation uses ui.listener, so a change to ui.listener can break ui.panel.conversation, while a change to ui.panel.conversation can't break ui.listener.
Position
Below the diagonal: ui.panel.conversation uses a module listed above it, which is the healthy direction.
16→35 ui.panel.conversation uses ui.panelpart of a loop✕
Connections
2 pairs of types, where a type in ui.panel.conversation uses a type in ui.panel.
ui.panel.conversation uses ui.panel, so a change to ui.panel can break ui.panel.conversation, while a change to ui.panel.conversation can't break ui.panel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→37 ui.panel.conversation uses servicepart of a loop✕
Connections
2 pairs of types, where a type in ui.panel.conversation uses a type in service.
ui.panel.conversation uses service, so a change to service can break ui.panel.conversation, while a change to ui.panel.conversation can't break service.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.settings uses model.enumarations, so a change to model.enumarations can break ui.settings, while a change to ui.settings can't break model.enumarations.
Position
Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
ui.settings uses chatmodel.cloud.router, so a change to chatmodel.cloud.router can break ui.settings, while a change to ui.settings can't break chatmodel.cloud.router.
Position
Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
service.projectscanner uses ui.settings, so a change to ui.settings can break service.projectscanner, while a change to service.projectscanner can't break ui.settings.
Position
Below the diagonal: service.projectscanner uses a module listed above it, which is the healthy direction.
service.prompt.command uses model.request, so a change to model.request can break service.prompt.command, while a change to service.prompt.command can't break model.request.
Position
Below the diagonal: service.prompt.command uses a module listed above it, which is the healthy direction.
service.prompt.command uses ui.settings, so a change to ui.settings can break service.prompt.command, while a change to service.prompt.command can't break ui.settings.
Position
Below the diagonal: service.prompt.command uses a module listed above it, which is the healthy direction.
20→35 service.prompt.command uses ui.panelpart of a loop✕
Connections
6 pairs of types, where a type in service.prompt.command uses a type in ui.panel.
service.prompt.command uses ui.panel, so a change to ui.panel can break service.prompt.command, while a change to service.prompt.command can't break ui.panel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
service.prompt.memory uses model.conversation, so a change to model.conversation can break service.prompt.memory, while a change to service.prompt.memory can't break model.conversation.
Position
Below the diagonal: service.prompt.memory uses a module listed above it, which is the healthy direction.
service.prompt.memory uses model.request, so a change to model.request can break service.prompt.memory, while a change to service.prompt.memory can't break model.request.
Position
Below the diagonal: service.prompt.memory uses a module listed above it, which is the healthy direction.
service.prompt.memory uses ui.settings, so a change to ui.settings can break service.prompt.memory, while a change to service.prompt.memory can't break ui.settings.
Position
Below the diagonal: service.prompt.memory uses a module listed above it, which is the healthy direction.
service.rag.embedding uses ui.settings, so a change to ui.settings can break service.rag.embedding, while a change to service.rag.embedding can't break ui.settings.
Position
Below the diagonal: service.rag.embedding uses a module listed above it, which is the healthy direction.
service.analyzer uses service.projectscanner, so a change to service.projectscanner can break service.analyzer, while a change to service.analyzer can't break service.projectscanner.
Position
Below the diagonal: service.analyzer uses a module listed above it, which is the healthy direction.
service.chromadb uses service.rag.embedding, so a change to service.rag.embedding can break service.chromadb, while a change to service.chromadb can't break service.rag.embedding.
Position
Below the diagonal: service.chromadb uses a module listed above it, which is the healthy direction.
service.rag uses service.projectscanner, so a change to service.projectscanner can break service.rag, while a change to service.rag can't break service.projectscanner.
Position
Below the diagonal: service.rag uses a module listed above it, which is the healthy direction.
service.rag uses service.rag.embedding, so a change to service.rag.embedding can break service.rag, while a change to service.rag can't break service.rag.embedding.
Position
Below the diagonal: service.rag uses a module listed above it, which is the healthy direction.
service.agent.tool uses model.agent, so a change to model.agent can break service.agent.tool, while a change to service.agent.tool can't break model.agent.
Position
Below the diagonal: service.agent.tool uses a module listed above it, which is the healthy direction.
service.agent.tool uses service.rag, so a change to service.rag can break service.agent.tool, while a change to service.agent.tool can't break service.rag.
Position
Below the diagonal: service.agent.tool uses a module listed above it, which is the healthy direction.
26→30 service.agent.tool uses service.agentpart of a loop✕
Connections
2 pairs of types, where a type in service.agent.tool uses a type in service.agent.
service.agent.tool uses service.agent, so a change to service.agent can break service.agent.tool, while a change to service.agent.tool can't break service.agent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.settings.rag uses service.rag.embedding, so a change to service.rag.embedding can break ui.settings.rag, while a change to ui.settings.rag can't break service.rag.embedding.
Position
Below the diagonal: ui.settings.rag uses a module listed above it, which is the healthy direction.
ui.settings.rag uses service.chromadb, so a change to service.chromadb can break ui.settings.rag, while a change to ui.settings.rag can't break service.chromadb.
Position
Below the diagonal: ui.settings.rag uses a module listed above it, which is the healthy direction.
service.agent uses service.agent.tool, so a change to service.agent.tool can break service.agent, while a change to service.agent can't break service.agent.tool.
Position
Below the diagonal: service.agent uses a module listed above it, which is the healthy direction.
service.prompt.response.nonstreaming uses model.request, so a change to model.request can break service.prompt.response.nonstreaming, while a change to service.prompt.response.nonstreaming can't break model.request.
Position
Below the diagonal: service.prompt.response.nonstreaming uses a module listed above it, which is the healthy direction.
service.prompt.response.nonstreaming uses service.prompt.memory, so a change to service.prompt.memory can break service.prompt.response.nonstreaming, while a change to service.prompt.response.nonstreaming can't break service.prompt.memory.
Position
Below the diagonal: service.prompt.response.nonstreaming uses a module listed above it, which is the healthy direction.
service.prompt.response.nonstreaming uses service.agent, so a change to service.agent can break service.prompt.response.nonstreaming, while a change to service.prompt.response.nonstreaming can't break service.agent.
Position
Below the diagonal: service.prompt.response.nonstreaming uses a module listed above it, which is the healthy direction.
service.prompt.strategy uses ui.compose, so a change to ui.compose can break service.prompt.strategy, while a change to service.prompt.strategy can't break ui.compose.
Position
Below the diagonal: service.prompt.strategy uses a module listed above it, which is the healthy direction.
service.prompt.strategy uses model.request, so a change to model.request can break service.prompt.strategy, while a change to service.prompt.strategy can't break model.request.
Position
Below the diagonal: service.prompt.strategy uses a module listed above it, which is the healthy direction.
service.prompt.strategy uses service.prompt.memory, so a change to service.prompt.memory can break service.prompt.strategy, while a change to service.prompt.strategy can't break service.prompt.memory.
Position
Below the diagonal: service.prompt.strategy uses a module listed above it, which is the healthy direction.
service.prompt.strategy uses service.agent, so a change to service.agent can break service.prompt.strategy, while a change to service.prompt.strategy can't break service.agent.
Position
Below the diagonal: service.prompt.strategy uses a module listed above it, which is the healthy direction.
service.prompt.strategy uses service.prompt.response.nonstreaming, so a change to service.prompt.response.nonstreaming can break service.prompt.strategy, while a change to service.prompt.strategy can't break service.prompt.response.nonstreaming.
Position
Below the diagonal: service.prompt.strategy uses a module listed above it, which is the healthy direction.
32→35 service.prompt.strategy uses ui.panelpart of a loop✕
Connections
7 pairs of types, where a type in service.prompt.strategy uses a type in ui.panel.
service.prompt.strategy uses ui.panel, so a change to ui.panel can break service.prompt.strategy, while a change to service.prompt.strategy can't break ui.panel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→37 service.prompt.strategy uses servicepart of a loop✕
Connections
2 pairs of types, where a type in service.prompt.strategy uses a type in service.
service.prompt.strategy uses service, so a change to service can break service.prompt.strategy, while a change to service.prompt.strategy can't break service.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
service.prompt uses service.prompt.command, so a change to service.prompt.command can break service.prompt, while a change to service.prompt can't break service.prompt.command.
Position
Below the diagonal: service.prompt uses a module listed above it, which is the healthy direction.
service.prompt uses service.prompt.strategy, so a change to service.prompt.strategy can break service.prompt, while a change to service.prompt can't break service.prompt.strategy.
Position
Below the diagonal: service.prompt uses a module listed above it, which is the healthy direction.
controller uses controller.listener, so a change to controller.listener can break controller, while a change to controller can't break controller.listener.
Position
Below the diagonal: controller uses a module listed above it, which is the healthy direction.
controller uses model.enumarations, so a change to model.enumarations can break controller, while a change to controller can't break model.enumarations.
Position
Below the diagonal: controller uses a module listed above it, which is the healthy direction.
controller uses ui.component.button, so a change to ui.component.button can break controller, while a change to controller can't break ui.component.button.
Position
Below the diagonal: controller uses a module listed above it, which is the healthy direction.
controller uses service.prompt.command, so a change to service.prompt.command can break controller, while a change to controller can't break service.prompt.command.
Position
Below the diagonal: controller uses a module listed above it, which is the healthy direction.
controller uses ui.component.input, so a change to ui.component.input can break controller, while a change to controller can't break ui.component.input.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.panel uses ui.panel.conversation, so a change to ui.panel.conversation can break ui.panel, while a change to ui.panel can't break ui.panel.conversation.
Position
Below the diagonal: ui.panel uses a module listed above it, which is the healthy direction.
ui.component.input uses ui.listener, so a change to ui.listener can break ui.component.input, while a change to ui.component.input can't break ui.listener.
Position
Below the diagonal: ui.component.input uses a module listed above it, which is the healthy direction.
service uses ui.panel.conversation, so a change to ui.panel.conversation can break service, while a change to service can't break ui.panel.conversation.
Position
Below the diagonal: service uses a module listed above it, which is the healthy direction.
chatmodel.local uses model.enumarations, so a change to model.enumarations can break chatmodel.local, while a change to chatmodel.local can't break model.enumarations.
Position
Below the diagonal: chatmodel.local uses a module listed above it, which is the healthy direction.
chatmodel.local.compatible uses model.enumarations, so a change to model.enumarations can break chatmodel.local.compatible, while a change to chatmodel.local.compatible can't break model.enumarations.
Position
Below the diagonal: chatmodel.local.compatible uses a module listed above it, which is the healthy direction.
chatmodel.local.compatible uses model, so a change to model can break chatmodel.local.compatible, while a change to chatmodel.local.compatible can't break model.
Position
Below the diagonal: chatmodel.local.compatible uses a module listed above it, which is the healthy direction.
chatmodel.local.compatible uses chatmodel.catalog, so a change to chatmodel.catalog can break chatmodel.local.compatible, while a change to chatmodel.local.compatible can't break chatmodel.catalog.
Position
Below the diagonal: chatmodel.local.compatible uses a module listed above it, which is the healthy direction.
chatmodel.local.compatible uses chatmodel.local, so a change to chatmodel.local can break chatmodel.local.compatible, while a change to chatmodel.local.compatible can't break chatmodel.local.
Position
Below the diagonal: chatmodel.local.compatible uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 41.7 · Weak · gated by R1, X5 ·
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
32
High / Critical
A03:2025 — Software Supply Chain Failures
5
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Bring the 20 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ProjectIndexerService.indexFiles (cyclomatic 30), ExoClusterPanel.parseState (cyclomatic 26), CombinedLogEntryRenderer.resolveEntryColor (cyclomatic 23).
God Classes: TooManyMethods: ComposeConversationViewController
How the grades work
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 — 34
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 — 520
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 — 149
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 70 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, 697 of 703 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (JaCoCo's report, finalizing the tests in build.gradle.kts) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.kt, .java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 3,731 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 17 test source file(s) (.kt) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt, .java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 1 artifact(s) across its subprojects (0 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (39 contributor(s) across 3079 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 38 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization 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 authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit 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 audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention 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 retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights 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 data-subject rights controls.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ProjectIndexerService.indexFiles at 30. A further 8 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 CodeLanguageUtil.mapLanguageToPrism at 38 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/main/java/com/devoxx/genie/ui/util/CodeLanguageUtil.java (CodeLanguageUtil.mapLanguageToPrism at 38), src/main/java/com/devoxx/genie/service/MessageCreationService.java (MessageCreationService.inferFenceLanguage at 35), src/main/java/com/devoxx/genie/service/agent/tool/HtmlToMarkdown.java (HtmlToMarkdown.render at 27), src/main/java/com/devoxx/genie/service/rag/chunking/RagChunker.java (RagChunker.splitterFor at 25), src/main/java/com/devoxx/genie/service/spec/BacklogConfigService.java (BacklogConfigService.applyConfigScalar at 25), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 20 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ProjectIndexerService.indexFiles (cyclomatic 30), ExoClusterPanel.parseState (cyclomatic 26), CombinedLogEntryRenderer.resolveEntryColor (cyclomatic 23). — 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 20 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 30 down to 30 or less in Cognitive Complexity — start with ExoClusterPanel.parseState (cognitive 57), ProjectIndexerService.indexFiles (cognitive 41), OpengrepScanner.parseOutput (cognitive 35). — 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 7 together lifts Cognitive Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.5 / 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 13 TooManyMethods finding(s) in God Classes — start with DevoxxGenieStateService.java, MCPTrafficLogger.java, ConversationViewModel.kt. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 12 ClassTooLong finding(s) in God Classes — start with LLMModelRegistryService.java, AgentSettingsComponent.java, DevoxxGenieStateService.java. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with LLMModelRegistryService.java, AgentSettingsComponent.java, DevoxxGenieStateService.java. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
123 duplicated block group(s) detected. 8.2 % of the production lines (5,966 of 72,471) are in a reported copy. A further 112 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (23 corresponding lines) · ×6src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:221
+ 110 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with LMStudioFimProvider.java (2), AgentSettingsComponent.java (2), GrokChatModelFactory.java. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 10 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MCPExecutionService.java, AcpPromptStrategy.java, EventAgentDialog.java. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with SearchCommand.java, ApAgentDetailsDialog.java, ExoModelService.java. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
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 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with DevoxxGenieStateService.java, BacklogConfigService.java, AbstractSettingsComponent.java. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 48 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
13 skipped (13 with a documented reason), 48 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3731 tests. Measured on the .java suite only — at least 17 test source file(s) (.kt) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: testTellAJoke · ×48src/test/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelTest.java:13
Resolve the 48 No assertions finding(s) in Test Quality — start with MCPTrafficLoggerTest.java (7), WebViewJavaScriptExecutorTest.java (6), CompletionSettingsConfigurableTest.java (5). — One of this dimension's main actionable groups (48 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 41 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 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 package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What 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.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ProjectIndexerService.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_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.
6 deducted task-comment markers across 72471 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 6 TodoComment finding(s) in Explicit Debt — start with JavaProjectScannerExtension.java (3), ChatMemorySizeListener.java (2), MCPSettingsConfigurable.java. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 58 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namessrc/main/resources/webview/js/kanban.js:379
What to do
Resolve the 2 redundant comment finding(s) in Comment Value — start with fix-image-paths.js, update-metadata.js. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (Gradle, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionbuild.gradle.kts:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability9.0 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
58 % of calls cross a namespace and 20 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
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).
32 finding(s): 0 critical, 28 high, 3 medium, 1 low. 22 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `gradlew` (line 74, line 178), `src/main/java/com/devoxx/genie/service/spec/FuzzySearchHelper.java` (line 64), `src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 22 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 (22 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_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.
18 of 342 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java. Counted over 342 of the 635 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 13 Change coupling finding(s) in Change Coupling — start with ExpandablePanel.java (2), ProjectContentService.java (2), ChatModelFactoryProvider.java (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 9 Change-coupling hub finding(s) in Change Coupling — start with DeepInfraChatModelFactory.java, AnthropicChatModelFactory.java, GroqChatModelFactory.java. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d35_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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 1 platform declaration(s) and 45 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.
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.
Do you agree with this assessment?
AC3 · Page structure3.5 / 10Weak✓ Tool-verified
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.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/main/resources/webview/html/kanban.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/main/resources/webview/html/kanban.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 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.
`.feature-card a` 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. — docusaurus/src/css/custom.css:54
`.progress-fill` moves (`transition: width 0.2s`) 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/main/resources/webview/css/kanban.css:230
`.featureIcon` 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. — docusaurus/src/components/HomepageFeatures/styles.module.css:57
`.arrow` moves (`transition: transform 0.2s 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. — docusaurus/src/components/HomepageFeatures/styles.module.css:77
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.
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.
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.
`DevoxxGenieSettingsService` declares 129 abstract methods: `getAnthropicKey`, `getAwsAccessKeyId`, `getAwsBearerToken`, `getAwsBedrockAuthMode`, `getAwsProfileName`, `getAwsRegion`, `getAwsSecretKey`, `getAzureOpenAIDeployment`, `getAzureOpenAIEndpoint`, `getAzureOpenAIKey`, `getChatMemorySize`, `getCloudflareAccountId`, `getCloudflareGatewayName`, `getCloudflareKey`, `getCloudflareModelName`, `getCommands`, `getCustomOpenAIApiKey`, `getCustomOpenAIContextWindow`, `getCustomOpenAIInputCost`, `getCustomOpenAIModelName`, `getCustomOpenAIOutputCost`, `getCustomOpenAIUrl`, `getDeepInfraKey`, `getDeepSeekKey`, `getDefaultWindowContext`, `getExcludeJavaDoc`, `getExcludedDirectories`, `getExcludedFiles`, `getExoModelUrl`, `getExplainPrompt`, `getGeminiKey`, `getGlmKey`, `getGoogleCSIKey`, `getGoogleSearchKey`, `getGrokKey`, `getGroqKey`, `getIncludedFileExtensions`, `getIsWebSearchEnabled`, `getKimiKey`, `getLanguageModels`, and 89 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/devoxx/genie/service/DevoxxGenieSettingsService.java:10
`ConversationViewController` declares 27 abstract methods: `isInitialized`, `ensureBrowserInitialized`, `dispose`, `getComponent`, `loadWelcomeContent`, `updateCustomPrompts`, `cancelPendingWelcomeLoad`, `addChatMessage`, `addUserPromptMessage`, `addSteeringMessage`, `addQueuedPromptMessage`, `removeSteeringMessage`, `updateAiMessageContent`, `addFileReferences`, `addChangedFiles`, `addSystemMessage`, `onActivityMessage`, `currentActivityGeneration`, `deactivateActivityHandlers`, `hideLoadingIndicator`, `markMCPLogsAsCompleted`, `setTerminalState`, `clearConversation`, `refreshForNewConversation`, `setRestoringConversation`, `themeChanged`, `appearanceSettingsChanged`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/kotlin/com/devoxx/genie/ui/compose/ConversationViewController.kt:16
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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✓ Tool-verified
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's code 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.
4 public types in `com.devoxx.genie.service.generator.content.impl` are marked as implementation by their own namespace, folder or name: `GradleCommandsGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/GradleCommandsGenerator.java:8, `impl`), `JavaStyleGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/JavaStyleGenerator.java:8, `impl`), `RustCommandsGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/RustCommandsGenerator.java:8, `impl`), `RustStyleGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/RustStyleGenerator.java:8, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/main/java/com/devoxx/genie/service/generator/content/impl/GradleCommandsGenerator.java:8
What to do
Hide `com.devoxx.genie.service.generator.content.impl` (`GradleCommandsGenerator`, `JavaStyleGenerator`, `RustCommandsGenerator`, `RustStyleGenerator`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
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.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `npm` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
`HttpClient {` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/main/java/com/devoxx/genie/chatmodel/local/compatible/CompactJsonHttpClient.java:24
`HttpClient.newBuilder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingModelFactory.java:39
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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 each language's code 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.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 33 plain JS — the untyped files are docusaurus/create-placeholders.js, docusaurus/generate-png-placeholders.js, docusaurus/placeholder-setup.js, docusaurus/scripts/fix-image-paths.js, docusaurus/scripts/update-metadata.js, docusaurus/sidebars.js (+27 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
docusaurus/placeholder-setup.js:57 · docusaurus/static/img/create-placeholders.js:117 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — docusaurus/placeholder-setup.js:57
docusaurus/scripts/fix-image-paths.js:51 · docusaurus/scripts/update-metadata.js:137 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — docusaurus/scripts/fix-image-paths.js:51
docusaurus/src/pages/index.js:274 · docusaurus/src/pages/index.js:396 — 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. — docusaurus/src/pages/index.js:274
docusaurus/placeholder-setup.js:74 · docusaurus/static/img/copy-placeholders.js:25 · docusaurus/static/img/create-placeholders.js:134 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — docusaurus/placeholder-setup.js:74
docusaurus/src/pages/index.js:250 · docusaurus/src/pages/index.js:302 · docusaurus/src/pages/index.js:424 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — docusaurus/src/pages/index.js:250
docusaurus/src/pages/index.js:232 · docusaurus/src/pages/index.js:284 · docusaurus/src/pages/index.js:406 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — docusaurus/src/pages/index.js:232
src/main/resources/webview/js/kanban.js:245 · src/main/resources/webview/js/kanban.js:300 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/resources/webview/js/kanban.js:245
docusaurus/generate-png-placeholders.js:80 · docusaurus/placeholder-setup.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — docusaurus/generate-png-placeholders.js:80
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:108
(anonymous) has cyclomatic complexity 13 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/main/resources/webview/js/kanban.js:245
Do you agree with this assessment?
R3 · Large Files8.8 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
docusaurus/src/pages/index.js has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — docusaurus/src/pages/index.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code5.9 / 10Adequate✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 16 application, 1 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×9) — docusaurus/src/components/HomepageFeatures/index.js, docusaurus/create-placeholders.js, docusaurus/src/components/NewsletterSignup/index.js, …
no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×9) — docusaurus/src/components/HomepageFeatures/icons/SpecDrivenDev.js, docusaurus/src/components/HomepageFeatures/icons/SecurityScanner.js, docusaurus/src/components/HomepageFeatures/icons/SubAgents.js, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — docusaurus/sidebars.js:14
Declared in docusaurus/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — docusaurus/package.json:29, docusaurus/package.json:20
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Do you agree with this assessment?
X13 · Undrained process stream5.3 / 10Adequate✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stdout and stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/transport/StdioTransportPanel.java:281
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
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 (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — 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)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. 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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements 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?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:42, src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:120, src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:127, …
`catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:54, src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:91, src/main/kotlin/com/devoxx/genie/ui/compose/util/IdeAnimations.kt:35
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×23) — src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:824, src/main/java/com/devoxx/genie/ui/panel/conversationhistory/ConversationHistoryPanel.java:327, src/main/java/com/devoxx/genie/service/rag/watcher/RAGFileWatcher.java:173, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:110, src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:150, src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:382, …
`catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/main/java/com/devoxx/genie/service/rag/RAGEventPublisher.java:90, src/main/java/com/devoxx/genie/service/credentials/PasswordSafeCredentialService.java:52
`catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/java/com/devoxx/genie/chatmodel/local/compatible/CompactJsonHttpClient.java:58
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error` at line 150 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/webview/WebServer.java:150
`info` at line 158 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/webview/WebServer.java:158
`error` at line 35 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/util/FileTypeIconUtil.java:35
`error` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/util/FileTypeIconUtil.java:63
`error` at line 229 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:229
`error` at line 235 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:235
`error` at line 308 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:308
`warn` at line 297 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/MessageCreationService.java:297
`debug` at line 46 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/prompt/websearch/WebSearchPromptExecutionService.java:46
`debug` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/prompt/websearch/WebSearchPromptExecutionService.java:63
`info` at line 55 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/prompt/threading/ThreadPoolShutdownManager.java:55
`info` at line 61 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/prompt/threading/ThreadPoolShutdownManager.java:61
`info` at line 112 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:112
`info` at line 120 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:120
`warn` at line 127 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:127
`info` at line 189 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:189
`info` at line 195 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:195
`info` at line 197 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:197
`info` at line 202 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:202
`info` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:207
`info` at line 210 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:210
`info` at line 217 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:217
`info` at line 224 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:224
`info` at line 273 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:273
`debug` at line 401 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:401
`info` at line 412 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:412
`info` at line 428 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:428
`info` at line 434 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:434
`info` at line 59 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/ProjectScannerService.java:59
`info` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/projectscanner/ProjectScannerService.java:63
`error` at line 237 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/mcp/MCPExecutionService.java:237
`info` at line 319 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:319
`warn` at line 321 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:321
`error` at line 69 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/chromadb/ChromaDockerService.java:69
`error` at line 72 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/chromadb/ChromaDockerService.java:72
`error` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/chromadb/ChromaDockerService.java:75
`warn` at line 105 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:105
`warn` at line 197 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:197
`warn` at line 276 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:276
`error` at line 99 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/devoxx/genie/service/analyzer/util/GitignoreParser.java:99
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/162 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 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 — 4 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.
D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
C3 Audit Trail — Not assessed: these audit 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 audit 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.
C4 Data Retention — Not assessed: these retention 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 retention 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.
C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 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.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. 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
AX8 Test isolation — no test/production split to check
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 — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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 — Not assessed: these authorization 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 authorization 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.
D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
D12 Dependency Hygiene — Not scored — a Gradle build resolved 1 artifact(s) across its subprojects (0 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (model), which is a layered codebase, not two contexts. 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"]`.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
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.
D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 25 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
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 — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (33 production file(s)) has no JavaScript/TypeScript test, but it is 3.22% of this repository's production source and the other 96.78% carries 64,756 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 9% of this repository's production lines — java (68,007 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 9% of this repository's production lines — java (68,007 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
<html> without a lang src/main/resources/webview/html/kanban.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
No assertions: testTellAJoke src/test/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelTest.java:13— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testHandlePromptSubmission_WithACPRunner_CreatesDefaultModel src/test/java/com/devoxx/genie/controller/ActionButtonsPanelControllerTest.java:333— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testHandlePromptSubmission_WithCLIRunnerAndNoModel_CreatesDefaultModel src/test/java/com/devoxx/genie/controller/ActionButtonsPanelControllerTest.java:320— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testHandlePromptSubmission_WithLocalProvider_CreatesDefaultModelWith4096Tokens src/test/java/com/devoxx/genie/controller/ActionButtonsPanelControllerTest.java:344— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testHandlePromptSubmission_WithSelectedModel_UsesSelectedModel src/test/java/com/devoxx/genie/controller/ActionButtonsPanelControllerTest.java:264— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: usageOnlyFeatureIdCannotBeEnabled src/test/java/com/devoxx/genie/service/analytics/AnalyticsSessionSnapshotServiceTest.java:215— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: semanticSearchUsedWithNullModelDoesNotThrow src/test/java/com/devoxx/genie/service/analytics/FeatureUsageTrackerTest.java:64— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: parse_assistantTextContent_returnsIntermediateResponse src/test/java/com/devoxx/genie/service/cli/ClaudeStreamJsonParserTest.java:88— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: cancelCurrentProcess_noProcess_doesNotThrow src/test/java/com/devoxx/genie/service/cli/CliTaskExecutorServiceTest.java:85— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: dispose_noProcess_doesNotThrow src/test/java/com/devoxx/genie/service/cli/CliTaskExecutorServiceTest.java:175— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: notifyTaskDone_noProcessOrCommand_doesNotThrow src/test/java/com/devoxx/genie/service/cli/CliTaskExecutorServiceTest.java:111— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: migrateLegacyDatabase_copiesFileWhenLegacyExistsAndNewDoesNot src/test/java/com/devoxx/genie/service/conversations/ConversationStorageServiceTest.java:22— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testParseHttpSseTransport src/test/java/com/devoxx/genie/service/mcp/MCPConfigurationParserTest.java:132— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: consumerDoesNothingWhenDebugDisabled src/test/java/com/devoxx/genie/service/mcp/MCPExecutionServiceTest.java:561— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: onRequest_activityMessagePublisherThrows_doesNotPropagate src/test/java/com/devoxx/genie/service/mcp/MCPListenerServiceTest.java:314— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handleLogMessage_messageBusException_doesNotThrow src/test/java/com/devoxx/genie/service/mcp/MCPLogMessageHandlerTest.java:151— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: logDebug_whenDebugDisabled_doesNotThrow src/test/java/com/devoxx/genie/service/mcp/MCPServiceTest.java:131— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: logDebug_whenDebugEnabled_doesNotThrow src/test/java/com/devoxx/genie/service/mcp/MCPServiceTest.java:122— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resetNotificationFlag_doesNotThrow src/test/java/com/devoxx/genie/service/mcp/MCPServiceTest.java:114— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: delegationMethods_doNotThrow src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:101— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: isDebugEnabled_delegates src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:129— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: isErrorEnabled_delegates src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:144— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: isInfoEnabled_delegates src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:134— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: isTraceEnabled_delegates src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:123— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: isWarnEnabled_delegates src/test/java/com/devoxx/genie/service/mcp/MCPTrafficLoggerTest.java:139— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:42— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:54— `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:91— `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:120— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:127— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:911— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/kotlin/com/devoxx/genie/ui/compose/util/IdeAnimations.kt:35— `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:824— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/ui/panel/conversationhistory/ConversationHistoryPanel.java:327— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/RAGEventPublisher.java:90— `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/watcher/RAGFileWatcher.java:173— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/validator/ChromeDBValidator.java:80— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/validator/DockerValidator.java:14— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/validator/EmbeddingModelValidator.java:42— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/validator/EmbeddingProviderValidator.java:69— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/rag/validator/OllamaValidator.java:37— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/prompt/error/ProviderErrorTranslator.java:166— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:175— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/credentials/PasswordSafeCredentialService.java:52— `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/cli/ClaudeStreamJsonParser.java:326— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/cli/ClaudeStreamJsonParser.java:336— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/blog/BlogFeedService.java:215— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/analytics/AnalyticsService.java:252— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/analytics/AnalyticsSessionSnapshotService.java:110— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/main/java/com/devoxx/genie/service/analytics/FeatureUsageTracker.java:125— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (7 lines × 2) src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:39— src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:39-45 | src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:37-43 — before extracting anything, compare `src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:46` calls `baseUrl` and `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:44` 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 (7 lines × 2) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:227— src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:227-233 | src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:250-256 — 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 `src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:227` 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. 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 (7 lines × 2) src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:37— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:37-43 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:42-48 — before extracting anything, compare `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java` and `src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:50` calls `addProperty`, `JsonObject` and `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:45` 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 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:55— src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:55-61 | src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:76-82 — 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 `src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:55` 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 (7 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:233— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:233-239 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:189-195 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java` and `src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:233` 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 (7 lines × 2) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:392— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:392-398 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:569-575 — 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/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:680— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:680-686 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:1234-1240 — 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 `src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:680` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (7 lines × 2) src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:80— src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:80-86 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:105-111 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:80` 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 (7 lines × 2) src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:50— src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:50-56 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:786-792 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (7 lines × 2) src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:123— src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:123-129 | src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:149-155 — 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/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:115— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:115-121 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:122-128 — before extracting anything, compare `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java` and `src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 (7 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/EditFileToolExecutor.java:149— src/main/java/com/devoxx/genie/service/agent/tool/EditFileToolExecutor.java:149-155 | src/main/java/com/devoxx/genie/service/agent/tool/WriteFileToolExecutor.java:107-113 — 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/main/java/com/devoxx/genie/ui/webview/handler/WebViewJavaScriptExecutor.java:363— src/main/java/com/devoxx/genie/ui/webview/handler/WebViewJavaScriptExecutor.java:363-369 | src/main/java/com/devoxx/genie/ui/webview/template/HtmlTemplate.java:36-42 — 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 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 (7 lines × 2) src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:201— src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:201-207 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:363-369 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java` and `src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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.
TooManyMethods: DevoxxGenieStateService src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:50— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× 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: MCPTrafficLogger src/main/java/com/devoxx/genie/service/mcp/MCPTrafficLogger.java:24— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× 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: ConversationViewModel src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:26— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: ActionButtonsPanel src/main/java/com/devoxx/genie/ui/panel/ActionButtonsPanel.java:48— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: AgentSettingsComponent src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:40— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: RAGSettingsComponent src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:61— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: FileListManager src/main/java/com/devoxx/genie/service/FileListManager.java:15— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: LlmProviderPanel src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:55— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: ChatMemoryManager REDACTED:56— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: ComposeConversationViewController src/main/kotlin/com/devoxx/genie/ui/compose/ComposeConversationViewController.kt:26— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: AgentMcpLogPanel src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:55— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: ApNewRunPanel src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:67— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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: LLMProvidersComponent src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java:31— 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.
Change coupling: AiBubble.kt ↔ UserBubble.kt src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:1— `src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt` and `src/main/kotlin/com/devoxx/genie/ui/compose/components/UserBubble.kt` change together 91% of the time (10 of the 11 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `78f747b1` refactor(ui): build syntax highlights per code block (#1278); `aa035ba0` fix(ui): guard code highlighting against malformed ranges (#1277); `0dba5ba2` feat(ui): scale chat input/output text with IDE zoom (task-237) — run `git show` on any of them.
Change coupling: ExpandablePanel.java ↔ ActionButtonsPanel.java src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java:1— `src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java` and `src/main/java/com/devoxx/genie/ui/panel/ActionButtonsPanel.java` change together 70% of the time (7 of the 10 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 7 shared commits counted here, the most recent 3 are `db9a86a6` Cleanup chatmodels; `bcf12aad` Fix #296 : File Context is not include for OpenAI o1-models; `4895a9cb` Fix #296 : File Context is not include for OpenAI o1-models — run `git show` on any of them.
Change coupling: ComposeConversationViewController.kt ↔ ConversationScreen.kt src/main/kotlin/com/devoxx/genie/ui/compose/ComposeConversationViewController.kt:1— `src/main/kotlin/com/devoxx/genie/ui/compose/ComposeConversationViewController.kt` and `src/main/kotlin/com/devoxx/genie/ui/compose/screen/ConversationScreen.kt` change together 60% of the time (6 of the 10 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 6 shared commits counted here, the most recent 3 are `f99a2e05` Show "Add Skill" and "Add MCP" buttons when none are defined; `c306cece` Add "Add MCP" button on welcome page when no skills installed; `2832f4b1` feat(ui): TASK-233 timeline visuals, live status line and Open Logs a… — run `git show` on any of them.
Change coupling: ProjectContentService.java ↔ ActionButtonsPanel.java src/main/java/com/devoxx/genie/service/ProjectContentService.java:1— `src/main/java/com/devoxx/genie/service/ProjectContentService.java` and `src/main/java/com/devoxx/genie/ui/panel/ActionButtonsPanel.java` change together 58% of the time (22 of the 38 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 22 shared commits counted here, the most recent 3 are `f3bfa847` Feat #261 : DeepSeek added for DeepSeek Code v2 support; `5b459293` Feat #261 : DeepSeek added for DeepSeek Code v2 support; `20856705` Fix #232 Calc correct input tokens when using Ollama + FIX Project c… — run `git show` on any of them.
Change coupling: ChatModelFactoryProvider.java ↔ DevoxxGenieStateService.java src/main/java/com/devoxx/genie/chatmodel/ChatModelFactoryProvider.java:1— `src/main/java/com/devoxx/genie/chatmodel/ChatModelFactoryProvider.java` and `src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java` change together 56% of the time (23 of the 41 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 23 shared commits counted here, the most recent 3 are `670624bb` fix(local): llama.cpp model dropdown, name, and blank chat crash (#1413); `2a0172a1` feat(local): serve LLaMA.c++ from the generic local provider (#1409); `4f62d1f4` feat(local): serve GPT4All from the generic local provider (#1408) — run `git show` on any of them.
Change coupling: FileSelectionPanelFactory.java ↔ PromptContextFileListPanel.java src/main/java/com/devoxx/genie/ui/panel/FileSelectionPanelFactory.java:1— `src/main/java/com/devoxx/genie/ui/panel/FileSelectionPanelFactory.java` and `src/main/java/com/devoxx/genie/ui/panel/PromptContextFileListPanel.java` change together 55% of the time (12 of the 22 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `3b7925f6` Feat #426: Show full path/package when adding files; `76e40a24` feat(issue-413): Modification of FileListManager so each VirtualFiles…; `097f727f` Fix #276 : Sort files by name in attached/popup file list — run `git show` on any of them.
Change coupling: ProjectContentService.java ↔ TokenUsageBar.java src/main/java/com/devoxx/genie/service/ProjectContentService.java:1— `src/main/java/com/devoxx/genie/service/ProjectContentService.java` and `src/main/java/com/devoxx/genie/ui/component/TokenUsageBar.java` change together 55% of the time (6 of the 11 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 6 shared commits counted here, the most recent 3 are `154dcf63` Fix #133 Use display model name; `c10fa777` Fix #133 Use display model name; `bb0c1f7a` ProgressBar clean up — run `git show` on any of them.
Change coupling: ProjectScannerService.java ↔ CopyProjectSettingsComponent.java src/main/java/com/devoxx/genie/service/projectscanner/ProjectScannerService.java:1— `src/main/java/com/devoxx/genie/service/projectscanner/ProjectScannerService.java` and `src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `8c0044df` feat(settings): make the Scan & Copy settings per project (#1329); `170b3027` Feature #325: Exclude specific files by name; `54d3a4bc` Feature #325: Exclude specific files by name — run `git show` on any of them.
Change coupling: CopyProjectSettingsComponent.java ↔ LLMProvidersConfigurable.java src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java:1— `src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java` and `src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `00a3edb4` feat: add "More Info" help links to all settings panels; `d16c5f99` Renamed Settings class; `7f152cf4` Renamed Settings class — run `git show` on any of them.
Change coupling: ChatModelFactoryProvider.java ↔ LLMProviderService.java src/main/java/com/devoxx/genie/chatmodel/ChatModelFactoryProvider.java:1— `src/main/java/com/devoxx/genie/chatmodel/ChatModelFactoryProvider.java` and `src/main/java/com/devoxx/genie/service/LLMProviderService.java` change together 54% of the time (22 of the 41 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 22 shared commits counted here, the most recent 3 are `1a674c32` feat(cloudflare): register factory and wire provider discovery; `3a205651` feat: add NVIDIA as a cloud LLM provider; `eaa44504` feat: register ACP Runners as a new provider — run `git show` on any of them.
Change coupling: GoogleChatModelFactory.java ↔ OpenAIChatModelFactory.java src/main/java/com/devoxx/genie/chatmodel/cloud/google/GoogleChatModelFactory.java:1— `src/main/java/com/devoxx/genie/chatmodel/cloud/google/GoogleChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java` change together 50% of the time (9 of the 18 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 9 shared commits counted here, the most recent 3 are `038bacc2` Added more chat language model listeners; `e3799a0b` feat(): refactoring apikey retrieval first pass (at that commit the files were still `src/main/java/com/devoxx/genie/chatmodel/google/GoogleChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/openai/OpenAIChatModelFactory.java`); `363ff872` feat(): refactoring apikey retrieval first pass (at that commit the files were still `src/main/java/com/devoxx/genie/chatmodel/google/GoogleChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/openai/OpenAIChatModelFactory.java`) — run `git show` on any of them.
Change coupling: ConversationScreen.kt ↔ WelcomeScreen.kt src/main/kotlin/com/devoxx/genie/ui/compose/screen/ConversationScreen.kt:1— `src/main/kotlin/com/devoxx/genie/ui/compose/screen/ConversationScreen.kt` and `src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt` change together 50% of the time (5 of the 10 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `f99a2e05` Show "Add Skill" and "Add MCP" buttons when none are defined; `c306cece` Add "Add MCP" button on welcome page when no skills installed; `fd9ba055` Show active skills on the welcome page above Quick Commands (#1041) — run `git show` on any of them.
Change coupling: ExpandablePanel.java ↔ ChatMessageContextUtil.java src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java:1— `src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java` and `src/main/java/com/devoxx/genie/util/ChatMessageContextUtil.java` change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `db9a86a6` Cleanup chatmodels; `a1dc166c` Fix #220; `25c32df1` Fix #220 — run `git show` on any of them.
ClassTooLong: LLMModelRegistryService src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:28— ClassTooLong — 1042 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 642 over it, 2.61× 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.
ClassTooLong: AgentSettingsComponent src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:40— ClassTooLong — 805 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 405 over it, 2.01× 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.
ClassTooLong: DevoxxGenieStateService src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:50— ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 97 methods. The bar is 400 significant lines; this is 301 over it, 1.75× 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.
ClassTooLong: RunnerSettingsComponent src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:24— ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 239 over it, 1.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.
ClassTooLong: AgentMcpLogPanel src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:55— ClassTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 216 over it, 1.54× 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.
ClassTooLong: LLMProvidersComponent src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java:31— ClassTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 167 over it, 1.42× 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.
ClassTooLong: RAGSettingsComponent src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:61— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 154 over it, 1.39× 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.
ClassTooLong: MCPSettingsComponent src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:43— ClassTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 130 over it, 1.33× 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.
ClassTooLong: LlmProviderPanel src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:55— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 108 over it, 1.27× 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.
ClassTooLong: LLMProvidersConfigurable src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java:27— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 13 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.
ClassTooLong: ApNewRunPanel src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:67— ClassTooLong — 411 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 11 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.
ClassTooLong: MCPServerDialog src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPServerDialog.java:31— ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 7 over it, 1.02× 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.
FileTooLong: models/LLMModelRegistryService.java src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java— FileTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: LLMModelRegistryService (28-1295). The bar is 500 significant lines; this is 565 over it, 2.13× 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: agent/AgentSettingsComponent.java src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java— FileTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: AgentSettingsComponent (40-1242). The bar is 500 significant lines; this is 340 over it, 1.68× 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: settings/DevoxxGenieStateService.java src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java— FileTooLong — 744 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: DevoxxGenieStateService (50-1370). The bar is 500 significant lines; this is 244 over it, 1.49× 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: log/AgentMcpLogPanel.java src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java— FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: AgentMcpLogPanel (55-941). The bar is 500 significant lines; this is 163 over it, 1.33× 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: runner/RunnerSettingsComponent.java src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: RunnerSettingsComponent (24-940). The bar is 500 significant lines; this is 156 over it, 1.31× 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: rag/RAGSettingsComponent.java src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: RAGSettingsComponent (61-879). The bar is 500 significant lines; this is 110 over it, 1.22× 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: llm/LLMProvidersComponent.java src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java— FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: LLMProvidersComponent (31-848). The bar is 500 significant lines; this is 94 over it, 1.19× 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: mcp/MCPSettingsComponent.java src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: MCPSettingsComponent (43-902). The bar is 500 significant lines; this is 69 over it, 1.14× 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: panel/LlmProviderPanel.java src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: LlmProviderPanel (55-925). The bar is 500 significant lines; this is 58 over it, 1.12× 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: viewmodel/ConversationViewModel.kt src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: onRetryPrompt (64-964). The bar is 500 significant lines; this is 51 over it, 1.10× 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: screen/WelcomeScreen.kt src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3 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.
Duplicated block (6 lines × 2) src/main/java/com/devoxx/genie/service/mcp/MCPExecutionService.java:423— src/main/java/com/devoxx/genie/service/mcp/MCPExecutionService.java:423-428 | src/main/java/com/devoxx/genie/service/mcp/MCPExecutionService.java:431-436 — 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) src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:62— src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:62-67 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:96-101 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java` and `src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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 × 2) src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java:106— src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java:106-111 | src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java:136-141 — 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) src/main/java/com/devoxx/genie/service/analytics/AnalyticsEventBuilder.java:173— src/main/java/com/devoxx/genie/service/analytics/AnalyticsEventBuilder.java:173-178 | src/main/java/com/devoxx/genie/service/analytics/AnalyticsEventBuilder.java:180-185 — 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) src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:108— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:108-113 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:115-120 — before extracting anything, compare `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java` and `src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 × 2) src/main/java/com/devoxx/genie/model/automation/EventAutomationSettings.java:28— src/main/java/com/devoxx/genie/model/automation/EventAutomationSettings.java:28-33 | src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:218-223 — 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 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 (6 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java:75— src/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java:75-80 | src/main/java/com/devoxx/genie/service/agent/tool/SearchFilesToolExecutor.java:106-111 — 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 (6 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:209— src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:209-214 | src/main/java/com/devoxx/genie/service/agent/tool/RunTestsToolExecutor.java:123-128 — 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 (6 lines × 2) src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:26— src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:26-31 | src/main/java/com/devoxx/genie/service/prompt/steering/SteeringMessageQueue.java:38-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.
Duplicated block (6 lines × 2) src/main/java/com/devoxx/genie/ui/settings/ap/ApSettingsConfigurable.java:47— src/main/java/com/devoxx/genie/ui/settings/ap/ApSettingsConfigurable.java:47-52 | src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsConfigurable.java:44-49 — 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.
Change-coupling hub: DeepInfraChatModelFactory.java → GoogleChatModelFactory.java, GroqChatModelFactory.java, MistralChatModelFactory.java, OpenAIChatModelFactory.java, LMStudioChatModelFactory.java, OllamaChatModelFactory.java src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java— `src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java` changes together with 6 other files — `src/main/java/com/devoxx/genie/chatmodel/cloud/google/GoogleChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/lmstudio/LMStudioChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: AnthropicChatModelFactory.java → DeepInfraChatModelFactory.java, GoogleChatModelFactory.java, GroqChatModelFactory.java, MistralChatModelFactory.java, OpenAIChatModelFactory.java, LMStudioChatModelFactory.java, OllamaChatModelFactory.java src/main/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelFactory.java— `src/main/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelFactory.java` changes together with 7 other files — `src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/google/GoogleChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/lmstudio/LMStudioChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Change-coupling hub: GroqChatModelFactory.java → GoogleChatModelFactory.java, MistralChatModelFactory.java, OpenAIChatModelFactory.java, LMStudioChatModelFactory.java, OllamaChatModelFactory.java src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java— `src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java` changes together with 5 other files — `src/main/java/com/devoxx/genie/chatmodel/cloud/google/GoogleChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/lmstudio/LMStudioChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: MistralChatModelFactory.java → OpenAIChatModelFactory.java, LMStudioChatModelFactory.java, OllamaChatModelFactory.java src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java— `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java` changes together with 3 other files — `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/lmstudio/LMStudioChatModelFactory.java`, `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: CalcTokensForDirectoryAction.java → AddDirectoryAction.java, ProjectContentService.java, ActionButtonsPanel.java src/main/java/com/devoxx/genie/action/CalcTokensForDirectoryAction.java— `src/main/java/com/devoxx/genie/action/CalcTokensForDirectoryAction.java` changes together with 3 other files — `src/main/java/com/devoxx/genie/action/AddDirectoryAction.java`, `src/main/java/com/devoxx/genie/service/ProjectContentService.java`, `src/main/java/com/devoxx/genie/ui/panel/ActionButtonsPanel.java` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: CopyProjectSettingsConfigurable.java → ProjectScannerService.java, DevoxxGenieStateService.java, LLMProvidersConfigurable.java src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsConfigurable.java— `src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsConfigurable.java` changes together with 3 other files — `src/main/java/com/devoxx/genie/service/projectscanner/ProjectScannerService.java`, `src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java`, `src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: DevoxxGenieToolWindowContent.java → CalcTokensForDirectoryAction.java, FileEntryComponent.java, TokenUsageBar.java, PromptContextFileListPanel.java, DevoxxGenieIconsUtil.java src/main/java/com/devoxx/genie/ui/window/DevoxxGenieToolWindowContent.java— `src/main/java/com/devoxx/genie/ui/window/DevoxxGenieToolWindowContent.java` changes together with 5 other files — `src/main/java/com/devoxx/genie/action/CalcTokensForDirectoryAction.java`, `src/main/java/com/devoxx/genie/ui/component/FileEntryComponent.java`, `src/main/java/com/devoxx/genie/ui/component/TokenUsageBar.java`, `src/main/java/com/devoxx/genie/ui/panel/PromptContextFileListPanel.java`, `src/main/java/com/devoxx/genie/ui/util/DevoxxGenieIconsUtil.java` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: LLMProvidersComponent.java → CustomOpenAIChatModelFactory.java, DevoxxGenieSettingsService.java, DevoxxGenieStateService.java, LLMConfigSettingsConfigurable.java src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java— `src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java` changes together with 4 other files — `src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java`, `src/main/java/com/devoxx/genie/service/DevoxxGenieSettingsService.java`, `src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java`, `src/main/java/com/devoxx/genie/ui/settings/llmconfig/LLMConfigSettingsConfigurable.java` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: LLMConfigSettingsConfigurable.java → LLMProvidersConfigurable.java, PromptSettingsComponent.java, PromptSettingsConfigurable.java src/main/java/com/devoxx/genie/ui/settings/llmconfig/LLMConfigSettingsConfigurable.java— `src/main/java/com/devoxx/genie/ui/settings/llmconfig/LLMConfigSettingsConfigurable.java` changes together with 3 other files — `src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java`, `src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java`, `src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsConfigurable.java` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×9
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:46— src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:46-56 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:784-792 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java:304— src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java:304-312 | src/main/java/com/devoxx/genie/ui/panel/ap/ApSessionsTab.java:206-215 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:41— src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:41-49 | src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:357-365 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:330— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:330-339 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:725-733 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:235— src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:235-244 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:353-361 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelFactory.java:24— src/main/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelFactory.java:24-34 | src/main/java/com/devoxx/genie/chatmodel/cloud/anthropic/AnthropicChatModelFactory.java:37-45 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java:408— src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersComponent.java:408-416 | src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:284-292 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:151— src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:151-160 | src/main/java/com/devoxx/genie/ui/settings/ap/ApSettingsComponent.java:193-201 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:139— src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:139-147 | src/main/java/com/devoxx/genie/service/security/TrivyScanner.java:104-112 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
MethodTooLong: LLMModelRegistryService.addBedrockModels src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:765— MethodTooLong — addBedrockModels runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× 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: LLMModelRegistryService.addOpenAiModels src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:195— MethodTooLong — addOpenAiModels runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: BuiltInToolProvider.<init> src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:32— MethodTooLong — <init> runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: AgentSettingsComponent.<init> src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:150— MethodTooLong — <init> runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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: MCPMarketplaceInstallDialog.createCenterPanel src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceInstallDialog.java:49— MethodTooLong — createCenterPanel runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: ProjectIndexerService.indexFiles src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java:106— MethodTooLong — indexFiles runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: LLMModelRegistryService.addDeepInfraModels src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:367— MethodTooLong — addDeepInfraModels runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: BuiltInToolProvider.registerPsiTools src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:238— MethodTooLong — registerPsiTools runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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 (12 lines × 2) src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:38— src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:38-49 | src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:58-69 — 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 `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:38` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:37` calls `maxRetries`, `getMaxRetries` and `src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:57` 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 (12 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:219— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:219-230 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:194-205 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java` and `src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 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 (12 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:296— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:296-307 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:104-115 — 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 (12 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:265— src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:265-276 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:149-160 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/main/java/com/devoxx/genie/ui/component/input/PromptInputArea.java:197— src/main/java/com/devoxx/genie/ui/component/input/PromptInputArea.java:197-208 | src/main/java/com/devoxx/genie/ui/component/input/PromptInputArea.java:243-254 — 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 `src/main/java/com/devoxx/genie/ui/component/input/PromptInputArea.java:197` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 lines × 2) src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:121— src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:121-132 | src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:153-164 — 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 `src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:52— src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:52-63 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:138-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:52` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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.
TodoComment src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsConfigurable.java:53— // TODO Check if things have changed, if so Notify listeners that settings have changed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/com/devoxx/genie/ui/listener/ChatMemorySizeListener.java:5— // TODO - This method is currently not used anywhere in the codebase — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/com/devoxx/genie/ui/listener/ChatMemorySizeListener.java:6— // TODO - Should be triggered when user changes the chat memory size in the settings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/com/devoxx/genie/service/analyzer/languages/java/JavaProjectScannerExtension.java:22— // TODO Get Java version from project — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/com/devoxx/genie/service/analyzer/languages/java/JavaProjectScannerExtension.java:42— // TODO More Java-specific info like frameworks, libraries, etc. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/com/devoxx/genie/service/analyzer/languages/java/JavaProjectScannerExtension.java:64— // TODO Add dependency resolution and other Maven-specific info — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×6
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:221— src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:221-243 | src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPServerDialog.java:696-730 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:225— src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:225-248 | src/main/java/com/devoxx/genie/ui/settings/websearch/WebSearchProvidersComponent.java:103-125 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/psi/DocumentSymbolsToolExecutor.java:47— src/main/java/com/devoxx/genie/service/agent/tool/psi/DocumentSymbolsToolExecutor.java:47-69 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindSymbolsToolExecutor.java:53-81 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:84— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:84-106 | src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:176-204 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:144— src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:144-169 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:281-303 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) src/main/java/com/devoxx/genie/service/automation/listeners/FileEventListener.java:30— src/main/java/com/devoxx/genie/service/automation/listeners/FileEventListener.java:30-52 | src/main/java/com/devoxx/genie/service/automation/listeners/ProcessExitListener.java:26-52 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×6
Edited copy of a member (11 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:24— src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:24-35 | src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:23-33 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:555— src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:555-565 | src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:568-582 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java:404— src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java:404-414 | src/main/java/com/devoxx/genie/ui/settings/llm/LLMProvidersConfigurable.java:416-429 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:1122— src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:1122-1132 | src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:1237-1247 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/error/PromptErrorHandler.java:77— src/main/java/com/devoxx/genie/service/prompt/error/PromptErrorHandler.java:77-87 | src/main/java/com/devoxx/genie/service/prompt/error/PromptErrorHandler.java:96-106 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1238— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1238-1249 | src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:136-146 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:110— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:150— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:382— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:396— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:426— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:446— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/azureopenai/AzureOpenAIChatModelFactory.java:25— src/main/java/com/devoxx/genie/chatmodel/cloud/azureopenai/AzureOpenAIChatModelFactory.java:25-41 | src/main/java/com/devoxx/genie/chatmodel/cloud/azureopenai/AzureOpenAIChatModelFactory.java:63-75 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:68— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:68-81 | src/main/java/com/devoxx/genie/chatmodel/cloud/router/RouterChatModelFactory.java:101-113 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/main/java/com/devoxx/genie/ui/processor/FencedCodeBlockProcessor.java:33— src/main/java/com/devoxx/genie/ui/processor/FencedCodeBlockProcessor.java:33-48 | src/main/java/com/devoxx/genie/ui/processor/IndentedCodeBlockProcessor.java:28-40 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:164— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:164-176 | src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:140-153 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:326— src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:326-338 | src/main/java/com/devoxx/genie/util/FileUtil.java:29-42 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Dead file (~20 LoC) docusaurus/src/components/HomepageFeatures/icons/DragDrop.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~20 LoC) docusaurus/src/components/HomepageFeatures/icons/MCPSupport.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~20 LoC) docusaurus/src/components/HomepageFeatures/icons/MultipleLLM.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~20 LoC) docusaurus/src/components/HomepageFeatures/icons/NaiveRAG.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) docusaurus/src/components/HomepageFeatures/icons/TokenCost.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:38— src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:38-49 | src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:37-47 | src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java:174-185 | src/main/java/com/devoxx/genie/chatmodel/local/LocalChatModelFactory.java:83-95 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:69— src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:69-113 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:61-85 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:67-123 | src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java:83-113 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:41— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:41-59 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDefinitionToolExecutor.java:33-52 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:36-54 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindReferencesToolExecutor.java:39-57 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:150— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:150-360 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:54-117 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:34-120 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:65-148 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:328— src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:328-342 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:344-358 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/acprunners/AcpRunnersChatModelFactory.java:26— src/main/java/com/devoxx/genie/chatmodel/local/acprunners/AcpRunnersChatModelFactory.java:26-40 | src/main/java/com/devoxx/genie/chatmodel/local/clirunners/CliRunnersChatModelFactory.java:26-40 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:152— src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:152-169 | src/main/java/com/devoxx/genie/service/tips/TipService.java:166-180 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsConfigurable.java:46— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsConfigurable.java:46-60 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsConfigurable.java:49-65 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×4
Edited copy of a member (14 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:122— src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:122-137 | src/main/java/com/devoxx/genie/ui/settings/prompt/KeyboardShortcutPanel.java:148-161 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:794— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:794-807 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:829-846 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:59— src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:59-76 | src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:115-128 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java:21— src/main/java/com/devoxx/genie/chatmodel/cloud/groq/GroqChatModelFactory.java:21-34 | src/main/java/com/devoxx/genie/chatmodel/cloud/router/RouterChatModelFactory.java:85-98 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:226— src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:226-242 | src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:249-270 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java:80— src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java:80-96 | src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java:99-115 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:481— src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:481-497 | src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:510-526 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) src/main/kotlin/com/devoxx/genie/ui/compose/components/ActivitySection.kt:274— src/main/kotlin/com/devoxx/genie/ui/compose/components/ActivitySection.kt:274-290 | src/main/kotlin/com/devoxx/genie/ui/compose/components/StreamingCaret.kt:26-43 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:154— src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:154-163 | src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:169-178 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:38— src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:38-48 | src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:36-45 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:695— src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:695-704 | src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:710-719 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/conversation/MessageRenderer.java:148— src/main/java/com/devoxx/genie/ui/panel/conversation/MessageRenderer.java:148-157 | src/main/java/com/devoxx/genie/ui/panel/conversation/MessageRenderer.java:163-172 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) src/main/java/com/devoxx/genie/service/FileListManager.java:172— src/main/java/com/devoxx/genie/service/FileListManager.java:172-177 | src/main/java/com/devoxx/genie/service/FileListManager.java:194-199 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/main/java/com/devoxx/genie/ui/renderer/ModelProviderRenderer.java:17— src/main/java/com/devoxx/genie/ui/renderer/ModelProviderRenderer.java:17-24 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:665-670 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/commands/CommandsSettingsComponent.java:119— src/main/java/com/devoxx/genie/ui/settings/commands/CommandsSettingsComponent.java:119-124 | src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java:276-282 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceDialog.java:424— src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceDialog.java:424-429 | src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPServerDialog.java:508-513 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:383— src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:383-397 | src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:420-434 — 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 `src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:383` 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 (15 lines × 2) src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:34— src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:34-48 | src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:67-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsHandler.java:220— src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsHandler.java:220-234 | src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsHandler.java:253-267 — 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 (15 lines × 2) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:615— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:615-629 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:908-922 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:89— src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:89-99 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:107-117 — 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 (11 lines × 2) src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:46— src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:46-56 | src/main/java/com/devoxx/genie/service/prompt/steering/SteeringMessageQueue.java:46-56 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:797— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:797-807 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:836-846 — 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 `src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:797` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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/main/java/com/devoxx/genie/service/prompt/error/ExecutionException.java:7— src/main/java/com/devoxx/genie/service/prompt/error/ExecutionException.java:7-17 | src/main/java/com/devoxx/genie/service/prompt/error/MemoryException.java:16-52 — 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 × 2) src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:70— src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:70-78 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:73-81 — 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 (9 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:119— src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:119-127 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:175-183 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:119` 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 (9 lines × 2) src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:50— src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:50-58 | src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:83-91 — 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 `src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (9 lines × 2) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:67— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:67-75 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:101-109 — 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) src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:25— src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:25-32 | src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:24-31 — before extracting anything, compare `src/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/chatmodel/cloud/grok/GrokChatModelFactory.java:33` calls `baseUrl` and `src/main/java/com/devoxx/genie/chatmodel/cloud/openai/OpenAIChatModelFactory.java:32` 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 (8 lines × 2) src/main/java/com/devoxx/genie/service/LLMProviderService.java:108— src/main/java/com/devoxx/genie/service/LLMProviderService.java:108-115 | src/main/java/com/devoxx/genie/ui/settings/ProviderEnabledResolver.java:39-46 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/LLMProviderService.java:108` 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/main/java/com/devoxx/genie/ui/settings/ProviderEnabledResolver.java:47` calls `isCloudflareEnabled` and `src/main/java/com/devoxx/genie/service/LLMProviderService.java:116` 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 × 2) src/main/java/com/devoxx/genie/service/agent/tool/AgentDiffPreviewFactory.java:90— src/main/java/com/devoxx/genie/service/agent/tool/AgentDiffPreviewFactory.java:90-97 | src/main/java/com/devoxx/genie/service/agent/tool/EditFileToolExecutor.java:115-122 — 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/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:42— src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:42-49 | src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:358-365 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Low cohesion: DevoxxGenieStateService (LCOM4 9) src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:50— DevoxxGenieStateService's methods fall into 9 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 9 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: BacklogConfigService (LCOM4 5) src/main/java/com/devoxx/genie/service/spec/BacklogConfigService.java:28— BacklogConfigService'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: AbstractSettingsComponent (LCOM4 5) src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:18— AbstractSettingsComponent'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: ContentBuilder (LCOM4 4) src/main/java/com/devoxx/genie/service/generator/content/ContentBuilder.java:14— ContentBuilder'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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×3
Animation without a prefers-reduced-motion guard src/main/resources/webview/css/kanban.css:230— `.progress-fill` moves (`transition: width 0.2s`) 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 docusaurus/src/components/HomepageFeatures/styles.module.css:57— `.featureIcon` 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 docusaurus/src/components/HomepageFeatures/styles.module.css:77— `.arrow` moves (`transition: transform 0.2s 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:123— src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:123-133 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:135-145 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:147-157 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:159-169 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:171-181 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:50— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:50-65 | src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:22-35 | src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:22-34 | src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java:158-171 | src/main/java/com/devoxx/genie/chatmodel/local/LocalChatModelFactory.java:67-81 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:124— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:124-154 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:221-256 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:258-286 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:100-135 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:137-172 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members 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· Edited copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:113— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:113-134 | src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:228-255 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:42— src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:42-63 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogDocumentToolExecutor.java:123-149 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ValidatorStatusPanel.java:36— src/main/java/com/devoxx/genie/ui/panel/ValidatorStatusPanel.java:36-57 | src/main/java/com/devoxx/genie/ui/panel/ValidatorStatusPanel.java:59-80 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentsTab.java:129— src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentsTab.java:129-144 | src/main/java/com/devoxx/genie/ui/panel/ap/ApSessionsTab.java:132-153 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/command/FindCommand.java:26— src/main/java/com/devoxx/genie/service/prompt/command/FindCommand.java:26-41 | src/main/java/com/devoxx/genie/service/prompt/command/SearchCommand.java:28-44 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:380— src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:380-398 | src/main/java/com/devoxx/genie/service/skill/SkillRegistry.java:419-434 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:30— src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:30-49 | src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaChatModelFactory.java:52-69 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:115— src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:115-132 | src/main/java/com/devoxx/genie/ui/settings/AbstractSettingsComponent.java:147-164 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:505— src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:505-523 | src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:583-600 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×3
Edited copies of one member (3 members, 10+ corresponding lines) src/main/java/com/devoxx/genie/ui/renderer/ModelProviderRenderer.java:31— src/main/java/com/devoxx/genie/ui/renderer/ModelProviderRenderer.java:31-46 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:677-686 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:1231-1240 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:135— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:135-144 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:353-362 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:207-216 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) src/main/java/com/devoxx/genie/service/acp/protocol/AgentRequestHandler.java:147— src/main/java/com/devoxx/genie/service/acp/protocol/AgentRequestHandler.java:147-156 | src/main/java/com/devoxx/genie/service/ap/ApCliService.java:367-377 | src/main/java/com/devoxx/genie/service/security/AbstractScanner.java:115-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java:109— src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java:109-116 | src/main/java/com/devoxx/genie/ui/component/ExpandablePanel.java:119-126 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:982— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:982-989 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:274-281 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/main/java/com/devoxx/genie/service/ChatService.java:57— src/main/java/com/devoxx/genie/service/ChatService.java:57-64 | src/main/java/com/devoxx/genie/ui/panel/conversation/ConversationPanel.java:233-240 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×3
Edited copies of one member (3 members, 4+ corresponding lines) src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java:194— src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java:194-200 | src/main/java/com/devoxx/genie/service/rag/RAGEventPublisher.java:95-98 | src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:479-483 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) src/main/java/com/devoxx/genie/action/AddDirectoryAction.java:137— src/main/java/com/devoxx/genie/action/AddDirectoryAction.java:137-140 | src/main/java/com/devoxx/genie/action/CalcTokensForDirectoryAction.java:39-42 | src/main/java/com/devoxx/genie/action/ExcludeDirectoryAction.java:60-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) src/main/java/com/devoxx/genie/service/security/GitleaksScanner.java:109— src/main/java/com/devoxx/genie/service/security/GitleaksScanner.java:109-112 | src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:160-163 | src/main/java/com/devoxx/genie/service/security/TrivyScanner.java:136-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) src/main/java/com/devoxx/genie/service/debug/SecretRedactor.java:47— src/main/java/com/devoxx/genie/service/debug/SecretRedactor.java:47-52 | src/main/java/com/devoxx/genie/service/security/GitleaksScanner.java:100-103 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:39— src/main/java/com/devoxx/genie/service/prompt/steering/PendingPromptQueue.java:39-42 | src/main/java/com/devoxx/genie/service/prompt/steering/SteeringMessageQueue.java:58-61 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) src/main/java/com/devoxx/genie/service/security/GitleaksScanner.java:114— src/main/java/com/devoxx/genie/service/security/GitleaksScanner.java:114-117 | src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:165-168 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:84— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:84-105 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:88-109 — before extracting anything, compare `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java` and `src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (22 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:33— src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:33-54 | src/main/java/com/devoxx/genie/service/agent/tool/ReadOnlyToolProvider.java:27-48 — 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/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:33` 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 (22 lines × 2) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:435— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:435-456 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:821-842 — 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 `src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:435` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:453— src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:453-466 | src/main/java/com/devoxx/genie/service/analyzer/util/GitignoreParser.java:234-247 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:429— src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:429-442 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:739-752 — 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 `src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:429` 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 (14 lines × 2) src/main/java/com/devoxx/genie/chatmodel/cloud/router/RouterRegistry.java:82— src/main/java/com/devoxx/genie/chatmodel/cloud/router/RouterRegistry.java:82-95 | src/main/java/com/devoxx/genie/chatmodel/local/compatible/LocalProviderRegistry.java:74-87 — 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.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:309— src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:309-343 | src/main/java/com/devoxx/genie/service/mcp/MCPApprovalService.java:91-146 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:339— src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:339-375 | src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:377-407 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:147— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:147-196 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:288-342 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:289-313 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:364-386 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:162-218 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:132-181 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:100-120 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 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 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:991— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:991-1007 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:140-156 | src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java:352-368 | src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:378-399 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:210-226 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:230-241 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:290-306 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 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 7 times.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×2
Edited copy of a member (49 corresponding lines) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:132— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:132-193 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1168-1216 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (49 corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:21— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:21-69 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:21-76 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:33— src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:33-58 | src/main/java/com/devoxx/genie/ui/component/JEditorPaneUtils.java:66-91 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) src/main/java/com/devoxx/genie/service/prompt/memory/ChatMemoryService.java:112— src/main/java/com/devoxx/genie/service/prompt/memory/ChatMemoryService.java:112-144 | src/main/java/com/devoxx/genie/service/prompt/memory/ChatMemoryService.java:224-249 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×2
Edited copies of one member (3 members, 23+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/TestResultParser.java:53— src/main/java/com/devoxx/genie/service/agent/tool/TestResultParser.java:53-80 | src/main/java/com/devoxx/genie/service/agent/tool/TestResultParser.java:82-108 | src/main/java/com/devoxx/genie/service/agent/tool/TestResultParser.java:110-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 23+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:175— src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:175-197 | src/main/java/com/devoxx/genie/service/agent/AgentLoopTracker.java:206-237 | src/main/java/com/devoxx/genie/service/agent/tool/ParallelExploreToolExecutor.java:162-184 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:54— src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:54-72 | src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:75-93 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:357— src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:357-377 | src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:384-402 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java:48— src/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java:48-73 | src/main/java/com/devoxx/genie/service/agent/tool/SearchFilesToolExecutor.java:80-104 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:29— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:29-53 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:22-62 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:215— src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:215-226 | src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:718-731 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:216— src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:216-227 | src/main/java/com/devoxx/genie/service/agent/tool/RunTestsToolExecutor.java:130-142 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java:225— src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java:225-231 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:432-436 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java:246— src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java:246-251 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:495-499 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (35 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:101— src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:101-135 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:138-172 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (35 lines × 2) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:197— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:197-231 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:262-296 — 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 `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:197` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:195` calls `addOpenAiModels` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:260` 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 (16 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:67— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:67-82 | src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java:89-104 — 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 (16 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:57— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:57-72 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindReferencesToolExecutor.java:60-75 — 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 (15 lines × 3) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25-39 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:25-39 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:25-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25` 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/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:40` calls `findChild` and `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java: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 (15 lines × 3) src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:428— src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:428-442 | src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:473-487 | src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:606-620 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:428` 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 (14 lines × 3) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:62— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:62-75 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:68-81 | src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java:84-97 — 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. 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 × 3) src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:225— src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:225-238 | src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:324-337 | src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:362-375 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/conversations/ConversationStorageService.java:225` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (13 lines × 3) src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java:23— src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java:23-35 | src/main/java/com/devoxx/genie/chatmodel/cloud/glm/GLMChatModelFactory.java:23-35 | src/main/java/com/devoxx/genie/chatmodel/cloud/kimi/KimiChatModelFactory.java:23-35 — before extracting anything, compare `src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/cloud/glm/GLMChatModelFactory.java` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 3) src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:165— src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:165-177 | src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:210-222 | src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:246-258 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:165` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (13 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/BacklogMilestoneToolExecutor.java:185— src/main/java/com/devoxx/genie/service/agent/tool/BacklogMilestoneToolExecutor.java:185-197 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogMilestoneToolExecutor.java:230-242 — 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/main/java/com/devoxx/genie/service/models/ModelConfigService.java:119— src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:119-135 | src/main/java/com/devoxx/genie/service/tips/TipService.java:140-152 — 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 (11–12 lines × 6) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:148— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:148-159 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:289-300 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:290-300 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:365-375 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:163-174 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:133-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:146` calls `SuppressWarnings` and `src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:362` 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 (11–12 lines × 6) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1053— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1053-1064 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1066-1077 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1079-1090 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1092-1103 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1105-1116 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1117-1127 — all 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1053` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 lines × 3) src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java:39— src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java:39-50 | src/main/java/com/devoxx/genie/chatmodel/cloud/glm/GLMChatModelFactory.java:39-50 | src/main/java/com/devoxx/genie/chatmodel/cloud/kimi/KimiChatModelFactory.java:39-50 — before extracting anything, compare `src/main/java/com/devoxx/genie/chatmodel/cloud/deepseek/DeepSeekChatModelFactory.java` and `src/main/java/com/devoxx/genie/chatmodel/cloud/glm/GLMChatModelFactory.java` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 3) src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java:147— src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java:147-158 | src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java:183-194 | src/main/java/com/devoxx/genie/ui/settings/copyproject/CopyProjectSettingsComponent.java:267-278 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11–12 lines × 2) src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:32— src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:32-42 | src/main/java/com/devoxx/genie/ui/mcp/MCPToolsManager.java:60-71 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:32` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/ui/mcp/MCPToolsManager.java:59` calls `setToolTipText` and `src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:31` 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 (11–12 lines × 2) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:611— src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:611-622 | src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:628-638 — 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 `src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:611` 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 (10 lines × 2) src/main/java/com/devoxx/genie/ui/settings/commands/CommandsSettingsComponent.java:65— src/main/java/com/devoxx/genie/ui/settings/commands/CommandsSettingsComponent.java:65-74 | src/main/java/com/devoxx/genie/ui/settings/skill/SkillsSettingsComponent.java:98-107 — 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 (10 lines × 2) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:511— src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:511-520 | src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:576-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:511` 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 (7–9 lines × 2) src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:108— src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:108-116 | src/main/java/com/devoxx/genie/service/tips/TipService.java:131-137 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:108` 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 (7–9 lines × 2) src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceInstallDialog.java:50— src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceInstallDialog.java:50-56 | src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPServerDialog.java:124-132 — 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.
Outbound HTTP without resilience src/main/java/com/devoxx/genie/chatmodel/local/compatible/CompactJsonHttpClient.java:24— `HttpClient {` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience src/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingModelFactory.java:39— `HttpClient.newBuilder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Dead file (~26 LoC) docusaurus/src/components/HomepageFeatures/icons/SecurityScanner.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~26 LoC) docusaurus/src/plugins/schema-plugin/index.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~21 LoC) docusaurus/src/components/HomepageFeatures/icons/ChatMemory.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~21 LoC) docusaurus/src/components/HomepageFeatures/icons/ProjectScanner.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) docusaurus/src/components/HomepageFeatures/icons/InlineCompletion.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~19 LoC) docusaurus/src/components/HomepageFeatures/icons/WebSearch.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark src/main/resources/webview/html/kanban.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement docusaurus/src/css/custom.css:54— `.feature-card a` 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.
ProjectIndexerService.indexFiles (cyclomatic 30) src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java:106— ProjectIndexerService.indexFiles 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.
ExoClusterPanel.parseState (cyclomatic 26) src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:114— ExoClusterPanel.parseState 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.
CombinedLogEntryRenderer.resolveEntryColor (cyclomatic 23) src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:911— CombinedLogEntryRenderer.resolveEntryColor has cyclomatic complexity 23 (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.
FindDeadCodeToolExecutor.findDeadCode (cyclomatic 20) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:67— FindDeadCodeToolExecutor.findDeadCode 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.
PhpProjectScannerExtension.enhanceProjectInfo (cyclomatic 19) src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:21— PhpProjectScannerExtension.enhanceProjectInfo has cyclomatic complexity 19 (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.
PythonProjectScannerExtension.enhanceProjectInfo (cyclomatic 19) src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:21— PythonProjectScannerExtension.enhanceProjectInfo has cyclomatic complexity 19 (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.
SpecFrontmatterParser.parseSections (cyclomatic 19) src/main/java/com/devoxx/genie/service/spec/SpecFrontmatterParser.java:223— SpecFrontmatterParser.parseSections 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.
AgentMcpLogPanel.formatAgentActivityMessage (cyclomatic 19) src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:550— AgentMcpLogPanel.formatAgentActivityMessage has cyclomatic complexity 19 (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.
ConversationViewModel.onActivityMessage (cyclomatic 19) src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:418— ConversationViewModel.onActivityMessage has cyclomatic complexity 19 (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.
PhpProjectScannerExtension.enhanceBuildSystem (cyclomatic 18) src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:162— PhpProjectScannerExtension.enhanceBuildSystem 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.
OpengrepScanner.parseOutput (cyclomatic 18) src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:44— OpengrepScanner.parseOutput 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.
AgentMcpLogPanel.formatForListRow (cyclomatic 18) src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:641— AgentMcpLogPanel.formatForListRow 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.
AiBubbleKt.AiBubble (cyclomatic 18) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:311— AiBubbleKt.AiBubble 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.
BacklogTaskToolExecutor.createTask (cyclomatic 17) src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:73— BacklogTaskToolExecutor.createTask has cyclomatic complexity 17 (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.
SpecFrontmatterGenerator.generate (cyclomatic 17) src/main/java/com/devoxx/genie/service/spec/SpecFrontmatterGenerator.java:20— SpecFrontmatterGenerator.generate has cyclomatic complexity 17 (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.
TokenCalculationService.showOnlyScanInfo (cyclomatic 17) src/main/java/com/devoxx/genie/service/TokenCalculationService.java:53— TokenCalculationService.showOnlyScanInfo has cyclomatic complexity 17 (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.
CommandKeyListener.keyPressed (cyclomatic 17) src/main/java/com/devoxx/genie/ui/component/input/CommandAutoCompleteTextField.java:134— CommandKeyListener.keyPressed has cyclomatic complexity 17 (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.
FeatureUsageTracker.emitForPrompt (cyclomatic 16) src/main/java/com/devoxx/genie/service/analytics/FeatureUsageTracker.java:40— FeatureUsageTracker.emitForPrompt 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.
ProviderErrorTranslator.translateCloudflare (cyclomatic 16) src/main/java/com/devoxx/genie/service/prompt/error/ProviderErrorTranslator.java:49— ProviderErrorTranslator.translateCloudflare 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.
createSitemapItems (cyclomatic 16) REDACTED:105— createSitemapItems has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 108). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Hotspot: src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java:106— src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ProjectIndexerService.indexFiles at line 106. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 09:34:41 +01:00' --until='2026-11-16 09:34:41 +01:00' --full-history --no-merges -- src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java`: 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.
ExoClusterPanel.parseState (cognitive 57) src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java:114— ExoClusterPanel.parseState has cognitive complexity 57 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 4 (11 pts), ternaries 3 (9 pts), boolean chains 7 (nesting depth added 31). 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.
ProjectIndexerService.indexFiles (cognitive 41) src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java:106— ProjectIndexerService.indexFiles has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 5, ternaries 3 (5 pts), error handling 2 (4 pts), loops 3 (4 pts) (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.
OpengrepScanner.parseOutput (cognitive 35) src/main/java/com/devoxx/genie/service/security/OpengrepScanner.java:44— OpengrepScanner.parseOutput has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (28 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 18). 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.
AgentMcpLogPanel.formatForListRow (cognitive 33) src/main/java/com/devoxx/genie/ui/panel/log/AgentMcpLogPanel.java:641— AgentMcpLogPanel.formatForListRow has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 2 (7 pts), boolean chains 4, loops 1 (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.
TokenCalculationService.showOnlyScanInfo (cognitive 31) src/main/java/com/devoxx/genie/service/TokenCalculationService.java:53— TokenCalculationService.showOnlyScanInfo has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts) (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.
kanban.document.addEventListener("mouseup") (cognitive 31) src/main/resources/webview/js/kanban.js:245— kanban.document.addEventListener("mouseup") has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 2 (nesting depth added 17). 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.
(anonymous) (cognitive 31) src/main/resources/webview/js/kanban.js:245— (anonymous) has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 2 (nesting depth added 17). 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.
FindDeadCodeToolExecutor.findDeadCode (cognitive 28) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:67— FindDeadCodeToolExecutor.findDeadCode has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), loops 4, 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.
MCPSettingsComponent.importFromJson (cognitive 28) src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:161— MCPSettingsComponent.importFromJson has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (7 pts), error handling 2 (4 pts) (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.
ConversationManager.updateTabDisplayName (cognitive 23) src/main/java/com/devoxx/genie/ui/panel/conversation/ConversationManager.java:178— ConversationManager.updateTabDisplayName has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (15 pts), ternaries 1 (5 pts), boolean chains 2, loops 1 (nesting depth added 14). 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.
SpecFrontmatterGenerator.generate (cognitive 22) src/main/java/com/devoxx/genie/service/spec/SpecFrontmatterGenerator.java:20— SpecFrontmatterGenerator.generate has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 2 (6 pts), loops 2 (4 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.
AcpTransport.close (cognitive 21) src/main/java/com/devoxx/genie/service/acp/protocol/AcpTransport.java:259— AcpTransport.close has cognitive complexity 21 (threshold 15). Drivers by points: error handling 9 (17 pts), if/else 3 (4 pts) (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.
ChatMemoryManager.sanitizeOrphanedToolMessages (cognitive 21) REDACTED:286— ChatMemoryManager.sanitizeOrphanedToolMessages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4 (8 pts), boolean chains 2, 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.
SpecTaskRunnerService.executeNextLayer (cognitive 21) src/main/java/com/devoxx/genie/service/spec/SpecTaskRunnerService.java:592— SpecTaskRunnerService.executeNextLayer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2, ternaries 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.
CommandKeyListener.keyPressed (cognitive 21) src/main/java/com/devoxx/genie/ui/component/input/CommandAutoCompleteTextField.java:134— CommandKeyListener.keyPressed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, ternaries 1 (2 pts) (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.
MCPSettingsComponent.apply (cognitive 21) src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:392— MCPSettingsComponent.apply has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (6 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.
OllamaApiService.findContextLength (cognitive 20) src/main/java/com/devoxx/genie/chatmodel/local/ollama/OllamaApiService.java:77— OllamaApiService.findContextLength has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 1 (4 pts), loops 2 (4 pts), boolean chains 3 (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.
VcsCommitListener.beforeCheckin (cognitive 20) src/main/java/com/devoxx/genie/service/automation/listeners/VcsCommitListener.java:33— VcsCommitListener.beforeCheckin has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (6 pts), boolean chains 2, error handling 1 (2 pts), loops 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.
DevoxxGenieStateService.migrateCredentialsToPasswordSafe (cognitive 20) src/main/java/com/devoxx/genie/ui/settings/DevoxxGenieStateService.java:1306— DevoxxGenieStateService.migrateCredentialsToPasswordSafe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 3 (5 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (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.
DevoxxGenieToolWindowFactory.updateSpecTabs (cognitive 20) src/main/java/com/devoxx/genie/ui/window/DevoxxGenieToolWindowFactory.java:261— DevoxxGenieToolWindowFactory.updateSpecTabs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 1 (2 pts) (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.
AnalyticsEventBuilder.build (cognitive 19) src/main/java/com/devoxx/genie/service/analytics/AnalyticsEventBuilder.java:79— AnalyticsEventBuilder.build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 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.
PhpProjectScannerExtension.enhanceBuildSystem (cognitive 19) src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:162— PhpProjectScannerExtension.enhanceBuildSystem has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6 (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.
PythonProjectScannerExtension.enhanceProjectInfo (cognitive 19) src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:21— PythonProjectScannerExtension.enhanceProjectInfo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 3, error handling 2 (3 pts) (nesting depth added 1). 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.
ClaudeStreamJsonParser.extractContentText (cognitive 19) src/main/java/com/devoxx/genie/service/cli/ClaudeStreamJsonParser.java:246— ClaudeStreamJsonParser.extractContentText has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 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.
ProjectIndexerService.isRagExcluded (cognitive 19) src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java:414— ProjectIndexerService.isRagExcluded has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 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.
Trace.walk (cognitive 18) src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java:136— Trace.walk has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1, ternaries 1 (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.
BacklogTaskToolExecutor.createTask (cognitive 18) src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:73— BacklogTaskToolExecutor.createTask has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, loops 2 (4 pts), boolean chains 1 (nesting depth added 2). 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.
PhpProjectScannerExtension.enhanceProjectInfo (cognitive 18) src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:21— PhpProjectScannerExtension.enhanceProjectInfo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, boolean chains 5, error handling 1. 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.
ProviderErrorTranslator.translateCloudflare (cognitive 18) src/main/java/com/devoxx/genie/service/prompt/error/ProviderErrorTranslator.java:49— ProviderErrorTranslator.translateCloudflare has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, ternaries 1 (nesting depth added 3). 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.
SpecFrontmatterParser.parseFrontmatter (cognitive 18) src/main/java/com/devoxx/genie/service/spec/SpecFrontmatterParser.java:70— SpecFrontmatterParser.parseFrontmatter has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 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.
SpecTaskRunnerService.runTasks (cognitive 18) src/main/java/com/devoxx/genie/service/spec/SpecTaskRunnerService.java:144— SpecTaskRunnerService.runTasks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, error handling 2 (4 pts), ternaries 3, loops 1 (2 pts), 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.
MCPMarketplaceInstallDialog.populateEnvVars (cognitive 18) src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceInstallDialog.java:215— MCPMarketplaceInstallDialog.populateEnvVars has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 2 (6 pts), ternaries 1 (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.
PromptSettingsComponent.createShortcutPanel (cognitive 18) src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java:370— PromptSettingsComponent.createShortcutPanel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15 (18 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.
AiBubbleKt.AiBubble (cognitive 18) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:311— AiBubbleKt.AiBubble has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, match/switch 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.
Trace.render (cognitive 17) src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java:173— Trace.render has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 6 (7 pts), loops 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.
SearchFilesToolExecutor.searchInDirectory (cognitive 17) src/main/java/com/devoxx/genie/service/agent/tool/SearchFilesToolExecutor.java:113— SearchFilesToolExecutor.searchInDirectory has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, 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.
FeatureUsageTracker.emitForPrompt (cognitive 17) src/main/java/com/devoxx/genie/service/analytics/FeatureUsageTracker.java:40— FeatureUsageTracker.emitForPrompt has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, error handling 1, ternaries 1 (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.
MCPConfigurationParser.parseServerConfig (cognitive 17) src/main/java/com/devoxx/genie/service/mcp/MCPConfigurationParser.java:89— MCPConfigurationParser.parseServerConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts), boolean chains 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.
CalculateComplexityToolExecutor.compute (cognitive 16) src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:69— CalculateComplexityToolExecutor.compute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (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.
PsiToolUtils.findNamedElementOnLine (cognitive 16) src/main/java/com/devoxx/genie/service/agent/tool/psi/PsiToolUtils.java:173— PsiToolUtils.findNamedElementOnLine 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.
GoProjectScannerExtension.detectGoTools (cognitive 16) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:156— GoProjectScannerExtension.detectGoTools has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 2 (4 pts), ternaries 1 (3 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.
RAGFileWatcher.handleEvents (cognitive 16) src/main/java/com/devoxx/genie/service/rag/watcher/RAGFileWatcher.java:106— RAGFileWatcher.handleEvents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (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.
ChunkQualityFilter.countDistinctMeaningfulTokens (cognitive 16) src/main/java/com/devoxx/genie/service/rag/ChunkQualityFilter.java:43— ChunkQualityFilter.countDistinctMeaningfulTokens has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 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.
TipService.selectWeighted (cognitive 16) src/main/java/com/devoxx/genie/service/tips/TipService.java:197— TipService.selectWeighted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4, boolean chains 3 (nesting depth added 3). 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.
ApNewRunPanel.pollOnce (cognitive 16) src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:576— ApNewRunPanel.pollOnce has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 2, error handling 1, 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.
ApNewRunPanel.renderProgressTail (cognitive 16) src/main/java/com/devoxx/genie/ui/panel/ap/ApNewRunPanel.java:652— ApNewRunPanel.renderProgressTail has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 1, if/else 1, loops 1 (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.
MCPMarketplaceInstallDialog.createCenterPanel (cognitive 16) src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPMarketplaceInstallDialog.java:49— MCPMarketplaceInstallDialog.createCenterPanel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (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.
AiBubbleKt.ErrorCard (cognitive 16) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:503— AiBubbleKt.ErrorCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 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.
FunctionTooLong: index.Home docusaurus/src/pages/index.js:78— FunctionTooLong — Home runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.86× 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.
Near-duplicate member pair (51 shared lines) src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:36— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:36-105 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:41-109 — These two members are variants of one another: 51 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.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:104— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:104-133 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:71-95 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:78-116 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:91-120 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:96-130 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:64-98 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 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 6 times.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:574— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:574-647 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:649-733 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:56— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:56-92 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindReferencesToolExecutor.java:59-105 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:472— src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:472-524 | src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt:605-663 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:123— src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:123-177 | src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:179-222 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:97— src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:97-149 | src/main/java/com/devoxx/genie/service/tips/TipService.java:128-163 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) src/main/java/com/devoxx/genie/service/MessageCreationService.java:315— src/main/java/com/devoxx/genie/service/MessageCreationService.java:315-343 | src/main/java/com/devoxx/genie/ui/util/CodeLanguageUtil.java:21-56 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:92— src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:92-112 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:317-341 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/AgentApprovalProvider.java:59— src/main/java/com/devoxx/genie/service/agent/AgentApprovalProvider.java:59-96 | src/main/java/com/devoxx/genie/service/mcp/ApprovalRequiredToolProvider.java:43-80 | src/main/java/com/devoxx/genie/service/mcp/InstrumentedMcpToolProvider.java:44-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:29— src/main/java/com/devoxx/genie/ui/agent/AgentToggleManager.java:29-48 | src/main/java/com/devoxx/genie/ui/mcp/MCPToolsManager.java:56-78 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:213— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:213-230 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:232-254 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:187-205 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/ReadFileToolExecutor.java:24— src/main/java/com/devoxx/genie/service/agent/tool/ReadFileToolExecutor.java:24-36 | src/main/java/com/devoxx/genie/service/agent/tool/psi/DocumentSymbolsToolExecutor.java:33-45 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java:54-65 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindSymbolsToolExecutor.java:37-51 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:211— src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:211-221 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:385-400 | src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:564-577 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:140— src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:140-154 | src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:372-385 | src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:387-399 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:23— src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:23-31 | src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:33-41 | src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:43-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:87— src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:87-101 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:256-267 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:269-281 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:305-318 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogToolSpecifications.java:320-331 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:166— src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:166-179 | src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:368-382 | src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/MCPServerDialog.java:223-236 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) src/main/java/com/devoxx/genie/action/AddSnippetAction.java:72— src/main/java/com/devoxx/genie/action/AddSnippetAction.java:72-79 | src/main/java/com/devoxx/genie/ui/panel/ActionButtonsPanel.java:166-172 | src/main/java/com/devoxx/genie/ui/panel/FileSelectionPanelFactory.java:277-283 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) src/main/java/com/devoxx/genie/service/cli/command/CodexCliCommand.java:20— src/main/java/com/devoxx/genie/service/cli/command/CodexCliCommand.java:20-26 | src/main/java/com/devoxx/genie/service/cli/command/KimiCliCommand.java:35-42 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (31 lines × 2) src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:310— src/main/java/com/devoxx/genie/service/agent/AgentApprovalService.java:310-340 | src/main/java/com/devoxx/genie/service/mcp/MCPApprovalService.java:106-136 — 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 (30 lines × 3) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:257— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:257-286 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:322-351 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:219-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 2) src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:77— src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:77-105 | src/main/java/com/devoxx/genie/service/agent/tool/ReadOnlyToolProvider.java:40-68 — 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/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:77` 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 (22–23 lines × 2) src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:49— src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:49-70 | src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java:57-79 — before extracting anything, compare `src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java` and `src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:49` 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. 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 (19–21 lines × 2) src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:149— src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:149-169 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:285-303 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java` and `src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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/main/java/com/devoxx/genie/service/prompt/strategy/AcpPromptStrategy.java:149` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (19 lines × 2) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:491— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:491-509 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:841-859 — 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 `src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:491` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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/main/java/com/devoxx/genie/ui/dialog/CustomPromptDialog.java:43— src/main/java/com/devoxx/genie/ui/dialog/CustomPromptDialog.java:43-60 | src/main/java/com/devoxx/genie/ui/dialog/PersonaDialog.java:44-59 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25-41 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:25-41 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java` and `src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25` 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 (16–17 lines × 2) src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:417— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:417-433 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:804-819 — 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 `src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:417` 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 lines × 3) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25-40 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:27-42 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:25-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:25` 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–15 lines × 2) src/main/java/com/devoxx/genie/service/prompt/response/nonstreaming/NonStreamingPromptExecutionService.java:239— src/main/java/com/devoxx/genie/service/prompt/response/nonstreaming/NonStreamingPromptExecutionService.java:239-253 | src/main/java/com/devoxx/genie/service/prompt/strategy/StreamingPromptStrategy.java:243-254 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/prompt/response/nonstreaming/NonStreamingPromptExecutionService.java:239` 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–14 lines × 3) src/main/java/com/devoxx/genie/service/agent/AgentApprovalProvider.java:60— src/main/java/com/devoxx/genie/service/agent/AgentApprovalProvider.java:60-71 | src/main/java/com/devoxx/genie/service/mcp/ApprovalRequiredToolProvider.java:44-57 | src/main/java/com/devoxx/genie/service/mcp/InstrumentedMcpToolProvider.java:45-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/agent/AgentApprovalProvider.java:60` 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 (13–14 lines × 2) src/main/java/com/devoxx/genie/ui/dialog/CustomPromptDialog.java:25— src/main/java/com/devoxx/genie/ui/dialog/CustomPromptDialog.java:25-38 | src/main/java/com/devoxx/genie/ui/dialog/PersonaDialog.java:27-39 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 5) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:32— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:32-44 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:24-36 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:24-36 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:24-36 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:24-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:32` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:40` calls `findChild` and `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java: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 (12 lines × 6) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:112— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:112-123 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:76-87 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:83-94 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:96-107 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:108-119 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:68-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:104` calls `contains`, `put` and `src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:109` 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 (11–12 lines × 5) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:510— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:510-521 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:523-534 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:536-547 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:549-560 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:561-571 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:510` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 lines × 4) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:156— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:156-167 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:55-66 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:35-46 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:66-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:68` calls `JPanel`, `FlowLayout`, `add` and `src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:169` 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 (11 lines × 13) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:198— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:198-208 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:211-221 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:224-234 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:237-247 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:250-260 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:263-273 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:276-286 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:289-299 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:302-312 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:315-325 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:328-338 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:341-351 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:354-364 — all 13 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:195` calls `addOpenAiModels` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:208` 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 × 11) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:370— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:370-380 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:382-392 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:394-404 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:406-416 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:418-428 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:430-440 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:442-452 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:454-464 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:466-476 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:478-488 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:489-498 — all 11 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:370` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (10–11 lines × 6) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:578— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:578-588 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:590-600 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:602-612 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:614-624 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:626-636 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:637-646 — all 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:578` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:578` calls `builder` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:637` 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 (11 lines × 3) src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:267— src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:267-277 | src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:298-308 | src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:322-332 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolProvider.java:267` 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 (10–11 lines × 4) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1171— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1171-1181 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1183-1193 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1195-1205 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1206-1215 — all 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1171` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1171` calls `builder` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1206` 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 × 2) src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:230— src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:230-240 | src/main/java/com/devoxx/genie/service/agent/tool/BacklogTaskToolExecutor.java:246-255 — 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 (10–11 lines × 3) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1133— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1133-1143 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1145-1155 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1156-1165 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (9–10 lines × 22) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:771— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:771-780 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:782-791 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:793-802 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:804-813 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:815-830 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:832-842 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:844-854 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:856-866 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:868-878 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:880-890 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:892-901 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:903-927 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:929-939 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:941-951 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:953-963 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:965-976 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:978-988 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:990-1002 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1004-1014 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1016-1026 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1028-1038 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:1039-1047 — all 22 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:771` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (10 lines × 7) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:651— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:651-660 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:663-672 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:675-684 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:687-696 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:699-708 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:711-720 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:723-732 — all 7 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:649` calls `addMistralModels` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:660` 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 lines × 6) src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:31— src/main/java/com/devoxx/genie/service/analyzer/languages/cpp/CppProjectScannerExtension.java:31-40 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:23-32 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:23-32 | src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:23-32 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:23-32 | src/main/java/com/devoxx/genie/service/analyzer/languages/rust/RustProjectScannerExtension.java:24-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. 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 × 5) src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:135— src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:135-144 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:147-156 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:159-168 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:171-180 | src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:183-192 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:195` calls `addOpenAiModels` and `src/main/java/com/devoxx/genie/service/models/LLMModelRegistryService.java:146` 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 × 5) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:57— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:57-65 | src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:27-35 | src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:26-34 | src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java:163-171 | src/main/java/com/devoxx/genie/chatmodel/local/LocalChatModelFactory.java:73-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:57` 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 before the matched lines, `src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:24` calls `baseUrl` and `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:23` 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/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:44— src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:44-52 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDefinitionToolExecutor.java:37-45 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindImplementationsToolExecutor.java:39-47 | src/main/java/com/devoxx/genie/service/agent/tool/psi/FindReferencesToolExecutor.java:42-50 — 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. 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/main/java/com/devoxx/genie/service/agent/tool/psi/FindDefinitionToolExecutor.java:36` calls `getInt`, `arguments` and `src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java:43` 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 lines × 4) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:992— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:992-1007 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:141-156 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:211-226 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:291-306 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:454— src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:454-463 | src/main/java/com/devoxx/genie/service/analyzer/util/CachedProjectScanner.java:328-336 | src/main/java/com/devoxx/genie/service/analyzer/util/GitignoreParser.java:235-244 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:535— src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:535-542 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:881-889 — 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 × 5) src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:126— src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:126-133 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:138-145 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:150-157 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:162-169 | src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:174-181 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/chatmodel/cloud/bedrock/BedrockModelFactory.java:126` 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 (8 lines × 4) src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:42— src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:42-49 | src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:40-47 | src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java:178-185 | src/main/java/com/devoxx/genie/chatmodel/local/LocalChatModelFactory.java:88-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:42` 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 before the matched lines, `src/main/java/com/devoxx/genie/chatmodel/cloud/deepinfra/DeepInfraChatModelFactory.java:40` calls `baseUrl` and `src/main/java/com/devoxx/genie/chatmodel/cloud/mistral/MistralChatModelFactory.java:38` 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 × 3) src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:124— src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:124-131 | src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:180-187 | src/main/java/com/devoxx/genie/ui/settings/appearance/AppearanceSettingsComponent.java:225-232 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 6) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:996— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:996-1003 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:145-152 | src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java:357-364 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:215-222 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:232-239 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:295-302 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 6) src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:995— src/main/java/com/devoxx/genie/ui/settings/agent/AgentSettingsComponent.java:995-1001 | src/main/java/com/devoxx/genie/ui/settings/completion/CompletionSettingsComponent.java:144-150 | src/main/java/com/devoxx/genie/ui/settings/prompt/PromptSettingsComponent.java:356-362 | src/main/java/com/devoxx/genie/ui/settings/rag/RAGSettingsComponent.java:379-385 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:214-220 | src/main/java/com/devoxx/genie/ui/settings/security/SecurityScanSettingsComponent.java:294-300 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
Duplicated block (4–7 lines × 3) src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:122— src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:122-128 | src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java:217-220 | src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java:239-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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. 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 (5 lines × 5) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:131— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:131-135 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:232-240 | src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:269-277 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:126-130 | src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:163-167 — there are 5 copies across 3 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:131` 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. 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 (5 lines × 3) src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:216— src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:216-220 | src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:235-239 | src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java:191-195 — before extracting anything, compare `src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java` and `src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:216` 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 (3–5 lines × 3) src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:143— src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:143-149 | src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:161-165 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:589-591 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:589` 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/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java:160` calls `getBasePath` and `src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:141` 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 (4–5 lines × 3) src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:92— src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:92-95 | src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:108-112 | src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:116-120 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:108` 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/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:89` calls `get` and `src/main/java/com/devoxx/genie/service/generator/content/PromptBuilder.java:105` 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 (5 lines × 2) src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:399— src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:399-403 | src/main/java/com/devoxx/genie/ui/panel/LlmProviderPanel.java:475-479 — 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 × 3) src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:316— src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:316-321 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:342-347 | src/main/java/com/devoxx/genie/ui/settings/runner/RunnerSettingsComponent.java:736-741 — 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.
Duplicated block (27 lines × 2) src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:187— src/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:187-213 | src/main/kotlin/com/devoxx/genie/ui/compose/components/UserBubble.kt:39-65 — 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/main/kotlin/com/devoxx/genie/ui/compose/components/AiBubble.kt:187` 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 (17–18 lines × 2) src/main/kotlin/com/devoxx/genie/ui/compose/components/ChangedFilesSection.kt:53— src/main/kotlin/com/devoxx/genie/ui/compose/components/ChangedFilesSection.kt:53-69 | src/main/kotlin/com/devoxx/genie/ui/compose/components/FileReferencesSection.kt:45-62 — 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/main/kotlin/com/devoxx/genie/ui/compose/components/ChangedFilesSection.kt:53` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14–15 lines × 3) src/main/kotlin/com/devoxx/genie/ui/compose/components/ActivitySection.kt:68— src/main/kotlin/com/devoxx/genie/ui/compose/components/ActivitySection.kt:68-82 | src/main/kotlin/com/devoxx/genie/ui/compose/components/ChangedFilesSection.kt:38-51 | src/main/kotlin/com/devoxx/genie/ui/compose/components/FileReferencesSection.kt:29-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/com/devoxx/genie/ui/compose/components/ActivitySection.kt:68` 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 (34 lines × 2 locations) docusaurus/placeholder-setup.js:57— docusaurus/placeholder-setup.js:57 · docusaurus/static/img/create-placeholders.js:117 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (20 lines × 2 locations) docusaurus/scripts/fix-image-paths.js:51— docusaurus/scripts/fix-image-paths.js:51 · docusaurus/scripts/update-metadata.js:137 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) docusaurus/src/pages/index.js:274— docusaurus/src/pages/index.js:274 · docusaurus/src/pages/index.js:396 — 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 (17 lines × 3 locations) docusaurus/placeholder-setup.js:74— docusaurus/placeholder-setup.js:74 · docusaurus/static/img/copy-placeholders.js:25 · docusaurus/static/img/create-placeholders.js:134 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 3 locations) docusaurus/src/pages/index.js:250— docusaurus/src/pages/index.js:250 · docusaurus/src/pages/index.js:302 · docusaurus/src/pages/index.js:424 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3 locations) docusaurus/src/pages/index.js:232— docusaurus/src/pages/index.js:232 · docusaurus/src/pages/index.js:284 · docusaurus/src/pages/index.js:406 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication· Duplicated block with local edits (8 matched lines × 2 locations) · ×1
Duplicated block with local edits (8 matched lines × 2 locations) src/main/resources/webview/js/kanban.js:245— src/main/resources/webview/js/kanban.js:245 · src/main/resources/webview/js/kanban.js:300 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (6 lines × 2 locations) docusaurus/generate-png-placeholders.js:80— docusaurus/generate-png-placeholders.js:80 · docusaurus/placeholder-setup.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function (anonymous) (cyclomatic 16, cognitive 14) REDACTED:108— (anonymous) has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 31) src/main/resources/webview/js/kanban.js:245— (anonymous) has cyclomatic complexity 13 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· docusaurus/src/pages/index.js · ×1
docusaurus/src/pages/index.js: 460 lines of code docusaurus/src/pages/index.js:1— docusaurus/src/pages/index.js has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~142 LoC) docusaurus/src/components/HomepageFeatures/index.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~67 LoC) docusaurus/create-placeholders.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~63 LoC) docusaurus/src/components/NewsletterSignup/index.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~32 LoC) docusaurus/src/components/HomepageFeatures/icons/SpecDrivenDev.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~23 LoC) docusaurus/src/components/HomepageFeatures/icons/SubAgents.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~22 LoC) docusaurus/src/components/HomepageFeatures/icons/MCPMarketplace.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~18 LoC) docusaurus/src/components/HomepageFeatures/icons/CliRunners.js— no import path from any entry point (16 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docusaurus/src/components/HomepageFeatures/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unlisted import '@docusaurus/plugin-content-docs' docusaurus/sidebars.js:14— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unused dependency '@docusaurus/module-type-aliases' docusaurus/package.json:29— Declared in docusaurus/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@docusaurus/plugin-sitemap' docusaurus/package.json:20— Declared in docusaurus/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) src/main/java/com/devoxx/genie/ui/settings/mcp/dialog/transport/StdioTransportPanel.java:281— The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stdout and stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
Duplicated predicate src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java:75— `!PsiToolUtils.isJavaAvailable() || !PsiToolUtils.isJavaFile(psiFile)` appears character-identically in 4 files — src/main/java/com/devoxx/genie/service/agent/tool/psi/CalculateComplexityToolExecutor.java, src/main/java/com/devoxx/genie/service/agent/tool/psi/FindCalleesToolExecutor.java, src/main/java/com/devoxx/genie/service/agent/tool/psi/FindDeadCodeToolExecutor.java, src/main/java/com/devoxx/genie/service/agent/tool/psi/TraceCallChainsToolExecutor.java. 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/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java:221— `!file.isDirectory() && globPattern.matcher(file.getName()).matches()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/analyzer/languages/go/GoProjectScannerExtension.java, src/main/java/com/devoxx/genie/service/analyzer/languages/python/PythonProjectScannerExtension.java. 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/main/java/com/devoxx/genie/service/models/ModelConfigService.java:111— `!response.isSuccessful() || response.body() == null` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/models/ModelConfigService.java, src/main/java/com/devoxx/genie/service/tips/TipService.java. 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/main/java/com/devoxx/genie/service/models/ModelConfigService.java:157— `cachedJson == null || cachedJson.isEmpty()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/models/ModelConfigService.java, src/main/java/com/devoxx/genie/service/tips/TipService.java. 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/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java:152— `cliTool.getEnvVars() != null && !cliTool.getEnvVars().isEmpty()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/cli/CliTaskExecutorService.java, src/main/java/com/devoxx/genie/service/prompt/strategy/CliPromptStrategy.java. 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/main/java/com/devoxx/genie/ui/settings/ap/ApSettingsConfigurable.java:43— `component != null && component.isModified()` appears character-identically in 4 files — src/main/java/com/devoxx/genie/ui/settings/ap/ApSettingsConfigurable.java, src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsConfigurable.java, src/main/java/com/devoxx/genie/ui/settings/debug/DebugSettingsConfigurable.java, src/main/java/com/devoxx/genie/ui/settings/general/GeneralSettingsConfigurable.java. 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/main/java/com/devoxx/genie/service/models/ModelConfigService.java:162— `config != null && config.getSchemaVersion() <= SUPPORTED_SCHEMA_VERSION` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/models/ModelConfigService.java, src/main/java/com/devoxx/genie/service/tips/TipService.java. 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/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java:270— `current == null || !current.isDirectory()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/analyzer/languages/kotlin/KotlinProjectScannerExtension.java, src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java. 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/main/java/com/devoxx/genie/ui/util/ThemeChangeListener.java:43— `currentTheme != null && currentTheme.isDark()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/ui/util/ThemeChangeListener.java, src/main/java/com/devoxx/genie/ui/util/ThemeDetector.java. 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/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java:158— `e.getClickCount() == 2 && !e.isPopupTrigger()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentDetailsDialog.java, src/main/java/com/devoxx/genie/ui/panel/ap/ApAgentsTab.java. 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/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java:117— `end > 0 && Character.isWhitespace(text.charAt(end - 1))` appears character-identically in 2 files — src/main/java/com/devoxx/genie/completion/LMStudioFimProvider.java, src/main/java/com/devoxx/genie/completion/OllamaFimProvider.java. 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/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:317— `indicator != null && indicator.isCanceled()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java, src/main/java/com/devoxx/genie/service/rag/ProjectIndexerService.java. 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/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:127— `model != null && model.getId() != null && !model.getId().isBlank()` appears character-identically in 3 files — src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java, src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java, src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java. 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/main/java/com/devoxx/genie/service/analytics/FeatureUsageTracker.java:115— `model == null || model.getProvider() == null` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/analytics/FeatureUsageTracker.java, src/main/java/com/devoxx/genie/service/prompt/PromptExecutionService.java. 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/main/java/com/devoxx/genie/service/agent/SubAgentRunner.java:248— `modelName != null && !modelName.isBlank()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/agent/SubAgentRunner.java, src/main/java/com/devoxx/genie/service/prompt/error/ProviderErrorTranslator.java. 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/main/java/com/devoxx/genie/completion/InlineCompletionService.java:51— `modelName == null || modelName.isBlank()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/completion/InlineCompletionService.java, src/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingFingerprint.java. 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/main/java/com/devoxx/genie/service/rag/validator/EmbeddingModelValidator.java:21— `ollamaModelUrl == null || ollamaModelUrl.isEmpty()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/rag/validator/EmbeddingModelValidator.java, src/main/java/com/devoxx/genie/service/rag/validator/OllamaValidator.java. 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/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingFingerprint.java:51— `outputDimension != null && outputDimension <= 0` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingFingerprint.java, src/main/java/com/devoxx/genie/service/rag/embedding/EmbeddingProfile.java. 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/main/java/com/devoxx/genie/service/prompt/error/PromptErrorHandler.java:132— `panel != null && panel.getConversationPanel() != null && panel.getConversationPanel().viewController != null` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/prompt/error/PromptErrorHandler.java, src/main/java/com/devoxx/genie/service/prompt/strategy/NonStreamingPromptStrategy.java. 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/main/java/com/devoxx/genie/service/prompt/strategy/AbstractPromptExecutionStrategy.java:409— `panel.getConversationPanel() != null && panel.getConversationPanel().viewController != null` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/prompt/strategy/AbstractPromptExecutionStrategy.java, src/main/java/com/devoxx/genie/service/prompt/strategy/NonStreamingPromptStrategy.java. 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/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java:76— `path == null || path.isBlank() || path.equals(".")` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/agent/tool/ListFilesToolExecutor.java, src/main/java/com/devoxx/genie/service/agent/tool/SearchFilesToolExecutor.java. 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/main/java/com/devoxx/genie/service/MessageCreationService.java:166— `persona != null && persona.getPrompt() != null && !persona.getPrompt().isBlank()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/service/MessageCreationService.java, 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/main/java/com/devoxx/genie/completion/InlineCompletionService.java:46— `providerName == null || providerName.isBlank()` appears character-identically in 2 files — src/main/java/com/devoxx/genie/completion/InlineCompletionService.java, src/main/java/com/devoxx/genie/service/agent/SubAgentRunner.java. 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/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java:458— `r.has("RunnerReady") || r.has("RunnerRunning")` appears character-identically in 2 files — src/main/java/com/devoxx/genie/chatmodel/local/exo/ExoModelService.java, src/main/java/com/devoxx/genie/ui/panel/ExoClusterPanel.java. 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/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java:123— `response == null || response.getData() == null` appears character-identically in 3 files — src/main/java/com/devoxx/genie/chatmodel/cloud/cloudflare/CloudflareChatModelFactory.java, src/main/java/com/devoxx/genie/chatmodel/cloud/nvidia/NvidiaChatModelFactory.java, src/main/java/com/devoxx/genie/chatmodel/local/customopenai/CustomOpenAIChatModelFactory.java. 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.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/webview/WebServer.java:150— `error` at line 150 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/webview/WebServer.java:158— `info` at line 158 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/util/FileTypeIconUtil.java:35— `error` at line 35 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/util/FileTypeIconUtil.java:63— `error` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:229— `error` at line 229 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:235— `error` at line 235 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/ui/settings/mcp/MCPSettingsComponent.java:308— `error` at line 308 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/MessageCreationService.java:297— `warn` at line 297 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/prompt/websearch/WebSearchPromptExecutionService.java:46— `debug` at line 46 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/prompt/websearch/WebSearchPromptExecutionService.java:63— `debug` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/prompt/threading/ThreadPoolShutdownManager.java:55— `info` at line 55 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/prompt/threading/ThreadPoolShutdownManager.java:61— `info` at line 61 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:112— `info` at line 112 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:120— `info` at line 120 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:127— `warn` at line 127 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:189— `info` at line 189 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:195— `info` at line 195 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:197— `info` at line 197 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:202— `info` at line 202 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:207— `info` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:210— `info` at line 210 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:217— `info` at line 217 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:224— `info` at line 224 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:273— `info` at line 273 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/java/com/devoxx/genie/service/projectscanner/FileScanner.java:401— `debug` at line 401 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Orphaned file src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java: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/main/java/com/devoxx/genie/service/mcp/MCPConfigurationParser.java: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/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java: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/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java: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/main/java/com/devoxx/genie/service/agent/tool/ParallelExploreToolExecutor.java: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/main/java/com/devoxx/genie/service/rag/watcher/RAGFileWatcher.java: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/main/java/com/devoxx/genie/util/SafeJacksonJsonCodecFactory.java: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/main/java/com/devoxx/genie/service/mcp/MCPApprovalService.java: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/main/java/com/devoxx/genie/chatmodel/cloud/azureopenai/AzureOpenAIChatModelFactory.java: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/main/java/com/devoxx/genie/service/agent/CommandBlacklist.java: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/main/java/com/devoxx/genie/service/agent/tool/psi/FindSymbolsToolExecutor.java: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/main/java/com/devoxx/genie/service/automation/listeners/TestExecutionListener.java: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/main/java/com/devoxx/genie/service/agent/tool/psi/FindReferencesToolExecutor.java: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/main/java/com/devoxx/genie/service/agent/tool/ReadOnlyToolProvider.java: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/main/java/com/devoxx/genie/service/automation/listeners/BuildCompilationListener.java: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/main/java/com/devoxx/genie/service/agent/tool/psi/DocumentSymbolsToolExecutor.java: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/main/java/com/devoxx/genie/service/rag/manifest/JsonFileIndexManifest.java: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/main/java/com/devoxx/genie/service/automation/PromptTemplateRenderer.java: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.
Silent fallback default in catch src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:120— `readFontSize` swallows every exception into `13` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:127— `readCodeFontSize` swallows every exception into `12` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:833— `loadBlogPosts` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:870— `loadCustomPrompts` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch src/main/kotlin/com/devoxx/genie/ui/compose/viewmodel/ConversationViewModel.kt:896— `loadSkills` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/agent/tool/BuiltInToolDescriptions.java:114— `storedOverrides` swallows every exception into `return Collections.emptyMap()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:80— `readShellEnvFileSetting` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/agent/tool/RunCommandToolExecutor.java:89— `readShellSetting` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:69— `getIntArray` swallows every exception into `return Collections.emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/agent/tool/ToolArgumentParser.java:90— `getStringArray` swallows every exception into `return Collections.emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/analytics/AnalyticsService.java:252— `ideVersion` swallows every exception into `return "unknown"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/service/models/ModelConfigService.java:175— `getPluginVersion` swallows every exception into `return "unknown"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch src/main/java/com/devoxx/genie/ui/panel/conversationhistory/ConversationHistoryPanel.java:327— `formatTimeSince` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
Hand-rolled JSON/XML parsing via regex REDACTED:624— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/ProjectAnalyzer.java:607— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:96— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/php/PhpProjectScannerExtension.java:103— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:83— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:90— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:97— 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 JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex src/main/java/com/devoxx/genie/service/analyzer/languages/javascript/JavaScriptProjectScannerExtension.java:123— 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 JVM code already uses a real parser in the same package; use it here too.
Fat interface: DevoxxGenieSettingsService (129 abstract methods) src/main/java/com/devoxx/genie/service/DevoxxGenieSettingsService.java:10— `DevoxxGenieSettingsService` declares 129 abstract methods: `getAnthropicKey`, `getAwsAccessKeyId`, `getAwsBearerToken`, `getAwsBedrockAuthMode`, `getAwsProfileName`, `getAwsRegion`, `getAwsSecretKey`, `getAzureOpenAIDeployment`, `getAzureOpenAIEndpoint`, `getAzureOpenAIKey`, `getChatMemorySize`, `getCloudflareAccountId`, `getCloudflareGatewayName`, `getCloudflareKey`, `getCloudflareModelName`, `getCommands`, `getCustomOpenAIApiKey`, `getCustomOpenAIContextWindow`, `getCustomOpenAIInputCost`, `getCustomOpenAIModelName`, `getCustomOpenAIOutputCost`, `getCustomOpenAIUrl`, `getDeepInfraKey`, `getDeepSeekKey`, `getDefaultWindowContext`, `getExcludeJavaDoc`, `getExcludedDirectories`, `getExcludedFiles`, `getExoModelUrl`, `getExplainPrompt`, `getGeminiKey`, `getGlmKey`, `getGoogleCSIKey`, `getGoogleSearchKey`, `getGrokKey`, `getGroqKey`, `getIncludedFileExtensions`, `getIsWebSearchEnabled`, `getKimiKey`, `getLanguageModels`, and 89 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ConversationViewController (27 abstract methods) src/main/kotlin/com/devoxx/genie/ui/compose/ConversationViewController.kt:16— `ConversationViewController` declares 27 abstract methods: `isInitialized`, `ensureBrowserInitialized`, `dispose`, `getComponent`, `loadWelcomeContent`, `updateCustomPrompts`, `cancelPendingWelcomeLoad`, `addChatMessage`, `addUserPromptMessage`, `addSteeringMessage`, `addQueuedPromptMessage`, `removeSteeringMessage`, `updateAiMessageContent`, `addFileReferences`, `addChangedFiles`, `addSystemMessage`, `onActivityMessage`, `currentActivityGeneration`, `deactivateActivityHandlers`, `hideLoadingIndicator`, `markMCPLogsAsCompleted`, `setTerminalState`, `clearConversation`, `refreshForNewConversation`, `setRestoringConversation`, `themeChanged`, `appearanceSettingsChanged`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
redundant comment docusaurus/scripts/fix-image-paths.js:39— "Replace absolute paths with relative paths" repeats the code it sits on: 4 of its 4 words (replace, absolute, paths, relative) are already in `const updatedContent = content.replace(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment docusaurus/scripts/update-metadata.js:134— "Write updated content" repeats the code it sits on: 3 of its 3 words (write, updated, content) are already in `writeFile(filePath, updatedContent);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default on parse failure src/main/java/com/devoxx/genie/service/agent/tool/HtmlToMarkdown.java:266— `startNumberOf` returns `1` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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 in the catch or in the Javadoc, and the row stops firing.
Silent fallback default on parse failure src/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java:277— `getCategoryDisplay` returns `"Unknown"` when `IllegalArgumentException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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 in the catch or in the Javadoc, and the row stops firing.
No ADRs found build.gradle.kts:141— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `build.gradle.kts` makes this repository a deployable product (line 141).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion build.gradle.kts:1— `(repository root)` (72823 LoC, 706 module-visible types across 167 directories) overshoots its size bounds. 1 of 2 build unit(s) (Gradle, npm) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 18 of 342 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, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 342 of the 635 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/main/java/com/devoxx/genie/ui/settings/automation/EventAutomationSettingsComponent.java, src/main/java/com/devoxx/genie/service/mcp/MCPConfigurationParser.java, src/main/java/com/devoxx/genie/service/debug/RawTrafficListenerService.java, src/main/java/com/devoxx/genie/ui/settings/automation/EventAgentDialog.java, src/main/java/com/devoxx/genie/service/agent/tool/ParallelExploreToolExecutor.java, src/main/java/com/devoxx/genie/service/rag/watcher/RAGFileWatcher.java, src/main/java/com/devoxx/genie/util/SafeJacksonJsonCodecFactory.java, src/main/java/com/devoxx/genie/service/mcp/MCPApprovalService.java (and 10 more). 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.
P10 · Library API & versioning· Implementation type on the public API · ×1
Implementation type on the public API src/main/java/com/devoxx/genie/service/generator/content/impl/GradleCommandsGenerator.java:8— 4 public types in `com.devoxx.genie.service.generator.content.impl` are marked as implementation by their own namespace, folder or name: `GradleCommandsGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/GradleCommandsGenerator.java:8, `impl`), `JavaStyleGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/JavaStyleGenerator.java:8, `impl`), `RustCommandsGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/RustCommandsGenerator.java:8, `impl`), `RustStyleGenerator` (src/main/java/com/devoxx/genie/service/generator/content/impl/RustStyleGenerator.java:8, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch github-actions/npm · ×1
Dependabot does not watch github-actions/npm REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/162 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Skipped (documented): createChatModelShouldCallEnsureInstance src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoChatModelFactoryTest.java:101— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): createChatModelShouldNotThrowWhenEnsureInstanceFails src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoChatModelFactoryTest.java:117— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): createChatModelShouldReturnNonNull src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoChatModelFactoryTest.java:62— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): createStreamingChatModelShouldReturnNonNull src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoChatModelFactoryTest.java:83— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): ensureInstanceShouldSkipWhenInstanceAlreadyExists src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoModelServiceTest.java:184— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): getModelsShouldParseResponseCorrectly src/test/java/com/devoxx/genie/chatmodel/local/exo/ExoModelServiceTest.java:154— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): distributionMustNotBundlePlatformCoroutinesJars src/test/java/com/devoxx/genie/packaging/PluginDistributionPackagingTest.java:59— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): healthCheckEndpoint src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:117— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): notFoundForUnknownResource src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:163— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): serveDynamicResourceViaHttp src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:129— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): serveDynamicScriptViaHttp src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:143— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): startAndStop src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:91— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): startIsIdempotent src/test/java/com/devoxx/genie/ui/webview/WebServerTest.java:104— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
doc comments repeat the names src/main/resources/webview/js/kanban.js:379— 0 of 0 documented parameters and 1 of 13 summaries in `.` only repeat the member or parameter name (e.g. "Find a task object by its ID." for `findTaskById`). Delete the restating tags, or add what the name does not say.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/kotlin/com/devoxx/genie/ui/compose/screen/WelcomeScreen.kt` — so the PII/GDPR sweep did not cover them at all.
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 01a1e83a-5dea-73cd-b5e8-4a13bc64884c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 34 · Warnings: 520 · Recommendations: 135 · Info: 14 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 06:38 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.