Public report of vaadin/flow, 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 report Measured 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, 22:42 UTC · Survey ID cd_c1c7f23344e540c9907cfdca2cafd048

vaadin/flow

Measured 17 November 2026, 22:40 UTC, at code version b128e53

First survey, so nothing to compare with yet Code coverage: not measuredTest reliability: not measured

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

CAI score 57.3out of 100 Adequate
CriticalWeakAdequateStrongExemplary

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 large codebase: 364,924 lines of product code in 217 projects, tests not counted · Estimated rebuild effort: about 4.8 person-years · Weakest lens: Security and Compliance, 52.7

Findings by how serious they are

33 critical 1479 serious 438 minor

14 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 22:40 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.

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 ▸

80of 80 dimensions measured by tools.
1917of 1950 findings point to an exact file and line, so you can open each one in the code. The other 33 concern the repository as a whole, such as missing documentation.
80dimensions across 7 lenses, read from 364,924 lines of product code in 217 projects.
Chapters

Executive summary

vaadin/flow falls short of our standard for production, in part because it has security weaknesses in the code. It scores 57.3 out of 100 and is rated Adequate, and 17 of its 33 critical findings are security problems.

Security and Compliance, at 52.7, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 3.4 points. Tidying the declared packages comes next, worth about 3.3 points. Raising Security and Compliance to 70 would lift the score to about 60.6.

Seven known security holes in the packages the code depends on can be used by attackers. Five weaknesses in the code could be used by an attacker, and two places in the code run text as code, which an attacker could use. Updating the vulnerable packages, fixing the weaknesses the scanner points to and replacing text run as code with direct calls would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the password or key in the code's history needs replacing, with the old one switched off. The four pages or frames without a title need a descriptive title.

The product code is 364,924 lines, about €700,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 for The 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.
Security and Compliance 52.7 · counts for 46%Production Readiness 53.1 · counts for 25%Accessibility 60.6 · counts for 14%Maturity 69.4 · counts for 8%Code Health 78.1 · counts for 4%Architecture 79.4 · counts for 2%Performance 88.6 · counts for 1%

If Security and Compliance rose from 52.7 to 70, the lowest score rated Strong, the score would rise from 57.3 to about 60.6.

Code composition: what the lines of code are
Product code 54%Tests 46%
Rebuild cost: about €700,000 · Estimate
Cost to rebuild€230,000 to €1,200,000, for 3,862 to 12,251 hours of work, about 4.8 person-years for 2 to 10 engineers
Difficulty of the problemStandard, 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.8 at a score of 57. 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.
SizeLarge: 364,924 lines of product code
What it is notNot 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 1 No assertions (empty test) finding(s) in Test Quality — start with DeprecatedJandexArtifactsWarningBuildTest.java.
Raises the score by about 3.4 points · Low effort · Test Quality
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 3.3 points · Medium effort · Dependency Hygiene
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 1.0 point · Low effort · ADR Quality

Diagnosis: what the measurements show together

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 €700,000 to build again, about 4.8 person-years of work. Its weakest lens is Security and Compliance, at 52.7 (checked 4 of 10). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3.4 points for low effort, because it clears the 1 Test Quality 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 — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch flow-client flow-client flow-html-components flow-html-components flow-server flow-server flow-html-components->flow-server flow-html-components-testbench flow-html-components-testbench flow-lit-template flow-lit-template flow-lit-template->flow-server flow-plugin-base flow-plugin-base flow-plugin-base->flow-server flow-polymer-template flow-polymer-template flow-polymer-template->flow-server flow-test-common flow-test-common flow-test-lumo flow-test-lumo flow-test-resources flow-test-resources flow-test-lumo->flow-test-resources test-dev-bundle test-dev-bundle test-dev-bundle->flow-test-lumo vaadin-dev-server vaadin-dev-server test-dev-bundle->vaadin-dev-server test-spring-security-flow test-spring-security-flow test-spring-security-flow->flow-html-components-testbench test-spring-security-flow->flow-server test-spring-security-flow->vaadin-dev-server vaadin-spring vaadin-spring test-spring-security-flow->vaadin-spring vaadin-test-spring-helpers vaadin-test-spring-helpers test-spring-security-flow->vaadin-test-spring-helpers vaadin-dev-server->flow-server vaadin-quarkus vaadin-quarkus vaadin-quarkus->flow-server vaadin-quarkus-development-tests vaadin-quarkus-development-tests vaadin-quarkus-development-tests->flow-client vaadin-quarkus-development-tests->flow-html-components vaadin-quarkus-development-tests->flow-lit-template vaadin-quarkus-development-tests->flow-server vaadin-quarkus-development-tests->vaadin-dev-server vaadin-quarkus-development-tests->vaadin-quarkus vaadin-quarkus-embedded-plugin-tests vaadin-quarkus-embedded-plugin-tests vaadin-quarkus-embedded-plugin-tests->flow-client vaadin-quarkus-embedded-plugin-tests->flow-html-components vaadin-quarkus-embedded-plugin-tests->flow-lit-template vaadin-quarkus-embedded-plugin-tests->flow-server vaadin-quarkus-embedded-plugin-tests->vaadin-quarkus vaadin-quarkus-production-tests vaadin-quarkus-production-tests vaadin-quarkus-production-tests->flow-client vaadin-quarkus-production-tests->flow-html-components vaadin-quarkus-production-tests->flow-lit-template vaadin-quarkus-production-tests->flow-server vaadin-quarkus-production-tests->vaadin-quarkus vaadin-spring->flow-client vaadin-spring->flow-server vaadin-spring->vaadin-dev-server vaadin-test-spring-common vaadin-test-spring-common vaadin-test-spring-common->flow-html-components-testbench vaadin-test-spring-common->flow-polymer-template vaadin-test-spring-common->flow-server vaadin-test-spring-common->vaadin-spring vaadin-test-spring-common->vaadin-test-spring-helpers vaadin-test-spring-helpers->flow-server vaadin-test-spring-helpers->vaadin-spring __more__ +197 more projects

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.

251 modules, with 686 dependencies between them. 4 loops run through 72 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 211 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.
uses →1 flow-client.src.main.frontend.internal.client.Registry2 com.vaadin.flow.i18n3 com.vaadin.flow.js4 com.vaadin.flow.shared5 com.vaadin.flow.shared.ui6 flow-client.src.main.frontend.internal.client.flow.nodefeature.MapProperty7 com.vaadin.flow.router.internal8 com.vaadin.flow.server.streams9 com.vaadin.flow.signals.shared.impl10 flow-client.src.main.frontend.internal.client.flow.nodefeature.NodeMap11 com.vaadin.flow.router12 com.vaadin.flow.signals.impl13 flow-client.src.main.frontend.internal.client.flow.StateNode14 com.vaadin.flow.component.webcomponent15 com.vaadin.flow.server.communication16 com.vaadin.flow.signals.shared17 flow-client.src.main.frontend.internal.client.communication18 flow-client.src.main.frontend.internal.client.flow.binding19 com.vaadin.flow.signals20 com.vaadin.flow.internal.nodefeature21 com.vaadin.flow.signals.local22 com.vaadin.flow.internal23 com.vaadin.flow.server.startup24 com.vaadin.flow.server25 com.vaadin.flow.function26 com.vaadin.flow.dom.impl27 com.vaadin.flow.server.frontend.scanner28 com.vaadin.flow.dom29 com.vaadin.flow.component.page30 com.vaadin.flow.component.internal31 com.vaadin.flow.component32 com.vaadin.flow.component.trigger.internal33 com.vaadin.flow.data.provider34 com.vaadin.flow.server.auth35 com.vaadin.flow.data.binder36 com.vaadin.flow.di37 com.vaadin.cdi38 com.vaadin.flow.server.frontend39 com.vaadin.flow.spring40 com.vaadin.base.devserver
1 flow-client.src.main.frontend.internal.client.Registry
2 com.vaadin.flow.i18n41
3 com.vaadin.flow.js2314
4 com.vaadin.flow.shared1
5 com.vaadin.flow.shared.ui1
6 flow-client.src.main.frontend.internal.client.flow.nodefeature.MapProperty1
7 com.vaadin.flow.router.internal1619115
8 com.vaadin.flow.server.streams1123478
9 com.vaadin.flow.signals.shared.impl121485
10 flow-client.src.main.frontend.internal.client.flow.nodefeature.NodeMap1
11 com.vaadin.flow.router11102451441
12 com.vaadin.flow.signals.impl5112541
13 flow-client.src.main.frontend.internal.client.flow.StateNode1
14 com.vaadin.flow.component.webcomponent11215161
15 com.vaadin.flow.server.communication1241169042226
16 com.vaadin.flow.signals.shared194184
17 flow-client.src.main.frontend.internal.client.communication12
18 flow-client.src.main.frontend.internal.client.flow.binding114
19 com.vaadin.flow.signals131
20 com.vaadin.flow.internal.nodefeature14118405143815
21 com.vaadin.flow.signals.local14213
22 com.vaadin.flow.internal1131622082110
23 com.vaadin.flow.server.startup2412121271
24 com.vaadin.flow.server83621516214314412162
25 com.vaadin.flow.function31
26 com.vaadin.flow.dom.impl479643501
27 com.vaadin.flow.server.frontend.scanner31
28 com.vaadin.flow.dom7511874913110
29 com.vaadin.flow.component.page133111425
30 com.vaadin.flow.component.internal23311212115574627
31 com.vaadin.flow.component212134216118822502171
32 com.vaadin.flow.component.trigger.internal431312114113
33 com.vaadin.flow.data.provider106239113
34 com.vaadin.flow.server.auth821
35 com.vaadin.flow.data.binder413352292
36 com.vaadin.flow.di231110312
37 com.vaadin.cdi17142416
38 com.vaadin.flow.server.frontend72611821
39 com.vaadin.flow.spring221694185
40 com.vaadin.base.devserver19216132
Uses a module listed above itPart of a loopThe module itself
1 flow-client.src.main.frontend.internal.client.Registry2 com.vaadin.flow.i18n3 com.vaadin.flow.js4 com.vaadin.flow.shared5 com.vaadin.flow.shared.ui6 flow-client.src.main.frontend.internal.client.flow.nodefeature.MapProperty7 com.vaadin.flow.router.internal8 com.vaadin.flow.server.streams9 com.vaadin.flow.signals.shared.impl10 flow-client.src.main.frontend.internal.client.flow.nodefeature.NodeMap11 com.vaadin.flow.router12 com.vaadin.flow.signals.impl13 flow-client.src.main.frontend.internal.client.flow.StateNode14 com.vaadin.flow.component.webcomponent15 com.vaadin.flow.server.communication16 com.vaadin.flow.signals.shared17 flow-client.src.main.frontend.internal.client.communication18 flow-client.src.main.frontend.internal.client.flow.binding19 com.vaadin.flow.signals20 com.vaadin.flow.internal.nodefeature21 com.vaadin.flow.signals.local22 com.vaadin.flow.internal23 com.vaadin.flow.server.startup24 com.vaadin.flow.server25 com.vaadin.flow.function26 com.vaadin.flow.dom.impl27 com.vaadin.flow.server.frontend.scanner28 com.vaadin.flow.dom29 com.vaadin.flow.component.page30 com.vaadin.flow.component.internal31 com.vaadin.flow.component32 com.vaadin.flow.component.trigger.internal33 com.vaadin.flow.data.provider34 com.vaadin.flow.server.auth35 com.vaadin.flow.data.binder36 com.vaadin.flow.di37 com.vaadin.cdi38 com.vaadin.flow.server.frontend39 com.vaadin.flow.spring40 com.vaadin.base.devserverflow-client.src.main.frontend.internal.client.Registry1com.vaadin.flow.i18n2com.vaadin.flow.js3com.vaadin.flow.shared4com.vaadin.flow.shared.ui5flow-client.src.main.frontend.internal.client.flow.nodefeature.MapProperty6com.vaadin.flow.router.internal7com.vaadin.flow.server.streams8com.vaadin.flow.signals.shared.impl9flow-client.src.main.frontend.internal.client.flow.nodefeature.NodeMap10com.vaadin.flow.router11com.vaadin.flow.signals.impl12flow-client.src.main.frontend.internal.client.flow.StateNode13com.vaadin.flow.component.webcomponent14com.vaadin.flow.server.communication15com.vaadin.flow.signals.shared16flow-client.src.main.frontend.internal.client.communication17flow-client.src.main.frontend.internal.client.flow.binding18com.vaadin.flow.signals19com.vaadin.flow.internal.nodefeature20com.vaadin.flow.signals.local21com.vaadin.flow.internal22com.vaadin.flow.server.startup23com.vaadin.flow.server24com.vaadin.flow.function25com.vaadin.flow.dom.impl26com.vaadin.flow.server.frontend.scanner27com.vaadin.flow.dom28com.vaadin.flow.component.page29com.vaadin.flow.component.internal30com.vaadin.flow.component31com.vaadin.flow.component.trigger.internal32com.vaadin.flow.data.provider33com.vaadin.flow.server.auth34com.vaadin.flow.data.binder35com.vaadin.flow.di36com.vaadin.cdi37com.vaadin.flow.server.frontend38com.vaadin.flow.spring39com.vaadin.base.devserver40412314111161911511234781214851111024514415112541111215161124116904222619418412114131141184051438151421311316220821102412121271836215162143144121623147964350131751187491311013311142523311212115574627212134216118822502171431312114113106239113821413352292231110312171424167261182122169418519216132+211 more modules (most-connected shown)

At a glance — Code Health · 78.1 · Strong ·

At a glance — Architecture · 79.4 · Strong ·

At a glance — Maturity · 69.4 · Adequate ·

At a glance — Readiness · 53.1 · Adequate · gated by R8 ·

At a glance — Security · 52.7 · Checked 4 of 10 · gated by D29, D36 ·

At a glance — Accessibility · 60.6 · Adequate · gated by AC3 ·

At a glance — Performance · 88.6 · Strong ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures31High / Critical
A05:2025 — Injection26High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DeprecatedJandexArtifactsWarningBuildTest.java; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Resolve the 18 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (3).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DeprecatedJandexArtifactsWarningBuildTest.java.+3.4 ptsLowTest Quality
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.3 ptsMediumDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.+1.0 ptsLowADR Quality
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED.+0.9 ptsLowSecrets (history)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.+0.9 ptsLowStatic Analysis (SAST)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+0.9 ptsLowStatic Analysis (SAST)
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+0.9 ptsLowStatic Analysis (SAST)
Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED.+0.9 ptsLowDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 626 files carrying findings, judged against the Production bar: 0% slop · 41% mixed · 59% near-clean.

FileScoreBandWorst signal
REDACTED0.1SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java5.1MixedChange Coupling: Boundary-crossing change coupling: BuildFrontendUtil.java ↔ AbstractConfigurationFactory.java
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java5.7MixedCognitive Complexity: UIInternals.showRouteTarget (cognitive 17)
vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java5.9MixedCyclomatic Complexity: VaadinSecurityConfigurer.init (cyclomatic 16)
flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java5.9MixedGod Classes: TooManyMethods: VaadinService
flow-polymer2lit/convert.ts6.0MixedExplicit Debt: TodoComment
flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java6.0MixedExplicit Debt: TodoComment
flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java6.0MixedExplicit Debt: TodoComment
flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java6.0MixedExplicit Debt: FixmeComment
flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java6.0MixedExplicit Debt: TodoComment
flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java6.0MixedExplicit Debt: TodoComment
vaadin-dev-server/src/main/java/com/vaadin/base/devserver/startup/DevModeInitializer.java6.0MixedExplicit Debt: TodoComment
flow-server/src/main/java/com/vaadin/flow/component/UI.java6.0MixedExplicit Debt: FixmeComment
flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeMap.java6.0MixedExplicit Debt: TodoComment
flow-server/src/main/java/com/vaadin/flow/component/Component.java6.3MixedGod Classes: TooManyMethods: Component

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 — 33

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 — 1479

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 — 438

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 14

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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 — 80 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D19D20D21D24D26D27D28D29D30D34D35D36D43D44AC1AC2AC3AC5AC6AX1AX10AX2AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF3R1R10R2R3R4R5R6R7R8R9X12X13X16X17X18X19X20X21X23X24X25X27X28X29X3X30X4X5

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
  1. 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, 1917 of 1950 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1ebab-1dd1-78c9-bdf4-93efb9790145.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • 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 11,027 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 177 test source file(s) (.ts, .kt, .js) 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. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .ts, .kt, .js), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • 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 50 artifact(s) across its subprojects (38 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.
  • 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. A project file that is not well-formed XML, or a package.json that is not a JSON object, says nothing this dimension can read about whether the unit runs or ships: flow-tests/test-embedded-jetty-12/pom.xml.
  • D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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. 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 — 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. 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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. `flow-client/src/main/frontend/ConnectionIndicator.ts`, `flow-html-components/src/main/java/com/vaadin/flow/component/html/TableCell.java`, `flow-server/src/main/java/com/vaadin/flow/component/webcomponent/WebComponent.java`, `flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java`, `flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java`, … (+5 more) 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.
  • AX1 Captive dependencies — 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 also uses Guice and OSGi Declarative Services, whose singleton and shorter-lived bindings can capture one another the same way, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that those bindings are free of 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start` in vaadin-dev-server/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > npm run install-deps && web-dev-server --node-resolve / > install-deps / > playwright install / sh: 1: playwright: not found" 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` in vaadin-dev-server/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > npm run install-deps && web-dev-server --node-resolve / > install-deps / > playwright install / sh: 1: playwright: not found" 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.
  • ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • 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.
  • P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
  • R8 Dependency Hygiene — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • 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.

Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality 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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.6 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Prevented

58 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TransactionEngine.apply at 57. A further 2 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 ClassFile.readConstantPool at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/ClassFile.java (ClassFile.readConstantPool at 19). 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.

convert.convertFile::modifyClass (cyclomatic 24) · ×2flow-polymer2lit/convert.ts:118
BrowserDetails.isTooOldToFunctionProperly (cyclomatic 16) · ×2flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:824
TransactionEngine.apply (cyclomatic 57)flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379
NodeTasks.<init> (cyclomatic 37)flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111
BrowserDetails.parseBrowserVersion (cyclomatic 36)flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:180

+ 49 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with TransactionEngine.apply (cyclomatic 57), NodeTasks.<init> (cyclomatic 37), BrowserDetails.parseBrowserVersion (cyclomatic 36). — 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 6 together lifts Cyclomatic 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: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.1 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.1 / 10 · rule-coverage 100% · ceiling Prevented

135 method(s) exceeded the cognitive complexity threshold of 15; the worst was TransactionEngine.apply at 90.

convert.convertFile::rewriteElement (cognitive 44) · ×3flow-polymer2lit/convert.ts:342
BrowserDetails.isTooOldToFunctionProperly (cognitive 16) · ×2flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:824
TransactionEngine.apply (cognitive 90)flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379
NodeTasks.<init> (cognitive 60)flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111
TaskGenerateTsDefinitions.updateIfContentMissing (cognitive 56)flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTsDefinitions.java:125

+ 123 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with TransactionEngine.apply (cognitive 90). — Refactoring it lifts Cognitive Complexity from 6.1 to about 6.5/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.9 / 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.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

145 god class(es) detected.

TooManyMethods: VaadinService · ×61flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:115
ClassTooLong: VaadinService · ×36flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:115
FileTooLong: binder/Binder.java · ×34flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java
MethodTooLong: VaadinDevTools.styles · ×9vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:91
FunctionTooLong: convert.convertFile · ×5flow-polymer2lit/convert.ts:94

What to do

  1. Resolve the 61 TooManyMethods finding(s) in God Classes — start with Binder.java (2), VaadinService.java, UIInternals.java. — One of this dimension's main actionable groups (61 warning-level).
  2. Resolve the 36 ClassTooLong finding(s) in God Classes — start with VaadinService.java, BootstrapHandler.java, UIInternals.java. — One of this dimension's main actionable groups (36 warning-level).
  3. Resolve the 34 FileTooLong finding(s) in God Classes — start with Binder.java, VaadinService.java, REDACTED. — One of this dimension's main actionable groups (34 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication8.5 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Verified

274 duplicated block group(s) detected. 3.8 % of the production lines (13,749 of 364,924) are in a reported copy. A further 226 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 183 of the 500 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (7 lines × 2) · ×20flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:633
Duplicated block (8 lines × 2) · ×16flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:800
Edited copy of a member (10 corresponding lines) · ×14vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:116
Edited copy of a member (8 corresponding lines) · ×14flow-server/src/main/java/com/vaadin/flow/component/HasSize.java:477
Duplicated block (13 lines × 2) · ×14flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractBackEndDataProvider.java:40

+ 143 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 20 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with BuildDevBundleMojo.java (2), MultiSelect.java (2), AbstractContextualStorageManager.java (2). — One of this dimension's main actionable groups (20 warning-level).
  2. Resolve the 16 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with BootstrapHandler.java, VaadinTaskExecutorSelector.java, TaskGenerateTailwindCss.java. — One of this dimension's main actionable groups (16 warning-level).
  3. Resolve the 14 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with RouteScopedContext.java (2), Reflector.java, RouteAliasData.java. — One of this dimension's main actionable groups (14 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.4 / 10Stronggated by 15 serious findings✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

217 production modules (Gradle+Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 16 module(s) off the main sequence, with abstractness counted on 146 of the 217 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: custom-websockets · ×15
Off the main sequence: flow-test-common

What to do

  1. Resolve the 15 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (15 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.7 / 10Stronggated by 13 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

13 of 577 classes have LCOM4 above 3.

Low cohesion: Options (LCOM4 33) · ×13flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/Options.java:47

What to do

  1. Resolve the 13 Low cohesion finding(s) in Cohesion (LCOM4) — start with Options.java, Component.java, RangeInput.java. — One of this dimension's main actionable groups (13 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality9.6 / 10Adequategated by 1 critical finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Prevented

82 skipped (82 with a documented reason), 279 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 11027 tests. Measured on the .java suite only — at least 177 test source file(s) (.ts, .kt, .js) went unread, so its test quality is unmeasured and is not in these counts.

No assertions (empty test): indexDependencyReference_warningLoggedvaadin-quarkus/deployment/src/test/java/com/vaadin/flow/quarkus/test/DeprecatedJandexArtifactsWarningBuildTest.java:52
No assertions: nullProgressListenerWorks · ×278flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/installer/DefaultFileDownloaderTest.java:81
Test project verifies nothing: flow-test-parent-theme-prod · ×2flow-tests/test-express-build/test-parent-theme-prod/src/test/java/com/vaadin/flow/prodbuild/ParentThemeIT.java:31
Skipped (documented): bundleMissesSomeEntries_devMode_skipBundleBuildSet_noBundleRebuild · ×82flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2249

What to do

  1. Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DeprecatedJandexArtifactsWarningBuildTest.java. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 278 No assertions finding(s) in Test Quality — start with AppViewIT.java (17), JwtSecurityContextRepositoryTest.java (9), RouteRegistryInitializerTest.java (6). — One of this dimension's main actionable groups (278 warning-level).
  3. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with ParentThemeIT.java, CustomServletIT.java. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 44 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 243 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. 973 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 11 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 28 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java (9×57=513); vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java (12×24=288); flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java (13×16=208) Repeated repair below the complexity floor: vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java (8 of 13 changes were fixes); flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java (7 of 9 changes were fixes); flow-server/src/main/java/com/vaadin/flow/component/internal/PendingJavaScriptInvocation.java (5 of 7 changes were fixes)

Hotspot: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java · ×17flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379
Repeated repair: vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java · ×11vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java:680

What to do

  1. Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with TransactionEngine.java, DevLoopRedefiner.java, ElementListenerMap.java. — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 11 Repeated repair finding(s) in Churn × Complexity Hotspots — start with VaadinQuarkusNativeProcessor.java, Compile.java, PendingJavaScriptInvocation.java. — One of this dimension's main actionable groups (11 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Documented

83 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java. Counted over 1167 of the 2762 production source files in this repository: 1583 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Stronggated by 31 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

31 deducted task-comment markers across 364924 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.

TodoComment · ×25vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusProcessor.java:523
FixmeComment · ×4flow-server/src/main/java/com/vaadin/flow/component/UI.java:438
XxxCommentflow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1572
HackCommentflow-client/src/main/frontend/internal/client/ApplicationConnection.ts:150

What to do

  1. Resolve the 25 TodoComment finding(s) in Explicit Debt — start with convert.ts (5), NodeList.java (2), NodeMap.java (2). — One of this dimension's main actionable groups (25 warning-level).
  2. Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with convert.ts (2), UI.java, TaskUpdatePackages.java. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 XxxComment finding(s) in Explicit Debt — start with DataCommunicator.java. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality8.6 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

1 of 2 documentation facets pass in full; short on: F2 example. 39 document(s) read across 248 unit(s).

Documentation: no build, run or usage example · ×5README.md:1

What to do

  1. Resolve the 5 Documentation finding(s) in Documentation Quality — start with README.md (5). — One of this dimension's main actionable groups (5 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundvaadin-quarkus/pom.xml:67

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency5.1 / 10Adequate✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 5.1 / 10 · rule-coverage 100% · ceiling Verified

5 naming inconsistencies among 102 declarations measured against a convention their peers follow.

`isAllowedVAADINBuildUrl` spells `VAADIN` where 38 names in the project spell it `Vaadin`flow-server/src/main/java/com/vaadin/flow/internal/ResponseWriter.java:611
`getResourceURL` spells `URL` where 28 names in the project spell it `Url`vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringVaadinServletService.java:199
`jarPathURL` spells `URL` where 28 names in the project spell it `Url`vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:407
`UpdateJWTCookieOnCommitResponseWrapper` spells `JWT` where 12 names in the project spell it `Jwt`vaadin-spring/src/main/java/com/vaadin/flow/spring/security/stateless/VaadinStatelessSecurityConfigurer.java:360
`getConfigFromDOM` spells `DOM` where 25 names in the project spell it `Dom`flow-client/src/main/frontend/internal/client/bootstrap/Bootstrapper.ts:122

What to do

  1. Resolve the 1 `isAllowedVAADINBuildUrl` spells `VAADIN` where 38 names in the project… finding(s) in Naming Consistency — start with ResponseWriter.java. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `getResourceURL` spells `URL` where 28 names in the project spell it… finding(s) in Naming Consistency — start with SpringVaadinServletService.java. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `jarPathURL` spells `URL` where 28 names in the project spell it `Url` finding(s) in Naming Consistency — start with FilterableResourceResolver.java. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value9.5 9.2 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 98% · ceiling Documented

10 of 1928 judged comments only repeat the code they sit on (0.5 %). 56 comment(s) in another language or script were not judged.

redundant comment · ×10flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:190
doc comments repeat the names · ×3flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:39

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion8.1 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.1 / 10 · rule-coverage 100% · ceiling Documented

3 of 31 build units (Maven, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×3flow-server/pom.xml:1

What to do

  1. Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability9.5 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

18 % of calls cross a namespace and 10 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED 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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)1.1 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 1.1 / 10 · rule-coverage 100% · ceiling Documented

26 finding(s): 0 critical, 9 high, 11 medium, 6 low. semgrep hit a parse error in 12 file(s) — `flow-client/src/main/frontend/ConnectionIndicator.ts` (line 68, line 80, line 93, …), `flow-html-components/src/main/java/com/vaadin/flow/component/html/TableCell.java` (line 208, line 249), `flow-plugins/flow-gradle-plugin/gradlew` (line 74, line 178), `flow-server/src/main/java/com/vaadin/flow/component/webcomponent/WebComponent.java` (line 213, line 214, line 215), `flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java` (line 544, line 545, line 841, …), … (+7 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 9 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 8 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities4.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.5 / 10 · rule-coverage 100% · ceiling Documented

26 finding(s): 0 critical, 7 high, 18 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 18 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (3). — One of this dimension's main actionable groups (18 warning-level).
  2. Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness8.3 / 10Adequategated by 3 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Documented

211 of 1179 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java. Counted over 1179 of the 2762 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×3flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:1
Orphaned file · ×208flow-server/src/main/java/com/vaadin/flow/internal/Range.java:1
Further orphaned files (smaller)

What to do

  1. Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with RouteSegment.java, Node.java, InMemoryDataProvider.java. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 208 Orphaned file finding(s) in Knowledge Freshness — start with TestingServiceInitListener.java (2), Range.java, LookupInitializer.java. — One of this dimension's main actionable groups (208 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: VaadinFlowPluginExtension.kt↔PluginAdapterBase.java 84%; BasicElementStateProvider.java↔NodeFeatureRegistry.java 80%; BrowserLiveReload.java↔vaadin-dev-tools.ts 58%

Boundary-crossing change coupling: BuildFrontendUtil.java ↔ AbstractConfigurationFactory.javaflow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:1
Change coupling: VaadinFlowPluginExtension.kt ↔ PluginAdapterBase.java · ×5flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/VaadinFlowPluginExtension.kt:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with BuildFrontendUtil.java. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 5 Change coupling finding(s) in Change Coupling — start with VaadinFlowPluginExtension.kt, BasicElementStateProvider.java, BrowserLiveReload.java. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life8.5 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 5 platform declaration(s) and 323 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.

End-of-life framework: Spring Boot 2vaadin-dev-server/src/test/resources/stats-data/maven-project-folder1/pom.xml:1

What to do

  1. Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels5.7 / 10Adequate✓ Tool-verified

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.

  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:785

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure3.6 / 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.

  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — flow-client/src/main/frontend/Flow.ts:516
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×3) — REDACTED:2, flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6, vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — REDACTED:2, vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6, vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="outlet">, so there is no content here to wrap — render the <main> from the component mounted into it. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6

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.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety5.7 / 10Adequate✓ Tool-verified

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.

  • `.message::before` moves (`animation: spinner 0.5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:38
  • `div#annotated-div.layered` sets color: rgb(255, 0, 0) on background-color: rgb(255, 255, 0) — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — flow-tests/test-root-context/src/main/webapp/style-layer-annotated.css:2
  • `div#test-div.layered` sets color: rgb(255, 0, 0) on background-color: rgb(0, 0, 255) — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — flow-tests/test-root-context/src/main/webapp/style-layer-theme.css:2
  • `.css-in-js .window` 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. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:235
  • `.css-in-js .dev-tools.error` moves (`animation: bounce 0.5s`) 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. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:193
  • `.css-in-js .notification-tray .message` moves (`animation: slideIn var(--dev-tools-transition-duration)`) 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. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:468
  • `.css-in-js .notification-tray .message.animate-out` moves (`animation: slideOut forwards var(--dev-tools-transition-duration)`) 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. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:475
  • `.css-in-js .v-loading-indicator` moves (`animation: v-progress-start 1000ms 200ms both`) 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. — flow-client/src/main/frontend/ConnectionIndicator.ts:424
  • `.css-in-js .v-loading-indicator[style*='none']` moves (`transition: opacity 500ms 300ms, width 300ms`) 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. — flow-client/src/main/frontend/ConnectionIndicator.ts:431
  • `.css-in-js .v-loading-indicator.second` moves (`animation: v-progress-delay 3.8s forwards`) 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. — flow-client/src/main/frontend/ConnectionIndicator.ts:437
  • `.css-in-js .v-loading-indicator.third` moves (`animation: v-progress-wait 5s forwards, v-progress-wait-pulse 1s 4s infinite backwards`) 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. — flow-client/src/main/frontend/ConnectionIndicator.ts:441
  • `.css-in-js vaadin-connection-indicator[reconnecting] .v-status-message` moves (`animation: show-reconnecting-status 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. — flow-client/src/main/frontend/ConnectionIndicator.ts:486
  • `.css-in-js vaadin-connection-indicator[reconnecting] .v-status-message span::before` moves (`animation: v-spin 0.4s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — flow-client/src/main/frontend/ConnectionIndicator.ts:517

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.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.2 / 10Exemplary✓ Tool-verified

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.

AX2 · Stateful singletons5.9 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `NavigationAccessControl` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (loginUrl; e.g. `loginUrl` in `setLoginView` at line 209). — flow-server/src/main/java/com/vaadin/flow/server/auth/NavigationAccessControl.java:85
  • `AuthenticationContext` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (logoutSuccessHandler, logoutHandler; e.g. `logoutSuccessHandler` in `setLogoutHandlers` at line 473). — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/AuthenticationContext.java:71
  • `NavigationAccessControlConfigurer` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (disableAccessControl, enableViewAccessChecker, accessCheckersFilter, decisionResolver, loginView, loginViewPath; e.g. `disableAccessControl` in `disabled` at line 206). — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/NavigationAccessControlConfigurer.java:78
  • `RequestUtil` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (webIconsRequestMatcher, pwaResourcesRequestMatcher; e.g. `webIconsRequestMatcher` in `isCustomWebIcon` at line 269). — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:64
  • `VaadinDefaultRequestCache` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (ignoreRequestMatcher; e.g. `ignoreRequestMatcher` in `ignoreRequests` at line 196). — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinDefaultRequestCache.java:68
  • `VaadinRolePrefixHolder` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (rolePrefix, rolePrefixSet; e.g. `rolePrefix` in `resetRolePrefix` at line 131). — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinRolePrefixHolder.java:45
  • `VaadinServletContextInitializer` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (metadataReaderFactory; e.g. `metadataReaderFactory` in `getMetadataReaderFactory` at line 932). — vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:111

What to do

  • Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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.

  • `ConnectionStateHandler` declares 16 required operations: `heartbeatException`, `heartbeatInvalidStatusCode`, `heartbeatOk`, `pushClosed`, `pushClientTimeout`, `pushError`, `pushReconnectPending`, `pushOk`, `pushScriptLoadError`, `xhrException`, `xhrInvalidContent`, `xhrInvalidStatusCode`, `xhrOk`, `pushNotConnected`, `pushInvalidContent`, `configurationUpdated`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data 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. — flow-client/src/main/frontend/internal/client/communication/ConnectionStateHandler.ts:54
  • `ApplicationConnection` declares 16 required operations: `isActive`, `getDomElementByNodeId`, `getNodeId`, `addDomSetListener`, `poll`, `resolveUri`, `sendEventMessage`, `getUIId`, `connectWebComponent`, `debug`, `getJavaClass`, `isHiddenByServer`, `getElementStyleProperties`, `getProfilingData`, `getClientEvents`, `start`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data 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. — flow-client/src/main/frontend/internal/client/clientApi.ts:45
  • `Binding<BEAN, TARGET>` declares 20 abstract methods: `getEqualityPredicate`, `getField`, `getGetter`, `getSetter`, `getValidationStatusHandler`, `hasChanges`, `isAsRequiredEnabled`, `isConvertBackToPresentation`, `isDefaultValidatorEnabled`, `isReadOnly`, `isValidatorsDisabled`, `read`, `setAsRequiredEnabled`, `setConvertBackToPresentation`, `setDefaultValidatorEnabled`, `setIsAppliedPredicate`, `setReadOnly`, `setValidatorsDisabled`, `unbind`, `validate`. 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. — flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:122
  • `ListDataView<T, V>` declares 21 abstract methods: `addFilter`, `addItem`, `addItemAfter`, `addItemBefore`, `addItems`, `addItemsAfter`, `addItemsBefore`, `addSortComparator`, `addSortOrder`, `contains`, `getItemCount`, `getNextItem`, `getPreviousItem`, `removeFilters`, `removeItem`, `removeItems`, `removeSorting`, `setFilter`, `setItems`, `setSortComparator`, `setSortOrder`. 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. — flow-data/src/main/java/com/vaadin/flow/data/provider/ListDataView.java:38
  • `RouteRegistry` declares 21 abstract methods: `addRoutesChangeListener`, `clean`, `getContext`, `getLayout`, `getNavigationRouteTarget`, `getNavigationTarget`, `getNavigationTarget`, `getRegisteredAccessibleMenuRoutes`, `getRegisteredRoutes`, `getRouteTarget`, `getTargetUrl`, `getTargetUrl`, `getTemplate`, `hasLayout`, `hasMandatoryParameter`, `removeRoute`, `removeRoute`, `removeRoute`, `setLayout`, `setRoute`, `update`. 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. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — flow-server/src/main/java/com/vaadin/flow/server/RouteRegistry.java:49
  • `VaadinRequest` declares 32 abstract methods: `getAttribute`, `getAttributeNames`, `getAuthType`, `getCharacterEncoding`, `getContentLength`, `getContentType`, `getContextPath`, `getCookies`, `getDateHeader`, `getHeader`, `getHeaderNames`, `getHeaders`, `getInputStream`, `getLocale`, `getLocales`, `getMethod`, `getParameter`, `getParameterMap`, `getPathInfo`, `getReader`, `getRemoteAddr`, `getRemoteHost`, `getRemotePort`, `getRemoteUser`, `getService`, `getUserPrincipal`, `getWrappedSession`, `getWrappedSession`, `isSecure`, `isUserInRole`, `removeAttribute`, `setAttribute`. 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. Those 32 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — flow-server/src/main/java/com/vaadin/flow/server/VaadinRequest.java:38
  • `ElementStateProvider` declares 37 abstract methods: `addEventListener`, `addPropertyChangeListener`, `appendVirtualChild`, `attachExistingElement`, `attachShadow`, `bindAttributeSignal`, `bindPropertySignal`, `bindVisibleSignal`, `getAttribute`, `getAttributeNames`, `getChild`, `getChildCount`, `getClassList`, `getParent`, `getProperty`, `getPropertyNames`, `getShadowRoot`, `getStyle`, `getTag`, `getTextContent`, `hasAttribute`, `hasProperty`, `insertChild`, `isTextNode`, `isVisible`, `removeAllChildren`, `removeAttribute`, `removeChild`, `removeChild`, `removeProperty`, `setAttribute`, `setAttribute`, `setProperty`, `setTextContent`, `setVisible`, `supports`, `visit`. 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. Those 37 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — flow-server/src/main/java/com/vaadin/flow/dom/ElementStateProvider.java:38
  • `PluginAdapterBase` declares 40 abstract methods: `applicationIdentifier`, `applicationProperties`, `buildFolder`, `bunEnable`, `eagerServerLoad`, `excludePostinstallPackages`, `frontendDirectory`, `frontendExtraFileExtensions`, `generatedTsFolder`, `getClassFinder`, `getJarFiles`, `isDebugEnabled`, `isFrontendHotdeploy`, `isFrontendIgnoreVersionChecks`, `isJarProject`, `isNpmExcludeWebComponents`, `isPrepareFrontendCacheDisabled`, `isReactEnabled`, `javaResourceFolder`, `javaSourceFolder`, `logDebug`, `logDebug`, `logError`, `logError`, `logInfo`, `logWarn`, `logWarn`, `nodeDownloadRoot`, `nodeFolder`, `nodeVersion`, `npmFolder`, `openApiJsonFile`, `pnpmEnable`, `postinstallPackages`, `projectBaseDirectory`, `requireHomeNodeExec`, `servletResourceOutputDirectory`, `skipDevBundleBuild`, `useGlobalPnpm`, `webpackOutputDirectory`. 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. Those 40 declarations carry 37 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 37 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/PluginAdapterBase.java:34
  • `VaadinBuildTimeConfig` declares 36 abstract methods: `applicationIdentifier`, `applicationProperties`, `bunEnable`, `ciBuild`, `cleanFrontendFiles`, `commercialWithBanner`, `eagerServerLoad`, `enabled`, `excludePostinstallPackages`, `forceProductionBuild`, `frontendDirectory`, `frontendExtraFileExtensions`, `frontendIgnoreVersionChecks`, `frontendOutputDirectory`, `frontendResourcesDirectory`, `generateBundle`, `generateEmbeddableWebComponents`, `generatedResourceOutputDirectory`, `generatedTsFolder`, `minimumFrontendPackageAgeDays`, `nodeDownloadRoot`, `nodeFolder`, `nodeVersion`, `npmExcludeWebComponents`, `npmFolder`, `openApiJsonFile`, `optimizeBundle`, `pnpmEnable`, `postinstallPackages`, `reactEnabled`, `requireHomeNodeExec`, `resourcesOutputDirectory`, `runNpmInstall`, `skipDevBundleBuild`, `useGlobalPnpm`, `webpackOutputDirectory`. 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. — vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/vaadinplugin/VaadinBuildTimeConfig.java:39

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

  • `setAccessed` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeList.java:354

What to do

  • Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×34) — flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:399, flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/NodeUpdaterTest.java:400, flow-server/src/test/java/ClassInDefaultPackage.java:25, …

What to do

  • Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)6.9 / 10Adequate✓ Tool-verified

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.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy7.1 / 10Strong✓ Tool-verified

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.

  • flow-polymer2lit/README.md names Lit 1, but the manifest declares `lit` 3.3.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — flow-polymer2lit/README.md:81
  • flow-plugins/flow-gradle-plugin/README.md links to `CONTRIBUTING.md`, but `flow-plugins/flow-gradle-plugin/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — flow-plugins/flow-gradle-plugin/README.md:224

What to do

  • Reconcile the README with reality: flow-polymer2lit/README.md names Lit 1, but the manifest declares `lit` 3.3.3; flow-plugins/flow-gradle-plugin/README.md links to `CONTRIBUTING.md`, but `flow-plugins/flow-gradle-plugin/CONTRIBUTING.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language'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.

P2 · Observability8.9 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 22/23 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `flow-devloop-daemon`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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.

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, `gradle`, 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:7

What to do

  • Dependabot is configured but does not watch `github-actions`, `npm`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline8.0 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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.

R1 · Type Safety8.2 / 10Strong✓ 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.

R10 · Code Duplication8.6 / 10Strong✓ Tool-verified

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.

  • flow-client/src/main/frontend/FlowBootstrap.js:28 · flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:16 — the two spans are one implementation copied and then locally edited — 731 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-client/src/main/frontend/FlowBootstrap.js:28
  • flow-client/src/main/frontend/internal/client/communication/VaadinRequest.ts:107 · flow-client/src/main/frontend/internal/client/communication/VaadinServerMessage.ts:85 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-client/src/main/frontend/internal/client/communication/VaadinRequest.ts:107
  • flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:118 · flow-client/src/main/frontend/internal/client/communication/XhrConnection.ts:199 — the two spans are one implementation copied and then locally edited — 101 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:118
  • flow-client/src/main/frontend/internal/Timer.ts:26 · flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:32 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-client/src/main/frontend/internal/Timer.ts:26
  • vaadin-dev-server/src/main/frontend/live-reload-connection.ts:23 · vaadin-dev-server/src/main/frontend/websocket-connection.ts:66 — 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. — vaadin-dev-server/src/main/frontend/live-reload-connection.ts:23
  • flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:131 · flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:158 — the two spans are one implementation copied and then locally edited — 107 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. — flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:131
  • vaadin-dev-server/src/main/frontend/License.ts:146 · vaadin-dev-server/src/main/frontend/License.ts:166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vaadin-dev-server/src/main/frontend/License.ts:146
  • flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:135 · flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:158 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:135
  • flow-client/src/main/frontend/internal/client/UILifecycle.ts:26 · flow-client/src/main/frontend/internal/client/communication/ConnectionMessageType.ts:22 — 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. — flow-client/src/main/frontend/internal/client/UILifecycle.ts:26
  • REDACTED:286 · REDACTED:1654 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:286
  • flow-client/src/main/frontend/internal/client/Registry.ts:391 · flow-client/src/main/frontend/internal/client/UILifecycle.ts:109 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — flow-client/src/main/frontend/internal/client/Registry.ts:391
  • flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:143 · flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:162 — 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. — flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:143
  • scripts/memoryFootprint.js:236 · scripts/previewModule.js:237 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — scripts/memoryFootprint.js:236
  • flow-client/src/main/frontend/internal/client/ExecuteJavaScriptElementUtils.ts:81 · REDACTED:926 — the two spans are one implementation copied and then locally edited — 71 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-client/src/main/frontend/internal/client/ExecuteJavaScriptElementUtils.ts:81
  • flow-client/src/main/frontend/BrowserHelpers.ts:87 · flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:239 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — flow-client/src/main/frontend/BrowserHelpers.ts:87
  • flow-client/src/main/frontend/internal/client/ResourceLoader.ts:113 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:164 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:313 — 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. — flow-client/src/main/frontend/internal/client/ResourceLoader.ts:113
  • flow-client/src/main/frontend/internal/client/ResourceLoader.ts:204 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:310 — 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. — flow-client/src/main/frontend/internal/client/ResourceLoader.ts:204
  • flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:254 · flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:279 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:254
  • REDACTED:369 · REDACTED:489 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:369
  • flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:162 · flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:110 — 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. — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:162
  • flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js:52 · flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js:52
  • flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:94 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:114 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:141 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:168 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:94
  • flow-polymer2lit/convert.ts:343 · flow-polymer2lit/convert.ts:357 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — flow-polymer2lit/convert.ts:343
  • flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-copy.js:141 · flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:24 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-copy.js:141
  • flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:124 · flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:150 — the two spans are one implementation copied and then locally edited — 51 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. — flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:124
  • flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:68 · flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:73 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:68

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.
R2 · Cyclomatic Complexity9.4 / 10Exemplary✓ Tool-verified

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.

  • #parseBrowserVersion has cyclomatic complexity 36 and cognitive complexity 50; 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. — flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:232
  • logTimings has cyclomatic complexity 24 and cognitive complexity 45; 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. — flow-client/src/main/frontend/internal/client/Profiler.ts:398
  • rewriteElement has cyclomatic complexity 24 and cognitive complexity 44; 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. — flow-polymer2lit/convert.ts:342
  • modifyClass has cyclomatic complexity 24 and cognitive complexity 34; 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. — flow-polymer2lit/convert.ts:118
  • extractURL has cyclomatic complexity 24 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:69
  • #handleJSON has cyclomatic complexity 21 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. — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:288
  • convertFile has cyclomatic complexity 19 and cognitive complexity 24; 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. — flow-polymer2lit/convert.ts:94
  • writeThemeFiles has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:45
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:73
  • #processMessage has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:446
  • splitExpression has cyclomatic complexity 17 and cognitive complexity 33; 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. — flow-polymer2lit/convert.ts:50
  • #parseBrowserName has cyclomatic complexity 17 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. — flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:170
  • buildDigest has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/releaseDigest.js:155
  • collectBrowserDetails has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — flow-client/src/main/frontend/BrowserHelpers.ts:42
  • isTooOldToFunctionProperly has cyclomatic complexity 16 and cognitive complexity 16; 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. — flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:817
  • decodeWithTypeInfo has cyclomatic complexity 15 and cognitive complexity 28; 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. — flow-client/src/main/frontend/internal/client/flow/util/ClientJsonCodec.ts:269
  • onKeypress has cyclomatic complexity 15 and cognitive complexity 19; 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. — scripts/findMissingPrs.js:195
  • comment has cyclomatic complexity 14 and cognitive complexity 21; 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. — scripts/memoryFootprint.js:165
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 17; 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. — flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:71
  • trigger has cyclomatic complexity 14 and cognitive complexity 15; 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. — flow-client/src/main/frontend/internal/client/flow/binding/Debouncer.ts:82
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 24; 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. — flow-polymer2lit/convert.ts:214
  • handleDomEvent has cyclomatic complexity 13 and cognitive complexity 21; 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. — REDACTED:1229
  • initApplication has cyclomatic complexity 12 and cognitive complexity 18; 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. — flow-client/src/main/frontend/FlowBootstrap.js:108
  • init has cyclomatic complexity 12 and cognitive complexity 12; 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. — flow-client/src/main/frontend/FlowBootstrap.js:9
  • invokeFromBundle has cyclomatic complexity 12 and cognitive complexity 11; 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. — flow-client/src/main/frontend/internal/client/flow/ExecuteJavaScriptProcessor.ts:292
  • nullSafe has cyclomatic complexity 11 and cognitive complexity 28; 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. — flow-polymer2lit/convert.ts:770
  • updateAttributeValue has cyclomatic complexity 11 and cognitive complexity 15; 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. — REDACTED:1467
  • acquire has cyclomatic complexity 11 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 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. — flow-client/src/main/frontend/WakeLock.ts:42
  • #sendPayload has cyclomatic complexity 11 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 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. — flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:282
  • populateApplicationConfiguration has cyclomatic complexity 11 and cognitive complexity 11; 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. — flow-client/src/main/frontend/internal/client/bootstrap/Bootstrapper.ts:72
R3 · Large Files7.0 / 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.

  • REDACTED has 1677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts has 789 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:1
  • flow-polymer2lit/convert.ts has 788 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-polymer2lit/convert.ts:1
  • vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts has 784 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:1
  • flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts has 732 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:1
  • flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx has 664 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:1
  • flow-client/src/main/frontend/internal/client/communication/MessageSender.ts has 574 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:1
  • vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts:1
  • flow-client/src/main/frontend/internal/client/Profiler.ts has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/Profiler.ts:1
  • flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts:1
  • flow-client/src/main/frontend/ConnectionIndicator.ts has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/ConnectionIndicator.ts:1
  • flow-client/src/main/frontend/Flow.ts has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/Flow.ts:1
  • flow-client/src/main/frontend/internal/client/ResourceLoader.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/ResourceLoader.ts:1
  • vaadin-dev-server/src/main/frontend/hotswap-scroll.ts has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vaadin-dev-server/src/main/frontend/hotswap-scroll.ts:1
  • flow-client/src/main/frontend/internal/client/flow/StateTree.ts has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flow-client/src/main/frontend/internal/client/flow/StateTree.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage7.0 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4 imports '../../../styles/shared-styles.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4
  • flow-polymer2lit/src/test/resources/frontend/in/order-card-from-bakery.js:2 imports '../../../styles/shared-styles.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — flow-polymer2lit/src/test/resources/frontend/in/order-card-from-bakery.js:2
  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×38) — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:1, flow-polymer2lit/convert.ts:1, flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.9 / 10Strong✓ Tool-verified

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.

R6 · Tooling10.0 / 10Exemplary✓ 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.

  • The package in `flow-client` declares the lint script `lint` (`eslint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `flow-client` (or the workspace's task runner). — flow-client/package.json:12
  • This repository declares test tooling, and the ✓ above records that declaration — but flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js and 1 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4
R7 · Dead Code9.8 / 10Exemplary✓ 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.

  • 8 file(s) (~139 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: flow-tests/test-frontend/vite-basics/vite.config.ts imports './vite.generated.ts', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — flow-tests/test-frontend/vite-basics
  • 1 file(s) (~35 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — flow-tests/test-frontend/vite-context-path
  • 3 file(s) (~24 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: flow-tests/test-frontend/vite-production/vite.config.ts imports './vite.generated.ts', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — flow-tests/test-frontend/vite-production
  • Unreachable from the 119 application, 23 tooling and 157 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 (119 application, 23 tooling, 157 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 (×7) — vaadin-dev-server/export-metadata-script.ts, flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/fake-resources/com/vaadin/flow/server/frontend/Flow.tsx, flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/fake-plugin-resources/com/vaadin/flow/server/frontend/Flow.tsx, …
  • Nothing imports this binding — it is safe to review for removal. — flow-client/src/main/frontend/internal/client/WidgetUtil.ts:29
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — flow-client/src/test/frontend/FlowTests.ts:20

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/types.d.ts:7
  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. — flow-build-tools/src/main/resources/plugins/react-function-location-plugin/react-function-location-plugin.js:1
  • Declared in flow-polymer2lit/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) — flow-polymer2lit/package.json:21, flow-polymer2lit/package.json:23
  • Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/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. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json:9
  • Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json:11
  • Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/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. — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:5
  • Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. (×3) — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:6, flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:8, flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:9
  • Declared in flow-tests/test-frontend/vite-basics/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. (×10) — flow-tests/test-frontend/vite-basics/package.json:28, flow-tests/test-frontend/vite-basics/package.json:29, flow-tests/test-frontend/vite-basics/package.json:34, …
  • Declared in flow-tests/test-frontend/vite-basics/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — flow-tests/test-frontend/vite-basics/package.json:39
  • Declared in flow-tests/test-frontend/vite-basics/package.json but never imported anywhere in that package or its workspace members — while flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — flow-tests/test-frontend/vite-basics/package.json:40
  • Declared in flow-tests/test-frontend/vite-context-path/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. (×7) — flow-tests/test-frontend/vite-context-path/package.json:20, flow-tests/test-frontend/vite-context-path/package.json:21, flow-tests/test-frontend/vite-context-path/package.json:26, …
  • Declared in flow-tests/test-frontend/vite-context-path/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — flow-tests/test-frontend/vite-context-path/package.json:31
  • Declared in flow-tests/test-frontend/vite-context-path/package.json but never imported anywhere in that package or its workspace members — while flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — flow-tests/test-frontend/vite-context-path/package.json:32
  • Declared in flow-tests/test-frontend/vite-production/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. (×9) — flow-tests/test-frontend/vite-production/package.json:25, flow-tests/test-frontend/vite-production/package.json:26, flow-tests/test-frontend/vite-production/package.json:31, …

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports6.6 / 10Adequate✓ Tool-verified

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.

  • flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts → flow-client/src/main/frontend/internal/client/flow/reactive/Reactive.ts → flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts — flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts:22
  • vaadin-dev-server/src/main/frontend/License.ts → vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts → vaadin-dev-server/src/main/frontend/License.ts — vaadin-dev-server/src/main/frontend/License.ts:2

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

  • `ui == null` can never be true where it stands: control only reaches it when `ui != null` (line 1279). The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it. — flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1290

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.
X13 · Undrained process stream3.5 / 10Weak✓ 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 merges `stderr` into `stdout` here (`redirectErrorStream(true)`), and that one stream is still a pipe — and `process.waitFor()` is written before stdout is read, so nothing drains it while the parent waits. 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). — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/OpenInCurrentIde.java:213
  • The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `child.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). — flow-build-tools/src/main/java/com/vaadin/frontendtools/installer/DefaultArchiveExtractor.java:69
  • 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). — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:922

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.
X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X17 · Uncapped recursion over a caller-supplied document1.3 / 10Critical✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `decodeArgs` is not private, takes a value from its caller (line 243) and hands it on to `decodeArray`, which recurses at line 389 through `decodeArg` and back with a piece of `argValue` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `decodeArray` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/server/communication/rpc/PublishedServerEventHandlerRpcHandler.java:389
  • `toJson` is not private and takes `Object bean` from its caller, and it calls itself at line 94 with a piece of `bean` (and at line 104, line 134) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toJson` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:94
  • `toObject` is not private and takes `JsonNode json` from its caller, and it recurses at line 256 through `toRecord`, `toArray`, `toObjects`, `toCollection` and back with a piece of `json` (and at line 279, line 325, line 351) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toObject` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:256
  • `jsonObjectEquals` is not private and takes `JsonNode a` from its caller, and it recurses at line 329 through `jsonArrayEquals`, `jsonEquals` and back with a piece of `a` (and at line 355) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `jsonObjectEquals` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:329
  • `getNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 610 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `getNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:610
  • `setNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 657 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `setNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:657
  • `removeNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 684 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `removeNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:684
  • `isTrueish` is not private and takes `Object value` from its caller, and it calls itself at line 60 with a piece of `value` (and at line 75) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `isTrueish` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/internal/JavaScriptSemantics.java:60
  • `toJsoup` is not private and takes `Element element` from its caller, and it calls itself at line 242 with a piece of `element` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toJsoup` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:242
  • `fromJsoup` is not private and takes `Node node` from its caller, and it calls itself at line 282 with a piece of `node` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `fromJsoup` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:282
  • `removeCommentsRecursively` is not private and takes `Node node` from its caller, and it calls itself at line 50 with a piece of `node` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `removeCommentsRecursively` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/JsoupUtils.java:50
  • `createModelTree` is exported and takes `object: unknown` from its caller, and it calls itself at line 59 (`createModelTree`) with a piece of `object` (and at line 78, line 81) — and nowhere in `createModelTree` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `createModelTree` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:59
  • `decodeCopyWithTypeInfo` is exported, takes a document from its caller (line 252) and hands it to `copyWithoutRemovedNodes`, which calls itself at line 227 (`copyWithoutRemovedNodes`) with a piece of `value` (and at line 236) — and nowhere in `copyWithoutRemovedNodes` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `copyWithoutRemovedNodes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — flow-client/src/main/frontend/internal/client/flow/util/ClientJsonCodec.ts:227
  • `pinVersionsForNpm` is not private, takes a value from its caller (line 147) and hands it on to `flattenOverrides`, which calls itself at line 604 with a piece of `nestedOverrides` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `flattenOverrides` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:604
  • `sortObject` is not private, takes a value from its caller (line 627) and hands it on to `orderKeys`, which calls itself at line 648 with a piece of `object` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `orderKeys` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:648
  • `compareObjects` is not private and takes `JsonNode jsonObjectFromBundle` from its caller, and it recurses at line 368 through `checkMissedKeys`, `compareArrays`, `objectIncludesEntry` and back with a piece of `jsonObjectFromBundle` (and at line 418) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `compareObjects` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ThemeValidationUtil.java:368
  • `collectThemeJsonContentsInFrontend` is not private and takes `JsonNode themeJson` from its caller, and it calls itself at line 284 with a piece of `themeJson` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `collectThemeJsonContentsInFrontend` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ThemeValidationUtil.java:284

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X23 · Unguarded diagnostic materialisation7.6 / 10Strong✓ Tool-verified

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

  • `debug` at line 156 is called with an argument built by `stream()` (line 158), whose cost grows with the collection it walks. Java evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled`/`isTraceEnabled` test, no debug flag, no lambda or `Supplier` the logger calls only when the level is on. — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopHotswapper.java:156
  • `debug` at line 892 is called with an argument built by `String.join("…", command)` (line 892), whose cost grows with the collection it walks. Java evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled`/`isTraceEnabled` test, no debug flag, no lambda or `Supplier` the logger calls only when the level is on. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:892

What to do

  • In Java, put the construction behind the logger's own check (`if (log.isDebugEnabled())` for SLF4J and Log4j, `if (logger.isLoggable(Level.FINE))` for java.util.logging), or hand the logger a lambda it calls only when the level is on (Log4j 2's `Supplier` overloads, SLF4J 2's `log.atDebug().addArgument(() -> …)`). A `{}` placeholder alone is not the fix: it defers the formatting, not the stream, join or serialisation in the argument.
X24 · Document value interpolated into markup unescaped4.8 / 10Weak✓ Tool-verified

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.

  • `productAndMessage.messageHtml` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — vaadin-dev-server/src/main/frontend/License.ts:90
  • `productAndMessage.message` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — vaadin-dev-server/src/main/frontend/License.ts:91
  • `relative` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:785

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

X3 · Exception handling7.6 / 10Strong✓ Tool-verified

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 (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. (×5) — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:643, vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:784, vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:980, …
  • `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. — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1189
  • `catch (e)` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:622
  • `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) — vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.java:80, vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.java:350, vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.java:370, …
  • 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. (×5) — flow-server/src/main/java/com/vaadin/flow/internal/FileIOUtils.java:418, flow-client/src/main/frontend/Geolocation.ts:133, flow-client/src/main/frontend/WakeLock.ts:62, …

What to do

  • Swallowed exception (caught, then discarded)
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.

X4 · Structured logging7.7 / 10Strong✓ Tool-verified

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.

  • `warn` at line 186 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. — flow-server/src/main/java/com/vaadin/flow/server/auth/AnnotatedViewAccessChecker.java:186
  • `error` at line 1132 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. — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:1132

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types8.6 / 10Strong✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 21/22 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~2.7 `!` null assertions per 1k TypeScript source lines — 76 assertion(s) across the 28489 source line(s) of the 149 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: REDACTED (12), flow-client/src/main/frontend/internal/client/flow/binding/Debouncer.ts (8), flow-client/src/main/frontend/internal/client/Profiler.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 42 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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.

LensScoreRatingImpact
Code Health78.1StrongSolid.
Architecture79.4StrongSolid.
Maturity69.4AdequateAcceptable, with room to improve.
Readiness53.1Adequate — gated by R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security52.7Checked 4 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility60.6Adequate — gated by AC3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance88.6StrongStrongest area.
Unscored — 5 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.

  • D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .ts, .kt, .js), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • SC1 Supply-chain hygiene — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 38 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 8 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 — 40 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.

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run start` in vaadin-dev-server/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > npm run install-deps && web-dev-server --node-resolve / > install-deps / > playwright install / sh: 1: playwright: not found" 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.
  • D12 Dependency Hygiene — Not scored — a Gradle build resolved 50 artifact(s) across its subprojects (38 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.
  • 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.
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript, Kotlin surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. 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) — 10 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.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the web-test-runner suite in flow-client/ ran and not one test passed (TypeError: Failed to resolve module specifier "@open-wc/testing". Relative references must start with either "/", "./", or "../".), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 236 value object(s); 27 domain event(s); its domain events are published by services or handlers — no domain entity raises one
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (20 event handler(s))
  • ED5 Idempotency — Not assessed, and this one is on us: 20 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — Hibernate is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
  • 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
  • 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.
  • 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.
  • X1 Async correctness — X1 reached only 10% of this repository's production lines — java (335,871 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
  • X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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.

Critical — 33 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document without a <title> · ×3
  • Document without a <title> REDACTED:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×3
  • Orphaned knowledge flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge flow-server/src/main/java/com/vaadin/flow/dom/Node.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge flow-data/src/main/java/com/vaadin/flow/data/provider/InMemoryDataProvider.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts:22 — flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts → flow-client/src/main/frontend/internal/client/flow/reactive/Reactive.ts → flow-client/src/main/frontend/internal/client/flow/reactive/Computation.ts
  • Import cycle (2 files) vaadin-dev-server/src/main/frontend/License.ts:2 — vaadin-dev-server/src/main/frontend/License.ts → vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts → vaadin-dev-server/src/main/frontend/License.ts
AC2 · Forms & labels · Link with no accessible name · ×1
  • Link with no accessible name vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:785 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title flow-client/src/main/frontend/Flow.ts:516 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
D10 · Test Quality · No assertions (empty test) · ×1
  • No assertions (empty test): indexDependencyReference_warningLogged vaadin-quarkus/deployment/src/test/java/com/vaadin/flow/quarkus/test/DeprecatedJandexArtifactsWarningBuildTest.java:52 — Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability · Test declared unreliable · ×1
  • Test declared unreliable: countUisNumer_onlyOneUIShouldBeInitiialized flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/CountUIsIT.java:31 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Ignored because the test is flaky: https://github.com/vaadin/flow/issues/10493". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: BuildFrontendUtil.java ↔ AbstractConfigurationFactory.java flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:1 — `flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java` (context flow-plugins) and `flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractConfigurationFactory.java` (context flow-server) sit in DIFFERENT parts of the tree yet change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `4b4b6be1` feat(FrontendTools): Add support for custom node folder (#23124); `3d3747fb` feat: show watermark in production mode (#21915); `717d482e` feat: Add support for customizable projectFileExtensions (#20397) — run `git show` on any of them.
R8 · Dependency Hygiene · Unlisted import '@babel/types' · ×1
  • Unlisted import '@babel/types' flow-build-tools/src/main/resources/plugins/react-function-location-plugin/react-function-location-plugin.js:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 1479 finding(s)
D10 · Test Quality · No assertions · ×278
  • No assertions: nullProgressListenerWorks flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/installer/DefaultFileDownloaderTest.java:81 — 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: importingBinaryFile_importVisitorShouldNotFail flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/AbstractUpdateImportsTest.java:693 — 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: deleteNodeModules_nopIfNotExists flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendUtilsTest.java:349 — 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: missingImport_noServerRoutesDefined_noExceptionThrown flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskGenerateReactFilesTest.java:279 — 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: routesContainExport_noConst_noExceptionThrown flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskGenerateReactFilesTest.java:470 — 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: routesContainExport_twoSingleExports_noExceptionThrown flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskGenerateReactFilesTest.java:487 — 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: routesContainImportAndUsage_serverSideRoutes_noExceptionThrown flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskGenerateReactFilesTest.java:127 — 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: routesContainMultipleFlowImports_noExceptionThrown flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskGenerateReactFilesTest.java:186 — 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: execute_handlesMissingDirectory flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskProcessStylesheetCssTest.java:257 — 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: execute_handlesNullResourceOutputDirectory flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/TaskProcessStylesheetCssTest.java:266 — 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: assertFullSortOrder flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/UpdateImportsWithByteCodeScannerTest.java:69 — 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: assertFullSortOrder flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/UpdateImportsWithFullCPScannerTest.java:36 — 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: noReturnChannelMap_invocationIgnored flow-server/src/test/java/com/vaadin/flow/server/communication/rpc/ReturnChannelHandlerTest.java:86 — 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: doHandleMultipartFileUpload_IOExceptionIsThrown_exceptionIsNotRethrown_exceptionIsNotHandlerByErrorHandler flow-server/src/test/java/com/vaadin/flow/server/communication/StreamReceiverHandlerTest.java:469 — 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: handleFileUploadValidationAndData_inputStreamThrowsIOExceptionOnClose_exceptionIsNotRethrown_exceptionIsNotHandlerByErrorHandler flow-server/src/test/java/com/vaadin/flow/server/communication/StreamReceiverHandlerTest.java:449 — 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: responseIsNotSentOnIncorrectSecurityKey flow-server/src/test/java/com/vaadin/flow/server/communication/StreamReceiverHandlerTest.java:376 — 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: responseIsNotSentOnMissingSecurityKey flow-server/src/test/java/com/vaadin/flow/server/communication/StreamReceiverHandlerTest.java:386 — 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: doesNotRequireToCatchIOException flow-server/src/test/java/com/vaadin/flow/server/communication/UploadHandlerTest.java:620 — 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: fileUploadCallback_doesNotRequireCatch flow-server/src/test/java/com/vaadin/flow/server/communication/UploadHandlerTest.java:723 — 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: inmemoryUploadCallback_doesNotRequireCatch flow-server/src/test/java/com/vaadin/flow/server/communication/UploadHandlerTest.java:737 — 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: tmpUploadCallback_doesNotRequireCatch flow-server/src/test/java/com/vaadin/flow/server/communication/UploadHandlerTest.java:730 — 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: writeBootstrapPage_spepe flow-server/src/test/java/com/vaadin/flow/server/communication/WebComponentBootstrapHandlerViteTest.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: onStartUp_no_exception_is_thrown_for_correctly_setup_classes flow-server/src/test/java/com/vaadin/flow/server/startup/AnnotationValidatorTest.java:147 — 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: serviceInit_productionMode_licenseNotChecked flow-server/src/test/java/com/vaadin/flow/server/startup/BaseLicenseCheckerServiceInitListenerTest.java:66 — 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: process_one_body_size_in_chain_and_one_for_route_passes flow-server/src/test/java/com/vaadin/flow/server/startup/RouteRegistryInitializerTest.java:837 — 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.
  • + 253 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×61
  • TooManyMethods: VaadinService flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:115 — TooManyMethods — 128 methods. The bar is 30 methods; this is 98 over it, 4.27× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: UIInternals flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java:125 — TooManyMethods — 125 methods. The bar is 30 methods; this is 95 over it, 4.17× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: Options flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/Options.java:47 — TooManyMethods — 104 methods. The bar is 30 methods; this is 74 over it, 3.47× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: Binder flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:109 — TooManyMethods — 101 methods. The bar is 30 methods; this is 71 over it, 3.37× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: Element flow-server/src/main/java/com/vaadin/flow/dom/Element.java:93 — TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: UI flow-server/src/main/java/com/vaadin/flow/component/UI.java:121 — TooManyMethods — 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: Launch flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:53 — TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.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: DataCommunicator flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:72 — TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: Compile flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:70 — TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.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.
  • TooManyMethods: BeforeEvent flow-server/src/main/java/com/vaadin/flow/router/BeforeEvent.java:40 — TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: VaadinSession flow-server/src/main/java/com/vaadin/flow/server/VaadinSession.java:78 — TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: StateNode flow-server/src/main/java/com/vaadin/flow/internal/StateNode.java:73 — TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: QuarkusPluginAdapter vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/vaadinplugin/QuarkusPluginAdapter.java:53 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. Most of these members implement base.PluginAdapterBase (39 of 57 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: BuildDevBundleMojo flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:95 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. Most of these members implement base.PluginAdapterBase (38 of 57 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: Table flow-html-components/src/main/java/com/vaadin/flow/component/html/Table.java:73 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: GradlePluginAdapter flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/GradlePluginAdapter.kt:40 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: ShortcutRegistration flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java:55 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: AbstractNavigationStateRenderer flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java:83 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: FlowModeAbstractMojo flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:70 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. Most of these members implement base.PluginAdapterBase (39 of 49 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: DevLoopRedefiner vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:95 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: VaadinSecurityConfigurer vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java:148 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: RouteSegment flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:50 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FrontendUtils flow-server/src/main/java/com/vaadin/flow/internal/FrontendUtils.java:67 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • TooManyMethods: AbstractUpdateImports flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:78 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: Component flow-server/src/main/java/com/vaadin/flow/component/Component.java:65 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
  • + 36 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×38
  • No test reaches this file vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-polymer2lit/convert.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file vaadin-dev-server/src/main/frontend/hotswap-scroll.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-handle.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file vaadin-dev-server/src/main/frontend/License.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-copy.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/com/vaadin/flow/server/webcomponent/webcomponent-script-template.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/META-INF/frontend/theme-util.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/vite-plugin-service-worker/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file vaadin-dev-server/src/main/frontend/websocket-connection.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/com/vaadin/flow/server/frontend/vite-devmode.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/application-theme-plugin/css-theme-generator.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-server/src/main/resources/com/vaadin/flow/server/frontend/commercial-banner.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/plugins/react-function-location-plugin/react-function-location-plugin.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file flow-build-tools/src/main/resources/com/vaadin/flow/server/frontend/compress-static-resources.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file vaadin-dev-server/src/main/frontend/live-reload-connection.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 13 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×36
  • ClassTooLong: VaadinService flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:115 — ClassTooLong — 1070 significant lines (blank, comment-only and punctuation-only lines excluded), 128 methods. The bar is 400 significant lines; this is 670 over it, 2.68× 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: BootstrapHandler flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:101 — ClassTooLong — 794 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 394 over it, 1.99× 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: UIInternals flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java:125 — ClassTooLong — 771 significant lines (blank, comment-only and punctuation-only lines excluded), 125 methods. The bar is 400 significant lines; this is 371 over it, 1.93× 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: BundleValidationUtil flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/BundleValidationUtil.java:70 — ClassTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 335 over it, 1.84× 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: Launch flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:53 — ClassTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 400 significant lines; this is 315 over it, 1.79× 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: VaadinServletContextInitializer vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:111 — ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 21 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: DevLoopRedefiner vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:95 — ClassTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 285 over it, 1.71× 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: AbstractUpdateImports flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:78 — ClassTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 280 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Compile flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:70 — ClassTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 400 significant lines; this is 275 over it, 1.69× 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: DataCommunicator flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:72 — ClassTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The bar is 400 significant lines; this is 256 over it, 1.64× 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: BuildFrontendUtil flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:90 — ClassTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 240 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: AbstractNavigationStateRenderer flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java:83 — ClassTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 238 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: UI flow-server/src/main/java/com/vaadin/flow/component/UI.java:121 — ClassTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods. The bar is 400 significant lines; this is 218 over it, 1.55× 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: Element flow-server/src/main/java/com/vaadin/flow/dom/Element.java:93 — ClassTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 400 significant lines; this is 211 over it, 1.53× 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: FrontendDependencies flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:82 — ClassTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 195 over it, 1.49× 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: TaskRunNpmInstall flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:65 — ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 186 over it, 1.47× 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: TaskUpdatePackages flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:55 — ClassTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 184 over it, 1.46× 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: MutableTreeRevision flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:72 — ClassTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 174 over it, 1.44× 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: VaadinDevTools vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:85 — ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 17 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: ShortcutRegistration flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java:55 — ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 400 significant lines; this is 152 over it, 1.38× 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: StateNode flow-server/src/main/java/com/vaadin/flow/internal/StateNode.java:73 — ClassTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 400 significant lines; this is 126 over it, 1.32× 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: FrontendUtils flow-server/src/main/java/com/vaadin/flow/internal/FrontendUtils.java:67 — ClassTooLong — 490 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 90 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.
  • ClassTooLong: FrontendTools flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:68 — ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 83 over it, 1.21× 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: ReflectTools flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:58 — ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 83 over it, 1.21× 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: RouteSegment flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:50 — ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 78 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.
  • + 11 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×34
  • FileTooLong: binder/Binder.java flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java — FileTooLong — 1427 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 927 over it, 2.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: server/VaadinService.java flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java — FileTooLong — 1157 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: VaadinService (115-3232). The bar is 500 significant lines; this is 657 over it, 2.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: REDACTED REDACTED — FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 435 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: daemon/TransactionEngine.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java — FileTooLong — 905 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 405 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: server/BootstrapHandler.java flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java — FileTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: BootstrapHandler (101-1776). The bar is 500 significant lines; this is 367 over it, 1.73× 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: internal/UIInternals.java flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java — FileTooLong — 866 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: UIInternals (125-2529). The bar is 500 significant lines; this is 366 over it, 1.73× 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: spring/VaadinServletContextInitializer.java vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java — FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: VaadinServletContextInitializer (111-1259). The bar is 500 significant lines; this is 278 over it, 1.56× 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: frontend/BundleValidationUtil.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/BundleValidationUtil.java — FileTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: BundleValidationUtil (70-1273). The bar is 500 significant lines; this is 277 over it, 1.55× 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: devloop/DevLoopRedefiner.java vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java — FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: DevLoopRedefiner (95-1799). The bar is 500 significant lines; this is 242 over it, 1.48× 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: daemon/Launch.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java — FileTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: Launch (53-1860). The bar is 500 significant lines; this is 237 over it, 1.47× 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: frontend/AbstractUpdateImports.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java — FileTooLong — 729 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: AbstractUpdateImports (78-1150). The bar is 500 significant lines; this is 229 over it, 1.46× 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: daemon/Compile.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java — FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Compile (70-2003). The bar is 500 significant lines; this is 206 over it, 1.41× 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: base/BuildFrontendUtil.java flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java — FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: BuildFrontendUtil (90-1137). The bar is 500 significant lines; this is 206 over it, 1.41× 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: provider/DataCommunicator.java flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java — FileTooLong — 698 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: DataCommunicator (72-1696). The bar is 500 significant lines; this is 198 over it, 1.40× 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: component/UI.java flow-server/src/main/java/com/vaadin/flow/component/UI.java — FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: UI (121-2475). The bar is 500 significant lines; this is 197 over it, 1.39× 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: internal/AbstractNavigationStateRenderer.java flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java — FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: AbstractNavigationStateRenderer (83-1322). The bar is 500 significant lines; this is 193 over it, 1.39× 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: dom/Element.java flow-server/src/main/java/com/vaadin/flow/dom/Element.java — FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: Element (93-2649). The bar is 500 significant lines; this is 175 over it, 1.35× 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: scanner/FrontendDependencies.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java — FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: FrontendDependencies (82-1104). The bar is 500 significant lines; this is 149 over it, 1.30× 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: frontend/TaskRunNpmInstall.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java — FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: TaskRunNpmInstall (65-1139). The bar is 500 significant lines; this is 123 over it, 1.25× 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: impl/MutableTreeRevision.java flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java — FileTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: MutableTreeRevision (72-1033). The bar is 500 significant lines; this is 121 over it, 1.24× 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: frontend/TaskUpdatePackages.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java — FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: TaskUpdatePackages (55-1136). 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: frontend/vaadin-dev-tools.ts vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts — FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: VaadinDevTools (86-902). The bar is 500 significant lines; this is 91 over it, 1.18× 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: component/ShortcutRegistration.java flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java — FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ShortcutRegistration (55-1376). The bar is 500 significant lines; this is 81 over it, 1.16× 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: communication/IndexHtmlRequestHandler.java flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: deployment/VaadinQuarkusNativeProcessor.java vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java — FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: VaadinQuarkusNativeProcessor (150-846). The bar is 500 significant lines; this is 72 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.
  • + 9 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×25
  • TodoComment vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusProcessor.java:523 — // TODO: check that we don't register 2 of the same mapping — 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 vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/StatisticsSender.java:307 — // TODO is reason phrase needed here — 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 vaadin-dev-server/src/main/java/com/vaadin/base/devserver/startup/DevModeInitializer.java:239 — // TODO: make sure target directories are aligned with build — 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 REDACTED:407 — // TODO easier to read when testing — 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 flow-server/src/test/java/com/vaadin/tests/server/SerializationTest.java:326 — // TODO This is hilariously broken (#12723)
  • TodoComment flow-server/src/main/java/com/vaadin/flow/server/dau/DAUUtils.java:83 — // TODO: force removal of dau.enable system property to check only on — 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 flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java:651 — // TODO Implemented differently from sendRefreshAndDisconnect — 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 flow-server/src/main/java/com/vaadin/flow/server/communication/PushRequestHandler.java:282 — // TODO PUSH decide how to handle — 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 flow-server/src/main/java/com/vaadin/flow/internal/StateTree.java:303 — // TODO fire preCollect events — 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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:367 — //// TODO to be removed with polymer template support removal — 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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeList.java:321 — // TODO Fire some listeners — 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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeList.java:355 — // TODO Set up listener if we're in a computation — 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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeMap.java:862 — // TODO notify listeners — 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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeMap.java:872 — // TODO register listener — 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 flow-polymer2lit/convert.ts:142 — // const css = modifiedTemplate.styles.join("\n"); //TODO — 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 flow-polymer2lit/convert.ts:279 — // TODO handle properties — 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 flow-polymer2lit/convert.ts:417 — // TODO rewrite input checked="[[checked]]" => ?checked=${this.checked} — 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 flow-polymer2lit/convert.ts:502 — // TODO href="mailto:[[item.email]]" — 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 flow-polymer2lit/convert.ts:503 — // TODO <template> tags — 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 flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:199 — // TODO For some reason, this strips comments — 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 flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/VaadinFlowPluginExtension.kt:680 — // TODO: Possibly get value from system param InitParameters.FRONTEND_EXTRA_EXTENSIONS — 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 flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:591 — // TODO it could be possible to cache the value returned here — 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 REDACTED:320 — // TODO: this code doesn't care about "security feature" which prevents sending — 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 flow-client/src/main/frontend/internal/client/communication/DefaultConnectionStateHandler.ts:388 — // TODO Reconnect, allowing client timeout to be set — 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 flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/AbstractNodeUpdatePackagesTest.java:372 — // TODO: Fixme — 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 · Duplicated block (7 lines × 2) · ×20
  • Duplicated block (7 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:633 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:633-639 | flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:284-290 — 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) flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:108 — flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:108-115 | flow-server/src/main/java/com/vaadin/flow/server/streams/ServletResourceDownloadHandler.java:98-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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.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. 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 (7 lines × 2) flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1186 — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1186-1192 | flow-server/src/main/java/com/vaadin/flow/server/webcomponent/WebComponentExporterUtils.java:90-96 — 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 `flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1186` 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 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:527 — flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:527-533 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/RootCache.java:130-136 — 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) flow-data/src/main/java/com/vaadin/flow/data/binder/BinderValidationStatus.java:143 — flow-data/src/main/java/com/vaadin/flow/data/binder/BinderValidationStatus.java:143-149 | flow-data/src/main/java/com/vaadin/flow/data/binder/ValidationException.java:61-67 — 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) flow-data/src/main/java/com/vaadin/flow/data/converter/AbstractStringToNumberConverter.java:142 — flow-data/src/main/java/com/vaadin/flow/data/converter/AbstractStringToNumberConverter.java:142-148 | flow-data/src/main/java/com/vaadin/flow/data/converter/StringToDateConverter.java:79-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 first that the copies are not typed on the same thing: the declarations holding them bind `value` to `T` in one and `Date` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:59 — flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:59-65 | flow-data/src/main/java/com/vaadin/flow/data/selection/SelectionModel.java:179-185 — 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 `flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:59` 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 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:78 — flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:78-84 | flow-data/src/main/java/com/vaadin/flow/data/selection/SelectionModel.java:204-210 — 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 `flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:78` 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 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:403 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:403-409 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:536-542 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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.
  • Duplicated block (7 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:75 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:75-81 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContextualStorageManager.java:64-70 — 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:75` 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 (7 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:121 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:121-127 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContextualStorageManager.java:102-108 — 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 (7 lines × 2) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:829 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:829-835 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:1107-1113 — 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) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:284 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:284-290 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:159-165 — 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 `flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:159` 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 (7 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/LitTemplateAttributeView.java:39 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/LitTemplateAttributeView.java:39-45 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/template/TemplateAttributeView.java:43-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.
  • Duplicated block (7 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:71 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:71-77 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIContextRootView.java:78-84 — 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:71` 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, `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIContextRootView.java:74` calls `Div`, `setId`, `setText` and `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:69` 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) flow-tests/test-multi-war/test-war1/src/main/java/com/vaadin/flow/multiwar/war1/HelloComponent.java:21 — flow-tests/test-multi-war/test-war1/src/main/java/com/vaadin/flow/multiwar/war1/HelloComponent.java:21-27 | flow-tests/test-multi-war/test-war2/src/main/java/com/vaadin/flow/multiwar/war2/HelloComponent.java:21-27 — before extracting anything, compare `flow-tests/test-multi-war/test-war1/src/main/java/com/vaadin/flow/multiwar/war1/HelloComponent.java` and `flow-tests/test-multi-war/test-war2/src/main/java/com/vaadin/flow/multiwar/war2/HelloComponent.java` as WHOLE FILES: 95% 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 1 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.
  • Duplicated block (7 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:97 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:97-103 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java:89-95 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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.
  • Duplicated block (7 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java:77 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java:77-83 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShortcutsWithValueChangeModeView.java:65-71 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShortcutsWithValueChangeModeView.java` as WHOLE FILES: 85% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java:61 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java:61-67 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/instantiator/ProxiedNavigationTargetView.java:57-63 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/instantiator/ProxiedNavigationTargetView.java` as WHOLE FILES: 88% 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java:61` 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 (7 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/ShortcutView.java:34 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/ShortcutView.java:34-40 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ShortcutView.java:34-40 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/ShortcutView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ShortcutView.java` as WHOLE FILES: 91% 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 1 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×18
  • JavaScript dependencies are not locked flow-build-tools/src/main/resources/plugins/application-theme-plugin/package.json:17 — flow-build-tools/src/main/resources/plugins/application-theme-plugin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/package.json:19 — flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-build-tools/src/main/resources/plugins/vite-plugin-local-web-components/package.json:17 — flow-build-tools/src/main/resources/plugins/vite-plugin-local-web-components/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-build-tools/src/main/resources/plugins/vite-plugin-service-worker/package.json:17 — flow-build-tools/src/main/resources/plugins/vite-plugin-service-worker/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-polymer2lit/package.json:17 — flow-polymer2lit/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json:4 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/react-router/package.json:4 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/react-router/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/tailwindcss/package.json:4 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/tailwindcss/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/vaadin-router/package.json:4 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/vaadin-router/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/vite/package.json:11 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/vite/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:4 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/test/resources/com/vaadin/flow/server/frontend/dependencies/hilla/components/lit/package.json:4 — flow-server/src/test/resources/com/vaadin/flow/server/frontend/dependencies/hilla/components/lit/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/test/resources/com/vaadin/flow/server/frontend/dependencies/hilla/components/react/package.json:4 — flow-server/src/test/resources/com/vaadin/flow/server/frontend/dependencies/hilla/components/react/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-server/src/test/resources/versions/package.json:5 — flow-server/src/test/resources/versions/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-tests/test-frontend/vite-basics/package.json:9 — flow-tests/test-frontend/vite-basics/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-tests/test-frontend/vite-context-path/package.json:5 — flow-tests/test-frontend/vite-context-path/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked flow-tests/test-frontend/vite-production/package.json:6 — flow-tests/test-frontend/vite-production/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked vaadin-dev-server/package.json:8 — vaadin-dev-server/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
D15 · Churn × Complexity Hotspots · Hotspot · ×17
  • Hotspot: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in TransactionEngine.apply at line 379. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.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.
  • Hotspot: vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:236 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in DevLoopRedefiner.redefine at line 236. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.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.
  • Hotspot: flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:725 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ElementListenerMap.collectEventExpressions at line 725. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.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.
  • Hotspot: flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:288 — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in MessageHandler.#handleJSON at line 288. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: flow-tests/scripts/generate-migration-list.py flow-tests/scripts/generate-migration-list.py:113 — flow-tests/scripts/generate-migration-list.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in generate-migration-list.target at line 113. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-tests/scripts/generate-migration-list.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:271 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TaskRunNpmInstall.runNpmInstall at line 271. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.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.
  • Hotspot: flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java:253 — flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in JsDefinitionProxy.checkMethods at line 253. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.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.
  • Hotspot: flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in NodeTasks.<init> at line 111. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.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.
  • Hotspot: flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java:108 — flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in IndexHtmlRequestHandler.synchronizedHandleRequest at line 108. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.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.
  • Hotspot: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java:401 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in AppProcess.start at line 401. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.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.
  • Hotspot: flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java:262 — flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in AbstractDownloadHandler.transferContent at line 262. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.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.
  • Hotspot: flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java:471 — flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PushHandler.handleConnectionLost at line 471. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.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.
  • Hotspot: flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:349 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Flow.Flow at line 349. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java:703 — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in VaadinSecurityConfigurer.init at line 703. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.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.
  • Hotspot: vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:632 — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in VaadinDevTools.openWebSocketConnection at line 632. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:561 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Watch.drain at line 561. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.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.
  • Hotspot: scripts/memoryFootprint.js scripts/memoryFootprint.js:165 — scripts/memoryFootprint.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in memoryFootprint.comment at line 165. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- scripts/memoryFootprint.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×17
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/server/communication/rpc/PublishedServerEventHandlerRpcHandler.java:389 — `decodeArgs` is not private, takes a value from its caller (line 243) and hands it on to `decodeArray`, which recurses at line 389 through `decodeArg` and back with a piece of `argValue` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `decodeArray` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:94 — `toJson` is not private and takes `Object bean` from its caller, and it calls itself at line 94 with a piece of `bean` (and at line 104, line 134) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toJson` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:256 — `toObject` is not private and takes `JsonNode json` from its caller, and it recurses at line 256 through `toRecord`, `toArray`, `toObjects`, `toCollection` and back with a piece of `json` (and at line 279, line 325, line 351) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toObject` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:329 — `jsonObjectEquals` is not private and takes `JsonNode a` from its caller, and it recurses at line 329 through `jsonArrayEquals`, `jsonEquals` and back with a piece of `a` (and at line 355) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `jsonObjectEquals` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:610 — `getNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 610 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `getNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:657 — `setNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 657 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `setNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:684 — `removeNestedKey` is not private and takes `ObjectNode objectNode` from its caller, and it calls itself at line 684 with a piece of `objectNode` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `removeNestedKey` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/internal/JavaScriptSemantics.java:60 — `isTrueish` is not private and takes `Object value` from its caller, and it calls itself at line 60 with a piece of `value` (and at line 75) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `isTrueish` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:242 — `toJsoup` is not private and takes `Element element` from its caller, and it calls itself at line 242 with a piece of `element` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `toJsoup` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:282 — `fromJsoup` is not private and takes `Node node` from its caller, and it calls itself at line 282 with a piece of `node` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `fromJsoup` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/JsoupUtils.java:50 — `removeCommentsRecursively` is not private and takes `Node node` from its caller, and it calls itself at line 50 with a piece of `node` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `removeCommentsRecursively` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:59 — `createModelTree` is exported and takes `object: unknown` from its caller, and it calls itself at line 59 (`createModelTree`) with a piece of `object` (and at line 78, line 81) — and nowhere in `createModelTree` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `createModelTree` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-client/src/main/frontend/internal/client/flow/util/ClientJsonCodec.ts:227 — `decodeCopyWithTypeInfo` is exported, takes a document from its caller (line 252) and hands it to `copyWithoutRemovedNodes`, which calls itself at line 227 (`copyWithoutRemovedNodes`) with a piece of `value` (and at line 236) — and nowhere in `copyWithoutRemovedNodes` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `copyWithoutRemovedNodes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:604 — `pinVersionsForNpm` is not private, takes a value from its caller (line 147) and hands it on to `flattenOverrides`, which calls itself at line 604 with a piece of `nestedOverrides` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `flattenOverrides` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:648 — `sortObject` is not private, takes a value from its caller (line 627) and hands it on to `orderKeys`, which calls itself at line 648 with a piece of `object` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `orderKeys` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ThemeValidationUtil.java:368 — `compareObjects` is not private and takes `JsonNode jsonObjectFromBundle` from its caller, and it recurses at line 368 through `checkMissedKeys`, `compareArrays`, `objectIncludesEntry` and back with a piece of `jsonObjectFromBundle` (and at line 418) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `compareObjects` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ThemeValidationUtil.java:284 — `collectThemeJsonContentsInFrontend` is not private and takes `JsonNode themeJson` from its caller, and it calls itself at line 284 with a piece of `themeJson` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `collectThemeJsonContentsInFrontend` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×16
  • Duplicated block (8 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:800 — flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:800-807 | flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1492-1499 — 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 `flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:800` 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 (8 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/VaadinTaskExecutorSelector.java:90 — vaadin-cdi/src/main/java/com/vaadin/cdi/VaadinTaskExecutorSelector.java:90-97 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:122-129 — 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/VaadinTaskExecutorSelector.java:90` 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 first that the copies are not typed on the same thing: `VaadinServiceEnabled` names `com.vaadin.cdi.annotation.VaadinServiceEnabled` in one and `com.vaadin.quarkus.annotation.VaadinServiceEnabled` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:298 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:298-305 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskProcessStylesheetCss.java:145-152 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/converter/StringToBigDecimalConverter.java:96 — flow-data/src/main/java/com/vaadin/flow/data/converter/StringToBigDecimalConverter.java:96-103 | flow-data/src/main/java/com/vaadin/flow/data/converter/StringToBigIntegerConverter.java:97-104 — before extracting anything, compare `flow-data/src/main/java/com/vaadin/flow/data/converter/StringToBigDecimalConverter.java` and `flow-data/src/main/java/com/vaadin/flow/data/converter/StringToBigIntegerConverter.java` as WHOLE FILES: 88% 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 1 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. 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 (8 lines × 2) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementData.java:50 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementData.java:50-57 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:124-131 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:55 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:55-62 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContextualStorageManager.java:42-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.
  • Duplicated block (8 lines × 2) vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringUtil.java:32 — vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringUtil.java:32-39 | vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringVaadinServletService.java:243-250 — 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) flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateTimeToDateConverter.java:62 — flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateTimeToDateConverter.java:62-69 | flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateToDateConverter.java:68-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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateTimeToDateConverter.java:62` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/VaadinServletRequest.java:89 — flow-server/src/main/java/com/vaadin/flow/server/VaadinServletRequest.java:89-96 | flow-server/src/main/java/com/vaadin/flow/server/VaadinServletResponse.java:93-100 — 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) flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/ProdModeConfigView.java:26 — flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/ProdModeConfigView.java:26-33 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DevModeConfigView.java:30-37 — 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 (8 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerReadFromClipboardView.java:95 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerReadFromClipboardView.java:95-102 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerWriteToClipboardView.java:267-274 — 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 (8 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:100 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:100-107 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:99-106 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:100` 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 (8 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30-37 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30-37 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` as WHOLE FILES: 100% 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 (8 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:125 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:125-132 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:125-132 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 133 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. 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 (8 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/FocusView.java:33 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/FocusView.java:33-40 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/FocusView.java:34-41 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/keyboard/FocusView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/FocusView.java` as WHOLE FILES: 94% 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 1 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.
  • Duplicated block (8 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MainLayout.java:49 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MainLayout.java:49-56 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/MainLayout.java:45-52 — 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.
D5 · Coupling · Off the main sequence · ×15
  • Off the main sequence: custom-websockets — custom-websockets: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: flow-html-components-testbench — flow-html-components-testbench: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
  • Off the main sequence: flow-test-resources — flow-test-resources: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 29 project(s), so it's rigid to change.
  • Off the main sequence: java-add-on — java-add-on: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: flow-test-lumo — flow-test-lumo: abstractness 0.00, instability 0.02, distance 0.98 — zone of pain — concrete and depended on by 40 project(s), so it's rigid to change.
  • Off the main sequence: flow-devloop-daemon — flow-devloop-daemon: abstractness 0.08, instability 0.00, distance 0.92 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
  • Off the main sequence: test-prod-bundle — test-prod-bundle: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: vaadin-dev-server — vaadin-dev-server: abstractness 0.13, instability 0.03, distance 0.84 — zone of pain — concrete and depended on by 85 project(s), so it's rigid to change.
  • Off the main sequence: flow-client — flow-client: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
  • Off the main sequence: test-dev-bundle — test-dev-bundle: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
  • Off the main sequence: vaadin-spring — vaadin-spring: abstractness 0.11, instability 0.12, distance 0.77 — zone of pain — concrete and depended on by 36 project(s), so it's rigid to change.
  • Off the main sequence: flow-lit-template — flow-lit-template: abstractness 0.20, instability 0.06, distance 0.74 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
  • Off the main sequence: flow-test-generic — flow-test-generic: abstractness 0.27, instability 0.00, distance 0.73 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: flow-build-tools — flow-build-tools: abstractness 0.12, instability 0.17, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: flow-html-components — flow-html-components: abstractness 0.10, instability 0.20, distance 0.70 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×14
  • Edited copy of a member (10 corresponding lines) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:116 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:116-125 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:117-126 — 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:218 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:218-227 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:228-237 — 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) flow-server/src/main/java/com/vaadin/flow/router/RouteAliasData.java:78 — flow-server/src/main/java/com/vaadin/flow/router/RouteAliasData.java:78-87 | flow-server/src/main/java/com/vaadin/flow/router/RouteData.java:148-158 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:599 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:599-608 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:511-520 — 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) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:1167 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:1167-1178 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:1192-1201 — 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) vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:224 — vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:224-233 | vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:257-266 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:423 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:423-434 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:345-354 — 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) flow-server/src/main/java/com/vaadin/flow/server/SessionRouteRegistry.java:171 — flow-server/src/main/java/com/vaadin/flow/server/SessionRouteRegistry.java:171-180 | flow-server/src/main/java/com/vaadin/flow/server/SessionRouteRegistry.java:244-253 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendBuildUtils.java:244 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendBuildUtils.java:244-253 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java:574-583 — 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) flow-server/src/main/java/com/vaadin/flow/internal/EncodeUtil.java:154 — flow-server/src/main/java/com/vaadin/flow/internal/EncodeUtil.java:154-163 | flow-server/src/main/java/com/vaadin/flow/server/HandlerHelper.java:511-520 — 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) flow-server/src/main/java/com/vaadin/flow/component/HasComponentsOfType.java:310 — flow-server/src/main/java/com/vaadin/flow/component/HasComponentsOfType.java:310-319 | flow-server/src/main/java/com/vaadin/flow/component/Html.java:416-425 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uievents/UIEventsView.java:56 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uievents/UIEventsView.java:56-65 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uievents/UIEventsView.java:73-82 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIScopedView.java:39 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIScopedView.java:39-48 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIScopedView.java:37-46 — 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) flow-tests/test-embedding/embedding-test-assets/src/main/java/com/vaadin/flow/webcomponent/PushComponent.java:46 — flow-tests/test-embedding/embedding-test-assets/src/main/java/com/vaadin/flow/webcomponent/PushComponent.java:46-55 | flow-tests/test-frontend/vite-embedded/src/main/java/com/vaadin/viteapp/PushComponent.java:59-68 — 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 (8 corresponding lines) · ×14
  • Edited copy of a member (8 corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/HasSize.java:477 — flow-server/src/main/java/com/vaadin/flow/component/HasSize.java:477-484 | flow-server/src/main/java/com/vaadin/flow/component/HasSize.java:519-526 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:413 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:413-420 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:335-342 — 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) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:984 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:984-991 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:1007-1014 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextualStorage.java:72 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextualStorage.java:72-81 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/ContextualStorage.java:48-55 — 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:245 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:245-252 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:257-264 — 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) flow-data/src/main/java/com/vaadin/flow/data/provider/DataProvider.java:209 — flow-data/src/main/java/com/vaadin/flow/data/provider/DataProvider.java:209-218 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataProvider.java:418-425 — 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) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:438 — flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:438-445 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:195-203 — 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) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1995 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1995-2002 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:1127-1134 — 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) flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1157 — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1157-1164 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/AbstractServerHandlers.java:180-187 — 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) flow-html-components/src/main/java/com/vaadin/flow/component/html/IFrame.java:306 — flow-html-components/src/main/java/com/vaadin/flow/component/html/IFrame.java:306-314 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Image.java:252-259 — 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) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:447 — flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:447-454 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:205-212 — 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) flow-server/src/main/java/com/vaadin/flow/component/fullscreen/Fullscreen.java:161 — flow-server/src/main/java/com/vaadin/flow/component/fullscreen/Fullscreen.java:161-168 | flow-server/src/main/java/com/vaadin/flow/server/auth/AccessAnnotationChecker.java:71-78 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LogoutView.java:29 — flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LogoutView.java:29-39 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/TimeoutView.java:29-36 — 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) flow-tests/test-express-build/test-parent-theme-express-build/src/main/java/com/vaadin/flow/devbuild/ParentThemeView.java:27 — flow-tests/test-express-build/test-parent-theme-express-build/src/main/java/com/vaadin/flow/devbuild/ParentThemeView.java:27-37 | flow-tests/test-express-build/test-reusing-theme-express-build/src/main/java/com/vaadin/flow/devbuild/ReusingThemeView.java:26-33 — 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 · Duplicated block (13 lines × 2) · ×14
  • Duplicated block (13 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractBackEndDataProvider.java:40 — flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractBackEndDataProvider.java:40-52 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/AbstractBackEndHierarchicalDataProvider.java:48-60 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `Query<T, F>` in one and `HierarchicalQuery<T, F>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13 lines × 2) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:226 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:226-238 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java:224-236 — before extracting anything, compare `flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java` and `flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 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. 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 × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:665 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:665-677 | flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:363-375 — 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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:665` 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 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/geolocation/Geolocation.java:339 — flow-server/src/main/java/com/vaadin/flow/component/geolocation/Geolocation.java:339-351 | flow-server/src/main/java/com/vaadin/flow/component/wakelock/WakeLock.java:355-367 — 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 (13 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:98 — vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:98-110 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusInstantiator.java:102-114 — 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 (13 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:151 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:151-163 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:150-162 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:272 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:272-284 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:271-283 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:386 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:386-398 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:385-397 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 × 2) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:336 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:336-348 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:355-370 — 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 `vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:336` 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 (13 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java:59 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java:59-71 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/ContextUtils.java:63-75 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/ContextUtils.java` as WHOLE FILES: 85% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java:59` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:71 — flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:71-83 | flow-tests/test-frontend/vite-production/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:60-72 — 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 (13 lines × 2) flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadView.java:33 — flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadView.java:33-45 | flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadWithShadowRootView.java:35-47 — before extracting anything, compare `flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadView.java` and `flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadWithShadowRootView.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 1 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. 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 (13 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java:45 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java:45-57 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/instantiator/ProxiedNavigationTargetView.java:41-53 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/smoke/ProxiedNavigationTargetView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/instantiator/ProxiedNavigationTargetView.java` as WHOLE FILES: 88% 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 × 2) flow-tests/scripts/generate-migration-list.py:178 — flow-tests/scripts/generate-migration-list.py:178-190 | flow-tests/scripts/generate-migration-list.py:193-205 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×14
  • Duplicated block (10 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/binder/BeanValidationBinder.java:572 — flow-data/src/main/java/com/vaadin/flow/data/binder/BeanValidationBinder.java:572-581 | flow-data/src/main/java/com/vaadin/flow/data/validator/BeanValidator.java:174-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.
  • Duplicated block (10 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:102 — flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:102-111 | flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:129-138 — 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 (10 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:77 — vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:77-86 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusInstantiator.java:81-90 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:104 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:104-113 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:105-114 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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. 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 (10 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:149 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:149-158 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:139-148 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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. 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 (10 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:468 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:468-477 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:546-555 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `sourceMojo` to `BuildDevBundleMojo` in one and `FlowModeAbstractMojo` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/HasComponentsOfType.java:321 — flow-server/src/main/java/com/vaadin/flow/component/HasComponentsOfType.java:321-330 | flow-server/src/main/java/com/vaadin/flow/component/HasText.java:206-215 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:274 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:274-283 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:208-217 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:625 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:625-634 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:537-546 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:625` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ProdBundleUtils.java:135 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ProdBundleUtils.java:135-144 | flow-server/src/main/java/com/vaadin/flow/internal/DevBundleUtils.java:118-127 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java:62 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java:62-71 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeUpdateView.java:61-70 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeUpdateView.java` as WHOLE FILES: 96% 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 (10 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:40 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:40-49 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:56-65 — 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:40` 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, `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:66` calls `log`, `push` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/ManualLongPollingPushView.java:50` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractErrorHandlerView.java:25 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractErrorHandlerView.java:25-34 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/template/ExceptionsDuringPropertyUpdatesView.java:77-86 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractErrorHandlerView.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/template/ExceptionsDuringPropertyUpdatesView.java` as WHOLE FILES: 82% 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 1 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.
  • Duplicated block (10 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:98 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:98-107 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java:96-105 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×14
  • Duplicated block (9 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateReactFiles.java:155 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateReactFiles.java:155-163 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateReactFiles.java:261-269 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateReactFiles.java:155` 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.
  • Duplicated block (9 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:1082 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:1082-1090 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:1096-1104 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:1082` 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 (9 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:421 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:421-429 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:490-498 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. 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 × 2) flow-server/src/main/java/com/vaadin/flow/component/UI.java:1824 — flow-server/src/main/java/com/vaadin/flow/component/UI.java:1824-1832 | flow-server/src/main/java/com/vaadin/flow/component/UI.java:1860-1868 — 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 `flow-server/src/main/java/com/vaadin/flow/component/UI.java:1824` 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) flow-server/src/main/java/com/vaadin/flow/server/AppShellRegistry.java:445 — flow-server/src/main/java/com/vaadin/flow/server/AppShellRegistry.java:445-453 | flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:768-776 — 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 (9 lines × 2) flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:181 — flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:181-189 | flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:284-292 — 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 `flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:181` 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:717 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:717-725 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:845-853 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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. 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:392 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:392-400 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:525-533 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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. 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) vaadin-cdi/src/main/java/com/vaadin/cdi/BeanLookup.java:67 — vaadin-cdi/src/main/java/com/vaadin/cdi/BeanLookup.java:67-75 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/BeanLookup.java:60-68 — 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/BeanLookup.java:67` 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 (9 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/VaadinServiceScopedContext.java:119 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/VaadinServiceScopedContext.java:119-127 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/VaadinServiceScopedContext.java:102-110 — 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/context/VaadinServiceScopedContext.java:119` 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 (9 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/provider/DataProvider.java:243 — flow-data/src/main/java/com/vaadin/flow/data/provider/DataProvider.java:243-251 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataProvider.java:404-413 — 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 `flow-data/src/main/java/com/vaadin/flow/data/provider/DataProvider.java:243` 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. 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) flow-html-components/src/main/java/com/vaadin/flow/component/html/Source.java:133 — flow-html-components/src/main/java/com/vaadin/flow/component/html/Source.java:133-141 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Video.java:116-124 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java:77 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java:77-85 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeProceedView.java:77-85 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeProceedView.java` as WHOLE FILES: 91% 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.
  • Duplicated block (9 lines × 2) flow-tests/test-npm-only-features/test-npm-general/src/main/java/com/vaadin/flow/testnpmonlyfeatures/general/ExternalJSModuleView.java:29 — flow-tests/test-npm-only-features/test-npm-general/src/main/java/com/vaadin/flow/testnpmonlyfeatures/general/ExternalJSModuleView.java:29-37 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/dependencies/ExternalJavaScriptView.java:29-37 — 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 (7 corresponding lines) · ×13
  • Edited copy of a member (7 corresponding lines) flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:3985 — flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:3985-3994 | flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractDataProvider.java:129-135 — 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.
  • Edited copy of a member (7 corresponding lines) flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableRowElement.java:82 — flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableRowElement.java:82-88 | flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableElement.java:418-424 — 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.
  • Edited copy of a member (7 corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/StreamResource.java:110 — flow-server/src/main/java/com/vaadin/flow/server/StreamResource.java:110-116 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/AbstractDevServerRunner.java:897-903 — 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.
  • Edited copy of a member (7 corresponding lines) flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateTimeToDateConverter.java:52 — flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateTimeToDateConverter.java:52-58 | flow-data/src/main/java/com/vaadin/flow/data/converter/LocalDateToDateConverter.java:59-65 — 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.
  • Edited copy of a member (7 corresponding lines) flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeDetails.java:327 — flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeDetails.java:327-333 | flow-server/src/main/java/com/vaadin/flow/router/RouterLink.java:480-486 — 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.
  • Edited copy of a member (7 corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1254 — flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1254-1262 | flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:2556-2562 — 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.
  • Edited copy of a member (7 corresponding lines) flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeTableCell.java:116 — flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeTableCell.java:116-122 | flow-html-components/src/main/java/com/vaadin/flow/component/html/TableColumnSpan.java:60-66 — 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.
  • Edited copy of a member (7 corresponding lines) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:277 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:277-283 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/MavenUtils.java:246-252 — 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.
  • Edited copy of a member (7 corresponding lines) flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeTableCell.java:103 — flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeTableCell.java:103-109 | flow-html-components/src/main/java/com/vaadin/flow/component/html/TableColumnSpan.java:47-53 — 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.
  • Edited copy of a member (7 corresponding lines) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MasterView.java:51 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MasterView.java:51-57 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/MasterView.java:49-55 — 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.
  • Edited copy of a member (7 corresponding lines) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MainLayout.java:37 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/MainLayout.java:37-46 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/MainLayout.java:36-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.
  • Edited copy of a member (7 corresponding lines) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/LogoutView.java:26 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/LogoutView.java:26-32 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/LogoutWithNotificationServlet.java:35-41 — 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.
  • Edited copy of a member (7 corresponding lines) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DnDDisabledView.java:152 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DnDDisabledView.java:152-158 | flow-tests/test-webpush/src/main/java/com/vaadin/flow/webpush/WebPushView.java:114-120 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×13
  • Low cohesion: Options (LCOM4 33) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/Options.java:47 — Options's methods fall into 33 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 33 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: Component (LCOM4 7) flow-server/src/main/java/com/vaadin/flow/component/Component.java:65 — Component's methods fall into 7 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 7 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: RangeInput (LCOM4 6) flow-html-components/src/main/java/com/vaadin/flow/component/html/RangeInput.java:46 — RangeInput's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ServiceInitEvent (LCOM4 5) flow-server/src/main/java/com/vaadin/flow/server/ServiceInitEvent.java:38 — ServiceInitEvent'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: VaadinService (LCOM4 5) flow-server/src/main/java/com/vaadin/flow/server/VaadinService.java:115 — VaadinService'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: UIInternals (LCOM4 5) flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java:125 — UIInternals'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: UI (LCOM4 5) flow-server/src/main/java/com/vaadin/flow/component/UI.java:121 — UI'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: NativeDetails (LCOM4 4) flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeDetails.java:47 — NativeDetails's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AppShellRegistry (LCOM4 4) flow-server/src/main/java/com/vaadin/flow/server/AppShellRegistry.java:70 — AppShellRegistry's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ViteWebsocketConnection (LCOM4 4) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/viteproxy/ViteWebsocketConnection.java:43 — ViteWebsocketConnection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: VaadinSecurityConfigurer (LCOM4 4) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java:148 — VaadinSecurityConfigurer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ReflectionsClassFinder (LCOM4 4) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:60 — ReflectionsClassFinder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: RefreshCurrentRouteView (LCOM4 4) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RefreshCurrentRouteView.java:34 — RefreshCurrentRouteView'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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×12
  • Edited copy of a member (15 corresponding lines) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1554 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1554-1572 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1582-1596 — 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) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/PublicStyleSheetBundler.java:142 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/PublicStyleSheetBundler.java:142-156 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:571-589 — 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) flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:180 — flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:180-194 | flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:279-297 — 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) vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringInstantiator.java:102 — vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringInstantiator.java:102-116 | vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringInstantiator.java:119-133 — 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) flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractListDataView.java:153 — flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractListDataView.java:153-170 | flow-data/src/main/java/com/vaadin/flow/data/provider/InMemoryDataProvider.java:235-249 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/PinnedNpmVersions.java:175 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/PinnedNpmVersions.java:175-189 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/PinnedNpmVersions.java:254-270 — 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) flow-server/src/main/java/com/vaadin/flow/component/ComponentUtil.java:833 — flow-server/src/main/java/com/vaadin/flow/component/ComponentUtil.java:833-847 | flow-server/src/main/java/com/vaadin/flow/component/ComponentUtil.java:1025-1039 — 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) flow-server/src/main/java/com/vaadin/flow/component/webcomponent/WebComponentUI.java:345 — flow-server/src/main/java/com/vaadin/flow/component/webcomponent/WebComponentUI.java:345-363 | flow-server/src/main/java/com/vaadin/flow/server/SessionRouteRegistry.java:72-86 — 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) flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:132 — flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:132-146 | flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:212-227 — 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) flow-server/src/main/java/com/vaadin/flow/server/VaadinSession.java:339 — flow-server/src/main/java/com/vaadin/flow/server/VaadinSession.java:339-353 | flow-server/src/main/java/com/vaadin/flow/server/communication/JSR356WebsocketInitializer.java:284-302 — 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) flow-server/src/main/java/com/vaadin/flow/router/internal/PathUtil.java:138 — flow-server/src/main/java/com/vaadin/flow/router/internal/PathUtil.java:138-152 | flow-test-generic/src/main/java/com/vaadin/flow/testutil/ClassFinder.java:68-83 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:161 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:161-177 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:125-139 — 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 (16 corresponding lines) · ×12
  • Edited copy of a member (16 corresponding lines) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:206 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:206-221 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:168-183 — 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) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:341 — flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:341-363 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:366-381 — 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) flow-data/src/main/java/com/vaadin/flow/data/binder/BeanValidationBinder.java:568 — flow-data/src/main/java/com/vaadin/flow/data/binder/BeanValidationBinder.java:568-583 | flow-data/src/main/java/com/vaadin/flow/data/validator/BeanValidator.java:170-185 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/ChunkInfo.java:91 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/ChunkInfo.java:91-106 | flow-server/src/main/java/com/vaadin/flow/component/internal/ComponentTracker.java:111-126 — 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) flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:343 — flow-server/src/main/java/com/vaadin/flow/internal/JacksonUtils.java:343-360 | flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/AsynchronousSignalTree.java:131-146 — 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:736 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:736-751 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:827-842 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:76 — vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:76-92 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusInstantiator.java:80-95 — 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) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:269 — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:269-284 | vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:299-314 — 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) flow-server/src/main/java/com/vaadin/flow/component/Html.java:287 — flow-server/src/main/java/com/vaadin/flow/component/Html.java:287-302 | flow-server/src/main/java/com/vaadin/flow/component/Html.java:329-345 — 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) flow-server/src/main/java/com/vaadin/flow/dom/Element.java:356 — flow-server/src/main/java/com/vaadin/flow/dom/Element.java:356-371 | flow-server/src/main/java/com/vaadin/flow/dom/Element.java:423-439 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:55 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:55-70 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java:53-68 — 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) flow-tests/test-embedding/test-embedding-theme-variant/src/main/java/com/vaadin/flow/webcomponent/VariantTheme.java:48 — flow-tests/test-embedding/test-embedding-theme-variant/src/main/java/com/vaadin/flow/webcomponent/VariantTheme.java:48-63 | flow-tests/test-lumo/src/main/java/com/vaadin/flow/theme/lumo/Lumo.java:57-75 — 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 · Duplicated block (5 lines × 2) · ×12
  • Duplicated block (5 lines × 2) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:160 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:160-164 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java:158-162 — before extracting anything, compare `flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java` and `flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/FrontendConverter.java:126 — flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/FrontendConverter.java:126-130 | flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:235-239 — 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 (5 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/clipboard/ClipboardContent.java:88 — flow-server/src/main/java/com/vaadin/flow/component/clipboard/ClipboardContent.java:88-92 | flow-server/src/main/java/com/vaadin/flow/component/webshare/ShareContent.java:119-123 — 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 `flow-server/src/main/java/com/vaadin/flow/component/clipboard/ClipboardContent.java:88` 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. 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 (5 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractFileUploadHandler.java:146 — flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractFileUploadHandler.java:146-151 | flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractUploadHandler.java:221-225 — 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 (5 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/streams/DownloadEvent.java:298 — flow-server/src/main/java/com/vaadin/flow/server/streams/DownloadEvent.java:298-302 | flow-server/src/main/java/com/vaadin/flow/server/streams/TransferContext.java:105-109 — 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 (5 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:283 — vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:283-287 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:188-192 — 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 (5 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:87 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:87-91 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:73-77 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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.
  • Duplicated block (5 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:81 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:81-85 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:63-67 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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. 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, `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:92` calls `isPassivatingScope` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:69` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:602 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:602-606 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:404-408 — 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 `flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:602` 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 (5 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:75 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:75-79 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java:67-71 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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.
  • Duplicated block (5 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/push/WebsocketPushView.java:37 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/push/WebsocketPushView.java:37-41 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/push/WebsocketXhrPushView.java:37-41 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/push/WebsocketPushView.java` and `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/push/WebsocketXhrPushView.java` as WHOLE FILES: 89% 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 1 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:69 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:69-73 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:68-72 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:69` 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×11
  • Repeated repair: vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java:680 — vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java changed 13 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is VaadinQuarkusNativeProcessor.detectErrorParameterTypes at line 680), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: register snippet type proxies for native images (#27017)”; “fix(quarkus): stop reading values from WebSocket build items (#26213)”; “fix: load service providers and i18n locales in native images (#26234)”; “fix(quarkus): initialize Vaadin servlets at runtime in native image (#26164)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.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.
  • Repeated repair: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1965 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is Compile.hintFor at line 1965), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(devloop): build sources changed while the daemon was down before a launch (#26987)”; “fix(devloop): seed the change baseline from a launch-time snapshot (#26347)”; “fix(devloop): cap future-dated file times in the change baseline (#26228)”; “fix(devloop): keep resource edits made since app start when re-seeding (#25958)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.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.
  • Repeated repair: flow-server/src/main/java/com/vaadin/flow/component/internal/PendingJavaScriptInvocation.java flow-server/src/main/java/com/vaadin/flow/component/internal/PendingJavaScriptInvocation.java:299 — flow-server/src/main/java/com/vaadin/flow/component/internal/PendingJavaScriptInvocation.java changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is PendingJavaScriptInvocation.acceptsElementalJson at line 299), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: run all JavaScript result handlers when one throws (#26939)”; “fix: name incompatible executeJs result handler in error (#26750)”; “fix: do not count JavaScript invocations in a closed UI (#25474)”; “fix: stop counting JavaScript invocations that are discarded (#25374)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/component/internal/PendingJavaScriptInvocation.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.
  • Repeated repair: flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java:296 — flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is AbstractNavigationStateRenderer.populateChain at line 296), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: resolve layout chain from matched route in NavigationContext (#26752)”; “fix: keep navigation trigger when reusing preserved chain (#26594)”; “fix: track visual modality so dialogs are refreshed on hotswap (#25417)”; “fix: keep UI locale when view is preserved on refresh (#25953)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.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.
  • Repeated repair: vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinBeanFactoryInitializationAotProcessor.java vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinBeanFactoryInitializationAotProcessor.java:280 — vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinBeanFactoryInitializationAotProcessor.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is VaadinBeanFactoryInitializationAotProcessor.findAndRegisterRoutes at line 280), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: register snippet type proxies for native images (#27017)”; “fix(vaadin-spring): add AOT hints for types in allowed packages (#26030)”; “fix: register @EventData types for reflection in native images (#26040)”; “fix(spring): register JavaScript definition proxies for native image (#25889)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinBeanFactoryInitializationAotProcessor.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.
  • Repeated repair: flow-server/src/main/java/com/vaadin/flow/internal/StateTree.java flow-server/src/main/java/com/vaadin/flow/internal/StateTree.java:397 — flow-server/src/main/java/com/vaadin/flow/internal/StateTree.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is StateTree.runExecutionsBeforeClientResponse at line 397), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: postpone executions registered while node is being detached (#26838)”; “fix: postpone executions for node detached earlier in same round (#26705)”; “fix: stop counting JavaScript invocations that are discarded (#25374)”; “fix: discard pending JavaScript invocations when their owner is detached or the tree resynchronizes (#25267)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/java/com/vaadin/flow/internal/StateTree.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.
  • Repeated repair: flow-client/src/main/frontend/Flow.ts flow-client/src/main/frontend/Flow.ts:105 — flow-client/src/main/frontend/Flow.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is Flow.constructor at line 105), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: load browser helpers in embedded web components (#26043)”; “fix(flow-client): log the init failure hidden by the offline stub (#25731)”; “fix: pre-bundle the client engine in dev mode (#25470)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-client/src/main/frontend/Flow.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: flow-client/src/main/frontend/internal/client/communication/ReconnectStateMachine.ts flow-client/src/main/frontend/internal/client/communication/ReconnectStateMachine.ts:101 — flow-client/src/main/frontend/internal/client/communication/ReconnectStateMachine.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ReconnectStateMachine.handleRecoverableError at line 101), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(flow-client): keep loading indication after heartbeat reconnect (#26452)”; “fix(flow-client): show connected after push or XHR reconnect (#26308)”; “fix(flow-client): restore the client diagnostics lost in the TypeScript port (#25450)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-client/src/main/frontend/internal/client/communication/ReconnectStateMachine.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:588 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is BuildFrontendUtil.runFrontendBuildTool at line 588), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: use Flow's Node.js and npm for frontend SBOM (#26778)”; “fix: remove chunks of earlier builds before production Vite build (#26864)”; “fix(plugins): drop development entries from production token file (#25871)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.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.
  • Repeated repair: flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts:270 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is sw.self.addEventListener("message") at line 270), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep PWA app shell and its files consistent after a rebuild (#24807)”; “fix(flow-server): add support for AppShell stylesheets in service worker precache (#25047)”; “fix: serve the PWA offline stub as same-origin frameable (#25504)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/DevCliInstaller.java flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/DevCliInstaller.java:232 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/DevCliInstaller.java changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is DevCliInstaller.provisionHotswapAgent at line 232), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: skip class scanning in install-dev-cli goal (#26359)”; “fix(devloop): make the dev-loop skill load before the first edit (#25524)”; “fix: provision devloop HotswapAgent from flow:install-dev-cli (#25444)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 15:51:29 +00:00' --until='2026-11-17 15:51:29 +00:00' --full-history --no-merges -- flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/DevCliInstaller.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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×11
  • Edited copy of a member (11 corresponding lines) flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/ModelEncoder.java:48 — flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/ModelEncoder.java:48-58 | flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/ModelEncoder.java:66-76 — 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) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:429 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:429-440 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:452-462 — 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) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:270 — flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:270-281 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:293-303 — 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) flow-server/src/main/java/com/vaadin/flow/component/ComponentUtil.java:1082 — flow-server/src/main/java/com/vaadin/flow/component/ComponentUtil.java:1082-1095 | flow-server/src/main/java/com/vaadin/flow/dom/Element.java:2451-2461 — 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) flow-server/src/main/java/com/vaadin/flow/internal/CaseUtil.java:50 — flow-server/src/main/java/com/vaadin/flow/internal/CaseUtil.java:50-60 | flow-server/src/main/java/com/vaadin/flow/shared/util/SharedUtil.java:270-280 — 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) flow-server/src/main/java/com/vaadin/flow/server/auth/AccessCheckResult.java:87 — flow-server/src/main/java/com/vaadin/flow/server/auth/AccessCheckResult.java:87-97 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/DebugWindowConnection.java:174-185 — 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) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:446 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:446-458 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:473-483 — 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) flow-server/src/main/java/com/vaadin/flow/component/fullscreen/FullscreenSupport.java:61 — flow-server/src/main/java/com/vaadin/flow/component/fullscreen/FullscreenSupport.java:61-71 | flow-server/src/main/java/com/vaadin/flow/component/page/Page.java:786-796 — 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) flow-server/src/main/java/com/vaadin/flow/router/LocationChangeEvent.java:65 — flow-server/src/main/java/com/vaadin/flow/router/LocationChangeEvent.java:65-76 | flow-server/src/main/java/com/vaadin/flow/router/NavigationEvent.java:54-64 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:306 — vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:306-317 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:198-208 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/PushWithRequireJSView.java:28 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/PushWithRequireJSView.java:28-38 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushView.java:29-39 — 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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×11
  • Edited copy of a member (9 corresponding lines) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:484 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:484-492 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedValueSignal.java:236-244 — 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) flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:196 — flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:196-204 | flow-server/src/main/java/com/vaadin/flow/signals/local/ListSignal.java:300-308 — 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) flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:444 — flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:444-452 | flow-data/src/main/java/com/vaadin/flow/data/binder/BeanPropertySet.java:474-484 — 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) flow-data/src/main/java/com/vaadin/flow/data/converter/DefaultConverterFactory.java:143 — flow-data/src/main/java/com/vaadin/flow/data/converter/DefaultConverterFactory.java:143-151 | flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:235-243 — 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) vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:171 — vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:171-179 | vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:121-129 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskCopyLocalFrontendFiles.java:130 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskCopyLocalFrontendFiles.java:130-138 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/utils/FlowFileUtils.java:47-55 — 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) flow-server/src/main/java/com/vaadin/flow/internal/CssBundler.java:567 — flow-server/src/main/java/com/vaadin/flow/internal/CssBundler.java:567-575 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:591-600 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/RootView.java:40 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/RootView.java:40-48 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/RootView.java:38-46 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:124 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:124-132 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:124-132 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerReadFromClipboardView.java:94 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerReadFromClipboardView.java:94-102 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerWriteToClipboardView.java:266-274 — 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) flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/partial/MainLayout.java:33 — flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/partial/MainLayout.java:33-41 | flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/partial/RootLayout.java:33-41 — 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.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×11
  • Edited copy of a member (6 corresponding lines) flow-server/src/main/java/com/vaadin/flow/internal/menu/MenuRegistry.java:463 — flow-server/src/main/java/com/vaadin/flow/internal/menu/MenuRegistry.java:463-468 | flow-server/src/main/java/com/vaadin/flow/internal/menu/MenuRegistry.java:794-799 — 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) flow-server/src/main/java/com/vaadin/flow/router/RouteData.java:138 — flow-server/src/main/java/com/vaadin/flow/router/RouteData.java:138-145 | flow-server/src/main/java/com/vaadin/flow/router/RouteAliasData.java:90-95 — 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) flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java:63 — flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java:63-68 | flow-server/src/main/java/com/vaadin/flow/server/streams/FileDownloadHandler.java:128-133 — 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) flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1602 — flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1602-1607 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:502-507 — 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) flow-server/src/main/java/com/vaadin/flow/di/Lookup.java:177 — flow-server/src/main/java/com/vaadin/flow/di/Lookup.java:177-182 | vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringLookupInitializer.java:144-149 — 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) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/PublicResourcesLiveUpdater.java:134 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/PublicResourcesLiveUpdater.java:134-139 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/ThemeLiveUpdater.java:136-141 — 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) flow-server/src/main/java/com/vaadin/flow/component/AbstractCompositeField.java:59 — flow-server/src/main/java/com/vaadin/flow/component/AbstractCompositeField.java:59-65 | flow-server/src/main/java/com/vaadin/flow/component/AbstractField.java:168-173 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:1116 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:1116-1121 | flow-server/src/main/java/com/vaadin/flow/server/communication/StreamRequestHandler.java:297-302 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/DetailApartView.java:46 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/DetailApartView.java:46-51 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/DetailApartView.java:44-49 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/DetailAssignedView.java:47 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/DetailAssignedView.java:47-52 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/DetailAssignedView.java:45-50 — 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) flow-tests/test-live-reload-multimodule/ui/src/main/java/com/vaadin/flow/uitest/multimodule/ui/ProjectFolderInfo.java:28 — flow-tests/test-live-reload-multimodule/ui/src/main/java/com/vaadin/flow/uitest/multimodule/ui/ProjectFolderInfo.java:28-33 | flow-tests/test-live-reload-multimodule/ui/src/main/java/com/vaadin/flow/uitest/multimodule/ui/ProjectHotdeployInfo.java:29-35 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×11
  • Duplicated block (6 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:163 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:163-168 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:172-179 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:163` 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 (6 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:209 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:209-214 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:171-176 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:209` 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 (6 lines × 2) flow-data/src/main/java/com/vaadin/flow/data/converter/BigDecimalToLongConverter.java:31 — flow-data/src/main/java/com/vaadin/flow/data/converter/BigDecimalToLongConverter.java:31-36 | flow-data/src/main/java/com/vaadin/flow/data/converter/IntegerToLongConverter.java:29-34 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `BigDecimal` in one and `Integer` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/LitTemplateDataAnalyzer.java:94 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/LitTemplateDataAnalyzer.java:94-99 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/TemplateDataAnalyzer.java:271-276 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `clazz` to `Class<? extends LitTemplate>` in one and `Class<? extends PolymerTemplate<?>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/ShareAction.java:121 — flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/ShareAction.java:121-126 | flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/WriteToClipboardAction.java:227-232 — 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 `flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/ShareAction.java:121` 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 (6 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/instantiatorcustomize/InstantiatorAlternative.java:44 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/instantiatorcustomize/InstantiatorAlternative.java:44-49 | vaadin-cdi/src/main/java/com/vaadin/cdi/CdiInstantiator.java:71-76 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:92 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/AbstractContextualStorageManager.java:92-97 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContextualStorageManager.java:80-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/GeolocationView.java:114 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/GeolocationView.java:114-119 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/GeolocationView.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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/GeolocationView.java:114` 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 (6 lines × 2) flow-tests/test-legacy-frontend/src/main/java/com/vaadin/flow/uitest/ui/theme/UtilityClassNameView.java:25 — flow-tests/test-legacy-frontend/src/main/java/com/vaadin/flow/uitest/ui/theme/UtilityClassNameView.java:25-30 | flow-tests/test-theme-no-polymer/src/main/java/com/vaadin/flow/uitest/ui/theme/UtilityClassNameView.java:25-30 — before extracting anything, compare `flow-tests/test-legacy-frontend/src/main/java/com/vaadin/flow/uitest/ui/theme/UtilityClassNameView.java` and `flow-tests/test-theme-no-polymer/src/main/java/com/vaadin/flow/uitest/ui/theme/UtilityClassNameView.java` as WHOLE FILES: 100% 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 1 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.
  • Duplicated block (6 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:118 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:118-123 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java:114-119 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (6 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterForwardToView.java:40 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterForwardToView.java:40-45 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterRerouteToView.java:40-45 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×11
  • Members sharing a duplicated core (4 members, 50+ identical tokens) flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:36 — flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:36-79 | flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:36-79 | flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:35-70 | flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:39-91 — 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) flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:38 — flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:38-79 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:38-75 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:38-74 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/TranslationView.java:35-60 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:110 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:110-129 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:109-128 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:165-184 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:147-166 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:45 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:45-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:45-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:45-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:45-53 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:34 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:34-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:34-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:34-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:34-47 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:50 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:50-64 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:49-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:49-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:49-63 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:31 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:31-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:31-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:31-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:31-63 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:46 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:46-64 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:43-60 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:43-60 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:57-75 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66-79 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:62-87 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:62-87 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:77-103 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:81 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:81-114 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:89-122 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:89-122 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:105-182 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:151 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:151-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:151-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:151-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:219-233 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×11
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:643 — `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.
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:784 — `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.
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:980 — `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.
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:998 — `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.
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1112 — `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.
  • Swallowed exception (caught, then discarded) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1189 — `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) vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:622 — `catch (e)` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.java:350 — `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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ClassUtils.java:370 — `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) flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:4113 — `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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×10
  • Animation without a prefers-reduced-motion guard vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:38 — `.message::before` moves (`animation: spinner 0.5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:193 — `.css-in-js .dev-tools.error` moves (`animation: bounce 0.5s`) 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 vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:468 — `.css-in-js .notification-tray .message` moves (`animation: slideIn var(--dev-tools-transition-duration)`) 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 vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:475 — `.css-in-js .notification-tray .message.animate-out` moves (`animation: slideOut forwards var(--dev-tools-transition-duration)`) 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 flow-client/src/main/frontend/ConnectionIndicator.ts:424 — `.css-in-js .v-loading-indicator` moves (`animation: v-progress-start 1000ms 200ms both`) 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 flow-client/src/main/frontend/ConnectionIndicator.ts:431 — `.css-in-js .v-loading-indicator[style*='none']` moves (`transition: opacity 500ms 300ms, width 300ms`) 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 flow-client/src/main/frontend/ConnectionIndicator.ts:437 — `.css-in-js .v-loading-indicator.second` moves (`animation: v-progress-delay 3.8s forwards`) 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 flow-client/src/main/frontend/ConnectionIndicator.ts:441 — `.css-in-js .v-loading-indicator.third` moves (`animation: v-progress-wait 5s forwards, v-progress-wait-pulse 1s 4s infinite backwards`) 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 flow-client/src/main/frontend/ConnectionIndicator.ts:486 — `.css-in-js vaadin-connection-indicator[reconnecting] .v-status-message` moves (`animation: show-reconnecting-status 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 flow-client/src/main/frontend/ConnectionIndicator.ts:517 — `.css-in-js vaadin-connection-indicator[reconnecting] .v-status-message span::before` moves (`animation: v-spin 0.4s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×10
  • Edited copy of a member (14 corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/Html.java:538 — flow-server/src/main/java/com/vaadin/flow/component/Html.java:538-551 | flow-server/src/main/java/com/vaadin/flow/component/internal/AbstractFieldSupport.java:218-232 — 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) flow-server/src/main/java/com/vaadin/flow/dom/Element.java:1460 — flow-server/src/main/java/com/vaadin/flow/dom/Element.java:1460-1474 | flow-server/src/main/java/com/vaadin/flow/dom/Element.java:2382-2395 — 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) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1227 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1227-1240 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1256-1272 — 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) flow-server/src/main/java/com/vaadin/flow/component/page/History.java:233 — flow-server/src/main/java/com/vaadin/flow/component/page/History.java:233-246 | flow-server/src/main/java/com/vaadin/flow/component/page/History.java:323-336 — 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) flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:101 — flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:101-114 | flow-data/src/main/java/com/vaadin/flow/data/selection/MultiSelect.java:128-141 — 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) flow-data/src/main/java/com/vaadin/flow/data/binder/SimpleResult.java:114 — flow-data/src/main/java/com/vaadin/flow/data/binder/SimpleResult.java:114-127 | flow-data/src/main/java/com/vaadin/flow/data/binder/ValidationResult.java:71-84 — 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) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:82 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:82-95 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:97-110 — 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) flow-server/src/main/java/com/vaadin/flow/router/RouteParameters.java:132 — flow-server/src/main/java/com/vaadin/flow/router/RouteParameters.java:132-145 | flow-server/src/main/java/com/vaadin/flow/router/RouteParameters.java:157-170 — 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) flow-server/src/main/java/com/vaadin/flow/component/Component.java:1050 — flow-server/src/main/java/com/vaadin/flow/component/Component.java:1050-1063 | flow-server/src/main/java/com/vaadin/flow/component/Component.java:1067-1083 — 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) flow-server/src/main/java/com/vaadin/flow/dom/DomListenerRegistration.java:712 — flow-server/src/main/java/com/vaadin/flow/dom/DomListenerRegistration.java:712-725 | flow-server/src/main/java/com/vaadin/flow/dom/DomListenerRegistration.java:845-861 — 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 · Duplicated block (12 lines × 2) · ×10
  • Duplicated block (12 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:223 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:223-234 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:322-333 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:223` 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 first that the copies are not typed on the same thing: the declarations holding them bind `wildcardPathExclusions` to `String...` in one and `Collection<String>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:321` calls `filter`, `includeFile` and `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:222` 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) flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:588 — flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:588-599 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:649-660 — 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 `flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:588` 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 (12 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:146 — flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:146-157 | flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:217-228 — 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 `flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:146` 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 (12 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:77 — flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:77-88 | flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:122-133 — 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 `flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:77` 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 (12 lines × 2) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:84 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:84-95 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.java:99-110 — 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 `vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/ProKey.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. 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) flow-server/src/main/java/com/vaadin/flow/router/internal/ConfigureRoutes.java:67 — flow-server/src/main/java/com/vaadin/flow/router/internal/ConfigureRoutes.java:67-78 | flow-server/src/main/java/com/vaadin/flow/router/internal/ConfiguredRoutes.java:77-88 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `original` to `ConfiguredRoutes` in one and `ConfigureRoutes` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:462 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:462-473 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:610-621 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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.
  • Duplicated block (12 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:183 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:183-194 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:145-156 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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.
  • Duplicated block (12 lines × 2) flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:47 — flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:47-58 | flow-tests/test-frontend/vite-production/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:46-57 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ParentNoOwnerView.java:36 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ParentNoOwnerView.java:36-47 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/ParentNoOwnerView.java:34-45 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ParentNoOwnerView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/ParentNoOwnerView.java` as WHOLE FILES: 86% 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 1 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.
D3 · God Classes · MethodTooLong · ×9
  • MethodTooLong: VaadinDevTools.styles vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:91 — MethodTooLong — styles runs 345 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 245 over it, 3.45× 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: PreTrial.render vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts:38 — MethodTooLong — render runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: TaskRunNpmInstall.runNpmInstall flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:271 — MethodTooLong — runNpmInstall runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: DevModeInitializer.initDevModeHandler vaadin-dev-server/src/main/java/com/vaadin/base/devserver/startup/DevModeInitializer.java:191 — MethodTooLong — initDevModeHandler 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: NodeTasks.<init> flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111 — MethodTooLong — <init> runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: AbstractUpdateImports.process flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:376 — MethodTooLong — process 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: TaskGenerateTsDefinitions.updateIfContentMissing flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTsDefinitions.java:125 — MethodTooLong — updateIfContentMissing 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: ConnectionIndicator.#getDefaultStyle flow-client/src/main/frontend/ConnectionIndicator.ts:366 — MethodTooLong — #getDefaultStyle runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: StaticFileServer.serveStaticResource flow-server/src/main/java/com/vaadin/flow/server/StaticFileServer.java:252 — MethodTooLong — serveStaticResource runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×9
  • Edited copy of a member (12 corresponding lines) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:382 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:382-394 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:305-316 — 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) flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1469 — flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1469-1480 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:582-594 — 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) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Reactor.java:620 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Reactor.java:620-631 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/MavenUtils.java:157-168 — 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) flow-server/src/main/java/com/vaadin/flow/router/internal/PathUtil.java:47 — flow-server/src/main/java/com/vaadin/flow/router/internal/PathUtil.java:47-58 | flow-server/src/main/java/com/vaadin/flow/router/internal/PathUtil.java:86-98 — 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) flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:327 — flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:327-338 | flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.java:353-364 — 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) flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:257 — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:257-268 | flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:296-312 — 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) flow-html-components/src/main/java/com/vaadin/flow/component/html/AnchorTargetValue.java:65 — flow-html-components/src/main/java/com/vaadin/flow/component/html/AnchorTargetValue.java:65-76 | flow-server/src/main/java/com/vaadin/flow/component/Key.java:2956-2967 — 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) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/AbstractPropertyMap.java:62 — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/AbstractPropertyMap.java:62-73 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementAttributeMap.java:292-304 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/LayoutEventView.java:42 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/LayoutEventView.java:42-54 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/LayoutEventView2.java:42-53 — 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 · Duplicated block (17 lines × 2) · ×9
  • Duplicated block (17 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:283 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:283-299 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:395-411 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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. 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) flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.java:192 — flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.java:192-208 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusResourceProvider.java:63-79 — 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 (17 lines × 2) flow-server/src/main/java/com/vaadin/flow/function/DeploymentConfiguration.java:243 — flow-server/src/main/java/com/vaadin/flow/function/DeploymentConfiguration.java:243-259 | flow-server/src/main/java/com/vaadin/flow/server/AbstractPropertyConfiguration.java:60-76 — 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 (17 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:98 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:98-114 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:71-87 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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. 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) flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:31 — flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:31-47 | flow-tests/test-redeployment/src/main/java/com/vaadin/flow/uitest/ui/DevModeClassCacheView.java:34-50 — 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 `flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:31` 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 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:41 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:41-57 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java:40-56 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:41` 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 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:84 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:84-100 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java:80-96 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (17 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ChildNoOwnerView.java:37 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ChildNoOwnerView.java:37-53 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/ChildNoOwnerView.java:35-51 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/ChildNoOwnerView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/ChildNoOwnerView.java` as WHOLE FILES: 85% 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 1 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 (17 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/ServiceView.java:36 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/ServiceView.java:36-52 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/ServiceView.java:39-55 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/ServiceView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/ServiceView.java` as WHOLE FILES: 82% 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 1 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×9
  • Duplicated block (14 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:738 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:738-751 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:829-842 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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. 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) flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:143 — flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:143-156 | flow-server/src/main/java/com/vaadin/flow/component/Focusable.java:195-208 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (14 lines × 2) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:394 — flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:394-407 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteSegment.java:427-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/streams/FileDownloadHandler.java:92 — flow-server/src/main/java/com/vaadin/flow/server/streams/FileDownloadHandler.java:92-105 | flow-server/src/main/java/com/vaadin/flow/server/streams/ServletResourceDownloadHandler.java:117-131 — 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 `flow-server/src/main/java/com/vaadin/flow/server/streams/FileDownloadHandler.java:92` 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:397 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:397-410 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:319-332 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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. 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:79 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:79-92 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:90-103 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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.
  • Duplicated block (14 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:57 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:57-70 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java:55-68 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:57` 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 (14 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:56 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:56-69 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIContextRootView.java:59-72 — 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. Note first that the copies are not typed on the same thing: `SetTextEvent` names `com.vaadin.cdi.itest.uicontext.UIScopedLabel.SetTextEvent` in one and `com.vaadin.flow.quarkus.it.uicontext.UIScopedLabel.SetTextEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIContextRootView.java:74` calls `Div`, `setId`, `setText` and `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:71` 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 (14 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SimpleLitTemplateNoShadowRootView.java:40 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SimpleLitTemplateNoShadowRootView.java:40-53 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SimpleLitTemplateShadowRootView.java:40-53 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SimpleLitTemplateNoShadowRootView.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SimpleLitTemplateShadowRootView.java` as WHOLE FILES: 88% 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 1 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. 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×9
  • Duplicated block (11 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:235 — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:235-245 | flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.java:220-230 — 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 (11 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:567 — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:567-577 | flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.java:259-269 — 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) flow-server/src/main/java/com/vaadin/flow/server/startup/RouteRegistryInitializer.java:202 — flow-server/src/main/java/com/vaadin/flow/server/startup/RouteRegistryInitializer.java:202-212 | vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:447-457 — 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 `flow-server/src/main/java/com/vaadin/flow/server/startup/RouteRegistryInitializer.java:202` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) flow-tests/test-frontend/vite-pwa-disabled-offline/src/main/java/com/vaadin/viteapp/ApplicationServiceInitListener.java:25 — flow-tests/test-frontend/vite-pwa-disabled-offline/src/main/java/com/vaadin/viteapp/ApplicationServiceInitListener.java:25-35 | flow-tests/test-pwa-disabled-offline/src/main/java/com/vaadin/flow/pwatest/ApplicationServiceInitListener.java:25-35 — before extracting anything, compare `flow-tests/test-frontend/vite-pwa-disabled-offline/src/main/java/com/vaadin/viteapp/ApplicationServiceInitListener.java` and `flow-tests/test-pwa-disabled-offline/src/main/java/com/vaadin/flow/pwatest/ApplicationServiceInitListener.java` as WHOLE FILES: 96% 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 1 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 (11 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:84 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:84-94 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java:76-86 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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. 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PopStateHandlerView.java:45 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PopStateHandlerView.java:45-55 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PopStateHandlerView.java:45-55 — 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 (11 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:63 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:63-73 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java:64-74 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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. 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/CounterFilter.java:41 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/CounterFilter.java:41-51 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CounterFilter.java:41-51 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/CounterFilter.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CounterFilter.java` as WHOLE FILES: 95% 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 1 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 (11 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:66 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:66-76 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java:62-72 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×8
  • Edited copy of a member (18 corresponding lines) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:716 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:716-733 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:844-862 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/BeanLookup.java:88 — vaadin-cdi/src/main/java/com/vaadin/cdi/BeanLookup.java:88-105 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/BeanLookup.java:82-100 — 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) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:141 — flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:141-158 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:93-110 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:95 — vaadin-cdi/src/main/java/com/vaadin/cdi/AbstractCdiInstantiator.java:95-112 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusInstantiator.java:98-116 — 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) flow-server/src/main/java/com/vaadin/flow/function/DeploymentConfiguration.java:242 — flow-server/src/main/java/com/vaadin/flow/function/DeploymentConfiguration.java:242-259 | flow-server/src/main/java/com/vaadin/flow/server/AbstractPropertyConfiguration.java:54-76 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:578 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:578-597 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:492-509 — 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) flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadView.java:32 — flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadView.java:32-50 | flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ThemeLiveReloadWithShadowRootView.java:34-51 — 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) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:78 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:78-95 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:77-94 — 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.
AX2 · Stateful singletons · Stateful singleton · ×7
  • Stateful singleton: NavigationAccessControl flow-server/src/main/java/com/vaadin/flow/server/auth/NavigationAccessControl.java:85 — `NavigationAccessControl` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (loginUrl; e.g. `loginUrl` in `setLoginView` at line 209).
  • Stateful singleton: AuthenticationContext vaadin-spring/src/main/java/com/vaadin/flow/spring/security/AuthenticationContext.java:71 — `AuthenticationContext` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (logoutSuccessHandler, logoutHandler; e.g. `logoutSuccessHandler` in `setLogoutHandlers` at line 473).
  • Stateful singleton: NavigationAccessControlConfigurer vaadin-spring/src/main/java/com/vaadin/flow/spring/security/NavigationAccessControlConfigurer.java:78 — `NavigationAccessControlConfigurer` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (disableAccessControl, enableViewAccessChecker, accessCheckersFilter, decisionResolver, loginView, loginViewPath; e.g. `disableAccessControl` in `disabled` at line 206).
  • Stateful singleton: RequestUtil vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:64 — `RequestUtil` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (webIconsRequestMatcher, pwaResourcesRequestMatcher; e.g. `webIconsRequestMatcher` in `isCustomWebIcon` at line 269).
  • Stateful singleton: VaadinDefaultRequestCache vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinDefaultRequestCache.java:68 — `VaadinDefaultRequestCache` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (ignoreRequestMatcher; e.g. `ignoreRequestMatcher` in `ignoreRequests` at line 196).
  • Stateful singleton: VaadinRolePrefixHolder vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinRolePrefixHolder.java:45 — `VaadinRolePrefixHolder` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (rolePrefix, rolePrefixSet; e.g. `rolePrefix` in `resetRolePrefix` at line 131).
  • Stateful singleton: VaadinServletContextInitializer vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:111 — `VaadinServletContextInitializer` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (metadataReaderFactory; e.g. `metadataReaderFactory` in `getMetadataReaderFactory` at line 932).
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×7
  • Edited copy of a member (13 corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java:1036 — flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java:1036-1048 | flow-server/src/main/java/com/vaadin/flow/component/ShortcutRegistration.java:1050-1069 — 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) flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:799 — flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:799-811 | flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:1491-1503 — 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) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1408 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1408-1421 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MavenCompile.java:586-598 — 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) flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:122 — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:122-134 | flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:160-173 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractTaskClientGenerator.java:58 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractTaskClientGenerator.java:58-70 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateIndexTs.java:61-74 — 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) vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:429 — vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:429-442 | flow-server/src/main/java/com/vaadin/flow/server/startup/RouteRegistryInitializer.java:186-198 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerRequestFullscreenRootView.java:35 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerRequestFullscreenRootView.java:35-47 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerRequestFullscreenView.java:36-50 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×7
  • Duplicated block (19 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:133 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:133-151 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:98-116 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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 `vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:133` 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 (19 lines × 2) flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/LoadingIndicatorNavigationFastTargetView.java:34 — flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/LoadingIndicatorNavigationFastTargetView.java:34-52 | flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/LoadingIndicatorNavigationSlowTargetView.java:34-52 — before extracting anything, compare `flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/LoadingIndicatorNavigationFastTargetView.java` and `flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/LoadingIndicatorNavigationSlowTargetView.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 1 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. 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. 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 (19 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:76 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:76-94 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java:77-95 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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. 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 (19 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java:51 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java:51-69 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShortcutsWithValueChangeModeView.java:41-59 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShortcutsWithValueChangeModeView.java` as WHOLE FILES: 85% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShadowRootShortcutsWithValueChangeModeView.java:49` calls `appendChild`, `getElement` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ShortcutsWithValueChangeModeView.java:39` 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 (19 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MenuListView.java:47 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MenuListView.java:47-65 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MenuListView.java:49-67 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MenuListView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MenuListView.java` as WHOLE FILES: 100% 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 1 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 (19 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:31 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:31-49 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java:32-50 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:31` 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 (19 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SetInitialTextLitView.java:37 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/littemplate/SetInitialTextLitView.java:37-55 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/template/SetInitialTextView.java:38-56 — 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 (17 corresponding lines) · ×6
  • Edited copy of a member (17 corresponding lines) vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:165 — vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:165-181 | vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:184-206 — 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) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:218 — flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:218-236 | flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:239-255 — 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) flow-data/src/main/java/com/vaadin/flow/data/converter/AbstractStringToNumberConverter.java:105 — flow-data/src/main/java/com/vaadin/flow/data/converter/AbstractStringToNumberConverter.java:105-128 | flow-data/src/main/java/com/vaadin/flow/data/converter/StringToDateConverter.java:60-76 — 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) flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/AbstractTemplate.java:132 — flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/AbstractTemplate.java:132-148 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/AbstractTemplate.java:173-191 — 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) flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:145 — flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:145-161 | flow-server/src/main/java/com/vaadin/flow/component/HasStyle.java:216-232 — 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) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/CleanFrontendUtil.java:251 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/CleanFrontendUtil.java:251-267 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/CleanFrontendUtil.java:285-302 — 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 · Duplicated block (15 lines × 2) · ×6
  • Duplicated block (15 lines × 2) flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:156 — flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:156-170 | flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:181-195 — 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 `flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:156` 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) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:112 — flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:112-126 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:154-168 — 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 `flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:112` 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 (15 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:208 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:208-222 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:306-320 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:208` 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, `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:321` calls `filter`, `includeFile` and `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:223` 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 (15 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:254 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:254-268 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:266-280 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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.
  • Duplicated block (15 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:403 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:403-417 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:472-486 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. 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 × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/serviceloader/ServiceLoaderView.java:34 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/serviceloader/ServiceLoaderView.java:34-48 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ServiceLoaderView.java:34-48 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/serviceloader/ServiceLoaderView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ServiceLoaderView.java` as WHOLE FILES: 97% 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 1 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.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×5
  • FunctionTooLong: convert.convertFile flow-polymer2lit/convert.ts:94 — FunctionTooLong — convertFile runs 508 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 408 over it, 5.08× 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.
  • FunctionTooLong: Flow.Flow flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:349 — FunctionTooLong — Flow runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: theme-generator.writeThemeFiles flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:45 — FunctionTooLong — writeThemeFiles runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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.
  • FunctionTooLong: FlowBootstrap.init flow-client/src/main/frontend/FlowBootstrap.js:9 — FunctionTooLong — init runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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.
  • FunctionTooLong: rollup-plugin-vaadin-i18n.vaadinI18n flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:37 — FunctionTooLong — vaadinI18n runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: VaadinFlowPluginExtension.kt ↔ PluginAdapterBase.java flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/VaadinFlowPluginExtension.kt:1 — `flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/VaadinFlowPluginExtension.kt` and `flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/PluginAdapterBase.java` change together 84% of the time (21 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 21 shared commits counted here, the most recent 3 are `47f664d2` feat: add npm.excludePostinstallPackages option (#24421); `4b4b6be1` feat(FrontendTools): Add support for custom node folder (#23124); `2df0aa8d` feat: allow production build with watermark (#21866) — run `git show` on any of them.
  • Change coupling: BasicElementStateProvider.java ↔ NodeFeatureRegistry.java flow-server/src/main/java/com/vaadin/flow/dom/impl/BasicElementStateProvider.java:1 — `flow-server/src/main/java/com/vaadin/flow/dom/impl/BasicElementStateProvider.java` and `flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeFeatureRegistry.java` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 8 shared commits counted here, the most recent 3 are `efd361d7` chore: remove TextBindingFeature (#23748); `fae00b76` feat: add HasEnabled::bindEnabled (#23107); `704541b9` feat: add signal binding to element text (#22406) (#22543) — run `git show` on any of them.
  • Change coupling: BrowserLiveReload.java ↔ vaadin-dev-tools.ts flow-server/src/main/java/com/vaadin/flow/internal/BrowserLiveReload.java:1 — `flow-server/src/main/java/com/vaadin/flow/internal/BrowserLiveReload.java` and `vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `ee5139eb` fix: update stylesheet when a referenced resource changes (#22563); `eb2ecb90` feat: HMR for translation files (#20142); `dc126300` feat: refresh browser using dev-tools connection (#19650) — run `git show` on any of them.
  • Change coupling: PrepareFrontendInputProperties.kt ↔ BuildFrontendUtil.java flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/PrepareFrontendInputProperties.kt:1 — `flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/PrepareFrontendInputProperties.kt` and `flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 8 shared commits counted here, the most recent 3 are `47f664d2` feat: add npm.excludePostinstallPackages option (#24421); `536bb086` feat: Optimize StyleSheet css for production build (#22852); `b325eb2d` refactor: replace and deprecate webpackOutputDirectory method (#21648) — run `git show` on any of them.
  • Change coupling: SecurityConfig.java ↔ MainView.java flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1 — `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `f5c972af` test: Add test for spring impersonate (#20938); `e4739d32` fix: push event allows redirects for expired session (#17796); `921268af` feat: Automatically use Flow view access checker vaadin/spring#780 — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×5
  • Edited copy of a member (22 corresponding lines) flow-server/src/main/java/com/vaadin/flow/router/internal/ConfigureRoutes.java:66 — flow-server/src/main/java/com/vaadin/flow/router/internal/ConfigureRoutes.java:66-87 | flow-server/src/main/java/com/vaadin/flow/router/internal/ConfiguredRoutes.java:76-103 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:1041 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:1041-1062 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:1064-1085 — 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) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/LitTemplateInitializer.java:78 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/LitTemplateInitializer.java:78-99 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/TemplateInitializer.java:73-96 — 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) flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.java:187 — flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.java:187-208 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusResourceProvider.java:58-79 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:40 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/HistoryView.java:40-64 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/HistoryView.java:39-60 — 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 (23 corresponding lines) · ×5
  • Edited copy of a member (23 corresponding lines) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:104 — flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:104-126 | flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:144-168 — 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) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:258 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:258-280 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:360-392 — 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) flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/TemplateModelUtil.java:61 — flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/TemplateModelUtil.java:61-83 | flow-polymer-template/src/main/java/com/vaadin/flow/templatemodel/TemplateModelUtil.java:102-124 — 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) flow-server/src/main/java/com/vaadin/flow/di/DefaultInstantiator.java:153 — flow-server/src/main/java/com/vaadin/flow/di/DefaultInstantiator.java:153-178 | flow-server/src/main/java/com/vaadin/flow/di/DefaultInstantiator.java:181-203 — 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) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:787 — flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:787-809 | flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:913-939 — 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 (19 corresponding lines) · ×5
  • Edited copy of a member (19 corresponding lines) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:230 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:230-249 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNodeSignal.java:404-422 — 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) flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractBackEndDataProvider.java:39 — flow-data/src/main/java/com/vaadin/flow/data/provider/AbstractBackEndDataProvider.java:39-57 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/AbstractBackEndHierarchicalDataProvider.java:47-65 — 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) flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:195 — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:195-213 | flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:240-263 — 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) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:697 — flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:697-715 | flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:717-735 — 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) flow-server/src/main/java/com/vaadin/flow/router/AbstractRouteNotFoundError.java:153 — flow-server/src/main/java/com/vaadin/flow/router/AbstractRouteNotFoundError.java:153-171 | flow-server/src/main/java/com/vaadin/flow/router/AbstractRouteNotFoundError.java:173-191 — 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 (5 corresponding lines) · ×5
  • Edited copy of a member (5 corresponding lines) flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableColumnGroupElement.java:37 — flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableColumnGroupElement.java:37-44 | flow-html-components-testbench/src/main/java/com/vaadin/flow/component/html/testbench/TableSectionElement.java:37-41 — 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) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateIndexTs.java:88 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateIndexTs.java:88-94 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdateOldIndexTs.java:53-57 — 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) flow-server/src/main/java/com/vaadin/flow/server/startup/ServletDeployer.java:262 — flow-server/src/main/java/com/vaadin/flow/server/startup/ServletDeployer.java:262-266 | vaadin-cdi/src/main/java/com/vaadin/cdi/CdiServletDeployer.java:100-104 — 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) flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/PropertyInput.java:64 — flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/PropertyInput.java:64-68 | flow-server/src/main/java/com/vaadin/flow/component/trigger/internal/SetPropertyAction.java:117-121 — 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) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1430 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1430-1434 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:1448-1452 — 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.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×5
  • Edited copy of a member (4 corresponding lines) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:371 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:371-376 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNodeSignal.java:347-350 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:291 — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:291-294 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.java:225-228 — 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) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:539 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:539-542 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNodeSignal.java:437-440 — 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) flow-data/src/main/java/com/vaadin/flow/data/provider/ListDataProvider.java:128 — flow-data/src/main/java/com/vaadin/flow/data/provider/ListDataProvider.java:128-131 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/TreeDataProvider.java:86-91 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:55 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:55-58 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:55-58 — 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×5
  • Duplicated block (16 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:50 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:50-65 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java:42-57 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:50` 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.
  • Duplicated block (16 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:80 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:80-95 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:79-94 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:80` 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 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:37 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:37-52 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:37-52 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` as WHOLE FILES: 100% 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 (16 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:117 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:117-132 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:185-200 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 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. 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 (16 lines × 2) flow-tests/test-frontend/vite-embedded-no-theme/src/main/java/com/vaadin/viteapp/BasicComponent.java:28 — flow-tests/test-frontend/vite-embedded-no-theme/src/main/java/com/vaadin/viteapp/BasicComponent.java:28-43 | flow-tests/test-frontend/vite-embedded/src/main/java/com/vaadin/viteapp/BasicComponent.java:27-42 — before extracting anything, compare `flow-tests/test-frontend/vite-embedded-no-theme/src/main/java/com/vaadin/viteapp/BasicComponent.java` and `flow-tests/test-frontend/vite-embedded/src/main/java/com/vaadin/viteapp/BasicComponent.java` as WHOLE FILES: 91% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/test-frontend/vite-embedded-no-theme/src/main/java/com/vaadin/viteapp/BasicComponent.java:28` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×5
  • Swallowed exception (empty catch) flow-server/src/main/java/com/vaadin/flow/internal/FileIOUtils.java:418 — 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) flow-client/src/main/frontend/Geolocation.ts:133 — 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) flow-client/src/main/frontend/WakeLock.ts:62 — 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) flow-client/src/main/frontend/WakeLock.ts:122 — 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) flow-client/src/main/frontend/internal/client/flow/binding/PolymerModelBinding.ts:62 — 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.
D17 · Explicit Debt · FixmeComment · ×4
  • FixmeComment flow-server/src/main/java/com/vaadin/flow/component/UI.java:438 — // FIXME Send info to client — 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.
  • FixmeComment flow-polymer2lit/convert.ts:315 — // Fixme trailing , — 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.
  • FixmeComment flow-polymer2lit/convert.ts:723 — //FIXME Broken — 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.
  • FixmeComment flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:721 — // FIXME do not do cleanup of node_modules every time platform is — 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 (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:695 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:695-714 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:805-824 — 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.
  • Edited copy of a member (20 corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractRouteRegistryInitializer.java:198 — flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractRouteRegistryInitializer.java:198-222 | flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractRouteRegistryInitializer.java:226-245 — 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.
  • Edited copy of a member (20 corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:142 — flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:142-163 | flow-server/src/main/java/com/vaadin/flow/component/Focusable.java:194-213 — 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.
  • Edited copy of a member (20 corresponding lines) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:183 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:183-202 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/server/scanner/ReflectionsClassFinder.java:205-224 — 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 · Duplicated block (20 lines × 2) · ×4
  • Duplicated block (20 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunDevBundleBuild.java:145 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunDevBundleBuild.java:145-164 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:597-616 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunDevBundleBuild.java:145` 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 (20 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:368 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:368-387 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:421-440 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:368` 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 (20 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:543 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:543-562 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:712-731 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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.
  • Duplicated block (20 lines × 2) flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:38 — flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:38-57 | flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:38-57 — before extracting anything, compare `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java` and `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:59` calls `add` and `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:59` 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×4
  • Duplicated block (6 lines × 4) flow-data/src/main/java/com/vaadin/flow/data/converter/DoubleToBigDecimalConverter.java:33 — flow-data/src/main/java/com/vaadin/flow/data/converter/DoubleToBigDecimalConverter.java:33-39 | flow-data/src/main/java/com/vaadin/flow/data/converter/FloatToBigDecimalConverter.java:33-38 | flow-data/src/main/java/com/vaadin/flow/data/converter/IntegerToBigDecimalConverter.java:34-40 | flow-data/src/main/java/com/vaadin/flow/data/converter/LongToBigDecimalConverter.java:31-36 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-data/src/main/java/com/vaadin/flow/data/converter/DoubleToBigDecimalConverter.java:33` 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. 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 first that the copies are not typed on the same thing: the declarations holding them bind `value` to `Double` in one and `Float` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:135 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:135-140 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:135-140 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:135-140 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:203-208 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:135` 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. 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 (6 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:143 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:143-148 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:143-148 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:143-148 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:211-216 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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.
  • Duplicated block (6 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:96 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:96-101 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:91-96 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:89-94 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:92-97 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×4
  • Duplicated block (9 lines × 2 locations) flow-client/src/main/frontend/BrowserHelpers.ts:87 — flow-client/src/main/frontend/BrowserHelpers.ts:87 · flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:239 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (9 lines × 2 locations) flow-client/src/main/frontend/internal/client/ResourceLoader.ts:204 — flow-client/src/main/frontend/internal/client/ResourceLoader.ts:204 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:310 — 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 (9 lines × 2 locations) flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:254 — flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:254 · flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:279 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) REDACTED:369 — REDACTED:369 · REDACTED:489 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R7 · Dead Code · Dead file (~1 LoC) · ×4
  • Dead file (~1 LoC) flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/alpha-addon/resources/META-INF/resources/frontend/alpha.js — no import path from any entry point (119 application, 23 tooling, 157 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 (~1 LoC) flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/alpha-addon/resources/META-INF/resources/frontend/not-used.js — no import path from any entry point (119 application, 23 tooling, 157 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 (~1 LoC) flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/beta-addon/resources/META-INF/resources/frontend/beta.js — no import path from any entry point (119 application, 23 tooling, 157 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 (~1 LoC) flow-plugins/flow-maven-plugin/src/it/frontend-scanner-tuning-project/src/main/frontend/project-component.js — no import path from any entry point (119 application, 23 tooling, 157 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
R8 · Dependency Hygiene · Unused dependency '@typescript/native' · ×4
  • Unused dependency '@typescript/native' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json:9 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/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 '@typescript/native' flow-tests/test-frontend/vite-basics/package.json:34 — Declared in flow-tests/test-frontend/vite-basics/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 '@typescript/native' flow-tests/test-frontend/vite-context-path/package.json:26 — Declared in flow-tests/test-frontend/vite-context-path/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 '@typescript/native' flow-tests/test-frontend/vite-production/package.json:31 — Declared in flow-tests/test-frontend/vite-production/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.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark flow-server/src/main/resources/com/vaadin/flow/server/frontend/index.html:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="outlet">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark vaadin-dev-server/src/main/resources/com/vaadin/base/devserver/dev-mode-not-ready.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D2 · Cognitive Complexity · convert.convertFile · ×3
  • convert.convertFile::rewriteElement (cognitive 44) flow-polymer2lit/convert.ts:342 — convert.convertFile::rewriteElement has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (35 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 20). 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. This shape REPEATS in the file: 3 other methods here (convert.convertFile, convert.convertFile::modifyClass, convert.convertFile::nullSafe) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • convert.convertFile::modifyClass (cognitive 31) flow-polymer2lit/convert.ts:118 — convert.convertFile::modifyClass has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 8, ternaries 2 (6 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (convert.convertFile, convert.convertFile::rewriteElement, convert.convertFile::nullSafe) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • convert.convertFile::nullSafe (cognitive 28) flow-polymer2lit/convert.ts:770 — convert.convertFile::nullSafe has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (23 pts), loops 2 (5 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. This shape REPEATS in the file: 3 other methods here (convert.convertFile, convert.convertFile::modifyClass, convert.convertFile::rewriteElement) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×3
  • Edited copy of a member (28 corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:207 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:207-234 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java:305-333 — These two members are one piece of code written twice and then edited apart: 28 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 (28 corresponding lines) flow-data/src/main/java/com/vaadin/flow/data/provider/DataFetchObserver.java:104 — flow-data/src/main/java/com/vaadin/flow/data/provider/DataFetchObserver.java:104-134 | flow-data/src/main/java/com/vaadin/flow/data/provider/DataFetchObserver.java:159-186 — These two members are one piece of code written twice and then edited apart: 28 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 (28 corresponding lines) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:118 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:118-148 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/components/NativeRadioButtonGroup.java:40-67 — These two members are one piece of code written twice and then edited apart: 28 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) · ×3
  • Edited copy of a member (26 corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:264 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:264-289 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskProcessStylesheetCss.java:108-136 — 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) vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:118 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/AbstractContext.java:118-151 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/AbstractContext.java:91-116 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterForwardToView.java:49 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterForwardToView.java:49-74 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SetParameterRerouteToView.java:49-74 — 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 · Duplicated block (35 lines × 2) · ×3
  • Duplicated block (35 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextualStorage.java:117 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextualStorage.java:117-151 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/ContextualStorage.java:91-125 — 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 (35 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:62 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:62-96 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:60-94 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:62` 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 (35 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/BootstrapCustomizer.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/BootstrapCustomizer.java:1-37 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/BootstrapCustomizer.java:1-35 — 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/BootstrapCustomizer.java:1` 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.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×3
  • Duplicated block (31 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:433 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:433-463 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:502-532 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:539` calls `getUrlsToScan` and `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:464` 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 (31 lines × 2) flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:37 — flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:37-67 | flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:43-73 — before extracting anything, compare `flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java` and `flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java` as WHOLE FILES: 92% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:40` calls `getCurrent`, `getPage`, `executeJs` and `flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:35` 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 (31 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/javascript/JsDefinitionView.java:105 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/javascript/JsDefinitionView.java:105-135 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/JsDefinitionView.java:105-135 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/javascript/JsDefinitionView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/JsDefinitionView.java` as WHOLE FILES: 99% 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 1 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×3
  • Duplicated block (22 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:482 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:482-503 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:560-581 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `sourceMojo` to `BuildDevBundleMojo` in one and `FlowModeAbstractMojo` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (22 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java:53 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java:53-74 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeProceedView.java:53-74 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeProceedView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeProceedView.java` as WHOLE FILES: 91% 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 (22 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/sessioncontext/SessionContextView.java:47 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/sessioncontext/SessionContextView.java:47-68 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/sessioncontext/SessionContextView.java:45-66 — 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.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×3
  • Duplicated block (11 lines × 2 locations) flow-client/src/main/frontend/internal/client/Registry.ts:391 — flow-client/src/main/frontend/internal/client/Registry.ts:391 · flow-client/src/main/frontend/internal/client/UILifecycle.ts:109 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (11 lines × 2 locations) flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:143 — flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:143 · flow-client/src/main/frontend/internal/flow/shared/util/SharedUtil.ts:162 — 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 locations) scripts/memoryFootprint.js:236 — scripts/memoryFootprint.js:236 · scripts/previewModule.js:237 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R8 · Dependency Hygiene · Unused dependency 'strip-css-comments' · ×3
  • Unused dependency 'strip-css-comments' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json:11 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/default/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
  • Unused dependency 'strip-css-comments' flow-tests/test-frontend/vite-basics/package.json:39 — Declared in flow-tests/test-frontend/vite-basics/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
  • Unused dependency 'strip-css-comments' flow-tests/test-frontend/vite-context-path/package.json:31 — Declared in flow-tests/test-frontend/vite-context-path/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/META-INF/frontend/theme-util.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@preact/signals-react' · ×3
  • Unused dependency '@preact/signals-react' flow-tests/test-frontend/vite-basics/package.json:28 — Declared in flow-tests/test-frontend/vite-basics/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 '@preact/signals-react' flow-tests/test-frontend/vite-context-path/package.json:20 — Declared in flow-tests/test-frontend/vite-context-path/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 '@preact/signals-react' flow-tests/test-frontend/vite-production/package.json:25 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@preact/signals-react-transform' · ×3
  • Unused dependency '@preact/signals-react-transform' flow-tests/test-frontend/vite-basics/package.json:29 — Declared in flow-tests/test-frontend/vite-basics/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 '@preact/signals-react-transform' flow-tests/test-frontend/vite-context-path/package.json:21 — Declared in flow-tests/test-frontend/vite-context-path/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 '@preact/signals-react-transform' flow-tests/test-frontend/vite-production/package.json:26 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@vaadin/bundles' · ×3
  • Unused dependency '@vaadin/bundles' flow-tests/test-frontend/vite-basics/package.json:11 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/bundles' flow-tests/test-frontend/vite-context-path/package.json:6 — Declared in flow-tests/test-frontend/vite-context-path/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 '@vaadin/bundles' flow-tests/test-frontend/vite-production/package.json:8 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@vaadin/testscope-all' · ×3
  • Unused dependency '@vaadin/testscope-all' flow-tests/test-frontend/vite-basics/package.json:14 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/testscope-all' flow-tests/test-frontend/vite-context-path/package.json:7 — Declared in flow-tests/test-frontend/vite-context-path/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 '@vaadin/testscope-all' flow-tests/test-frontend/vite-production/package.json:12 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@vaadin/testscope-button' · ×3
  • Unused dependency '@vaadin/testscope-button' flow-tests/test-frontend/vite-basics/package.json:15 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/testscope-button' flow-tests/test-frontend/vite-context-path/package.json:8 — Declared in flow-tests/test-frontend/vite-context-path/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 '@vaadin/testscope-button' flow-tests/test-frontend/vite-production/package.json:13 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@vaadin/testscope-map' · ×3
  • Unused dependency '@vaadin/testscope-map' flow-tests/test-frontend/vite-basics/package.json:16 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/testscope-map' flow-tests/test-frontend/vite-context-path/package.json:9 — Declared in flow-tests/test-frontend/vite-context-path/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 '@vaadin/testscope-map' flow-tests/test-frontend/vite-production/package.json:14 — Declared in flow-tests/test-frontend/vite-production/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) · ×3
  • Redirected process stream is never drained (deadlock) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/OpenInCurrentIde.java:213 — The JDK merges `stderr` into `stdout` here (`redirectErrorStream(true)`), and that one stream is still a pipe — and `process.waitFor()` is written before stdout is read, so nothing drains it while the parent waits. 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).
  • Redirected process stream is never drained (deadlock) flow-build-tools/src/main/java/com/vaadin/frontendtools/installer/DefaultArchiveExtractor.java:69 — The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `child.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).
  • Redirected process stream is never drained (deadlock) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:922 — 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).
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×3
  • Untrusted text written into markup unescaped vaadin-dev-server/src/main/frontend/License.ts:90 — `productAndMessage.messageHtml` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped vaadin-dev-server/src/main/frontend/License.ts:91 — `productAndMessage.message` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:785 — `relative` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
D1 · Cyclomatic Complexity · convert.convertFile · ×2
  • convert.convertFile::modifyClass (cyclomatic 24) flow-polymer2lit/convert.ts:118 — convert.convertFile::modifyClass has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (convert.convertFile, convert.convertFile::rewriteElement) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • convert.convertFile::rewriteElement (cyclomatic 24) flow-polymer2lit/convert.ts:342 — convert.convertFile::rewriteElement has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (convert.convertFile, convert.convertFile::modifyClass) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · BrowserDetails.isTooOldToFunctionProperly (cyclomatic 16) · ×2
  • BrowserDetails.isTooOldToFunctionProperly (cyclomatic 16) flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:824 — BrowserDetails.isTooOldToFunctionProperly has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • BrowserDetails.isTooOldToFunctionProperly (cyclomatic 16) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:817 — BrowserDetails.isTooOldToFunctionProperly has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: flow-test-parent-theme-prod flow-tests/test-express-build/test-parent-theme-prod/src/test/java/com/vaadin/flow/prodbuild/ParentThemeIT.java:31 — No conventional assertion call was detected in 1 of 1 tests in `flow-test-parent-theme-prod` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: vaadin-quarkus-custom-servlet-tests flow-tests/vaadin-quarkus-tests/custom-servlet-it/src/test/java/com/vaadin/flow/quarkus/it/customservlet/CustomServletIT.java:38 — No conventional assertion call was detected in 2 of 2 tests in `vaadin-quarkus-custom-servlet-tests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D2 · Cognitive Complexity · BrowserDetails.isTooOldToFunctionProperly (cognitive 16) · ×2
  • BrowserDetails.isTooOldToFunctionProperly (cognitive 16) flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:824 — BrowserDetails.isTooOldToFunctionProperly has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • BrowserDetails.isTooOldToFunctionProperly (cognitive 16) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:817 — BrowserDetails.isTooOldToFunctionProperly has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×2
  • Edited copy of a member (30 corresponding lines) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:632 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:632-661 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:767-805 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:587 — flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:587-632 | flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HierarchicalDataCommunicator.java:648-677 — These two members are one piece of code written twice and then edited apart: 30 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 (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:139 — vaadin-cdi/src/main/java/com/vaadin/cdi/CdiVaadinServletService.java:139-175 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/QuarkusVaadinServletService.java:140-173 — These two members are one piece of code written twice and then edited apart: 34 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 (34 corresponding lines) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:811 — flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:811-844 | flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:846-880 — These two members are one piece of code written twice and then edited apart: 34 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) flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:606 — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:606-630 | flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.java:334-362 — 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:35 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationTriggerView.java:35-67 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationTriggerView.java:35-59 — 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 copies of one member (3 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 13+ corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:359 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendTools.java:359-371 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:213-226 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/ConvertPolymerCommand.java:193-205 — 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.
  • Edited copies of one member (3 members, 13+ corresponding lines) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/DevModeUsageStatistics.java:262 — vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/DevModeUsageStatistics.java:262-275 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/DevModeUsageStatistics.java:288-300 | vaadin-dev-server/src/main/java/com/vaadin/base/devserver/stats/DevModeUsageStatistics.java:310-322 — 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, 12+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 12+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:76 — flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:76-90 | flow-server/src/main/java/com/vaadin/flow/component/Shortcuts.java:120-135 | flow-server/src/main/java/com/vaadin/flow/component/UI.java:1823-1834 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/internal/CaseUtil.java:70 — flow-server/src/main/java/com/vaadin/flow/internal/CaseUtil.java:70-81 | flow-server/src/main/java/com/vaadin/flow/shared/util/SharedUtil.java:127-138 | flow-server/src/main/java/com/vaadin/flow/shared/util/SharedUtil.java:148-159 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 14+ corresponding lines) vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:445 — vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinRouteScope.java:445-459 | vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinSessionScope.java:76-89 | vaadin-spring/src/main/java/com/vaadin/flow/spring/scopes/VaadinUIScope.java:117-130 — 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.
  • Edited copies of one member (3 members, 14+ corresponding lines) flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:33 — flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:33-47 | flow-tests/test-embedding/test-embedding-reusable-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:32-45 | flow-tests/test-express-build/test-embedding-express-build/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:32-45 — 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, 11+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 11+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/internal/EncodeUtil.java:131 — flow-server/src/main/java/com/vaadin/flow/internal/EncodeUtil.java:131-142 | flow-server/src/main/java/com/vaadin/flow/shared/util/SharedUtil.java:48-59 | REDACTED:118-128 — 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/InstrumentedReentrantLock.java:101 — flow-server/src/main/java/com/vaadin/flow/server/InstrumentedReentrantLock.java:101-111 | flow-server/src/main/java/com/vaadin/flow/server/InstrumentedReentrantLock.java:128-139 | flow-server/src/main/java/com/vaadin/flow/server/InstrumentedReentrantLock.java:143-154 — 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, 4+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 4+ corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateJsDefinitions.java:615 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateJsDefinitions.java:615-618 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdateVite.java:81-84 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Handshake.java:174-177 — 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) flow-html-components/src/main/java/com/vaadin/flow/component/html/IFrame.java:103 — flow-html-components/src/main/java/com/vaadin/flow/component/html/IFrame.java:103-106 | flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeButton.java:88-92 | flow-html-components/src/main/java/com/vaadin/flow/component/html/OrderedList.java:77-80 — 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 · Duplicated block (39 lines × 2) · ×2
  • Duplicated block (39 lines × 2) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:185 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:185-223 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java:183-221 — before extracting anything, compare `flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java` and `flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 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. 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 (39 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/Counter.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/Counter.java:1-39 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/Counter.java:1-39 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/Counter.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/Counter.java` as WHOLE FILES: 96% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/Counter.java:1` 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×2
  • Duplicated block (32 lines × 2) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:87 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:87-118 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java:88-119 — before extracting anything, compare `flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java` and `flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `clazz` to `Class<? extends LitTemplate>` in one and `Class<? extends PolymerTemplate<?>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (32 lines × 2) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:194 — flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:194-225 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:135-166 — 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 `flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:194` 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:123 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:123-151 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:134-162 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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. 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) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractPushUpdateDivView.java:38 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractPushUpdateDivView.java:38-67 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/push/PushUpdateDivView.java:40-68 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/AbstractPushUpdateDivView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/push/PushUpdateDivView.java` as WHOLE FILES: 91% 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 1 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:307 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:307-332 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:352-377 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:307` 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 (26 lines × 2) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:536 — vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java:536-561 | vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java:448-473 — before extracting anything, compare `vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanProvider.java` and `vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/BeanProvider.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:117 — flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:117-133 | flow-server/src/main/java/com/vaadin/flow/server/streams/ServletResourceDownloadHandler.java:106-123 — 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 `flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:117` 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 (17–18 lines × 2) vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java:801 — vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java:801-818 | vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/AtmosphereHintsRegistrar.java:75-91 — 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 · Duplicated block (15–16 lines × 2) · ×2
  • Duplicated block (15–16 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGeneratePackageJson.java:49 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGeneratePackageJson.java:49-63 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:118-133 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGeneratePackageJson.java:49` 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–16 lines × 2) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:234 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:234-249 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNodeSignal.java:408-422 — 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 `flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:234` 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×2
  • Duplicated block (11–13 lines × 2) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1557 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1557-1569 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1584-1594 — 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–13 lines × 2) flow-server/src/main/java/com/vaadin/flow/server/communication/UidlWriter.java:379 — flow-server/src/main/java/com/vaadin/flow/server/communication/UidlWriter.java:379-391 | flow-server/src/main/java/com/vaadin/flow/server/communication/UidlWriter.java:464-474 — 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 `flow-server/src/main/java/com/vaadin/flow/server/communication/UidlWriter.java:379` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:269 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:269-280 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java:380-392 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:269` 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–13 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationEventsView.java:39 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationEventsView.java:39-51 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationEventsView.java:38-49 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/NavigationEventsView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/NavigationEventsView.java` as WHOLE FILES: 94% 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 1 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:339 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:339-349 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:384-395 — before extracting anything, compare `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` and `flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 214 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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:339` 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 (11–12 lines × 2) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:338 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:338-349 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:420-430 — 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 `flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:338` 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:668 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:668-678 | flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:366-376 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:419-429 — 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 `flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:668` 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 (11 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:132 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:132-142 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:130-140 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:133-143 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:487 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:487-495 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:509-518 — 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 (9–10 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:158 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:158-167 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:220-228 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:158` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×2
  • Duplicated block (8–9 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/SignalPropertySupport.java:152 — flow-server/src/main/java/com/vaadin/flow/component/SignalPropertySupport.java:152-159 | flow-server/src/main/java/com/vaadin/flow/dom/ElementEffect.java:251-259 — 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 (8–9 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:39 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:39-47 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:39-46 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:39` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×2
  • Duplicated block (7–8 lines × 2) flow-server/src/main/java/com/vaadin/flow/internal/UrlUtil.java:108 — flow-server/src/main/java/com/vaadin/flow/internal/UrlUtil.java:108-114 | flow-server/src/main/java/com/vaadin/flow/internal/UrlUtil.java:132-139 — 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 `flow-server/src/main/java/com/vaadin/flow/internal/UrlUtil.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–8 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ExtendedClientDetailsView.java:70 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ExtendedClientDetailsView.java:70-77 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ExtendedClientDetailsView.java:84-90 — 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/ExtendedClientDetailsView.java:70` 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) flow-data/src/main/java/com/vaadin/flow/data/converter/BigDecimalToDoubleConverter.java:33 — flow-data/src/main/java/com/vaadin/flow/data/converter/BigDecimalToDoubleConverter.java:33-39 | flow-data/src/main/java/com/vaadin/flow/data/converter/FloatToDoubleConverter.java:29-34 | flow-data/src/main/java/com/vaadin/flow/data/converter/IntegerToDoubleConverter.java:30-36 — 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 `flow-data/src/main/java/com/vaadin/flow/data/converter/BigDecimalToDoubleConverter.java:33` 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. 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 first that the copies are not typed on the same thing: the declarations holding them bind `value` to `BigDecimal` in one and `Float` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 3) flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:106 — flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:106-111 | flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:118-123 | flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:130-135 — 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 `flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:106` 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, `flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:112` calls `add` and `flow-tests/test-live-reload/src/main/java/com/vaadin/flow/uitest/ui/ScrollPositionLiveReloadView.java:103` 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) flow-data/src/main/java/com/vaadin/flow/data/converter/StringToDoubleConverter.java:92 — flow-data/src/main/java/com/vaadin/flow/data/converter/StringToDoubleConverter.java:92-102 | flow-data/src/main/java/com/vaadin/flow/data/converter/StringToFloatConverter.java:92-102 | flow-data/src/main/java/com/vaadin/flow/data/converter/StringToLongConverter.java:107-116 — before extracting anything, compare `flow-data/src/main/java/com/vaadin/flow/data/converter/StringToDoubleConverter.java` and `flow-data/src/main/java/com/vaadin/flow/data/converter/StringToFloatConverter.java` as WHOLE FILES: 88% 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 1 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) flow-tests/test-common/src/main/java/com/vaadin/flow/uitest/servlet/RouterLayoutCustomScopeServlet.java:165 — flow-tests/test-common/src/main/java/com/vaadin/flow/uitest/servlet/RouterLayoutCustomScopeServlet.java:165-174 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:56-65 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java:54-63 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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 `flow-tests/test-common/src/main/java/com/vaadin/flow/uitest/servlet/RouterLayoutCustomScopeServlet.java:165` 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:44 — flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:44-51 | flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:43-50 | flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/PolymerIdTestView.java:37-44 | flow-tests/test-frontend/test-pnpm/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:43-50 | flow-tests/test-frontend/test-pnpm/src/main/java/com/vaadin/flow/mixedtest/ui/PolymerIdTestView.java:37-44 — 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) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:31 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:31-41 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:32-42 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:30-40 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:42-72 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/RolePrefixedAdminView.java:31-41 — 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 (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:51 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIContextRootView.java:51-79 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIContextRootView.java:54-86 — 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.
  • Edited copy of a member (29 corresponding lines) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/sessioncontext/SessionContextView.java:46 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/sessioncontext/SessionContextView.java:46-74 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/sessioncontext/SessionContextView.java:44-72 — 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 · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/binder/BinderView.java:41 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/binder/BinderView.java:41-64 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/BinderView.java:41-64 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/binder/BinderView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/BinderView.java` as WHOLE FILES: 86% 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 1 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 (24 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIScopedLabel.java:41 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIScopedLabel.java:41-64 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uicontext/UIScopedLabel.java:39-62 — 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uicontext/UIScopedLabel.java:41` 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.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×2
  • Duplicated block (22 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66-87 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66-87 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:82-103 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 133 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:66` 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, `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:80` calls `getElement`, `getThemeList`, `add` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:64` 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 (22 lines × 3) flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java:38 — flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java:38-59 | flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java:38-59 | flow-tests/test-frontend/test-pnpm/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java:38-59 — before extracting anything, compare `flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java` and `flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/MissingDependenciesView.java:38` 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.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java:41 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java:41-58 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeUpdateView.java:40-57 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/PostponeUpdateView.java` and `flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/PostponeUpdateView.java` as WHOLE FILES: 96% 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 (18 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/CountedPerUI.java:24 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/CountedPerUI.java:24-41 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/CountedPerUI.java:24-41 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/CountedPerUI.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/CountedPerUI.java` as WHOLE FILES: 86% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/CountedPerUI.java:24` 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 first that the copies are not typed on the same thing: `BeanProvider` names `com.vaadin.cdi.util.BeanProvider` in one and `com.vaadin.quarkus.context.BeanProvider` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×2
  • Duplicated block (14 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:51 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:51-64 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:50-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:50-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:50-63 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.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. 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 × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:152 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:152-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:152-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:152-165 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:220-233 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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. 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.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:35 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:35-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:35-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:35-47 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java:35-47 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/AccountService.java` as WHOLE FILES: 100% 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 1 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 × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:93 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:93-105 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:101-113 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:101-113 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:126-138 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:93` 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:37 — flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:37-47 | flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:37-47 | flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:36-46 | flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:42-52 — before extracting anything, compare `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java` and `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:49` calls `setId`, `Span` and `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:50` 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 × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:82 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:82-92 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:90-100 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:90-100 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:106-116 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:69 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:69-77 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:65-73 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:65-73 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:81-89 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:80` calls `getElement`, `getThemeList`, `add` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:68` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:66 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:66-74 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:65-73 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:65-73 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java:65-73 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/BankService.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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • Duplicated block (9 lines × 3) flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:83 — flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:83-91 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:79-87 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:78-86 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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 `flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:83` 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 × 3) flow-tests/test-common/src/main/java/com/vaadin/flow/uitest/servlet/RouterLayoutCustomScopeServlet.java:185 — flow-tests/test-common/src/main/java/com/vaadin/flow/uitest/servlet/RouterLayoutCustomScopeServlet.java:185-193 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java:76-84 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java:74-82 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/regression/RemoveOldContentView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/regression/RemoveOldContentView.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:46 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:46-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:46-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:46-53 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java:46-53 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/Account.java` as WHOLE FILES: 100% 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 1 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 (8 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:36 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:36-43 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:45-52 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:43-50 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:41-48 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×2
  • Duplicated block (40 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/EventObserver.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/EventObserver.java:1-43 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/EventObserver.java:1-40 — 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/EventObserver.java:1` 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 first that the copies are not typed on the same thing: `Counter` names `com.vaadin.cdi.itest.Counter` in one and `com.vaadin.flow.quarkus.it.Counter` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (40 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/TestSystemMessagesProvider.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/TestSystemMessagesProvider.java:1-40 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/TestSystemMessagesProvider.java:1-40 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/TestSystemMessagesProvider.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/service/TestSystemMessagesProvider.java` as WHOLE FILES: 91% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/service/TestSystemMessagesProvider.java:1` 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. Note first that the copies are not typed on the same thing: `VaadinServiceEnabled` names `com.vaadin.cdi.annotation.VaadinServiceEnabled` in one and `com.vaadin.quarkus.annotation.VaadinServiceEnabled` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×2
  • Duplicated block (37 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CustomAnnotatedEnpoint.java:1 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CustomAnnotatedEnpoint.java:1-37 | flow-tests/vaadin-quarkus-tests/custom-websocket-dependency/src/main/java/org/vaadin/sample/websockets/DependencyAnnotatedWS.java:1-37 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CustomAnnotatedEnpoint.java` and `flow-tests/vaadin-quarkus-tests/custom-websocket-dependency/src/main/java/org/vaadin/sample/websockets/DependencyAnnotatedWS.java` as WHOLE FILES: 83% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/CustomAnnotatedEnpoint.java:1` 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 (37 lines × 2) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java:1 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java:1-37 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java:1-37 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PassThroughView.java:1` 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.
R10 · Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (5 matched lines × 2 locations) flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-copy.js:141 — flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-copy.js:141 · flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:24 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (5 matched lines × 2 locations) flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:124 — flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:124 · flow-client/src/main/frontend/internal/client/communication/MessageOrdering.ts:150 — the two spans are one implementation copied and then locally edited — 51 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.
R4 · Test Coverage · This test file cannot be loaded · ×2
  • This test file cannot be loaded flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4 — flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4 imports '../../../styles/shared-styles.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded flow-polymer2lit/src/test/resources/frontend/in/order-card-from-bakery.js:2 — flow-polymer2lit/src/test/resources/frontend/in/order-card-from-bakery.js:2 imports '../../../styles/shared-styles.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R8 · Dependency Hygiene · Unused dependency '@vaadin/test-package-outside-npm' · ×2
  • Unused dependency '@vaadin/test-package-outside-npm' flow-tests/test-frontend/vite-basics/package.json:12 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/test-package-outside-npm' flow-tests/test-frontend/vite-production/package.json:10 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency '@vaadin/test-package2-outside-npm' · ×2
  • Unused dependency '@vaadin/test-package2-outside-npm' flow-tests/test-frontend/vite-basics/package.json:13 — Declared in flow-tests/test-frontend/vite-basics/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 '@vaadin/test-package2-outside-npm' flow-tests/test-frontend/vite-production/package.json:11 — Declared in flow-tests/test-frontend/vite-production/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.
R8 · Dependency Hygiene · Unused dependency 'transform-ast' · ×2
  • Unused dependency 'transform-ast' flow-tests/test-frontend/vite-basics/package.json:40 — Declared in flow-tests/test-frontend/vite-basics/package.json but never imported anywhere in that package or its workspace members — while flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
  • Unused dependency 'transform-ast' flow-tests/test-frontend/vite-context-path/package.json:32 — Declared in flow-tests/test-frontend/vite-context-path/package.json but never imported anywhere in that package or its workspace members — while flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.7 · ×1
  • Low contrast colour pair in CSS (3.7:1) flow-tests/test-root-context/src/main/webapp/style-layer-annotated.css:2 — `div#annotated-div.layered` sets color: rgb(255, 0, 0) on background-color: rgb(255, 255, 0) — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.1 · ×1
  • Low contrast colour pair in CSS (2.1:1) flow-tests/test-root-context/src/main/webapp/style-layer-theme.css:2 — `div#test-div.layered` sets color: rgb(255, 0, 0) on background-color: rgb(0, 0, 255) — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:235 — `.css-in-js .window` 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.
D1 · Cyclomatic Complexity · TransactionEngine.apply (cyclomatic 57) · ×1
  • TransactionEngine.apply (cyclomatic 57) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379 — TransactionEngine.apply has cyclomatic complexity 57 (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.
D1 · Cyclomatic Complexity · NodeTasks.<init> (cyclomatic 37) · ×1
  • NodeTasks.<init> (cyclomatic 37) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111 — NodeTasks.<init> has cyclomatic complexity 37 (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.
D1 · Cyclomatic Complexity · BrowserDetails.parseBrowserVersion (cyclomatic 36) · ×1
  • BrowserDetails.parseBrowserVersion (cyclomatic 36) flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:180 — BrowserDetails.parseBrowserVersion has cyclomatic complexity 36 (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.
D1 · Cyclomatic Complexity · FlowBootstrap.init (cyclomatic 36) · ×1
  • FlowBootstrap.init (cyclomatic 36) flow-client/src/main/frontend/FlowBootstrap.js:9 — FlowBootstrap.init has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 15 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 108, isInitializedInDom, a function literal at line 191, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · BrowserDetails.#parseBrowserVersion (cyclomatic 36) · ×1
  • BrowserDetails.#parseBrowserVersion (cyclomatic 36) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:232 — BrowserDetails.#parseBrowserVersion has cyclomatic complexity 36 (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.
D1 · Cyclomatic Complexity · StaticFileServer.serveStaticResource (cyclomatic 31) · ×1
  • StaticFileServer.serveStaticResource (cyclomatic 31) flow-server/src/main/java/com/vaadin/flow/server/StaticFileServer.java:252 — StaticFileServer.serveStaticResource has cyclomatic complexity 31 (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.
D1 · Cyclomatic Complexity · AbstractConfigurationFactory.getConfigParametersUsingTokenData (cyclomatic 29) · ×1
  • AbstractConfigurationFactory.getConfigParametersUsingTokenData (cyclomatic 29) flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractConfigurationFactory.java:84 — AbstractConfigurationFactory.getConfigParametersUsingTokenData has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · Flow.Flow (cyclomatic 28) · ×1
  • Flow.Flow (cyclomatic 28) flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:349 — Flow.Flow has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 525, 352, 434, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · TaskGenerateTsDefinitions.updateIfContentMissing (cyclomatic 27) · ×1
  • TaskGenerateTsDefinitions.updateIfContentMissing (cyclomatic 27) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTsDefinitions.java:125 — TaskGenerateTsDefinitions.updateIfContentMissing has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · TaskRunNpmInstall.runNpmInstall (cyclomatic 27) · ×1
  • TaskRunNpmInstall.runNpmInstall (cyclomatic 27) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:271 — TaskRunNpmInstall.runNpmInstall has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · AppProcess.start (cyclomatic 26) · ×1
  • AppProcess.start (cyclomatic 26) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java:401 — AppProcess.start 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.
D1 · Cyclomatic Complexity · TransactionEngine.render (cyclomatic 25) · ×1
  • TransactionEngine.render (cyclomatic 25) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1944 — TransactionEngine.render has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · StringUtil.removeComments (cyclomatic 24) · ×1
  • StringUtil.removeComments (cyclomatic 24) flow-server/src/main/java/com/vaadin/flow/internal/StringUtil.java:101 — StringUtil.removeComments has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DevLoopRedefiner.redefine (cyclomatic 24) · ×1
  • DevLoopRedefiner.redefine (cyclomatic 24) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:236 — DevLoopRedefiner.redefine has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Flow.extractURL (cyclomatic 24) · ×1
  • Flow.extractURL (cyclomatic 24) flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:69 — Flow.extractURL has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · RouteUtil.updateRouteRegistry (cyclomatic 22) · ×1
  • RouteUtil.updateRouteRegistry (cyclomatic 22) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:414 — RouteUtil.updateRouteRegistry has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · rollup-plugin-vaadin-i18n.vaadinI18n.transform (cyclomatic 22) · ×1
  • rollup-plugin-vaadin-i18n.vaadinI18n.transform (cyclomatic 22) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — rollup-plugin-vaadin-i18n.vaadinI18n.transform has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). 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.
D1 · Cyclomatic Complexity · Profiler.logTimings (cyclomatic 22) · ×1
  • Profiler.logTimings (cyclomatic 22) flow-client/src/main/frontend/internal/client/Profiler.ts:398 — Profiler.logTimings has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · vaadinI18n.transform (cyclomatic 22) · ×1
  • vaadinI18n.transform (cyclomatic 22) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — vaadinI18n.transform has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). 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.
D1 · Cyclomatic Complexity · ExtendedClientDetails.<init> (cyclomatic 21) · ×1
  • ExtendedClientDetails.<init> (cyclomatic 21) flow-server/src/main/java/com/vaadin/flow/component/page/ExtendedClientDetails.java:124 — ExtendedClientDetails.<init> has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · MessageHandler.#handleJSON (cyclomatic 21) · ×1
  • MessageHandler.#handleJSON (cyclomatic 21) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:288 — MessageHandler.#handleJSON has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AbstractUpdateImports.process (cyclomatic 20) · ×1
  • AbstractUpdateImports.process (cyclomatic 20) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:376 — AbstractUpdateImports.process 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.
D1 · Cyclomatic Complexity · Daemon.dispatch (cyclomatic 20) · ×1
  • Daemon.dispatch (cyclomatic 20) REDACTED:297 — Daemon.dispatch 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.
D1 · Cyclomatic Complexity · AbstractDownloadHandler.transferContent (cyclomatic 20) · ×1
  • AbstractDownloadHandler.transferContent (cyclomatic 20) flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java:262 — AbstractDownloadHandler.transferContent has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CleanFrontendUtil.runCleaning (cyclomatic 20) · ×1
  • CleanFrontendUtil.runCleaning (cyclomatic 20) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/CleanFrontendUtil.java:70 — CleanFrontendUtil.runCleaning 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.
D1 · Cyclomatic Complexity · IndexHtmlRequestHandler.synchronizedHandleRequest (cyclomatic 19) · ×1
  • IndexHtmlRequestHandler.synchronizedHandleRequest (cyclomatic 19) flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java:108 — IndexHtmlRequestHandler.synchronizedHandleRequest 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.
D1 · Cyclomatic Complexity · Reflector.createIsolatedClassLoader (cyclomatic 19) · ×1
  • Reflector.createIsolatedClassLoader (cyclomatic 19) flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:304 — Reflector.createIsolatedClassLoader 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.
D1 · Cyclomatic Complexity · convert.convertFile (cyclomatic 19) · ×1
  • convert.convertFile (cyclomatic 19) flow-polymer2lit/convert.ts:94 — convert.convertFile 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. This shape REPEATS in the file: 2 other methods here (convert.convertFile::modifyClass, convert.convertFile::rewriteElement) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · VaadinDevTools.openWebSocketConnection (cyclomatic 19) · ×1
  • VaadinDevTools.openWebSocketConnection (cyclomatic 19) vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:632 — VaadinDevTools.openWebSocketConnection has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (onUpdate, onReload, a function literal at line 696, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · writeThemeFiles (cyclomatic 19) · ×1
  • writeThemeFiles (cyclomatic 19) flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:45 — writeThemeFiles 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.
D1 · Cyclomatic Complexity · AbstractUpdateImports.getUniqueEs6ImportPaths (cyclomatic 18) · ×1
  • AbstractUpdateImports.getUniqueEs6ImportPaths (cyclomatic 18) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:710 — AbstractUpdateImports.getUniqueEs6ImportPaths 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.
D1 · Cyclomatic Complexity · Watch.drain (cyclomatic 18) · ×1
  • Watch.drain (cyclomatic 18) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:561 — Watch.drain 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.
D1 · Cyclomatic Complexity · JacksonSerializer.tryToConvertFromSimpleType (cyclomatic 18) · ×1
  • JacksonSerializer.tryToConvertFromSimpleType (cyclomatic 18) flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:356 — JacksonSerializer.tryToConvertFromSimpleType 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.
D1 · Cyclomatic Complexity · StyleSheetHotswapper.updateUIs (cyclomatic 18) · ×1
  • StyleSheetHotswapper.updateUIs (cyclomatic 18) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:296 — StyleSheetHotswapper.updateUIs 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.
D1 · Cyclomatic Complexity · MessageHandler.#processMessage (cyclomatic 18) · ×1
  • MessageHandler.#processMessage (cyclomatic 18) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:446 — MessageHandler.#processMessage 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.
D1 · Cyclomatic Complexity · Debouncer.trigger (cyclomatic 18) · ×1
  • Debouncer.trigger (cyclomatic 18) flow-client/src/main/frontend/internal/client/flow/binding/Debouncer.ts:82 — Debouncer.trigger has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
D1 · Cyclomatic Complexity · DevLoopBuildExtension.reconfigure (cyclomatic 17) · ×1
  • DevLoopBuildExtension.reconfigure (cyclomatic 17) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/mavenext/DevLoopBuildExtension.java:488 — DevLoopBuildExtension.reconfigure 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.
D1 · Cyclomatic Complexity · AbstractDevServerRunner.serveDevModeRequest (cyclomatic 17) · ×1
  • AbstractDevServerRunner.serveDevModeRequest (cyclomatic 17) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/AbstractDevServerRunner.java:770 — AbstractDevServerRunner.serveDevModeRequest 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.
D1 · Cyclomatic Complexity · CustomResourceLoader.collectResources (cyclomatic 17) · ×1
  • CustomResourceLoader.collectResources (cyclomatic 17) vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:1090 — CustomResourceLoader.collectResources 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.
D1 · Cyclomatic Complexity · BrowserHelpers.collectBrowserDetails (cyclomatic 17) · ×1
  • BrowserHelpers.collectBrowserDetails (cyclomatic 17) flow-client/src/main/frontend/BrowserHelpers.ts:42 — BrowserHelpers.collectBrowserDetails has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · BrowserDetails.#parseBrowserName (cyclomatic 17) · ×1
  • BrowserDetails.#parseBrowserName (cyclomatic 17) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:170 — BrowserDetails.#parseBrowserName has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · convert.splitExpression (cyclomatic 17) · ×1
  • convert.splitExpression (cyclomatic 17) flow-polymer2lit/convert.ts:50 — convert.splitExpression 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.
D1 · Cyclomatic Complexity · BundleValidationUtil.versionAccepted (cyclomatic 16) · ×1
  • BundleValidationUtil.versionAccepted (cyclomatic 16) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/BundleValidationUtil.java:651 — BundleValidationUtil.versionAccepted 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.
D1 · Cyclomatic Complexity · Json.unescape (cyclomatic 16) · ×1
  • Json.unescape (cyclomatic 16) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Json.java:115 — Json.unescape has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · PushHandler.handleConnectionLost (cyclomatic 16) · ×1
  • PushHandler.handleConnectionLost (cyclomatic 16) flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java:471 — PushHandler.handleConnectionLost 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.
D1 · Cyclomatic Complexity · ElementListenerMap.collectEventExpressions (cyclomatic 16) · ×1
  • ElementListenerMap.collectEventExpressions (cyclomatic 16) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:725 — ElementListenerMap.collectEventExpressions 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.
D1 · Cyclomatic Complexity · JacksonSerializer.toObject (cyclomatic 16) · ×1
  • JacksonSerializer.toObject (cyclomatic 16) flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:193 — JacksonSerializer.toObject 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.
D1 · Cyclomatic Complexity · JsDefinitionProxy.checkMethods (cyclomatic 16) · ×1
  • JsDefinitionProxy.checkMethods (cyclomatic 16) flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java:253 — JsDefinitionProxy.checkMethods 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.
D1 · Cyclomatic Complexity · Hotswapper.onHotswapInternal (cyclomatic 16) · ×1
  • Hotswapper.onHotswapInternal (cyclomatic 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/Hotswapper.java:283 — Hotswapper.onHotswapInternal has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · FilterableResourceResolver.readPackageProperties (cyclomatic 16) · ×1
  • FilterableResourceResolver.readPackageProperties (cyclomatic 16) vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:407 — FilterableResourceResolver.readPackageProperties 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.
D1 · Cyclomatic Complexity · VaadinSecurityConfigurer.init (cyclomatic 16) · ×1
  • VaadinSecurityConfigurer.init (cyclomatic 16) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java:703 — VaadinSecurityConfigurer.init has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · hotswap-scroll.restoreScrollPositions (cyclomatic 16) · ×1
  • hotswap-scroll.restoreScrollPositions (cyclomatic 16) vaadin-dev-server/src/main/frontend/hotswap-scroll.ts:326 — hotswap-scroll.restoreScrollPositions has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 367, waitForIdleClients, stopped, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1572 — // XXX Explicitly refresh anything that is updated — 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment flow-client/src/main/frontend/internal/client/ApplicationConnection.ts:150 — // Hack to avoid logging an error in endRequest(). — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · TransactionEngine.apply (cognitive 90) · ×1
  • TransactionEngine.apply (cognitive 90) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:379 — TransactionEngine.apply has cognitive complexity 90 (threshold 15). Drivers by points: if/else 37 (61 pts), ternaries 8 (16 pts), boolean chains 7, error handling 4 (6 pts) (nesting depth added 34). 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.
D2 · Cognitive Complexity · NodeTasks.<init> (cognitive 60) · ×1
  • NodeTasks.<init> (cognitive 60) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java:111 — NodeTasks.<init> has cognitive complexity 60 (threshold 15). Drivers by points: if/else 32 (51 pts), boolean chains 9 (nesting depth added 19). 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.
D2 · Cognitive Complexity · TaskGenerateTsDefinitions.updateIfContentMissing (cognitive 56) · ×1
  • TaskGenerateTsDefinitions.updateIfContentMissing (cognitive 56) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTsDefinitions.java:125 — TaskGenerateTsDefinitions.updateIfContentMissing has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (31 pts), error handling 7 (18 pts), boolean chains 7 (nesting depth added 27). 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.
D2 · Cognitive Complexity · StyleSheetHotswapper.updateUIs (cognitive 54) · ×1
  • StyleSheetHotswapper.updateUIs (cognitive 54) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/impl/StyleSheetHotswapper.java:296 — StyleSheetHotswapper.updateUIs has cognitive complexity 54 (threshold 15). Drivers by points: if/else 11 (37 pts), loops 3 (7 pts), error handling 1 (4 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 36). 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.
D2 · Cognitive Complexity · BrowserDetails.parseBrowserVersion (cognitive 50) · ×1
  • BrowserDetails.parseBrowserVersion (cognitive 50) flow-server/src/main/java/com/vaadin/flow/shared/BrowserDetails.java:180 — BrowserDetails.parseBrowserVersion has cognitive complexity 50 (threshold 15). Drivers by points: if/else 31 (42 pts), boolean chains 7, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BrowserDetails.#parseBrowserVersion (cognitive 50) · ×1
  • BrowserDetails.#parseBrowserVersion (cognitive 50) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:232 — BrowserDetails.#parseBrowserVersion has cognitive complexity 50 (threshold 15). Drivers by points: if/else 31 (42 pts), boolean chains 7, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Profiler.logTimings (cognitive 43) · ×1
  • Profiler.logTimings (cognitive 43) flow-client/src/main/frontend/internal/client/Profiler.ts:398 — Profiler.logTimings has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TaskRunNpmInstall.runNpmInstall (cognitive 42) · ×1
  • TaskRunNpmInstall.runNpmInstall (cognitive 42) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:271 — TaskRunNpmInstall.runNpmInstall has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (29 pts), error handling 4 (7 pts), boolean chains 4, loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AppProcess.start (cognitive 42) · ×1
  • AppProcess.start (cognitive 42) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java:401 — AppProcess.start has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 5 (12 pts), boolean chains 7, error handling 1 (2 pts), loops 1 (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.
D2 · Cognitive Complexity · TransactionEngine.render (cognitive 40) · ×1
  • TransactionEngine.render (cognitive 40) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1944 — TransactionEngine.render has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 7 (17 pts), boolean chains 3, match/switch 1 (nesting depth added 19). 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.
D2 · Cognitive Complexity · CustomResourceLoader.collectResources (cognitive 40) · ×1
  • CustomResourceLoader.collectResources (cognitive 40) vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:1090 — CustomResourceLoader.collectResources has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (36 pts), boolean chains 3, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StringUtil.removeComments (cognitive 38) · ×1
  • StringUtil.removeComments (cognitive 38) flow-server/src/main/java/com/vaadin/flow/internal/StringUtil.java:101 — StringUtil.removeComments has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 5, loops 2, match/switch 1 (2 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.
D2 · Cognitive Complexity · AbstractUpdateImports.process (cognitive 35) · ×1
  • AbstractUpdateImports.process (cognitive 35) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:376 — AbstractUpdateImports.process has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (29 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StaticFileServer.serveStaticResource (cognitive 35) · ×1
  • StaticFileServer.serveStaticResource (cognitive 35) flow-server/src/main/java/com/vaadin/flow/server/StaticFileServer.java:252 — StaticFileServer.serveStaticResource has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 10, error handling 2 (3 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · Flow.Flow (cognitive 34) · ×1
  • Flow.Flow (cognitive 34) flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:349 — Flow.Flow has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 7). None of this is in the body itself: all 34 points belong to 13 function literals inside it that branch (lines 525, 434, 600, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · AbstractNavigationStateRenderer.populateChain (cognitive 33) · ×1
  • AbstractNavigationStateRenderer.populateChain (cognitive 33) flow-server/src/main/java/com/vaadin/flow/router/internal/AbstractNavigationStateRenderer.java:296 — AbstractNavigationStateRenderer.populateChain has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 1 (5 pts), boolean chains 3 (nesting depth added 19). 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.
D2 · Cognitive Complexity · DevLoopRedefiner.redefine (cognitive 33) · ×1
  • DevLoopRedefiner.redefine (cognitive 33) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:236 — DevLoopRedefiner.redefine has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 5, loops 4 (5 pts), ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ServerConverter.transformModel (cognitive 31) · ×1
  • ServerConverter.transformModel (cognitive 31) flow-polymer2lit/src/main/java/com/vaadin/flow/polymer2lit/ServerConverter.java:110 — ServerConverter.transformModel has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 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.
D2 · Cognitive Complexity · AbstractConfigurationFactory.getConfigParametersUsingTokenData (cognitive 31) · ×1
  • AbstractConfigurationFactory.getConfigParametersUsingTokenData (cognitive 31) flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractConfigurationFactory.java:84 — AbstractConfigurationFactory.getConfigParametersUsingTokenData has cognitive complexity 31 (threshold 15). Drivers by points: if/else 26 (29 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · MessageHandler.#handleJSON (cognitive 31) · ×1
  • MessageHandler.#handleJSON (cognitive 31) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:288 — MessageHandler.#handleJSON has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · convert.splitExpression (cognitive 31) · ×1
  • convert.splitExpression (cognitive 31) flow-polymer2lit/convert.ts:50 — convert.splitExpression has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 5, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Watch.drain (cognitive 30) · ×1
  • Watch.drain (cognitive 30) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:561 — Watch.drain has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 7, ternaries 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FilterableResourceResolver.readPackageProperties (cognitive 30) · ×1
  • FilterableResourceResolver.readPackageProperties (cognitive 30) vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:407 — FilterableResourceResolver.readPackageProperties has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 3 (8 pts), error handling 2 (3 pts), loops 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.
D2 · Cognitive Complexity · TransferUtil.handleUpload (cognitive 29) · ×1
  • TransferUtil.handleUpload (cognitive 29) flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.java:155 — TransferUtil.handleUpload has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), error handling 4 (6 pts), loops 1 (3 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.
D2 · Cognitive Complexity · ExtendedClientDetails.<init> (cognitive 28) · ×1
  • ExtendedClientDetails.<init> (cognitive 28) flow-server/src/main/java/com/vaadin/flow/component/page/ExtendedClientDetails.java:124 — ExtendedClientDetails.<init> has cognitive complexity 28 (threshold 15). Drivers by points: error handling 7 (14 pts), if/else 12, 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.
D2 · Cognitive Complexity · ClientJsonCodec.decodeWithTypeInfo (cognitive 28) · ×1
  • ClientJsonCodec.decodeWithTypeInfo (cognitive 28) flow-client/src/main/frontend/internal/client/flow/util/ClientJsonCodec.ts:269 — ClientJsonCodec.decodeWithTypeInfo has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeInstaller.downloadFileIfMissing (cognitive 27) · ×1
  • NodeInstaller.downloadFileIfMissing (cognitive 27) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/installer/NodeInstaller.java:440 — NodeInstaller.downloadFileIfMissing has cognitive complexity 27 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 4 (10 pts), loops 1 (2 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.
D2 · Cognitive Complexity · Daemon.dispatch (cognitive 27) · ×1
  • Daemon.dispatch (cognitive 27) REDACTED:297 — Daemon.dispatch has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 5 (12 pts), boolean chains 1, error handling 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ElementListenerMap.collectEventExpressions (cognitive 27) · ×1
  • ElementListenerMap.collectEventExpressions (cognitive 27) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:725 — ElementListenerMap.collectEventExpressions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 4 (10 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · Reflector.createIsolatedClassLoader (cognitive 27) · ×1
  • Reflector.createIsolatedClassLoader (cognitive 27) flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:304 — Reflector.createIsolatedClassLoader has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (17 pts), error handling 2 (5 pts), boolean chains 2, ternaries 2, 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.
D2 · Cognitive Complexity · DevLoopBuildExtension.reconfigure (cognitive 26) · ×1
  • DevLoopBuildExtension.reconfigure (cognitive 26) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/mavenext/DevLoopBuildExtension.java:488 — DevLoopBuildExtension.reconfigure has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractDownloadHandler.transferContent (cognitive 26) · ×1
  • AbstractDownloadHandler.transferContent (cognitive 26) flow-server/src/main/java/com/vaadin/flow/server/streams/AbstractDownloadHandler.java:262 — AbstractDownloadHandler.transferContent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4, ternaries 3 (4 pts), error handling 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · TranslationFileRequestHandler.getChunkData (cognitive 26) · ×1
  • TranslationFileRequestHandler.getChunkData (cognitive 26) flow-server/src/main/java/com/vaadin/flow/i18n/TranslationFileRequestHandler.java:207 — TranslationFileRequestHandler.getChunkData has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (10 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CleanFrontendUtil.runCleaning (cognitive 26) · ×1
  • CleanFrontendUtil.runCleaning (cognitive 26) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/CleanFrontendUtil.java:70 — CleanFrontendUtil.runCleaning has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (18 pts), error handling 3 (5 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · DevLoopBuildExtension.aliasCompileExecution (cognitive 25) · ×1
  • DevLoopBuildExtension.aliasCompileExecution (cognitive 25) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/mavenext/DevLoopBuildExtension.java:292 — DevLoopBuildExtension.aliasCompileExecution has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexHtmlRequestHandler.synchronizedHandleRequest (cognitive 25) · ×1
  • IndexHtmlRequestHandler.synchronizedHandleRequest (cognitive 25) flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java:108 — IndexHtmlRequestHandler.synchronizedHandleRequest has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 4). 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.
D2 · Cognitive Complexity · VaadinBeanFactoryInitializationAotProcessor.findAndRegisterRoutes (cognitive 25) · ×1
  • VaadinBeanFactoryInitializationAotProcessor.findAndRegisterRoutes (cognitive 25) vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinBeanFactoryInitializationAotProcessor.java:280 — VaadinBeanFactoryInitializationAotProcessor.findAndRegisterRoutes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 5 (11 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.
D2 · Cognitive Complexity · ResourceLoader.loadStylesheet (cognitive 25) · ×1
  • ResourceLoader.loadStylesheet (cognitive 25) flow-client/src/main/frontend/internal/client/ResourceLoader.ts:197 — ResourceLoader.loadStylesheet has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 1 (nesting depth added 13). Of this number, 13 points are the body's own statements and 12 belong to 2 function literals inside it that branch. 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.
D2 · Cognitive Complexity · UidlRequestHandler.removeOffendingMprHashFragment (cognitive 24) · ×1
  • UidlRequestHandler.removeOffendingMprHashFragment (cognitive 24) flow-server/src/main/java/com/vaadin/flow/server/communication/UidlRequestHandler.java:297 — UidlRequestHandler.removeOffendingMprHashFragment has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResponseWriter.parseRanges (cognitive 24) · ×1
  • ResponseWriter.parseRanges (cognitive 24) flow-server/src/main/java/com/vaadin/flow/internal/ResponseWriter.java:230 — ResponseWriter.parseRanges has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (6 pts), boolean chains 3, error handling 1 (2 pts), loops 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.
D2 · Cognitive Complexity · DevLoopRedefiner.inspect (cognitive 24) · ×1
  • DevLoopRedefiner.inspect (cognitive 24) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:475 — DevLoopRedefiner.inspect has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · convert.convertFile (cognitive 24) · ×1
  • convert.convertFile (cognitive 24) flow-polymer2lit/convert.ts:94 — convert.convertFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 101 (183 pts), boolean chains 17, ternaries 6 (15 pts), loops 7 (11 pts), error handling 1 (nesting depth added 95). 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. This shape REPEATS in the file: 3 other methods here (convert.convertFile::modifyClass, convert.convertFile::rewriteElement, convert.convertFile::nullSafe) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AbstractUpdateImports.getUniqueEs6ImportPaths (cognitive 23) · ×1
  • AbstractUpdateImports.getUniqueEs6ImportPaths (cognitive 23) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:710 — AbstractUpdateImports.getUniqueEs6ImportPaths has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6, 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.
D2 · Cognitive Complexity · RouteUtil.updateRouteRegistry (cognitive 23) · ×1
  • RouteUtil.updateRouteRegistry (cognitive 23) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteUtil.java:414 — RouteUtil.updateRouteRegistry has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, if/else 9 (10 pts), ternaries 3 (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.
D2 · Cognitive Complexity · rollup-plugin-vaadin-i18n.vaadinI18n.transform (cognitive 23) · ×1
  • rollup-plugin-vaadin-i18n.vaadinI18n.transform (cognitive 23) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — rollup-plugin-vaadin-i18n.vaadinI18n.transform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). 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.
D2 · Cognitive Complexity · writeThemeFiles (cognitive 23) · ×1
  • writeThemeFiles (cognitive 23) flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:45 — writeThemeFiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 3, other 2 (nesting depth added 5). 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.
D2 · Cognitive Complexity · vaadinI18n.transform (cognitive 23) · ×1
  • vaadinI18n.transform (cognitive 23) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — vaadinI18n.transform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). 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.
D2 · Cognitive Complexity · AtmospherePushConnection.push (cognitive 22) · ×1
  • AtmospherePushConnection.push (cognitive 22) flow-server/src/main/java/com/vaadin/flow/server/communication/AtmospherePushConnection.java:195 — AtmospherePushConnection.push has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexHtmlRequestHandler.isAllowedDevToolsHost (cognitive 22) · ×1
  • IndexHtmlRequestHandler.isAllowedDevToolsHost (cognitive 22) flow-server/src/main/java/com/vaadin/flow/server/communication/IndexHtmlRequestHandler.java:589 — IndexHtmlRequestHandler.isAllowedDevToolsHost has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractFieldSupport.setValue (cognitive 22) · ×1
  • AbstractFieldSupport.setValue (cognitive 22) flow-server/src/main/java/com/vaadin/flow/component/internal/AbstractFieldSupport.java:244 — AbstractFieldSupport.setValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JsDefinitionProxy.checkMethods (cognitive 22) · ×1
  • JsDefinitionProxy.checkMethods (cognitive 22) flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java:253 — JsDefinitionProxy.checkMethods has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 1 (3 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · RouteFormat.hasRequiredParameter (cognitive 22) · ×1
  • RouteFormat.hasRequiredParameter (cognitive 22) flow-server/src/main/java/com/vaadin/flow/router/internal/RouteFormat.java:53 — RouteFormat.hasRequiredParameter has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (15 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResultBuilder.findInsertIndex (cognitive 22) · ×1
  • ResultBuilder.findInsertIndex (cognitive 22) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:311 — ResultBuilder.findInsertIndex has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Hotswapper.computeRefreshStrategy (cognitive 22) · ×1
  • Hotswapper.computeRefreshStrategy (cognitive 22) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/Hotswapper.java:445 — Hotswapper.computeRefreshStrategy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MessageHandler.#processMessage (cognitive 22) · ×1
  • MessageHandler.#processMessage (cognitive 22) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:446 — MessageHandler.#processMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Flow.extractURL (cognitive 22) · ×1
  • Flow.extractURL (cognitive 22) flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:69 — Flow.extractURL has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 8, loops 2, ternaries 1 (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.
D2 · Cognitive Complexity · AbstractUpdateImports.visitImportsRecursively (cognitive 21) · ×1
  • AbstractUpdateImports.visitImportsRecursively (cognitive 21) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:1003 — AbstractUpdateImports.visitImportsRecursively has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · TaskGenerateJsDefinitions.renderFunctions (cognitive 21) · ×1
  • TaskGenerateJsDefinitions.renderFunctions (cognitive 21) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateJsDefinitions.java:518 — TaskGenerateJsDefinitions.renderFunctions has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 4 (7 pts), loops 2, error handling 1 (nesting depth added 10). 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.
D2 · Cognitive Complexity · InputStreamDownloadHandler.handleDownloadRequest (cognitive 21) · ×1
  • InputStreamDownloadHandler.handleDownloadRequest (cognitive 21) flow-server/src/main/java/com/vaadin/flow/server/streams/InputStreamDownloadHandler.java:83 — InputStreamDownloadHandler.handleDownloadRequest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 3, ternaries 2 (nesting depth added 4). 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.
D2 · Cognitive Complexity · DefaultRouteResolver.resolve (cognitive 21) · ×1
  • DefaultRouteResolver.resolve (cognitive 21) flow-server/src/main/java/com/vaadin/flow/router/internal/DefaultRouteResolver.java:44 — DefaultRouteResolver.resolve has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (7 pts), boolean chains 1, error handling 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · Hotswapper.onHotswapInternal (cognitive 21) · ×1
  • Hotswapper.onHotswapInternal (cognitive 21) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/hotswap/Hotswapper.java:283 — Hotswapper.onHotswapInternal has cognitive complexity 21 (threshold 15). Drivers by points: error handling 3 (7 pts), if/else 4 (5 pts), loops 4 (5 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · VaadinDevTools.openWebSocketConnection (cognitive 21) · ×1
  • VaadinDevTools.openWebSocketConnection (cognitive 21) vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:632 — VaadinDevTools.openWebSocketConnection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (onUpdate, onReload, a function literal at line 696, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AnnotatedViewAccessChecker.check (cognitive 20) · ×1
  • AnnotatedViewAccessChecker.check (cognitive 20) flow-server/src/main/java/com/vaadin/flow/server/auth/AnnotatedViewAccessChecker.java:72 — AnnotatedViewAccessChecker.check has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · PushHandler.handleConnectionLost (cognitive 20) · ×1
  • PushHandler.handleConnectionLost (cognitive 20) flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java:471 — PushHandler.handleConnectionLost has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (14 pts), error handling 4, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CssBundler.inlineImports (cognitive 20) · ×1
  • CssBundler.inlineImports (cognitive 20) flow-server/src/main/java/com/vaadin/flow/internal/CssBundler.java:296 — CssBundler.inlineImports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResponseWriter.writeResponseContents (cognitive 20) · ×1
  • ResponseWriter.writeResponseContents (cognitive 20) flow-server/src/main/java/com/vaadin/flow/internal/ResponseWriter.java:125 — ResponseWriter.writeResponseContents has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 3 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · FlowBootstrap.init (cognitive 20) · ×1
  • FlowBootstrap.init (cognitive 20) flow-client/src/main/frontend/FlowBootstrap.js:9 — FlowBootstrap.init has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (8 pts), loops 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 5 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · JSAnnotationVisitor.visitEnd (cognitive 19) · ×1
  • JSAnnotationVisitor.visitEnd (cognitive 19) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendClassVisitor.java:115 — JSAnnotationVisitor.visitEnd has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 3 (6 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.
D2 · Cognitive Complexity · TaskUpdatePackages.flattenOverrides (cognitive 19) · ×1
  • TaskUpdatePackages.flattenOverrides (cognitive 19) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.java:585 — TaskUpdatePackages.flattenOverrides has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (8 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MavenCompile.install (cognitive 19) · ×1
  • MavenCompile.install (cognitive 19) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MavenCompile.java:467 — MavenCompile.install has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (5 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · PublishedServerEventHandlerRpcHandler.decodeArg (cognitive 19) · ×1
  • PublishedServerEventHandlerRpcHandler.decodeArg (cognitive 19) flow-server/src/main/java/com/vaadin/flow/server/communication/rpc/PublishedServerEventHandlerRpcHandler.java:306 — PublishedServerEventHandlerRpcHandler.decodeArg has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 1 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · VaadinAppShellInitializer.init (cognitive 19) · ×1
  • VaadinAppShellInitializer.init (cognitive 19) flow-server/src/main/java/com/vaadin/flow/server/startup/VaadinAppShellInitializer.java:94 — VaadinAppShellInitializer.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (6 pts), boolean chains 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.
D2 · Cognitive Complexity · BeanManagerProvider.getBeanManager (cognitive 19) · ×1
  • BeanManagerProvider.getBeanManager (cognitive 19) vaadin-cdi/src/main/java/com/vaadin/cdi/util/BeanManagerProvider.java:243 — BeanManagerProvider.getBeanManager has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reflector.createIsolatedClassLoader (cognitive 19) · ×1
  • Reflector.createIsolatedClassLoader (cognitive 19) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:281 — Reflector.createIsolatedClassLoader has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 2 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · vaadinI18n.generateBundle (cognitive 19) · ×1
  • vaadinI18n.generateBundle (cognitive 19) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:169 — vaadinI18n.generateBundle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (8 pts), other 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.
D2 · Cognitive Complexity · FrontendDependencies.computeApplicationTheme (cognitive 18) · ×1
  • FrontendDependencies.computeApplicationTheme (cognitive 18) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:700 — FrontendDependencies.computeApplicationTheme has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · ThemeValidationUtil.themeConfigurationChanged (cognitive 18) · ×1
  • ThemeValidationUtil.themeConfigurationChanged (cognitive 18) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ThemeValidationUtil.java:64 — ThemeValidationUtil.themeConfigurationChanged has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · DragSource.setDragImage (cognitive 18) · ×1
  • DragSource.setDragImage (cognitive 18) flow-dnd/src/main/java/com/vaadin/flow/component/dnd/DragSource.java:360 — DragSource.setDragImage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PushHandler.callWithUi (cognitive 18) · ×1
  • PushHandler.callWithUi (cognitive 18) flow-server/src/main/java/com/vaadin/flow/server/communication/PushHandler.java:320 — PushHandler.callWithUi has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 5, boolean chains 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.
D2 · Cognitive Complexity · StyleAttributeHandler.parseStyles (cognitive 18) · ×1
  • StyleAttributeHandler.parseStyles (cognitive 18) flow-server/src/main/java/com/vaadin/flow/dom/impl/StyleAttributeHandler.java:75 — StyleAttributeHandler.parseStyles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, error handling 1, 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.
D2 · Cognitive Complexity · ThemeListImpl.bind (cognitive 18) · ×1
  • ThemeListImpl.bind (cognitive 18) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:161 — ThemeListImpl.bind has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · ClassListView.bind (cognitive 18) · ×1
  • ClassListView.bind (cognitive 18) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:113 — ClassListView.bind has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 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.
D2 · Cognitive Complexity · JacksonSerializer.toJson (cognitive 18) · ×1
  • JacksonSerializer.toJson (cognitive 18) flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:68 — JacksonSerializer.toJson has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (4 pts), error handling 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.
D2 · Cognitive Complexity · AbstractDevServerRunner.serveDevModeRequest (cognitive 18) · ×1
  • AbstractDevServerRunner.serveDevModeRequest (cognitive 18) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/AbstractDevServerRunner.java:770 — AbstractDevServerRunner.serveDevModeRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, loops 1 (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.
D2 · Cognitive Complexity · rollup-plugin-vaadin-i18n.vaadinI18n.generateBundle (cognitive 18) · ×1
  • rollup-plugin-vaadin-i18n.vaadinI18n.generateBundle (cognitive 18) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:169 — rollup-plugin-vaadin-i18n.vaadinI18n.generateBundle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (8 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · theme-loader-utils.assetsContains (cognitive 18) · ×1
  • theme-loader-utils.assetsContains (cognitive 18) flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:12 — theme-loader-utils.assetsContains has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 10). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · SimpleElementBindingStrategy.handleDomEvent (cognitive 18) · ×1
  • SimpleElementBindingStrategy.handleDomEvent (cognitive 18) REDACTED:1229 — SimpleElementBindingStrategy.handleDomEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (5 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.
D2 · Cognitive Complexity · init · ×1
  • init::initApplication (cognitive 18) flow-client/src/main/frontend/FlowBootstrap.js:108 — init::initApplication has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rewriteCssUrls (cognitive 18) · ×1
  • rewriteCssUrls (cognitive 18) flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:68 — rewriteCssUrls has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, if/else 5, other 2 (nesting depth added 3). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 71). 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.
D2 · Cognitive Complexity · AbstractUpdateImports.addCssLines (cognitive 17) · ×1
  • AbstractUpdateImports.addCssLines (cognitive 17) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:928 — AbstractUpdateImports.addCssLines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 2 (4 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · BundleValidationUtil.frontendImportsFound (cognitive 17) · ×1
  • BundleValidationUtil.frontendImportsFound (cognitive 17) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/BundleValidationUtil.java:779 — BundleValidationUtil.frontendImportsFound has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (4 pts), ternaries 2, boolean chains 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.
D2 · Cognitive Complexity · BundleValidationUtil.versionAccepted (cognitive 17) · ×1
  • BundleValidationUtil.versionAccepted (cognitive 17) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/BundleValidationUtil.java:651 — BundleValidationUtil.versionAccepted has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4, ternaries 2 (4 pts), error handling 2 (nesting depth added 2). 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.
D2 · Cognitive Complexity · FrontendToolsLocator.executeCommand (cognitive 17) · ×1
  • FrontendToolsLocator.executeCommand (cognitive 17) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendToolsLocator.java:118 — FrontendToolsLocator.executeCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 3, boolean chains 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.
D2 · Cognitive Complexity · TaskRemoveOldFrontendGeneratedFiles.execute (cognitive 17) · ×1
  • TaskRemoveOldFrontendGeneratedFiles.execute (cognitive 17) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRemoveOldFrontendGeneratedFiles.java:76 — TaskRemoveOldFrontendGeneratedFiles.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (5 pts), 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.
D2 · Cognitive Complexity · DevLoopBuildExtension.apply (cognitive 17) · ×1
  • DevLoopBuildExtension.apply (cognitive 17) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/mavenext/DevLoopBuildExtension.java:697 — DevLoopBuildExtension.apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractAnnotationValidator.validateAnnotatedClasses (cognitive 17) · ×1
  • AbstractAnnotationValidator.validateAnnotatedClasses (cognitive 17) flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractAnnotationValidator.java:149 — AbstractAnnotationValidator.validateAnnotatedClasses has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · UIInternals.showRouteTarget (cognitive 17) · ×1
  • UIInternals.showRouteTarget (cognitive 17) flow-server/src/main/java/com/vaadin/flow/component/internal/UIInternals.java:1184 — UIInternals.showRouteTarget has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, error handling 1 (2 pts), loops 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Element.getProperty (cognitive 17) · ×1
  • Element.getProperty (cognitive 17) flow-server/src/main/java/com/vaadin/flow/dom/Element.java:1183 — Element.getProperty has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 2 (4 pts), error handling 1 (3 pts) (nesting depth added 5). 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.
D2 · Cognitive Complexity · ElementPropertyMap.isUpdateFromClientAllowedByFilter (cognitive 17) · ×1
  • ElementPropertyMap.isUpdateFromClientAllowedByFilter (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.java:361 — ElementPropertyMap.isUpdateFromClientAllowedByFilter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BeanUtil.collectPropertyPaths (cognitive 17) · ×1
  • BeanUtil.collectPropertyPaths (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/BeanUtil.java:245 — BeanUtil.collectPropertyPaths has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 1 (3 pts), ternaries 1 (2 pts), boolean chains 1, 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.
D2 · Cognitive Complexity · CompressUtil.uncompressFile (cognitive 17) · ×1
  • CompressUtil.uncompressFile (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/CompressUtil.java:114 — CompressUtil.uncompressFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 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.
D2 · Cognitive Complexity · FrontendVersion.<init> (cognitive 17) · ×1
  • FrontendVersion.<init> (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/FrontendVersion.java:160 — FrontendVersion.<init> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 3 (4 pts), ternaries 3 (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.
D2 · Cognitive Complexity · JacksonSerializer.toObject (cognitive 17) · ×1
  • JacksonSerializer.toObject (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:193 — JacksonSerializer.toObject has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 2, error handling 2, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · JacksonSerializer.tryToConvertFromSimpleType (cognitive 17) · ×1
  • JacksonSerializer.tryToConvertFromSimpleType (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/JacksonSerializer.java:356 — JacksonSerializer.tryToConvertFromSimpleType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 7. 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.
D2 · Cognitive Complexity · MutableTreeRevision.handleTransaction (cognitive 17) · ×1
  • MutableTreeRevision.handleTransaction (cognitive 17) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:957 — MutableTreeRevision.handleTransaction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FrontendUtils.isHillaViewsUsed (cognitive 17) · ×1
  • FrontendUtils.isHillaViewsUsed (cognitive 17) flow-server/src/main/java/com/vaadin/flow/internal/FrontendUtils.java:1362 — FrontendUtils.isHillaViewsUsed has cognitive complexity 17 (threshold 15). Drivers by points: error handling 3 (7 pts), if/else 4 (7 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ServerInfo.fetchContainerInfo (cognitive 17) · ×1
  • ServerInfo.fetchContainerInfo (cognitive 17) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/ServerInfo.java:185 — ServerInfo.fetchContainerInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), error handling 2, boolean chains 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.
D2 · Cognitive Complexity · FilterableResourceResolver.jarNamePatternMatch (cognitive 17) · ×1
  • FilterableResourceResolver.jarNamePatternMatch (cognitive 17) vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:276 — FilterableResourceResolver.jarNamePatternMatch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VaadinSavedRequestAwareAuthenticationSuccessHandler.onAuthenticationSuccess (cognitive 17) · ×1
  • VaadinSavedRequestAwareAuthenticationSuccessHandler.onAuthenticationSuccess (cognitive 17) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSavedRequestAwareAuthenticationSuccessHandler.java:216 — VaadinSavedRequestAwareAuthenticationSuccessHandler.onAuthenticationSuccess has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · ClientCallableAotProcessor.resolveTypes (cognitive 17) · ×1
  • ClientCallableAotProcessor.resolveTypes (cognitive 17) vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/ClientCallableAotProcessor.java:249 — ClientCallableAotProcessor.resolveTypes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4 (8 pts) (nesting depth added 6). 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.
D2 · Cognitive Complexity · RootExcludeHandler.getHandlerInternal (cognitive 17) · ×1
  • RootExcludeHandler.getHandlerInternal (cognitive 17) vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletConfiguration.java:154 — RootExcludeHandler.getHandlerInternal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · ThemeLiveReloadPlugin.apply (cognitive 17) · ×1
  • ThemeLiveReloadPlugin.apply (cognitive 17) REDACTED:47 — ThemeLiveReloadPlugin.apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 49, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · DataCommunicator.flush (cognitive 16) · ×1
  • DataCommunicator.flush (cognitive 16) flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1252 — DataCommunicator.flush has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · AppLog.report (cognitive 16) · ×1
  • AppLog.report (cognitive 16) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java:347 — AppLog.report has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · AtmospherePushConnection.disconnect (cognitive 16) · ×1
  • AtmospherePushConnection.disconnect (cognitive 16) flow-server/src/main/java/com/vaadin/flow/server/communication/AtmospherePushConnection.java:399 — AtmospherePushConnection.disconnect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 3 (6 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · HasComponentsOfType.replace (cognitive 16) · ×1
  • HasComponentsOfType.replace (cognitive 16) flow-server/src/main/java/com/vaadin/flow/component/HasComponentsOfType.java:351 — HasComponentsOfType.replace has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (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.
D2 · Cognitive Complexity · StateNode.getFeature (cognitive 16) · ×1
  • StateNode.getFeature (cognitive 16) flow-server/src/main/java/com/vaadin/flow/internal/StateNode.java:487 — StateNode.getFeature has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · MutableTreeRevision.handlePositionCondition (cognitive 16) · ×1
  • MutableTreeRevision.handlePositionCondition (cognitive 16) flow-server/src/main/java/com/vaadin/flow/signals/shared/impl/MutableTreeRevision.java:609 — MutableTreeRevision.handlePositionCondition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 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.
D2 · Cognitive Complexity · DevLoopRedefiner.frontendDependencies (cognitive 16) · ×1
  • DevLoopRedefiner.frontendDependencies (cognitive 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1445 — DevLoopRedefiner.frontendDependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 5 (6 pts), ternaries 1 (2 pts), boolean chains 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.
D2 · Cognitive Complexity · DevLoopRedefiner.viteErrorMessage (cognitive 16) · ×1
  • DevLoopRedefiner.viteErrorMessage (cognitive 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1049 — DevLoopRedefiner.viteErrorMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (5 pts), boolean chains 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.
D2 · Cognitive Complexity · DevModeInitializer.getFrontendLocationsFromResourceProvider (cognitive 16) · ×1
  • DevModeInitializer.getFrontendLocationsFromResourceProvider (cognitive 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/startup/DevModeInitializer.java:424 — DevModeInitializer.getFrontendLocationsFromResourceProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 1, 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, 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.
D2 · Cognitive Complexity · DevModeInitializer.initDevModeHandler (cognitive 16) · ×1
  • DevModeInitializer.initDevModeHandler (cognitive 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/startup/DevModeInitializer.java:191 — DevModeInitializer.initDevModeHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), error handling 1 (4 pts), loops 1 (3 pts), ternaries 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · ExternalDependencyWatcher.<init> (cognitive 16) · ×1
  • ExternalDependencyWatcher.<init> (cognitive 16) vaadin-dev-server/src/main/java/com/vaadin/base/devserver/ExternalDependencyWatcher.java:60 — ExternalDependencyWatcher.<init> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VaadinSecurityConfigurer.init (cognitive 16) · ×1
  • VaadinSecurityConfigurer.init (cognitive 16) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/VaadinSecurityConfigurer.java:703 — VaadinSecurityConfigurer.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 2, ternaries 1 (2 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.
D2 · Cognitive Complexity · RouteServletContextListener.failFastContextInitialized (cognitive 16) · ×1
  • RouteServletContextListener.failFastContextInitialized (cognitive 16) vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinServletContextInitializer.java:333 — RouteServletContextListener.failFastContextInitialized has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, error handling 1 (2 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.
D2 · Cognitive Complexity · hotswap-scroll.restoreScrollPositions (cognitive 16) · ×1
  • hotswap-scroll.restoreScrollPositions (cognitive 16) vaadin-dev-server/src/main/frontend/hotswap-scroll.ts:326 — hotswap-scroll.restoreScrollPositions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, loops 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 367, waitForIdleClients, cancel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (59 shared lines) · ×1
  • Near-duplicate member pair (59 shared lines) flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:283 — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:283-390 | flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:307-443 — These two members are variants of one another: 59 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 · Edited copy of a member (64 corresponding lines) · ×1
  • Edited copy of a member (64 corresponding lines) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:336 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:336-403 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:418-481 — These two members are one piece of code written twice and then edited apart: 64 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 (57 corresponding lines) · ×1
  • Edited copy of a member (57 corresponding lines) flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:161 — flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java:161-228 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.java:113-169 — These two members are one piece of code written twice and then edited apart: 57 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 (62 corresponding lines) · ×1
  • Edited copy of a member (62 corresponding lines) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:85 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.java:85-149 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/NpmTemplateParser.java:86-147 — These two members are one piece of code written twice and then edited apart: 62 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 (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:101 — flow-server/src/main/java/com/vaadin/flow/server/streams/ClassDownloadHandler.java:101-141 | flow-server/src/main/java/com/vaadin/flow/server/streams/ServletResourceDownloadHandler.java:89-132 — These two members are one piece of code written twice and then edited apart: 41 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 (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/InjectableLitElementInitializer.java:72 — flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/InjectableLitElementInitializer.java:72-111 | flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/InjectablePolymerElementInitializer.java:54-91 — These two members are one piece of code written twice and then edited apart: 38 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ProxyFactory.java:105 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ProxyFactory.java:105-134 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/ProxyFactory.java:136-162 — These two members are one piece of code written twice and then edited apart: 27 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 (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/ServerPlugin.java:591 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/ServerPlugin.java:591-625 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/ServerPlugin.java:674-709 — These two members are one piece of code written twice and then edited apart: 35 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/Platform.java:81 — flow-server/src/main/java/com/vaadin/flow/server/Platform.java:81-104 | flow-server/src/main/java/com/vaadin/flow/server/Platform.java:113-137 — These two members are one piece of code written twice and then edited apart: 24 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 (5 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 8+ corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:390 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:390-397 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:406-413 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:435-442 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:451-458 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendDependencies.java:466-473 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 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, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/server/streams/TransferProgressAwareHandler.java:167 — flow-server/src/main/java/com/vaadin/flow/server/streams/TransferProgressAwareHandler.java:167-184 | flow-server/src/main/java/com/vaadin/flow/server/streams/TransferProgressAwareHandler.java:286-304 | flow-server/src/main/java/com/vaadin/flow/server/streams/TransferProgressAwareHandler.java:326-344 — 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 (8 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 12+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/AttachNotifier.java:38 — flow-server/src/main/java/com/vaadin/flow/component/AttachNotifier.java:38-49 | flow-server/src/main/java/com/vaadin/flow/component/BlurNotifier.java:43-54 | flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:46-57 | flow-server/src/main/java/com/vaadin/flow/component/FocusNotifier.java:43-54 | flow-server/src/main/java/com/vaadin/flow/component/InputNotifier.java:38-49 | flow-server/src/main/java/com/vaadin/flow/component/KeyNotifier.java:39-50 | flow-server/src/main/java/com/vaadin/flow/component/KeyNotifier.java:60-71 | flow-server/src/main/java/com/vaadin/flow/component/KeyNotifier.java:81-92 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/UI.java:1352 — flow-server/src/main/java/com/vaadin/flow/component/UI.java:1352-1362 | flow-server/src/main/java/com/vaadin/flow/component/UI.java:1411-1418 | flow-server/src/main/java/com/vaadin/flow/component/UI.java:1456-1465 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:600 — flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedListSignal.java:600-606 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedMapSignal.java:402-408 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNodeSignal.java:528-533 | flow-server/src/main/java/com/vaadin/flow/signals/shared/SharedNumberSignal.java:201-206 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java:316 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java:316-328 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java:631-642 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/PnpmWorkspaceFile.java:67-76 — 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 copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/AbstractTemplate.java:89 — flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/AbstractTemplate.java:89-97 | flow-server/src/main/java/com/vaadin/flow/component/Composite.java:83-91 | flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/AbstractServerHandlers.java:256-264 — 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 (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) flow-server/src/main/java/com/vaadin/flow/component/Html.java:157 — flow-server/src/main/java/com/vaadin/flow/component/Html.java:157-176 | flow-server/src/main/java/com/vaadin/flow/component/Html.java:206-220 | flow-server/src/main/java/com/vaadin/flow/component/Svg.java:99-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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 · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:386 — vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:386-410 | vaadin-spring/src/main/java/com/vaadin/flow/spring/security/RequestUtil.java:415-439 — 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:357 — flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:357-377 | flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:438-458 — 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 `flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/BuildFrontendUtil.java:357` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1667 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1667-1682 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1730-1746 — 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 `flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1667` 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. 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:69 — flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:69-82 | flow-server/src/main/java/com/vaadin/flow/component/ClickNotifier.java:94-108 — 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:333 — vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:333-344 | vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:361-374 — 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 `vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:333` 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.
D4 · Code Duplication · Duplicated block (7–13 lines × 2) · ×1
  • Duplicated block (7–13 lines × 2) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:729 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:729-735 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:781-793 — 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.
D4 · Code Duplication · Duplicated block (6–11 lines × 2) · ×1
  • Duplicated block (6–11 lines × 2) flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MavenCompile.java:287 — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MavenCompile.java:287-292 | flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MavenGoalRuntime.java:108-118 — 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.
D4 · Code Duplication · Duplicated block (6–10 lines × 13) · ×1
  • Duplicated block (6–10 lines × 13) flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:745 — flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:745-753 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:754-762 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:763-771 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:772-780 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:781-789 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:790-798 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:799-808 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:809-818 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:819-826 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:827-836 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:837-844 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:845-853 | flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:854-859 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:745` 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, `flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:826` calls `add`, `PwaIcon`, `format` and `flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.java:745` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:171 — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:171-176 | flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:232-238 — 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 `flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:171` 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.
D4 · Code Duplication · Duplicated block (37 lines × 15) · ×1
  • Duplicated block (37 lines × 15) flow-html-components/src/main/java/com/vaadin/flow/component/html/Abbr.java:44 — flow-html-components/src/main/java/com/vaadin/flow/component/html/Abbr.java:44-81 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Code.java:43-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Emphasis.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H1.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H2.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H3.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H4.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H5.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/H6.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/ListItem.java:43-79 | flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeTableHeaderCell.java:42-79 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Paragraph.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Pre.java:43-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Span.java:44-80 | flow-html-components/src/main/java/com/vaadin/flow/component/html/TableDataCell.java:45-90 — 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 15 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) flow-html-components/src/main/java/com/vaadin/flow/component/html/TableBody.java:46 — flow-html-components/src/main/java/com/vaadin/flow/component/html/TableBody.java:46-70 | flow-html-components/src/main/java/com/vaadin/flow/component/html/TableFoot.java:46-70 | flow-html-components/src/main/java/com/vaadin/flow/component/html/TableHead.java:46-70 — 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.
D4 · Code Duplication · Duplicated block (31 lines × 3) · ×1
  • Duplicated block (31 lines × 3) flow-server/src/main/java/com/vaadin/flow/component/KeyDownEvent.java:73 — flow-server/src/main/java/com/vaadin/flow/component/KeyDownEvent.java:73-103 | flow-server/src/main/java/com/vaadin/flow/component/KeyPressEvent.java:73-103 | flow-server/src/main/java/com/vaadin/flow/component/KeyUpEvent.java:73-103 — before extracting anything, compare `flow-server/src/main/java/com/vaadin/flow/component/KeyDownEvent.java` and `flow-server/src/main/java/com/vaadin/flow/component/KeyPressEvent.java` as WHOLE FILES: 93% 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 1 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. 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 `flow-server/src/main/java/com/vaadin/flow/component/KeyDownEvent.java:73` 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeLabel.java:121 — flow-html-components/src/main/java/com/vaadin/flow/component/html/NativeLabel.java:121-128 | flow-server/src/main/java/com/vaadin/flow/component/HasAriaDescription.java:88-96 | flow-server/src/main/java/com/vaadin/flow/component/HasAriaLabel.java:131-139 — 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 `flow-server/src/main/java/com/vaadin/flow/component/HasAriaDescription.java:88` 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) flow-html-components/src/main/java/com/vaadin/flow/component/html/Source.java:105 — flow-html-components/src/main/java/com/vaadin/flow/component/html/Source.java:105-111 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Source.java:167-173 | flow-html-components/src/main/java/com/vaadin/flow/component/html/Video.java:87-93 — 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.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:29 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:29-37 | flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:35-65 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:36-52 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:44-96 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:36-52 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:42-94 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:29-37 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:40-71 — These 8 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 8 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 8 times.
D4 · Code Duplication · Edited copy of a member (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:29 — flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:29-88 | flow-tests/test-redeployment/src/main/java/com/vaadin/flow/uitest/ui/DevModeClassCacheView.java:29-88 — These two members are one piece of code written twice and then edited apart: 60 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:30 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/RouterLinkView.java:30-60 | flow-tests/test-vaadin-router/src/main/java/com/vaadin/flow/RouterLinkView.java:31-61 — 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 · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:46 — flow-tests/test-frontend/vite-basics/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:46-88 | flow-tests/test-frontend/vite-production/src/main/java/com/vaadin/viteapp/views/empty/MainView.java:45-76 — These two members are one piece of code written twice and then edited apart: 32 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 (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:171 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:171-174 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:171-174 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:171-174 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:239-242 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (32 lines × 4) · ×1
  • Duplicated block (32 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:32 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:32-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:32-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:32-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java:32-63 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/LoginView.java` as WHOLE FILES: 100% 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 1 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.
D4 · Code Duplication · Duplicated block (29 lines × 3) · ×1
  • Duplicated block (29 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:86 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:86-114 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:94-122 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:94-122 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:86` 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.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:37 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:37-63 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:46-72 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:44-70 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:37` 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.
D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:104 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:104-129 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:102-127 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:105-130 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:53 — flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:53-73 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:51-71 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:54-74 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:111 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:111-129 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:110-128 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:166-184 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:148-166 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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. 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorCustomMessagesServlet.java:41 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorCustomMessagesServlet.java:41-58 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorServlet.java:39-57 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorSilentReloadServlet.java:41-58 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorCustomMessagesServlet.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/SyncErrorServlet.java` as WHOLE FILES: 89% 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 1 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. 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. 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.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:61 — flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:61-76 | flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:73-90 — before extracting anything, compare `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java` and `flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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 `flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:73` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:78` calls `add`, `Div` and `flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:91` 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.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×1
  • Duplicated block (14–17 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:132 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:132-148 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/components/NativeRadioButtonGroup.java:54-67 — 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:132` 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 after the matched lines, `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/components/NativeRadioButtonGroup.java:69` calls `addValueChangeListener`, `add` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/JavaScriptReturnValueView.java:149` 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:53 — flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java:53-68 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/i18n/TranslationView.java:53-68 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/i18n/TranslationView.java:52-67 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/TranslationView.java:43-58 — before extracting anything, compare `flow-tests/test-misc/src/main/java/com/vaadin/flow/misc/ui/TranslationView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/TranslationView.java` as WHOLE FILES: 85% 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 1 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:50 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:50-64 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:46-60 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:46-60 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java:61-75 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 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 `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/MainView.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.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:59 — flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java:59-72 | flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:61-75 | flow-tests/test-themes/src/main/java/com/vaadin/flow/uitest/ui/theme/ThemeView.java:75-89 — before extracting anything, compare `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.java` and `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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 `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:61` 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, `flow-tests/test-application-theme/test-theme-reusable-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ReusableThemeView.java:59` calls `add` and `flow-tests/test-application-theme/test-reusable-as-parent-vite/src/main/java/com/vaadin/flow/uitest/ui/theme/ParentThemeView.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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:68 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:68-80 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:64-76 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:150-162 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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. 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:34 — flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:34-45 | flow-tests/test-embedding/test-embedding-reusable-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:33-44 | flow-tests/test-express-build/test-embedding-express-build/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:33-44 — before extracting anything, compare `flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java` and `flow-tests/test-embedding/test-embedding-reusable-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java` as WHOLE FILES: 100% 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 1 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flow-tests/test-embedding/test-embedding-application-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.java:46` calls `add`, `CssImportComponent` and `flow-tests/test-embedding/test-embedding-reusable-theme/src/main/java/com/vaadin/flow/webcomponent/ThemedComponent.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.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×1
  • Duplicated block (9–10 lines × 5) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:32 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:32-40 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:33-41 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:31-39 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:43-52 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/RolePrefixedAdminView.java:32-40 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java` as WHOLE FILES: 86% 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 1 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:29` calls `Menu` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AdminView.java:27` 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.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:40 — flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:40-48 | flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:49-57 | flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:58-67 | flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:68-77 | flow-tests/test-redeployment/src/main/java/com/vaadin/flow/uitest/ui/DevModeClassCacheView.java:43-51 — there are 5 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 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 `flow-tests/test-redeployment-no-cache/src/main/java/com/vaadin/flow/uitest/ui/DevModeNoClassCacheView.java:40` 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.
D4 · Code Duplication · Duplicated block (7 lines × 8) · ×1
  • Duplicated block (7 lines × 8) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30-36 | flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:36-42 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:37-43 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:45-51 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:37-43 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:43-49 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java:30-36 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PublicView.java:41-47 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/AnotherPublicView.java` as WHOLE FILES: 100% 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:45 — flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:45-51 | flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:44-50 | flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/PolymerIdTestView.java:38-44 | flow-tests/test-frontend/test-pnpm/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java:44-50 | flow-tests/test-frontend/test-pnpm/src/main/java/com/vaadin/flow/mixedtest/ui/PolymerIdTestView.java:38-44 — before extracting anything, compare `flow-tests/test-frontend/test-bun/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.java` and `flow-tests/test-frontend/test-npm/src/main/java/com/vaadin/flow/mixedtest/ui/IdTestView.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 1 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.
D4 · Code Duplication · Duplicated block (34 lines × 4) · ×1
  • Duplicated block (34 lines × 4) flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginForm.java:37 — flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginForm.java:37-70 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/LoginForm.java:37-70 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-wsxhr/src/main/java/com/vaadin/viteapp/LoginForm.java:37-70 | flow-tests/test-frontend/vite-embedded-webcomponent-resync/src/main/java/com/vaadin/viteapp/LoginForm.java:37-70 — before extracting anything, compare `flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginForm.java` and `flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/LoginForm.java` as WHOLE FILES: 100% 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 1 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginFormExporter.java:25 — flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginFormExporter.java:25-34 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/LoginFormExporter.java:25-34 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-wsxhr/src/main/java/com/vaadin/viteapp/LoginFormExporter.java:25-34 | flow-tests/test-frontend/vite-embedded-webcomponent-resync/src/main/java/com/vaadin/viteapp/LoginFormExporter.java:22-31 — before extracting anything, compare `flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/LoginFormExporter.java` and `flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/LoginFormExporter.java` as WHOLE FILES: 96% 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 1 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.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/UserService.java:24 — flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/UserService.java:24-41 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/UserService.java:24-41 | flow-tests/test-frontend/vite-embedded-webcomponent-resync-wsxhr/src/main/java/com/vaadin/viteapp/UserService.java:24-41 | flow-tests/test-frontend/vite-embedded-webcomponent-resync/src/main/java/com/vaadin/viteapp/UserService.java:24-41 — before extracting anything, compare `flow-tests/test-frontend/vite-embedded-webcomponent-resync-longpolling/src/main/java/com/vaadin/viteapp/UserService.java` and `flow-tests/test-frontend/vite-embedded-webcomponent-resync-ws/src/main/java/com/vaadin/viteapp/UserService.java` as WHOLE FILES: 100% 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 1 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DynamicPageTitleView.java:1 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DynamicPageTitleView.java:1-43 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TitleView.java:1-34 — 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/DynamicPageTitleView.java:1` 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.
D4 · Code Duplication · Duplicated block (32 lines × 6) · ×1
  • Duplicated block (32 lines × 6) flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushLongPollingView.java:1 — flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushLongPollingView.java:1-33 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushSseView.java:1-34 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushWebsocketView.java:1-34 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushWebsocketXhrView.java:1-34 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/PushLargeDataLongPollingView.java:1-32 | flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/PushLargeDataWebsocketView.java:1-32 — before extracting anything, compare `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushLongPollingView.java` and `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushSseView.java` as WHOLE FILES: 82% 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 1 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. 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 `flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/push/BasicPushLongPollingView.java:1` 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.
D4 · Code Duplication · Duplicated block (57 lines × 2) · ×1
  • Duplicated block (57 lines × 2) flow-tests/test-router-custom-context/src/main/java/com/vaadin/flow/contexttest/ui/PathLayout.java:1 — flow-tests/test-router-custom-context/src/main/java/com/vaadin/flow/contexttest/ui/PathLayout.java:1-66 | flow-tests/test-router-custom-context/src/main/java/com/vaadin/flow/contexttest/ui/RootContextLayout.java:1-57 — 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 `flow-tests/test-router-custom-context/src/main/java/com/vaadin/flow/contexttest/ui/PathLayout.java:1` 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/beandiscoverymode/CdiComponentGreetService.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/beandiscoverymode/CdiComponentGreetService.java:1-32 | flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/beandiscoverymode/NormalScopedGreetService.java:1-30 — 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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/beandiscoverymode/CdiComponentGreetService.java:1` 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.
D4 · Code Duplication · Duplicated block (71 lines × 2) · ×1
  • Duplicated block (71 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/EventView.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/EventView.java:1-74 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/EventView.java:1-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 `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/EventView.java:1` 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 first that the copies are not typed on the same thing: `RouteScopeOwner` names `com.vaadin.cdi.annotation.RouteScopeOwner` in one and `com.vaadin.quarkus.annotation.RouteScopeOwner` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (51 lines × 2) · ×1
  • Duplicated block (51 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/PostponeView.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/PostponeView.java:1-53 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/PostponeView.java:1-51 — before extracting anything, compare `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/PostponeView.java` and `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/routecontext/PostponeView.java` as WHOLE FILES: 85% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/routecontext/PostponeView.java:1` 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 first that the copies are not typed on the same thing: `RouteScoped` names `com.vaadin.cdi.annotation.RouteScoped` in one and `com.vaadin.quarkus.annotation.RouteScoped` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uievents/NavigationObserver.java:1 — flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uievents/NavigationObserver.java:1-49 | flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/uievents/NavigationObserver.java:1-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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-cdi-tests/src/main/java/com/vaadin/cdi/itest/uievents/NavigationObserver.java:1` 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. Note first that the copies are not typed on the same thing: `VaadinSessionScoped` names `com.vaadin.cdi.annotation.VaadinSessionScoped` in one and `com.vaadin.quarkus.annotation.VaadinSessionScoped` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/clientcallable/ClientCallableView.java:1 — flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/clientcallable/ClientCallableView.java:1-54 | flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ClientCallableView.java:1-54 — before extracting anything, compare `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/clientcallable/ClientCallableView.java` and `flow-tests/vaadin-spring-tests/test-spring-native/src/main/java/com/example/application/ClientCallableView.java` as WHOLE FILES: 90% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/clientcallable/ClientCallableView.java:1` 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.
D4 · Code Duplication · Duplicated block (47 lines × 4) · ×1
  • Duplicated block (47 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1-49 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1-49 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1-49 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1-47 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityUtils.java:1` 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.
D4 · Code Duplication · Duplicated block (63 lines × 4) · ×1
  • Duplicated block (63 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33-95 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33-95 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33-95 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33-95 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/data/UserInfo.java:33` 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. 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java:35 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java:35-46 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java:35-46 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java:35-46 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java:35-46 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/service/UserInfoService.java` as WHOLE FILES: 100% 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 1 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.
D4 · Code Duplication · Duplicated block (44 lines × 3) · ×1
  • Duplicated block (44 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java:1 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java:1-44 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java:1-44 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java:1-44 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/Broadcaster.java:1` 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.
D4 · Code Duplication · Duplicated block (36 lines × 3) · ×1
  • Duplicated block (36 lines × 3) flow-tests/vaadin-spring-tests/test-spring-security-pwa/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1 — flow-tests/vaadin-spring-tests/test-spring-security-pwa/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1-36 | flow-tests/vaadin-spring-tests/test-spring-security-webicons-urlmapping/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1-36 | flow-tests/vaadin-spring-tests/test-spring-security-webicons/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1-36 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-pwa/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` and `flow-tests/vaadin-spring-tests/test-spring-security-webicons-urlmapping/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java` as WHOLE FILES: 100% 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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `flow-tests/vaadin-spring-tests/test-spring-security-pwa/src/main/java/com/vaadin/flow/spring/flowsecurity/SecurityConfig.java:1` 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:81 — flow-tests/vaadin-spring-tests/test-spring-security-flow-methodsecurity/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:81-87 | flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:76-82 | flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:74-80 | flow-tests/vaadin-spring-tests/test-spring-security-flow/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java:77-83 — before extracting anything, compare `flow-tests/vaadin-spring-tests/test-spring-security-flow-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` and `flow-tests/vaadin-spring-tests/test-spring-security-flow-standalone-routepathaccesschecker/src/main/java/com/vaadin/flow/spring/flowsecurity/views/PrivateView.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D44 · Platform End-of-Life · End-of-life framework · ×1
  • End-of-life framework: Spring Boot 2 vaadin-dev-server/src/test/resources/stats-data/maven-project-folder1/pom.xml:1 — vaadin-dev-server/src/test/resources/stats-data/maven-project-folder1/pom.xml depends on `org.springframework.boot` at a version that pins Spring Boot 2, and Spring Boot 2.x, open-source support ended 2023-11-24. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the web-test-runner suite in flow-client/ ran and not one test passed (TypeError: Failed to resolve module specifier "@open-wc/testing". Relative references must start with either "/", "./", or "../".), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — empty body under a TODO marker flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/NodeList.java:354 — `setAccessed` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it.
P12 · CI test-gate honesty · Test failure does not fail the CI gate · ×1
  • Test failure does not fail the CI gate REDACTED:508 — `mvn -B -ntp -e -pl flow-tests/vaadin-cdi-tests verify >"$LOG" 2>&1 || {` runs the tests, and `|| {` discards their exit status — a failing suite leaves the check green. Let the test command's failure fail the step (re-raise it after logging).
R10 · Code Duplication · Duplicated block with local edits (118 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (118 matched lines × 2 locations) flow-client/src/main/frontend/FlowBootstrap.js:28 — flow-client/src/main/frontend/FlowBootstrap.js:28 · flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:16 — the two spans are one implementation copied and then locally edited — 731 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (32 matched lines × 2 locations) flow-client/src/main/frontend/internal/client/communication/VaadinRequest.ts:107 — flow-client/src/main/frontend/internal/client/communication/VaadinRequest.ts:107 · flow-client/src/main/frontend/internal/client/communication/VaadinServerMessage.ts:85 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (21 matched lines × 2 locations) flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:118 — flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:118 · flow-client/src/main/frontend/internal/client/communication/XhrConnection.ts:199 — the two spans are one implementation copied and then locally edited — 101 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (20 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (20 matched lines × 2 locations) flow-client/src/main/frontend/internal/Timer.ts:26 — flow-client/src/main/frontend/internal/Timer.ts:26 · flow-client/src/main/frontend/internal/client/communication/Heartbeat.ts:32 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) vaadin-dev-server/src/main/frontend/live-reload-connection.ts:23 — vaadin-dev-server/src/main/frontend/live-reload-connection.ts:23 · vaadin-dev-server/src/main/frontend/websocket-connection.ts:66 — 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.
R10 · Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (15 matched lines × 2 locations) flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:131 — flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:131 · flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:158 — the two spans are one implementation copied and then locally edited — 107 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.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) vaadin-dev-server/src/main/frontend/License.ts:146 — vaadin-dev-server/src/main/frontend/License.ts:146 · vaadin-dev-server/src/main/frontend/License.ts:166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:135 — flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:135 · flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:158 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) flow-client/src/main/frontend/internal/client/UILifecycle.ts:26 — flow-client/src/main/frontend/internal/client/UILifecycle.ts:26 · flow-client/src/main/frontend/internal/client/communication/ConnectionMessageType.ts:22 — 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.
R10 · Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (12 matched lines × 2 locations) REDACTED:286 — REDACTED:286 · REDACTED:1654 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (10 matched lines × 2 locations) flow-client/src/main/frontend/internal/client/ExecuteJavaScriptElementUtils.ts:81 — flow-client/src/main/frontend/internal/client/ExecuteJavaScriptElementUtils.ts:81 · REDACTED:926 — the two spans are one implementation copied and then locally edited — 71 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (9 lines × 3 locations) · ×1
  • Duplicated block (9 lines × 3 locations) flow-client/src/main/frontend/internal/client/ResourceLoader.ts:113 — flow-client/src/main/frontend/internal/client/ResourceLoader.ts:113 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:164 · flow-client/src/main/frontend/internal/client/ResourceLoader.ts:313 — 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 (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:162 — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:162 · flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:110 — 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.
R10 · Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (6 matched lines × 2 locations) flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js:52 — flow-build-tools/src/main/resources/plugins/rollup-plugin-postcss-lit-custom/rollup-plugin-postcss-lit.js:52 · flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:64 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (6 lines × 4 locations) · ×1
  • Duplicated block (6 lines × 4 locations) flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:94 — flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:94 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:114 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:141 · flow-client/src/main/frontend/internal/client/communication/ServerConnector.ts:168 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1
  • Duplicated block (6 lines × 2 locations) flow-polymer2lit/convert.ts:343 — flow-polymer2lit/convert.ts:343 · flow-polymer2lit/convert.ts:357 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×1
  • Duplicated block (5 lines × 2 locations) flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:68 — flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:68 · flow-dnd/src/main/resources/META-INF/frontend/dndConnector.js:73 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function #parseBrowserVersion (cyclomatic 36, cognitive 50) · ×1
  • Complex function #parseBrowserVersion (cyclomatic 36, cognitive 50) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:232 — #parseBrowserVersion has cyclomatic complexity 36 and cognitive complexity 50; 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.
R2 · Cyclomatic Complexity · Complex function logTimings (cyclomatic 24, cognitive 45) · ×1
  • Complex function logTimings (cyclomatic 24, cognitive 45) flow-client/src/main/frontend/internal/client/Profiler.ts:398 — logTimings has cyclomatic complexity 24 and cognitive complexity 45; 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.
R2 · Cyclomatic Complexity · Complex function rewriteElement (cyclomatic 24, cognitive 44) · ×1
  • Complex function rewriteElement (cyclomatic 24, cognitive 44) flow-polymer2lit/convert.ts:342 — rewriteElement has cyclomatic complexity 24 and cognitive complexity 44; 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.
R2 · Cyclomatic Complexity · Complex function modifyClass (cyclomatic 24, cognitive 34) · ×1
  • Complex function modifyClass (cyclomatic 24, cognitive 34) flow-polymer2lit/convert.ts:118 — modifyClass has cyclomatic complexity 24 and cognitive complexity 34; 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.
R2 · Cyclomatic Complexity · Complex function extractURL (cyclomatic 24, cognitive 22) · ×1
  • Complex function extractURL (cyclomatic 24, cognitive 22) flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:69 — extractURL has cyclomatic complexity 24 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function #handleJSON (cyclomatic 21, cognitive 31) · ×1
  • Complex function #handleJSON (cyclomatic 21, cognitive 31) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:288 — #handleJSON has cyclomatic complexity 21 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.
R2 · Cyclomatic Complexity · Complex function convertFile (cyclomatic 19, cognitive 24) · ×1
  • Complex function convertFile (cyclomatic 19, cognitive 24) flow-polymer2lit/convert.ts:94 — convertFile has cyclomatic complexity 19 and cognitive complexity 24; 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.
R2 · Cyclomatic Complexity · Complex function writeThemeFiles (cyclomatic 19, cognitive 23) · ×1
  • Complex function writeThemeFiles (cyclomatic 19, cognitive 23) flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:45 — writeThemeFiles has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 20) flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:73 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function #processMessage (cyclomatic 18, cognitive 22) · ×1
  • Complex function #processMessage (cyclomatic 18, cognitive 22) flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:446 — #processMessage has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function splitExpression (cyclomatic 17, cognitive 33) · ×1
  • Complex function splitExpression (cyclomatic 17, cognitive 33) flow-polymer2lit/convert.ts:50 — splitExpression has cyclomatic complexity 17 and cognitive complexity 33; 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.
R2 · Cyclomatic Complexity · Complex function #parseBrowserName (cyclomatic 17, cognitive 14) · ×1
  • Complex function #parseBrowserName (cyclomatic 17, cognitive 14) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:170 — #parseBrowserName has cyclomatic complexity 17 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.
R2 · Cyclomatic Complexity · Complex function buildDigest (cyclomatic 16, cognitive 23) · ×1
  • Complex function buildDigest (cyclomatic 16, cognitive 23) scripts/releaseDigest.js:155 — buildDigest has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function collectBrowserDetails (cyclomatic 16, cognitive 20) · ×1
  • Complex function collectBrowserDetails (cyclomatic 16, cognitive 20) flow-client/src/main/frontend/BrowserHelpers.ts:42 — collectBrowserDetails has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function isTooOldToFunctionProperly (cyclomatic 16, cognitive 16) · ×1
  • Complex function isTooOldToFunctionProperly (cyclomatic 16, cognitive 16) flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:817 — isTooOldToFunctionProperly has cyclomatic complexity 16 and cognitive complexity 16; 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.
R2 · Cyclomatic Complexity · Complex function decodeWithTypeInfo (cyclomatic 15, cognitive 28) · ×1
  • Complex function decodeWithTypeInfo (cyclomatic 15, cognitive 28) flow-client/src/main/frontend/internal/client/flow/util/ClientJsonCodec.ts:269 — decodeWithTypeInfo has cyclomatic complexity 15 and cognitive complexity 28; 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.
R2 · Cyclomatic Complexity · Complex function onKeypress (cyclomatic 15, cognitive 19) · ×1
  • Complex function onKeypress (cyclomatic 15, cognitive 19) scripts/findMissingPrs.js:195 — onKeypress has cyclomatic complexity 15 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function comment (cyclomatic 14, cognitive 21) · ×1
  • Complex function comment (cyclomatic 14, cognitive 21) scripts/memoryFootprint.js:165 — comment has cyclomatic complexity 14 and cognitive complexity 21; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 17) flow-build-tools/src/main/resources/plugins/theme-loader/theme-loader-utils.js:71 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 17; 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.
R2 · Cyclomatic Complexity · Complex function trigger (cyclomatic 14, cognitive 15) · ×1
  • Complex function trigger (cyclomatic 14, cognitive 15) flow-client/src/main/frontend/internal/client/flow/binding/Debouncer.ts:82 — trigger has cyclomatic complexity 14 and cognitive complexity 15; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 24) flow-polymer2lit/convert.ts:214 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 24; 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.
R2 · Cyclomatic Complexity · Complex function handleDomEvent (cyclomatic 13, cognitive 21) · ×1
  • Complex function handleDomEvent (cyclomatic 13, cognitive 21) REDACTED:1229 — handleDomEvent has cyclomatic complexity 13 and cognitive complexity 21; 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.
R2 · Cyclomatic Complexity · Complex function initApplication (cyclomatic 12, cognitive 18) · ×1
  • Complex function initApplication (cyclomatic 12, cognitive 18) flow-client/src/main/frontend/FlowBootstrap.js:108 — initApplication has cyclomatic complexity 12 and cognitive complexity 18; 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.
R2 · Cyclomatic Complexity · Complex function init (cyclomatic 12, cognitive 12) · ×1
  • Complex function init (cyclomatic 12, cognitive 12) flow-client/src/main/frontend/FlowBootstrap.js:9 — init has cyclomatic complexity 12 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function invokeFromBundle (cyclomatic 12, cognitive 11) · ×1
  • Complex function invokeFromBundle (cyclomatic 12, cognitive 11) flow-client/src/main/frontend/internal/client/flow/ExecuteJavaScriptProcessor.ts:292 — invokeFromBundle has cyclomatic complexity 12 and cognitive complexity 11; 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.
R2 · Cyclomatic Complexity · Complex function nullSafe (cyclomatic 11, cognitive 28) · ×1
  • Complex function nullSafe (cyclomatic 11, cognitive 28) flow-polymer2lit/convert.ts:770 — nullSafe has cyclomatic complexity 11 and cognitive complexity 28; 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.
R2 · Cyclomatic Complexity · Complex function updateAttributeValue (cyclomatic 11, cognitive 15) · ×1
  • Complex function updateAttributeValue (cyclomatic 11, cognitive 15) REDACTED:1467 — updateAttributeValue has cyclomatic complexity 11 and cognitive complexity 15; 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.
R2 · Cyclomatic Complexity · Complex function acquire (cyclomatic 11, cognitive 14) · ×1
  • Complex function acquire (cyclomatic 11, cognitive 14) flow-client/src/main/frontend/WakeLock.ts:42 — acquire has cyclomatic complexity 11 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 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.
R2 · Cyclomatic Complexity · Complex function #sendPayload (cyclomatic 11, cognitive 14) · ×1
  • Complex function #sendPayload (cyclomatic 11, cognitive 14) flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:282 — #sendPayload has cyclomatic complexity 11 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 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.
R2 · Cyclomatic Complexity · Complex function populateApplicationConfiguration (cyclomatic 11, cognitive 11) · ×1
  • Complex function populateApplicationConfiguration (cyclomatic 11, cognitive 11) flow-client/src/main/frontend/internal/client/bootstrap/Bootstrapper.ts:72 — populateApplicationConfiguration has cyclomatic complexity 11 and cognitive complexity 11; 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 · REDACTED · ×1
  • REDACTED: 1677 lines of code REDACTED:1 — REDACTED has 1677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts · ×1
  • flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts: 789 lines of code flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:1 — flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts has 789 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-polymer2lit/convert.ts · ×1
  • flow-polymer2lit/convert.ts: 788 lines of code flow-polymer2lit/convert.ts:1 — flow-polymer2lit/convert.ts has 788 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts · ×1
  • vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts: 784 lines of code vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:1 — vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts has 784 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts · ×1
  • flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts: 732 lines of code flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts:1 — flow-client/src/main/frontend/internal/client/communication/MessageHandler.ts has 732 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx · ×1
  • flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx: 664 lines of code flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx:1 — flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx has 664 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/communication/MessageSender.ts · ×1
  • flow-client/src/main/frontend/internal/client/communication/MessageSender.ts: 574 lines of code flow-client/src/main/frontend/internal/client/communication/MessageSender.ts:1 — flow-client/src/main/frontend/internal/client/communication/MessageSender.ts has 574 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts · ×1
  • vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts: 566 lines of code vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts:1 — vaadin-dev-server/src/main/frontend/pre-trial-splash-screen.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/Profiler.ts · ×1
  • flow-client/src/main/frontend/internal/client/Profiler.ts: 558 lines of code flow-client/src/main/frontend/internal/client/Profiler.ts:1 — flow-client/src/main/frontend/internal/client/Profiler.ts has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts · ×1
  • flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts: 509 lines of code flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts:1 — flow-client/src/main/frontend/internal/client/communication/AtmospherePushConnection.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/ConnectionIndicator.ts · ×1
  • flow-client/src/main/frontend/ConnectionIndicator.ts: 490 lines of code flow-client/src/main/frontend/ConnectionIndicator.ts:1 — flow-client/src/main/frontend/ConnectionIndicator.ts has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/Flow.ts · ×1
  • flow-client/src/main/frontend/Flow.ts: 483 lines of code flow-client/src/main/frontend/Flow.ts:1 — flow-client/src/main/frontend/Flow.ts has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/ResourceLoader.ts · ×1
  • flow-client/src/main/frontend/internal/client/ResourceLoader.ts: 481 lines of code flow-client/src/main/frontend/internal/client/ResourceLoader.ts:1 — flow-client/src/main/frontend/internal/client/ResourceLoader.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · vaadin-dev-server/src/main/frontend/hotswap-scroll.ts · ×1
  • vaadin-dev-server/src/main/frontend/hotswap-scroll.ts: 465 lines of code vaadin-dev-server/src/main/frontend/hotswap-scroll.ts:1 — vaadin-dev-server/src/main/frontend/hotswap-scroll.ts has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · flow-client/src/main/frontend/internal/client/flow/StateTree.ts · ×1
  • flow-client/src/main/frontend/internal/client/flow/StateTree.ts: 401 lines of code flow-client/src/main/frontend/internal/client/flow/StateTree.ts:1 — flow-client/src/main/frontend/internal/client/flow/StateTree.ts has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · This package's lint script runs in no CI job · ×1
  • This package's lint script runs in no CI job flow-client/package.json:12 — The package in `flow-client` declares the lint script `lint` (`eslint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `flow-client` (or the workspace's task runner).
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js:4 — This repository declares test tooling, and the ✓ above records that declaration — but flow-polymer2lit/src/test/resources/frontend/expected/order-card-from-bakery.js and 1 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~30 LoC) · ×1
  • Dead file (~30 LoC) vaadin-dev-server/export-metadata-script.ts — no import path from any entry point (119 application, 23 tooling, 157 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
R7 · Dead Code · Dead file (~19 LoC) · ×1
  • Dead file (~19 LoC) flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/fake-resources/com/vaadin/flow/server/frontend/Flow.tsx — no import path from any entry point (119 application, 23 tooling, 157 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
R7 · Dead Code · Dead file (~18 LoC) · ×1
  • Dead file (~18 LoC) flow-plugins/flow-maven-plugin/src/it/flow-addon/src/main/fake-plugin-resources/com/vaadin/flow/server/frontend/Flow.tsx — no import path from any entry point (119 application, 23 tooling, 157 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
R8 · Dependency Hygiene · Unlisted import 'lit' · ×1
  • Unlisted import 'lit' flow-server/src/main/resources/com/vaadin/flow/server/frontend/types.d.ts:7 — 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.
R8 · Dependency Hygiene · Unused dependency 'acorn-walk' · ×1
  • Unused dependency 'acorn-walk' flow-polymer2lit/package.json:21 — Declared in flow-polymer2lit/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.
R8 · Dependency Hygiene · Unused dependency 'patch-package' · ×1
  • Unused dependency 'patch-package' flow-polymer2lit/package.json:23 — Declared in flow-polymer2lit/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.
R8 · Dependency Hygiene · Unused dependency 'workbox-build' · ×1
  • Unused dependency 'workbox-build' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:5 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/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.
R8 · Dependency Hygiene · Unused dependency 'workbox-core' · ×1
  • Unused dependency 'workbox-core' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:6 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'workbox-routing' · ×1
  • Unused dependency 'workbox-routing' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:8 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'workbox-strategies' · ×1
  • Unused dependency 'workbox-strategies' flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json:9 — Declared in flow-server/src/main/resources/com/vaadin/flow/server/frontend/dependencies/workbox/package.json but never imported anywhere in that package or its workspace members — while flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'copy-to-clipboard' · ×1
  • Unused dependency 'copy-to-clipboard' flow-tests/test-frontend/vite-basics/package.json:18 — Declared in flow-tests/test-frontend/vite-basics/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.
X12 · Unreachable branch · Branch is unreachable · ×1
  • Branch is unreachable — its condition cannot hold here flow-data/src/main/java/com/vaadin/flow/data/provider/DataCommunicator.java:1290 — `ui == null` can never be true where it stands: control only reaches it when `ui != null` (line 1279). The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Minor — 352 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×208
  • Orphaned file flow-server/src/main/java/com/vaadin/flow/internal/Range.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 flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.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 flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/TemplateDataAnalyzer.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 vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/vaadinplugin/VaadinBuildTimeConfig.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 flow-server/src/main/java/com/vaadin/flow/server/webcomponent/WebComponentModulesWriter.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 flow-server/src/main/java/com/vaadin/flow/router/internal/HasUrlParameterFormat.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 vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringLookupInitializer.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 flow-server/src/main/java/com/vaadin/flow/internal/AnnotationReader.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 flow-data/src/main/java/com/vaadin/flow/data/selection/SelectionModel.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 flow-server/src/main/java/com/vaadin/flow/server/StreamResource.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 flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/GenerateMavenBOMMojo.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 flow-server/src/main/java/com/vaadin/flow/server/PwaConfiguration.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 flow-lit-template/src/main/java/com/vaadin/flow/component/littemplate/internal/LitTemplateParserImpl.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 flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/FrontendToolsLocator.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 flow-server/src/main/java/com/vaadin/flow/router/internal/RouteModel.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 flow-server/src/main/java/com/vaadin/flow/server/startup/LookupServletContainerInitializer.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 flow-dnd/src/main/java/com/vaadin/flow/component/dnd/DropTarget.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 flow-server/src/main/java/com/vaadin/flow/server/startup/AbstractAnnotationValidator.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 flow-test-generic/src/main/java/com/vaadin/flow/testutil/ClassFinder.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 vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringInstantiator.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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/InertData.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 vaadin-cdi/src/main/java/com/vaadin/cdi/DeploymentValidator.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 flow-data/src/main/java/com/vaadin/flow/data/binder/ValueContext.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 flow-server/src/main/java/com/vaadin/flow/component/template/internal/IdCollector.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 flow-server/src/main/java/com/vaadin/flow/dom/impl/ShadowRootStateProvider.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.
  • + 183 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×38
  • Duplicated predicate flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1191 — `!constructor.isPresent() || !Modifier.isPublic(constructor.get().getModifiers())` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java, flow-server/src/main/java/com/vaadin/flow/server/webcomponent/WebComponentExporterUtils.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 flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java:304 — `!lower.startsWith("http://") && !lower.startsWith("https://")` appears character-identically in 2 files — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateTailwindCss.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskProcessStylesheetCss.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 flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:696 — `"com.vaadin" .equals(artifact.getGroupId()) && "flow-server".equals(artifact.getArtifactId())` appears character-identically in 2 files — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java, flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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 flow-server/src/main/java/com/vaadin/flow/component/ComponentEventBus.java:380 — `Component.class.isAssignableFrom(type) || type == Element.class` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/component/ComponentEventBus.java, flow-server/src/main/java/com/vaadin/flow/component/internal/DomEventInfo.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 flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:302 — `artifact.getFile() != null && artifact.getArtifactHandler().isAddedToClasspath() && PRODUCTION_SCOPE_FILTER.include(artifact)` appears character-identically in 2 files — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java, flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.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 flow-server/src/main/java/com/vaadin/flow/component/Focusable.java:93 — `attribute == null || attribute.isEmpty()` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/component/Focusable.java, flow-server/src/main/java/com/vaadin/flow/dom/ElementUtil.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 vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java:61 — `beanManager.getContext(scopeAnnotationClass) == null || !beanManager.getContext(scopeAnnotationClass) .isActive()` appears character-identically in 2 files — vaadin-cdi/src/main/java/com/vaadin/cdi/util/ContextUtils.java, vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/ContextUtils.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 vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java:786 — `className .startsWith("com.vaadin.flow.component.charts.model.") || className.startsWith( "com.vaadin.flow.component.map.configuration.")` appears character-identically in 2 files — vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/VaadinQuarkusNativeProcessor.java, vaadin-spring/src/main/java/com/vaadin/flow/spring/springnative/VaadinHintsRegistrar.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 flow-server/src/main/java/com/vaadin/flow/component/internal/ComponentMetaData.java:245 — `clazz == null || clazz.equals(Object.class)` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/component/internal/ComponentMetaData.java, flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/AbstractServerHandlers.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 flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:1195 — `clazz.getEnclosingClass() != null && !Modifier.isStatic(clazz.getModifiers())` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java, flow-server/src/main/java/com/vaadin/flow/server/webcomponent/WebComponentExporterUtils.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 flow-server/src/main/java/com/vaadin/experimental/FeatureFlags.java:353 — `configuration != null && !configuration.isProductionMode()` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/experimental/FeatureFlags.java, flow-server/src/main/java/com/vaadin/flow/server/PwaRegistry.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 flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppRuntime.java:214 — `configured != null && !configured.isBlank()` appears character-identically in 3 files — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppRuntime.java, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/MainClass.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 flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java:892 — `configured == null || configured.isBlank()` appears character-identically in 2 files — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Launch.java, flow-server/src/main/java/com/vaadin/flow/server/AbstractDeploymentConfiguration.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 flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:575 — `contentType != null && contentType.toLowerCase().startsWith("multipart/")` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java, flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.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 flow-server/src/main/java/com/vaadin/flow/component/SignalPropertySupport.java:152 — `ctx.isInitialRun() || binding.hasCallbacks()` appears character-identically in 4 files — flow-server/src/main/java/com/vaadin/flow/component/SignalPropertySupport.java, flow-server/src/main/java/com/vaadin/flow/dom/ElementEffect.java, flow-server/src/main/java/com/vaadin/flow/dom/impl/ThemeListImpl.java, flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementClassList.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 flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java:123 — `current != null && current != Object.class` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/internal/ReflectTools.java, flow-server/src/main/java/com/vaadin/flow/internal/SignalFieldTransfer.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 flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java:255 — `dependenciesIncompatibility != null && !dependenciesIncompatibility.isEmpty()` appears character-identically in 2 files — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.java, flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/Reflector.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 flow-server/src/main/java/com/vaadin/flow/component/Component.java:388 — `eventBus != null && eventBus.hasListener(eventType)` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/component/Component.java, flow-server/src/main/java/com/vaadin/flow/server/InstrumentedReentrantLock.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 flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java:608 — `fileCountMax > -1 && parts.size() > fileCountMax` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/server/communication/StreamReceiverHandler.java, flow-server/src/main/java/com/vaadin/flow/server/communication/TransferUtil.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 flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java:694 — `listeners.size() == 1 && !(listeners instanceof HashMap)` appears character-identically in 2 files — flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java, flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementPropertyMap.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 flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java:1207 — `name.startsWith(".") || name.startsWith("~") || name.endsWith("~")` appears character-identically in 2 files — flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Compile.java, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/Frontend.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 flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java:638 — `options.isFrontendHotdeploy() || options.isBundleBuild()` appears character-identically in 3 files — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/AbstractUpdateImports.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeTasks.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskGenerateViteDevMode.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 flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java:142 — `options.isReactEnabled() && FrontendBuildUtils.isReactModuleAvailable(options)` appears character-identically in 2 files — flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/NodeUpdater.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskUpdatePackages.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 vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java:282 — `owner.equals(key.owner) && uiId.equals(key.uiId)` appears character-identically in 2 files — vaadin-cdi/src/main/java/com/vaadin/cdi/context/RouteScopedContext.java, vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/context/RouteScopedContext.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 flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java:721 — `pluginContext != null && pluginContext.containsKey(reflectorKey)` appears character-identically in 2 files — flow-plugins/flow-dev-bundle-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildDevBundleMojo.java, flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.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.
  • + 13 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×34
  • Disabled test flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:399 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/NodeUpdaterTest.java:400 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-server/src/test/java/ClassInDefaultPackage.java:25 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-server/src/test/java/com/vaadin/flow/component/UITest.java:502 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-server/src/test/java/com/vaadin/flow/server/communication/WebComponentBootstrapHandlerViteTest.java:293 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-server/src/test/java/com/vaadin/flow/server/communication/WebComponentBootstrapHandlerViteTest.java:327 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-ccdm-flow-navigation/src/test/java/com/vaadin/flow/navigate/ServiceWorkerOnNestedMappingIT.java:21 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-ccdm/src/test/java/com/vaadin/flow/ccdmtest/CCDMTest.java:27 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-frontend/test-bun/src/test/java/com/vaadin/flow/mixedtest/ui/IdTestIT.java:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-frontend/vite-basics/src/test/java/com/vaadin/viteapp/ThemeReloadIT.java:34 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-npm-only-features/test-npm-performance-regression/src/test/java/com/vaadin/flow/testnpmonlyfeatures/performanceregression/StartupPerformanceIT.java:42 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/CountUIsIT.java:31 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/DebounceSynchronizePropertyIT.java:67 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/FragmentLinkIT.java:50 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/FragmentLinkIT.java:64 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/RouteNotFoundProdModeIT.java:21 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/RouterLinkIT.java:51 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/RouterSessionExpirationIT.java:54 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/ValueChangeModeIT.java:49 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/dependencies/AnnotatedContextInlineIT.java:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/dependencies/ContextInlineApiIT.java:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/dependencies/DependenciesLoadingAnnotationsIT.java:59 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/dependencies/DependenciesLoadingPageApiIT.java:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/scroll/CustomScrollCallbacksIT.java:25 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test flow-tests/test-root-context/src/test/java/com/vaadin/flow/uitest/ui/scroll/ScrollIT.java:32 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 9 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×10
  • redundant comment flow-build-tools/src/main/resources/plugins/rollup-plugin-vaadin-i18n/rollup-plugin-vaadin-i18n.js:190 — "Add the main chunk keys to the main chunk key set" repeats the code it sits on: 5 of its 6 words (main, chunk, keys, key, set) are already in `for (const key of mainChunkKeySet)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/main/frontend/BrowserHelpers.ts:112 — "Device Pixel Ratio" repeats the code it sits on: 3 of its 3 words (device, pixel, ratio) are already in `params['v-pr'] = $wnd.devicePixelRatio;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/main/frontend/internal/client/SystemErrorHandler.ts:362 — "Set the popover attribute for native popovers." repeats the code it sits on: 4 of its 5 words (set, popover, attribute, popovers) are already in `systemErrorContainer.setAttribute('popover', 'manual');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/main/frontend/internal/client/bootstrap/Bootstrapper.ts:104 — "Debug or production mode?" repeats the code it sits on: 3 of its 3 words (debug, production, mode) are already in `conf.setProductionMode(!getConfigBoolean(jsoConfiguration, 'debug'));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:1279 — "map event.target to the closest state node" repeats the code it sits on: 6 of its 6 words (map, event, target, closest, state, node) are already in `eventData![MAP_STATE_NODE_EVENT_DATA] = getClosestStateNodeIdToEventTarget(node, event.target);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:227 — "Browser engine version parsing failed" repeats the code it sits on: 5 of its 5 words (browser, engine, version, parsing, failed) are already in `this.log(`Browser engine version parsing failed for: ${ua}`, e);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/main/frontend/internal/flow/shared/BrowserDetails.ts:334 — "Browser version parsing failed" repeats the code it sits on: 4 of its 4 words (browser, version, parsing, failed) are already in `this.log(`Browser version parsing failed for: ${ua}`, e);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-client/src/test/frontend/FlowTests.ts:19 — "A `changes` array that adds a div with 'Foo' text to body" repeats the code it sits on: 6 of its 7 words (changes, adds, div, foo, text, body) are already in `const changesResponse = `[`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment flow-server/src/main/resources/com/vaadin/flow/server/BootstrapHandler.js:265 — "Device Pixel Ratio" repeats the code it sits on: 3 of its 3 words (device, pixel, ratio) are already in `params['v-pr'] = window.devicePixelRatio;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment vaadin-dev-server/src/main/frontend/License.ts:125 — "Has been checked and the check failed" repeats the code it sits on: 3 of its 3 words (checked, check, failed) are already in `setTimeout(() => showNoLicenseFallback(cvdlElement, failedLicenseCheck), noLicenseFallbackTimeout);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
AX6 · Interface segregation · Fat interface · ×9
  • Fat interface: ConnectionStateHandler (16 required operations) flow-client/src/main/frontend/internal/client/communication/ConnectionStateHandler.ts:54 — `ConnectionStateHandler` declares 16 required operations: `heartbeatException`, `heartbeatInvalidStatusCode`, `heartbeatOk`, `pushClosed`, `pushClientTimeout`, `pushError`, `pushReconnectPending`, `pushOk`, `pushScriptLoadError`, `xhrException`, `xhrInvalidContent`, `xhrInvalidStatusCode`, `xhrOk`, `pushNotConnected`, `pushInvalidContent`, `configurationUpdated`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data 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.
  • Fat interface: ApplicationConnection (16 required operations) flow-client/src/main/frontend/internal/client/clientApi.ts:45 — `ApplicationConnection` declares 16 required operations: `isActive`, `getDomElementByNodeId`, `getNodeId`, `addDomSetListener`, `poll`, `resolveUri`, `sendEventMessage`, `getUIId`, `connectWebComponent`, `debug`, `getJavaClass`, `isHiddenByServer`, `getElementStyleProperties`, `getProfilingData`, `getClientEvents`, `start`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data 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.
  • Fat interface: Binding<BEAN, TARGET> (20 abstract methods) flow-data/src/main/java/com/vaadin/flow/data/binder/Binder.java:122 — `Binding<BEAN, TARGET>` declares 20 abstract methods: `getEqualityPredicate`, `getField`, `getGetter`, `getSetter`, `getValidationStatusHandler`, `hasChanges`, `isAsRequiredEnabled`, `isConvertBackToPresentation`, `isDefaultValidatorEnabled`, `isReadOnly`, `isValidatorsDisabled`, `read`, `setAsRequiredEnabled`, `setConvertBackToPresentation`, `setDefaultValidatorEnabled`, `setIsAppliedPredicate`, `setReadOnly`, `setValidatorsDisabled`, `unbind`, `validate`. 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: ListDataView<T, V> (21 abstract methods) flow-data/src/main/java/com/vaadin/flow/data/provider/ListDataView.java:38 — `ListDataView<T, V>` declares 21 abstract methods: `addFilter`, `addItem`, `addItemAfter`, `addItemBefore`, `addItems`, `addItemsAfter`, `addItemsBefore`, `addSortComparator`, `addSortOrder`, `contains`, `getItemCount`, `getNextItem`, `getPreviousItem`, `removeFilters`, `removeItem`, `removeItems`, `removeSorting`, `setFilter`, `setItems`, `setSortComparator`, `setSortOrder`. 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: RouteRegistry (21 abstract methods) flow-server/src/main/java/com/vaadin/flow/server/RouteRegistry.java:49 — `RouteRegistry` declares 21 abstract methods: `addRoutesChangeListener`, `clean`, `getContext`, `getLayout`, `getNavigationRouteTarget`, `getNavigationTarget`, `getNavigationTarget`, `getRegisteredAccessibleMenuRoutes`, `getRegisteredRoutes`, `getRouteTarget`, `getTargetUrl`, `getTargetUrl`, `getTemplate`, `hasLayout`, `hasMandatoryParameter`, `removeRoute`, `removeRoute`, `removeRoute`, `setLayout`, `setRoute`, `update`. 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. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: VaadinRequest (32 abstract methods) flow-server/src/main/java/com/vaadin/flow/server/VaadinRequest.java:38 — `VaadinRequest` declares 32 abstract methods: `getAttribute`, `getAttributeNames`, `getAuthType`, `getCharacterEncoding`, `getContentLength`, `getContentType`, `getContextPath`, `getCookies`, `getDateHeader`, `getHeader`, `getHeaderNames`, `getHeaders`, `getInputStream`, `getLocale`, `getLocales`, `getMethod`, `getParameter`, `getParameterMap`, `getPathInfo`, `getReader`, `getRemoteAddr`, `getRemoteHost`, `getRemotePort`, `getRemoteUser`, `getService`, `getUserPrincipal`, `getWrappedSession`, `getWrappedSession`, `isSecure`, `isUserInRole`, `removeAttribute`, `setAttribute`. 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. Those 32 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: ElementStateProvider (37 abstract methods) flow-server/src/main/java/com/vaadin/flow/dom/ElementStateProvider.java:38 — `ElementStateProvider` declares 37 abstract methods: `addEventListener`, `addPropertyChangeListener`, `appendVirtualChild`, `attachExistingElement`, `attachShadow`, `bindAttributeSignal`, `bindPropertySignal`, `bindVisibleSignal`, `getAttribute`, `getAttributeNames`, `getChild`, `getChildCount`, `getClassList`, `getParent`, `getProperty`, `getPropertyNames`, `getShadowRoot`, `getStyle`, `getTag`, `getTextContent`, `hasAttribute`, `hasProperty`, `insertChild`, `isTextNode`, `isVisible`, `removeAllChildren`, `removeAttribute`, `removeChild`, `removeChild`, `removeProperty`, `setAttribute`, `setAttribute`, `setProperty`, `setTextContent`, `setVisible`, `supports`, `visit`. 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. Those 37 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: PluginAdapterBase (40 abstract methods) flow-plugins/flow-plugin-base/src/main/java/com/vaadin/flow/plugin/base/PluginAdapterBase.java:34 — `PluginAdapterBase` declares 40 abstract methods: `applicationIdentifier`, `applicationProperties`, `buildFolder`, `bunEnable`, `eagerServerLoad`, `excludePostinstallPackages`, `frontendDirectory`, `frontendExtraFileExtensions`, `generatedTsFolder`, `getClassFinder`, `getJarFiles`, `isDebugEnabled`, `isFrontendHotdeploy`, `isFrontendIgnoreVersionChecks`, `isJarProject`, `isNpmExcludeWebComponents`, `isPrepareFrontendCacheDisabled`, `isReactEnabled`, `javaResourceFolder`, `javaSourceFolder`, `logDebug`, `logDebug`, `logError`, `logError`, `logInfo`, `logWarn`, `logWarn`, `nodeDownloadRoot`, `nodeFolder`, `nodeVersion`, `npmFolder`, `openApiJsonFile`, `pnpmEnable`, `postinstallPackages`, `projectBaseDirectory`, `requireHomeNodeExec`, `servletResourceOutputDirectory`, `skipDevBundleBuild`, `useGlobalPnpm`, `webpackOutputDirectory`. 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. Those 40 declarations carry 37 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 37 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: VaadinBuildTimeConfig (36 abstract methods) vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/vaadinplugin/VaadinBuildTimeConfig.java:39 — `VaadinBuildTimeConfig` declares 36 abstract methods: `applicationIdentifier`, `applicationProperties`, `bunEnable`, `ciBuild`, `cleanFrontendFiles`, `commercialWithBanner`, `eagerServerLoad`, `enabled`, `excludePostinstallPackages`, `forceProductionBuild`, `frontendDirectory`, `frontendExtraFileExtensions`, `frontendIgnoreVersionChecks`, `frontendOutputDirectory`, `frontendResourcesDirectory`, `generateBundle`, `generateEmbeddableWebComponents`, `generatedResourceOutputDirectory`, `generatedTsFolder`, `minimumFrontendPackageAgeDays`, `nodeDownloadRoot`, `nodeFolder`, `nodeVersion`, `npmExcludeWebComponents`, `npmFolder`, `openApiJsonFile`, `optimizeBundle`, `pnpmEnable`, `postinstallPackages`, `reactEnabled`, `requireHomeNodeExec`, `resourcesOutputDirectory`, `runNpmInstall`, `skipDevBundleBuild`, `useGlobalPnpm`, `webpackOutputDirectory`. 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.
D19 · Documentation Quality · Documentation · ×5
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example flow-tests/test-csp-strict-spring-security/README.md:1 — `test-csp-strict-spring-security` is an application (`spring-boot-maven-plugin`) and neither `flow-tests/test-csp-strict-spring-security/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example flow-tests/test-default/README.md:1 — `test-default` is an application (`spring-boot-maven-plugin`) and neither `flow-tests/test-default/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example flow-tests/test-legacy-frontend/README.md:1 — `test-legacy-frontend` is an application (`<packaging>war</packaging>`) and neither `flow-tests/test-legacy-frontend/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example flow-tests/test-theme-no-polymer/README.md:1 — `test-theme-no-polymer` is an application (`<packaging>war</packaging>`) and neither `flow-tests/test-theme-no-polymer/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 23 significant file(s) lose their only recent owner: vaadin-dev-server/src/main/frontend/hotswap-scroll.ts, flow-server/src/main/java/com/vaadin/flow/component/clipboard/ClipboardBinding.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/scanner/FrontendClassVisitor.java, flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/TriggerWriteToClipboardView.java, flow-server/src/main/java/com/vaadin/flow/component/PushConfiguration.java, flow-server/src/main/java/com/vaadin/flow/component/dependency/JavaScript.java, flow-tests/test-root-context/src/main/java/com/vaadin/flow/uitest/ui/GeolocationView.java, flow-server/src/main/java/com/vaadin/flow/component/geolocation/GeolocationOptions.java (+15 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 10 significant file(s) lose their only recent owner: flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/JarContentsManager.java, vaadin-quarkus/runtime/src/main/java/com/vaadin/quarkus/WebsocketHttpSessionAttachRecorder.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskPrepareProdBundle.java, flow-plugins/flow-gradle-plugin/src/main/kotlin/com/vaadin/gradle/ClasspathFilter.kt, flow-tests/vaadin-quarkus-tests/common-test-code/src/main/java/com/vaadin/flow/quarkus/it/javascript/JsDefinitionView.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/PnpmWorkspaceFile.java, flow-tests/test-ccdm-flow-navigation/src/main/java/com/vaadin/flow/navigate/DenyFramingFilter.java, vaadin-spring/src/main/java/com/vaadin/flow/spring/annotation/EnableVaadin.java (+2 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 6 significant file(s) lose their only recent owner: flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppLog.java, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/AppProcess.java, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/mavenext/DevLoopBuildExtension.java, REDACTED, REDACTED, flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/EffectiveModel.java. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: flow-server/src/main/java/com/vaadin/flow/server/PwaIcon.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskCompressStaticResources.java, flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskCopyNpmAssetsFiles.java, vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringServlet.java, flow-server/src/main/java/com/vaadin/flow/internal/UnmodifiableProperties.java, flow-server/src/main/java/com/vaadin/flow/internal/change/MapPutChange.java. Pair on, review, or document these before any departure.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×4
  • Silent fallback default on parse failure flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/EffectiveModel.java:188 — `count` returns `0` 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 flow-devloop-daemon/src/main/java/com/vaadin/flow/devloop/daemon/TransactionEngine.java:1784 — `parseInt` returns `0` 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 flow-server/src/main/java/com/vaadin/flow/component/clipboard/PasteFileHandler.java:318 — `parseFileCount` returns `0` 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 flow-server/src/main/java/com/vaadin/flow/component/clipboard/PasteFileHandler.java:307 — `parsePasteId` returns `0` 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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×4
  • Silent fallback default in catch vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1092 — `activeThemes` swallows every exception into `return Set.of()` — 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 vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopRedefiner.java:1112 — `agreesOnFolder` 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 flow-client/src/main/frontend/Geolocation.ts:146 — `resolveAvailability` swallows every exception into `return 'UNKNOWN'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch flow-client/src/main/frontend/internal/client/ResourceLoader.ts:459 — `getStyleSheetLength` swallows every exception into `return 1` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×3
  • Projects may be oversized for their cohesion flow-server/pom.xml:1 — `flow-server` (163767 LoC, 1082 module-visible types across 61 directories) overshoots its size bounds. 3 of 31 build unit(s) (Maven, npm) overshoot their size bounds, lowering Project Cohesion to 8.1/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.
  • Projects may be oversized for their cohesion flow-data/pom.xml:1 — `flow-data` (24257 LoC, 168 module-visible types across 8 directories) overshoots its size bounds. 3 of 31 build unit(s) (Maven, npm) overshoot their size bounds, lowering Project Cohesion to 8.1/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.
  • Projects may be oversized for their cohesion flow-client/pom.xml:1 — `flow-client` (21347 LoC, 160 module-visible types across 14 directories) overshoots its size bounds. 3 of 31 build unit(s) (Maven, npm) overshoot their size bounds, lowering Project Cohesion to 8.1/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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift flow-polymer2lit/README.md:81 — flow-polymer2lit/README.md names Lit 1, but the manifest declares `lit` 3.3.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift flow-plugins/flow-gradle-plugin/README.md:224 — flow-plugins/flow-gradle-plugin/README.md links to `CONTRIBUTING.md`, but `flow-plugins/flow-gradle-plugin/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×2
  • Diagnostic log message is built whether or not it is wanted vaadin-dev-server/src/main/java/com/vaadin/base/devserver/devloop/DevLoopHotswapper.java:156 — `debug` at line 156 is called with an argument built by `stream()` (line 158), whose cost grows with the collection it walks. Java evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled`/`isTraceEnabled` test, no debug flag, no lambda or `Supplier` the logger calls only when the level is on.
  • Diagnostic log message is built whether or not it is wanted flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:892 — `debug` at line 892 is called with an argument built by `String.join("…", command)` (line 892), whose cost grows with the collection it walks. Java evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled`/`isTraceEnabled` test, no debug flag, no lambda or `Supplier` the logger calls only when the level is on.
X4 · Structured logging · Interpolated log message defeats structured logging · ×2
  • Interpolated log message defeats structured logging flow-server/src/main/java/com/vaadin/flow/server/auth/AnnotatedViewAccessChecker.java:186 — `warn` at line 186 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 flow-build-tools/src/main/java/com/vaadin/flow/server/frontend/TaskRunNpmInstall.java:1132 — `error` at line 1132 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.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (83 single-owned of 1167 analysed files in total, 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; 1167 of the 2762 production source files in this repository met that bar). They are anonymized user #5 (3 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/HasHierarchicalDataProvider.java, flow-data/src/main/java/com/vaadin/flow/data/provider/hierarchy/Cache.java, flow-data/src/main/java/com/vaadin/flow/data/value/ValueChangeMode.java, flow-server/src/main/java/com/vaadin/flow/component/HasValidation.java, flow-data/src/main/java/com/vaadin/flow/data/provider/HasDataView.java, flow-server/src/main/java/com/vaadin/flow/router/RouterLink.java, flow-data/src/main/java/com/vaadin/flow/data/converter/Converter.java.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found vaadin-quarkus/pom.xml:67 — 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 `vaadin-quarkus/pom.xml` makes this repository a deployable product (line 67).
D21 · Naming Consistency · `isAllowedVAADINBuildUrl` spells `VAADIN` where 38 names in the project spell it `Vaadin` · ×1
  • `isAllowedVAADINBuildUrl` spells `VAADIN` where 38 names in the project spell it `Vaadin` flow-server/src/main/java/com/vaadin/flow/internal/ResponseWriter.java:611 — 38 of 39 names in project flow-server spell the token `Vaadin` (38 of 39; unit: names in project flow-server containing `Vaadin`). Peers: FrontendUtils.getVaadinHomeDirectory (flow-server/src/main/java/com/vaadin/flow/internal/FrontendUtils.java:1072); com.vaadin.flow.internal.streams.TerminableVaadinServletRequest (flow-server/src/main/java/com/vaadin/flow/internal/streams/TerminableStreamsUtil.java:100); com.vaadin.flow.internal.streams.TerminableVaadinServletResponse (flow-server/src/main/java/com/vaadin/flow/internal/streams/TerminableStreamsUtil.java:142); AppShellRegistry.resolveVaadinUri (flow-server/src/main/java/com/vaadin/flow/server/AppShellRegistry.java:356); BootstrapUriResolver.resolveVaadinUri (flow-server/src/main/java/com/vaadin/flow/server/BootstrapHandler.java:507). Rename to `isAllowedVaadinBuildUrl`. [rule N6]
D21 · Naming Consistency · `getResourceURL` spells `URL` where 28 names in the project spell it `Url` · ×1
  • `getResourceURL` spells `URL` where 28 names in the project spell it `Url` vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringVaadinServletService.java:199 — 28 of 30 names in project vaadin-spring spell the token `Url` (28 of 30; unit: names in project vaadin-spring containing `Url`). Peers: DevModeBrowserLauncher.getUrl (vaadin-spring/src/main/java/com/vaadin/flow/spring/DevModeBrowserLauncher.java:106); RootMappedCondition.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/RootMappedCondition.java:74); VaadinConfigurationProperties.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:56); VaadinConfigurationProperties.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:420); VaadinConfigurationProperties.setUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:430). Rename to `getResourceUrl`. [rule N6]
D21 · Naming Consistency · `jarPathURL` spells `URL` where 28 names in the project spell it `Url` · ×1
  • `jarPathURL` spells `URL` where 28 names in the project spell it `Url` vaadin-spring/src/main/java/com/vaadin/flow/spring/io/FilterableResourceResolver.java:407 — 28 of 30 names in project vaadin-spring spell the token `Url` (28 of 30; unit: names in project vaadin-spring containing `Url`). Peers: DevModeBrowserLauncher.getUrl (vaadin-spring/src/main/java/com/vaadin/flow/spring/DevModeBrowserLauncher.java:106); RootMappedCondition.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/RootMappedCondition.java:74); VaadinConfigurationProperties.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:56); VaadinConfigurationProperties.getUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:420); VaadinConfigurationProperties.setUrlMapping (vaadin-spring/src/main/java/com/vaadin/flow/spring/VaadinConfigurationProperties.java:430). Rename to `jarPathUrl`. [rule N6]
D21 · Naming Consistency · `UpdateJWTCookieOnCommitResponseWrapper` spells `JWT` where 12 names in the project spell it `Jwt` · ×1
  • `UpdateJWTCookieOnCommitResponseWrapper` spells `JWT` where 12 names in the project spell it `Jwt` vaadin-spring/src/main/java/com/vaadin/flow/spring/security/stateless/VaadinStatelessSecurityConfigurer.java:360 — 12 of 13 names in project vaadin-spring spell the token `Jwt` (12 of 13; unit: names in project vaadin-spring containing `Jwt`). Peers: JwtSecurityContextRepository.getJwtDecoder (vaadin-spring/src/main/java/com/vaadin/flow/spring/security/stateless/JwtSecurityContextRepository.java:107); JwtSecurityContextRepository.encodeJwt (vaadin-spring/src/main/java/com/vaadin/flow/spring/security/stateless/JwtSecurityContextRepository.java:128); JwtSecurityContextRepository.decodeJwt (vaadin-spring/src/main/java/com/vaadin/flow/spring/security/stateless/JwtSecurityContextRepository.java:162); com.vaadin.flow.spring.security.stateless.SerializedJwtSplitCookieRepository (REDACTED:28); SerializedJwtSplitCookieRepository.loadSerializedJwt (REDACTED:54). Rename to `UpdateJwtCookieOnCommitResponseWrapper`. [rule N6]
D21 · Naming Consistency · `getConfigFromDOM` spells `DOM` where 25 names in the project spell it `Dom` · ×1
  • `getConfigFromDOM` spells `DOM` where 25 names in the project spell it `Dom` flow-client/src/main/frontend/internal/client/bootstrap/Bootstrapper.ts:122 — 25 of 26 names in project repository spell the token `Dom` (25 of 26; unit: names in project repository containing `Dom`). Peers: ApplicationConnection.getDomElementByNodeId (flow-client/src/main/frontend/internal/client/ApplicationConnection.ts:192); ApplicationConnection.addDomSetListener (flow-client/src/main/frontend/internal/client/ApplicationConnection.ts:209); PolymerModelTree.getFirstParentWithDomNode (flow-client/src/main/frontend/internal/client/PolymerModelTree.ts:254); PolymerUtils.getDomElementById (flow-client/src/main/frontend/internal/client/PolymerUtils.ts:195); PolymerUtils.getDomRoot (flow-client/src/main/frontend/internal/client/PolymerUtils.ts:243). Rename to `getConfigFromDom`. [rule N6]
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 208 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: flow-server/src/main/java/com/vaadin/flow/internal/Range.java, flow-server/src/main/java/com/vaadin/flow/di/LookupInitializer.java, flow-polymer-template/src/main/java/com/vaadin/flow/component/polymertemplate/TemplateDataAnalyzer.java, vaadin-quarkus/deployment/src/main/java/com/vaadin/quarkus/deployment/vaadinplugin/VaadinBuildTimeConfig.java, flow-server/src/main/java/com/vaadin/flow/server/webcomponent/WebComponentModulesWriter.java, flow-server/src/main/java/com/vaadin/flow/router/internal/HasUrlParameterFormat.java, vaadin-spring/src/main/java/com/vaadin/flow/spring/SpringLookupInitializer.java, flow-server/src/main/java/com/vaadin/flow/internal/AnnotationReader.java (and 200 more) (211 orphaned of 1179 analysed files in total, 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; 1179 of the 2762 production source files in this repository met that bar). 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 22/23 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `flow-devloop-daemon`.
P3 · Security & performance tooling · Dependabot does not watch github-actions/npm/gradle · ×1
  • Dependabot does not watch github-actions/npm/gradle REDACTED:7 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, `gradle`, 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused export 'refresh' · ×1
  • Unused export 'refresh' flow-client/src/main/frontend/internal/client/WidgetUtil.ts:29 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'changesResponse' · ×1
  • Unused module-local declaration 'changesResponse' flow-client/src/test/frontend/FlowTests.ts:20 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 21/22 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~2.7 `!` null assertions per 1k TypeScript source lines — 76 assertion(s) across the 28489 source line(s) of the 149 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: REDACTED (12), flow-client/src/main/frontend/internal/client/flow/binding/Debouncer.ts (8), flow-client/src/main/frontend/internal/client/Profiler.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 86 finding(s)
D10 · Test Quality · Skipped (documented) · ×82
  • Skipped (documented): bundleMissesSomeEntries_devMode_skipBundleBuildSet_noBundleRebuild flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2249 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): commercialBannerBuild_commercialBannerComponentChanged_rebuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2637 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): commercialBannerBuild_commercialBannerComponentMissing_rebuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2620 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): commercialBannerBuild_commercialBannerComponentNotChanged_rebuildNotRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2662 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): compressedProdBundleExists_noBuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2349 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): defaultDevBundleExists_noCompressedDevBundleFile_reactDisabled_buildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2457 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): defaultProdBundleExists_noCompressedProdBundleFileAndWithVersionsJsonExclusions_noBuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2521 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): defaultProdBundleExists_noCompressedProdBundleFile_noBuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2485 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): defaultProdBundleExists_noCompressedProdBundleFile_reactDisabled_buildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2592 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): developmentMode_commercialBannerComponentNotPresent_rebuildNotRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2715 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): developmentMode_commercialBannerComponentPresent_rebuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2732 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): forceProductionBundle_bundleRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2284 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): indexHtmlChanged_developmentMode_rebuildNotRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2072 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): indexHtmlChanged_productionMode_rebuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2041 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): loadDependenciesOnStartup_annotatedClassInProject_compilationRequiredForProduction flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:372 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): noDevFolder_compressedDevBundleExists_noBuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2298 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): nonCommercialBannerBuild_commercialBannerComponentPresent_rebuildRequired flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/BundleValidationTest.java:2685 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): toolLocated_verificationFailed flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsLocatorTest.java:38 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): getPnpmExecutable_executableIsAvailable flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:401 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
  • Skipped (documented): getSuitablePnpm_notUsingGlobalPnpm_pinsDefaultPnpmVersion flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:693 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): getSuitablePnpm_useGlobalPnpm_noPnpmInstalled_throws flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:716 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): nodeFolder_validFolderWithNode_usesSpecifiedNode flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendToolsTest.java:820 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): deleteNodeModules_canDeleteSymlinksAndNotFollowThem flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/FrontendUtilsTest.java:363 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): acquire_lockOfEarlierProcessWithSamePid_isTakenOver flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/LockFileTest.java:159 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): tryAcquire_heldByAnotherRunningProcess_returnsWithoutTakingIt flow-build-tools/src/test/java/com/vaadin/flow/server/frontend/LockFileTest.java:130 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • + 57 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×3
  • doc comments repeat the names flow-build-tools/src/main/resources/plugins/application-theme-plugin/theme-generator.js:39 — 1 of 30 documented parameters and 0 of 13 summaries in `@vaadin/application-theme-plugin` only repeat the member or parameter name (e.g. "folder of the theme" for `themeFolder`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names flow-client/src/main/frontend/internal/client/ApplicationConfiguration.ts:82 — 27 of 578 documented parameters and 6 of 1038 summaries in `@vaadin/flow-client` only repeat the member or parameter name (e.g. "the id for the application" for `applicationId`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names vaadin-dev-server/src/main/frontend/vaadin-dev-tools.ts:22 — 0 of 7 documented parameters and 1 of 20 summaries in `vaadin-dev-server` only repeat the member or parameter name (e.g. "The command" for `command`). Delete the restating tags, or add what the name does not say.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: flow-test-common — flow-test-common: abstractness 0.05, instability 0.00, distance 0.95 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=12800" --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=17000 --max-count=18267" --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/history-4.json --exit-code 0 --source .1artifacts/raw/gitleaks-history-4.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4ccd7fb07594e2f8d78a2269864c4b2/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude flow-client/coverage .26artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .26artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `flow-client/src/main/frontend/ConnectionIndicator.ts`, `flow-html-components/src/main/java/com/vaadin/flow/component/html/TableCell.java`, `flow-server/src/main/java/com/vaadin/flow/component/webcomponent/WebComponent.java`, `flow-server/src/main/java/com/vaadin/flow/internal/nodefeature/ElementListenerMap.java`, `flow-server/src/main/java/com/vaadin/flow/js/JsDefinitionProxy.java`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1ebab-1dd1-78c9-bdf4-93efb9790145 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md