Public report of MaibornWolff/codecharta, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 01:09 UTC · Survey ID cd_c504f8b1e4c1481eba79d5d840b677bf
MaibornWolff/codecharta
Measured 17 November 2026, 01:07 UTC, at code version fff099c
Code coverage is not measured: .NET and JavaScript/TypeScript suite (Unclassified, CouldNotMeasureTestRunFailed).
Test reliability is not measured: The .NET half of a polyglot suite was not re-run.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAdequate
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: 117,577 lines of product code in 42 projects, tests not counted · Estimated rebuild effort: about 3.1 person-years · Weakest lens: Security and Compliance, 57.6
Findings by how serious they are
149 critical337 serious153 minor
16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 01:07 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 ▸
67of 67 dimensions measured by tools.
613of 639 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
67dimensions across 7 lenses, read from 117,577 lines of product code in 42 projects.
MaibornWolff/codecharta falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 69.5 out of 100 and is rated Adequate, and 143 of its 149 critical findings are security problems.
Security and Compliance, at 57.6, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the five pipeline jobs with more access than they need, worth about 1.8 points. Stopping the 21 pipeline steps that hand secrets to unpinned tools comes next, worth about 2.7 points. Raising Security and Compliance to 70 would lift the score to about 75.2.
Eighty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-two secrets can leak from the build pipeline, and ten pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Fixing the weaknesses the scanner points to would fix the six security weaknesses in the code, and the ten unsafe settings in infrastructure or container files need changing to safe values. The three loops of files that import each other need breaking.
The product code is 117,577 lines, about €460,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 57.6 to 70, the lowest score rated Strong, the score would rise from 69.5 to about 75.2.
Code composition: what the lines of code are
Business logic 0%Supporting code 1%Tests 99%
Rebuild cost: about €460,000 · Estimate
Cost to rebuild
€150,000 to €760,000, for 2,530 to 8,026 hours of work, about 3.1 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×1.0 at a score of 70. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 117,577 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
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 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
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 €460,000 to build again, about 3.1 person-years of work. Its weakest lens is Security and Compliance, at 57.6 (Adequate). 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 5 REDACTED finding(s) in Supply-chain Provenance & Signing. Of all the actions in this report, it raises the score most for the work it takes: about 1.8 points for low effort, because it clears the 5 Supply-chain Provenance & Signing 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.
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.
1538 modules, with 1716 dependencies between them. 21 loops run through 45 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1498 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.
3 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.input.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses de.maibornwolff.codecharta.analysers.parsers.dependency.input, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.input can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can't break de.maibornwolff.codecharta.analysers.parsers.dependency.input.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses a type in de.maibornwolff.treesitter.excavationsite.shared.domain.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses de.maibornwolff.treesitter.excavationsite.shared.domain, so a change to de.maibornwolff.treesitter.excavationsite.shared.domain can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can't break de.maibornwolff.treesitter.excavationsite.shared.domain.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords uses a type in de.maibornwolff.treesitter.excavationsite.shared.domain.
de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords uses de.maibornwolff.treesitter.excavationsite.shared.domain, so a change to de.maibornwolff.treesitter.excavationsite.shared.domain can break de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords, while a change to de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords can't break de.maibornwolff.treesitter.excavationsite.shared.domain.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.treesitter.excavationsite.languages.vba.model uses a type in de.maibornwolff.treesitter.excavationsite.shared.domain.
de.maibornwolff.treesitter.excavationsite.languages.vba.model uses de.maibornwolff.treesitter.excavationsite.shared.domain, so a change to de.maibornwolff.treesitter.excavationsite.shared.domain can break de.maibornwolff.treesitter.excavationsite.languages.vba.model, while a change to de.maibornwolff.treesitter.excavationsite.languages.vba.model can't break de.maibornwolff.treesitter.excavationsite.shared.domain.
Position
Below the diagonal: de.maibornwolff.treesitter.excavationsite.languages.vba.model uses a module listed above it, which is the healthy direction.
visualization.app.codeCharta.model.domain_model uses visualization.app.codeCharta.model.rectangle, so a change to visualization.app.codeCharta.model.rectangle can break visualization.app.codeCharta.model.domain_model, while a change to visualization.app.codeCharta.model.domain_model can't break visualization.app.codeCharta.model.rectangle.
Position
Below the diagonal: visualization.app.codeCharta.model.domain_model uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.input.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses de.maibornwolff.codecharta.analysers.parsers.dependency.input, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.input can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can't break de.maibornwolff.codecharta.analysers.parsers.dependency.input.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a type in de.maibornwolff.treesitter.excavationsite.shared.domain.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses de.maibornwolff.treesitter.excavationsite.shared.domain, so a change to de.maibornwolff.treesitter.excavationsite.shared.domain can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can't break de.maibornwolff.treesitter.excavationsite.shared.domain.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing uses a type in de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords.
de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing uses de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords, so a change to de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords can break de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing, while a change to de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing can't break de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing.keywords.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.domainlanguage.processing uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions, while a change to visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions uses a module listed above it, which is the healthy direction.
visualization.app.codeCharta.features.sidebarExplorer uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.features.sidebarExplorer, while a change to visualization.app.codeCharta.features.sidebarExplorer can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.features.sidebarExplorer uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.model.state_model uses a type in visualization.app.codeCharta.model.dependencyGraph_model.
visualization.app.codeCharta.model.state_model uses visualization.app.codeCharta.model.dependencyGraph_model, so a change to visualization.app.codeCharta.model.dependencyGraph_model can break visualization.app.codeCharta.model.state_model, while a change to visualization.app.codeCharta.model.state_model can't break visualization.app.codeCharta.model.dependencyGraph_model.
Position
Below the diagonal: visualization.app.codeCharta.model.state_model uses a module listed above it, which is the healthy direction.
visualization.app.codeCharta.model.state_model uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.model.state_model, while a change to visualization.app.codeCharta.model.state_model can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.model.state_model uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in visualization.app.codeCharta.renderer.dependencyGraph.util uses a type in visualization.app.codeCharta.model.dependencyGraph_model.
visualization.app.codeCharta.renderer.dependencyGraph.util uses visualization.app.codeCharta.model.dependencyGraph_model, so a change to visualization.app.codeCharta.model.dependencyGraph_model can break visualization.app.codeCharta.renderer.dependencyGraph.util, while a change to visualization.app.codeCharta.renderer.dependencyGraph.util can't break visualization.app.codeCharta.model.dependencyGraph_model.
Position
Below the diagonal: visualization.app.codeCharta.renderer.dependencyGraph.util uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in visualization.app.codeCharta.renderer.dependencyGraph.util uses a type in visualization.app.codeCharta.model.rectangle.
visualization.app.codeCharta.renderer.dependencyGraph.util uses visualization.app.codeCharta.model.rectangle, so a change to visualization.app.codeCharta.model.rectangle can break visualization.app.codeCharta.renderer.dependencyGraph.util, while a change to visualization.app.codeCharta.renderer.dependencyGraph.util can't break visualization.app.codeCharta.model.rectangle.
Position
Below the diagonal: visualization.app.codeCharta.renderer.dependencyGraph.util uses a module listed above it, which is the healthy direction.
20 pairs of types, where a type in visualization.app.codeCharta.renderer.dependencyGraph.util uses a type in visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel.
visualization.app.codeCharta.renderer.dependencyGraph.util uses visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel, so a change to visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel can break visualization.app.codeCharta.renderer.dependencyGraph.util, while a change to visualization.app.codeCharta.renderer.dependencyGraph.util can't break visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel.
Position
Below the diagonal: visualization.app.codeCharta.renderer.dependencyGraph.util uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in visualization.app.codeCharta.renderer.dependencyGraph.util uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.renderer.dependencyGraph.util uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.renderer.dependencyGraph.util, while a change to visualization.app.codeCharta.renderer.dependencyGraph.util can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.renderer.dependencyGraph.util uses a module listed above it, which is the healthy direction.
visualization.app.codeCharta.renderer.radialMap.util uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.renderer.radialMap.util, while a change to visualization.app.codeCharta.renderer.radialMap.util can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.renderer.radialMap.util uses a module listed above it, which is the healthy direction.
18 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a type in de.maibornwolff.treesitter.excavationsite.languages.rust.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses de.maibornwolff.treesitter.excavationsite.languages.rust.model, so a change to de.maibornwolff.treesitter.excavationsite.languages.rust.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust can't break de.maibornwolff.treesitter.excavationsite.languages.rust.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a module listed above it, which is the healthy direction.
11 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.rust uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.input.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses de.maibornwolff.codecharta.analysers.parsers.dependency.input, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.input can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript can't break de.maibornwolff.codecharta.analysers.parsers.dependency.input.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a module listed above it, which is the healthy direction.
17 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a type in de.maibornwolff.treesitter.excavationsite.shared.domain.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses de.maibornwolff.treesitter.excavationsite.shared.domain, so a change to de.maibornwolff.treesitter.excavationsite.shared.domain can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript can't break de.maibornwolff.treesitter.excavationsite.shared.domain.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a module listed above it, which is the healthy direction.
35 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.typescript uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a type in de.maibornwolff.treesitter.excavationsite.languages.sql.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses de.maibornwolff.treesitter.excavationsite.languages.sql.model, so a change to de.maibornwolff.treesitter.excavationsite.languages.sql.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba can't break de.maibornwolff.treesitter.excavationsite.languages.sql.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a module listed above it, which is the healthy direction.
11 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a type in de.maibornwolff.treesitter.excavationsite.languages.vba.model.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses de.maibornwolff.treesitter.excavationsite.languages.vba.model, so a change to de.maibornwolff.treesitter.excavationsite.languages.vba.model can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba can't break de.maibornwolff.treesitter.excavationsite.languages.vba.model.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a type in de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers, so a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers can break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba, while a change to de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba can't break de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.
Position
Below the diagonal: de.maibornwolff.codecharta.analysers.parsers.dependency.analysis.analyzers.vba uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.MeshModels.generalMesh uses a type in visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions.
visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.MeshModels.generalMesh uses visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions, so a change to visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions can break visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.MeshModels.generalMesh, while a change to visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.MeshModels.generalMesh can't break visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.geometryOptions.
Position
Below the diagonal: visualization.app.codeCharta.features.3dPrint.3DExports.3DPreview.MeshModels.generalMesh uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, while a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow, while a change to visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.stores.mapState.store.mapState_readWindow, while a change to visualization.app.codeCharta.stores.mapState.store.mapState_readWindow can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.stores.mapState.store.mapState_readWindow, while a change to visualization.app.codeCharta.stores.mapState.store.mapState_readWindow can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.stores.mapState.store.mapState_readWindow uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.stores.rootStore.ccState_snapshot uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.stores.rootStore.ccState_snapshot uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.stores.rootStore.ccState_snapshot, while a change to visualization.app.codeCharta.stores.rootStore.ccState_snapshot can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.stores.rootStore.ccState_snapshot uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in visualization.app.codeCharta.load.loadInitialFile_store uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.load.loadInitialFile_store uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.load.loadInitialFile_store, while a change to visualization.app.codeCharta.load.loadInitialFile_store can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.load.loadInitialFile_store uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in visualization.app.codeCharta.load.loadInitialFile_store uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.load.loadInitialFile_store uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.load.loadInitialFile_store, while a change to visualization.app.codeCharta.load.loadInitialFile_store can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.load.loadInitialFile_store uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.load.loadInitialFile_store uses a type in visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
visualization.app.codeCharta.load.loadInitialFile_store uses visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow, so a change to visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow can break visualization.app.codeCharta.load.loadInitialFile_store, while a change to visualization.app.codeCharta.load.loadInitialFile_store can't break visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
Position
Below the diagonal: visualization.app.codeCharta.load.loadInitialFile_store uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.load.loadInitialFile_store uses a type in visualization.app.codeCharta.stores.mapState.store.mapState_readWindow.
visualization.app.codeCharta.load.loadInitialFile_store uses visualization.app.codeCharta.stores.mapState.store.mapState_readWindow, so a change to visualization.app.codeCharta.stores.mapState.store.mapState_readWindow can break visualization.app.codeCharta.load.loadInitialFile_store, while a change to visualization.app.codeCharta.load.loadInitialFile_store can't break visualization.app.codeCharta.stores.mapState.store.mapState_readWindow.
Position
Below the diagonal: visualization.app.codeCharta.load.loadInitialFile_store uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.renderer.threeViewer.threeSceneService, while a change to visualization.app.codeCharta.renderer.threeViewer.threeSceneService can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can break visualization.app.codeCharta.renderer.threeViewer.threeSceneService, while a change to visualization.app.codeCharta.renderer.threeViewer.threeSceneService can't break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
Position
Below the diagonal: visualization.app.codeCharta.renderer.threeViewer.threeSceneService uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can break visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service can't break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a type in visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow, so a change to visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow can break visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service can't break visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses visualization.app.codeCharta.renderer.threeViewer.threeSceneService, so a change to visualization.app.codeCharta.renderer.threeViewer.threeSceneService can break visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service can't break visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service uses a module listed above it, which is the healthy direction.
visualization.app.codeCharta.load.loadFiles_useCase uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.load.loadFiles_useCase, while a change to visualization.app.codeCharta.load.loadFiles_useCase can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.load.loadFiles_useCase uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.load.loadFiles_useCase uses a type in visualization.app.codeCharta.load.loadInitialFile_store.
visualization.app.codeCharta.load.loadFiles_useCase uses visualization.app.codeCharta.load.loadInitialFile_store, so a change to visualization.app.codeCharta.load.loadInitialFile_store can break visualization.app.codeCharta.load.loadFiles_useCase, while a change to visualization.app.codeCharta.load.loadFiles_useCase can't break visualization.app.codeCharta.load.loadInitialFile_store.
Position
Below the diagonal: visualization.app.codeCharta.load.loadFiles_useCase uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can break visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service, while a change to visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service can't break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
Position
Below the diagonal: visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses visualization.app.codeCharta.renderer.threeViewer.threeSceneService, so a change to visualization.app.codeCharta.renderer.threeViewer.threeSceneService can break visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service, while a change to visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service can't break visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
Position
Below the diagonal: visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow, so a change to visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.stores.fileStore.store.fileStore_readWindow.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.renderer.threeViewer.threeSceneService, so a change to visualization.app.codeCharta.renderer.threeViewer.threeSceneService can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.renderer.threeViewer.threeSceneService.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a type in visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service.
visualization.app.codeCharta.features.codeMap.codeMap_render_service uses visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service, so a change to visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service can break visualization.app.codeCharta.features.codeMap.codeMap_render_service, while a change to visualization.app.codeCharta.features.codeMap.codeMap_render_service can't break visualization.app.codeCharta.features.codeMap.codeMap_mouseEvent_service.
Position
Below the diagonal: visualization.app.codeCharta.features.codeMap.codeMap_render_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a type in visualization.app.codeCharta.model.state_model.
visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses visualization.app.codeCharta.model.state_model, so a change to visualization.app.codeCharta.model.state_model can break visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service can't break visualization.app.codeCharta.model.state_model.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service can break visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service can't break visualization.app.codeCharta.renderer.threeViewer.threeRenderer_service.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service.
visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service can break visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service can't break visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarioApplier_service uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarios_service uses a type in visualization.app.codeCharta.model.domain_model.
visualization.app.codeCharta.features.scenarios.services.scenarios_service uses visualization.app.codeCharta.model.domain_model, so a change to visualization.app.codeCharta.model.domain_model can break visualization.app.codeCharta.features.scenarios.services.scenarios_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarios_service can't break visualization.app.codeCharta.model.domain_model.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarios_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in visualization.app.codeCharta.features.scenarios.services.scenarios_service uses a type in visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service.
visualization.app.codeCharta.features.scenarios.services.scenarios_service uses visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service, so a change to visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service can break visualization.app.codeCharta.features.scenarios.services.scenarios_service, while a change to visualization.app.codeCharta.features.scenarios.services.scenarios_service can't break visualization.app.codeCharta.renderer.threeViewer.threeMapControls_service.
Position
Below the diagonal: visualization.app.codeCharta.features.scenarios.services.scenarios_service uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
140
High / Critical
A03:2025 — Software Supply Chain Failures
26
High / Critical
A02:2025 — Security Misconfiguration
15
High / Critical
Roadmap
Top priorities: Resolve the 21 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (3), REDACTED (3); Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED; Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (10).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Per-file score 0–10 — a quality signature. Of 143 files carrying findings, judged against the Production bar: 8% slop · 30% mixed · 62% near-clean.
File
Score
Band
Worst signal
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.5
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
IaC & Container Security: High IaC: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
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 — 149
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 — 337
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 — 153
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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 67 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 — 67 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 613 of 639 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
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 1 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 1,283 test source file(s) (.ts, .kt, .java, .js, .tsx, .jsx) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in sample-projects/typescript/ was NOT MEASURED: the install for sample-projects/typescript/ left no `vitest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in sample-projects/vue/ was NOT MEASURED: the install for sample-projects/vue/ left no `vitest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
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 NuGet package 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.
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 a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — measured, with a gap in what it reached — 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 1 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .kt (49,863 lines, 44% of production source), .ts (47,794 lines, 42% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 4 task marker(s) (TODO/FIXME/HACK/XXX) across 4 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — 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. 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.
D23 Boundary Type-Coupling — 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. Large codebase (108,780 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — 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.
D27 Navigability — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D31 IaC & Container Security — 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
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. `analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/AnalyserDialogInterface.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/LanguageAnalyzer.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/delphi/UnitScope.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlAnalyzer.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/vba/VbaModuleFile.kt`, … (+39 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.
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. User interface: 226 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:9001: page.addScriptTag: Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'sha25 rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:9000: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:9000/
Call log:
- navigating to "http://127.0.0.1:9000/", waiting until "load"
ran the repo's playwright suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics.
DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
DM9 Scattered domain decisions — 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 frontend declares that it computes whether a construction is produced or passed, yet 2293 of 2322 constructions arrived without the answer. Arm two skipped them; it did not clear them.
IC1 Incompleteness & stubs — 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.
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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 60 further occurrence(s) are not listed individually; the score already reflects all 100.
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. 65 further occurrence(s) are not listed individually; the score already reflects all 105.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — 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.
X18 Disposal-pattern 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.
X21 Side-effecting pattern guard — 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.
X24 Document value interpolated into markup unescaped — 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.
X27 Collection changed while being enumerated — 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.
X28 Index access outside its own emptiness guard — 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.
X3 Exception handling — 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages 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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 5 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 LanguageAnalyzerFactory.createAnalyzer at 18 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/LanguageAnalyzerFactory.kt (LanguageAnalyzerFactory.createAnalyzer at 18), analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/dependencies/DependencyResolverService.kt (DependencyResolverService.standardLibraryFor at 18), visualization/app/codeCharta/features/viewCube/viewCube.component.ts (ViewCubeComponent.onCubeClicked at 18), analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/dependencies/LanguageRules.kt (LanguageRules.namesOf at 17), analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/extraction/extractors/common/StringExtractor.kt (StringExtractor.extract at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What 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.
Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Dialog.collectAnalyserArgs (cognitive 16), LabelCollisionService.buildCollisionGroups (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.8 / 10Stronggated by 5 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 4 TooManyMethods finding(s) in God Classes — start with codeMapMesh.ts, threeSceneService.ts, TreeSitterApi.java. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with AttributeDescriptors.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
33 duplicated block group(s) detected. 2.3 % of the production lines (2,449 of 108,780) are in a reported copy. A further 63 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (42% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (4 corresponding lines) · ×8sample-projects/tools/compare_dependency_builds.py:32
Edited copy of a member (15 corresponding lines) · ×7analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/accesslayout/AccessLayoutAnalyzer.kt:34
Edited copy of a member (9 corresponding lines) · ×6analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/SignatureTypeExtractor.kt:28
Edited copy of a member (6 corresponding lines) · ×6analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TypeNames.kt:20
Edited copy of a member (11 corresponding lines) · ×5analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/federation/FederationConfigParser.kt:17
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with compare_dependency_builds.py, AcceptedDependencyReader.kt, LocalNames.kt. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with AccessLayoutAnalyzer.kt, SonarMeasuresAPIDatasource.kt, LogLineCollector.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with DependencyParser.kt (2), SignatureTypeExtractor.kt, DeclarationExtractor.kt. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.9 / 10Strong✓ 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.
42 production modules (Gradle+Cargo+npm+Go+SwiftPM+RubyGems+Composer), 0 dependency cycle(s), 4 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; 6 module(s) off the main sequence, with abstractness counted on 38 of the 42 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with EncounterEdgeCases.kt, FrameworkDetector.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 12 mechanizable ADR(s) are enforced: 12 by analyzers, 0 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, 1 mock references across 1 tests. Measured on the C# suite only — at least 1,283 test source file(s) (.ts, .kt, .java, .js, .tsx, .jsx) went unread, so its test quality is unmeasured and is not in these counts.
Mock framework: NSubstitute
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 97 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 3 direct `PackageReference`(s), and 94 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json and a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Node.kt (9 of 12 changes were fixes); analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/LogicalProjection.kt (6 of 8 changes were fixes); analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/TypeImportResolver.kt (5 of 9 changes were fixes)
Resolve the 21 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Node.kt, LogicalProjection.kt, TypeImportResolver.kt. — One of this dimension's main actionable groups (21 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.4 / 10Adequate✓ 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.
251 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts. Counted over 691 of the 3633 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
1 deducted debt markers + 0 dead symbols across 845 LoC in the .NET projects (0.0/KLoC) → score 9.9. Measured on the .NET source only: .kt, .ts (85% of production source) was not read, and carries at least 4 uncounted task marker(s) in 4 file(s).
Resolve the 1 TodoComment finding(s) in Explicit Debt — start with EncounterEdgeCases.cs. — 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.
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.
2 of 2 documentation facets pass in full. 108 document(s) read across 15 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality5.8 / 10Adequate✓ 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.
12 of 13 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
ADR has no Context section · ×10dev_docs/adr/2017-01-02-ADR_1_decide_tech_stack.md:17detected by adr-integrity
ADR declares no statusdev_docs/adr/2017-01-01-ADR_0_write_adrs.md:19detected by adr-integrity
ADR has no Context and Decision sectiondev_docs/adr/2023-10-09-ADR_10_change_visualization_standalone.md:30detected by adr-integrity
ADR links a record that does not existdev_docs/adr/2017-01-02-ADR_3_pick_visualization_language.md:16detected by adr-integrity
What to do
Resolve the 10 ADR has no Context section finding(s) in ADR Quality — start with 2017-01-02-ADR_1_decide_tech_stack.md, 2017-01-02-ADR_2_pick_analysis_language.md, 2017-01-02-ADR_3_pick_visualization_language.md. — One of this dimension's main actionable groups (10 recommendation-level).
Resolve the 1 ADR declares no status finding(s) in ADR Quality — start with 2017-01-01-ADR_0_write_adrs.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 ADR has no Context and Decision section finding(s) in ADR Quality — start with 2023-10-09-ADR_10_change_visualization_standalone.md. — 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.
Do you agree with this assessment?
D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
140 finding(s): 0 critical, 130 high, 10 medium, 0 low. 87 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 33 file(s) — `analysis/gradlew` (line 74, line 178), `analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeId.kt` (line 57), `analysis/script/automated_sonar_analysis/helpers.sh` (line 127), `sample-projects/bash/lib/adapter/persistence/creature_entity.sh` (line 14, line 19), `sample-projects/bash/lib/application/creature_util.sh` (line 34, lines 34–38), … (+28 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. In 1 of those file(s) — `sample-projects/csharp/src/De.Sots.CellarsAndCentaurs/Domain/Service/EncounterEdgeCases.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 5 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
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 21 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 issue-level).
No action in Static Analysis (SAST) — all 87 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (87 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
12 finding(s): 0 critical, 3 high, 8 medium, 1 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
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.
Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
83 of 691 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts. Counted over 691 of the 3633 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with metricColorRangeDiagram.component.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 82 Orphaned file finding(s) in Knowledge Freshness — start with Dialog.kt (6), AttributeDescriptors.kt (4), CSVProjectBuilder.kt (2). — One of this dimension's main actionable groups (82 recommendation-level).
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.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with DialogDrawing.kt (2), CodeMaatImporter.kt (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with GitLogParser.kt, ValidationTool.kt, CSVImporter.kt. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 36 platform declaration(s) and 60 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
`EncounterEdgeCases` references the aggregate root `EncounterResolver` directly (via `resolver`) — hold its `EncounterResolverId` instead. — sample-projects/rust/src/domain/service/encounter_edge_cases.rs:28
What to do
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
`CreatureEntity`'s public constructor takes `type` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CreatureEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — sample-projects/java/src/main/java/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.java:19
`Creature`'s public constructor takes `xp_value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Creature` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — sample-projects/python/de/sots/cellarsandcentaurs/domain/model/creature.py:16
What to do
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Do you agree with this assessment?
DM4 · Rich vs anemic model8.8 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Creature` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — sample-projects/ruby/lib/de/sots/cellars_and_centaurs/domain/model/creature.rb:16
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
`Creature` exposes exported guard-free setter(s) (SetType, SetArmorClass, SetSpeeds, SetHitPoints) that rewrite business state without enforcing invariants. — sample-projects/go/domain/model/creature.go:34
What to do
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.
Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.
Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
visualization.app.codeCharta.model.rectangle.Rectangle's [x, y] are judged in visualization.app.codeCharta.renderer.dependencyGraph.util.axisWindow, visualization.app.codeCharta.renderer.dependencyGraph.util.geometry, visualization.app.codeCharta.renderer.dependencyGraph.util.overlaps, visualization.app.codeCharta.renderer.dependencyGraph.util.paintOrder — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel.LayoutBox's [declarationCount, kind] are judged in visualization.app.codeCharta.renderer.dependencyGraph.util.dependencyGraphBoxes, visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in 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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
visualization/README.md links to `../DEV_START_GUIDE.md`, but `DEV_START_GUIDE.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. — visualization/README.md:174
What to do
Reconcile the README with reality: visualization/README.md links to `../DEV_START_GUIDE.md`, but `DEV_START_GUIDE.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language'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.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse. — REDACTED:40
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety9.5 / 10Exemplary✓ 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.
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.
33 duplicated blocks under visualization/app/codeCharta/features/ have copies in at least two of the sibling directories changelog, clusterExplorer, codeMap, dependencyMap, domainBar, domainToolbox (+16 more sibling(s) not listed) — 20 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 33 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9
15 duplicated blocks under visualization/app/codeCharta/ have copies in at least two of the sibling directories features, load, renderer, stores, views — 4 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.ts:64
14 of the duplicated blocks reported below have copies in at least two of the sibling directories javascript, typescript, vue under sample-projects/. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13
6 duplicated blocks under visualization/app/codeCharta/stores/ have copies in at least two of the sibling directories dependencyLensSource, domainLensSource, domainState, fileStore, mapState, metricsLensSource (+2 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — visualization/app/codeCharta/stores/domainState/store/domainState.reducer.ts:18
visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts:21 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:19 — the two spans are one implementation copied and then locally edited — 1175 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. — visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts:21
sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:11 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.vue:12 — 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. — sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:11
visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/horizontalStrip.ts:7 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/verticalStrip.ts:7 — 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. — visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/horizontalStrip.ts:7
sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:14 — the two spans are one implementation copied and then locally edited — 200 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. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13
visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:97 · visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:159 — the two spans are one implementation copied and then locally edited — 278 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. — visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:97
sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:25 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:25 — the two spans are one implementation copied and then locally edited — 137 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. — sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:25
sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Creature.js:29 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:23 — the two spans are one implementation copied and then locally edited — 106 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. — sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Creature.js:29
visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:271 · visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts:131 — 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. — visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:271
visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV6.ts:4 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV7.ts:4 — 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. — visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV6.ts:4
sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:13 · sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:12 — the two spans are one implementation copied and then locally edited — 173 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. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:13
visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV4.ts:10 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV5.ts:8 — 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. — visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV4.ts:10
visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV8.ts:8 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV9.ts:8 — 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. — visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV8.ts:8
visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:98 · visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:217 — the two spans are one implementation copied and then locally edited — 134 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. — visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:98
visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/qrCodeSettings/qrCodeSettings.component.ts:3 · visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/secondRowTextInput/secondRowTextInput.component.ts:3 — 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. — visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/qrCodeSettings/qrCodeSettings.component.ts:3
sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6 — the two spans are one implementation copied and then locally edited — 73 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. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6
visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:403 · visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:422 — 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. — visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:403
visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/backMWLogoMesh.ts:7 · visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/codeChartaLogoMesh.ts:9 — the two spans are one implementation copied and then locally edited — 83 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. — visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/backMWLogoMesh.ts:7
visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:22 · visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:23 — 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. — visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:22
visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9 · visualization/app/codeCharta/features/radialMap/stores/radialMap.write.store.ts:6 — the two spans are one implementation copied and then locally edited — 96 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. — visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9
visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:50 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:86 — 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. — visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:50
sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1 — the two spans are one implementation copied and then locally edited — 90 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. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1
visualization/app/codeCharta/features/dependencyMap/components/boxBadgesSegment/boxBadgesSegment.component.ts:19 · visualization/app/codeCharta/features/metricsBar/components/edgeSettingsPopover/edgeSettingsPopover.component.ts:18 — 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. — visualization/app/codeCharta/features/dependencyMap/components/boxBadgesSegment/boxBadgesSegment.component.ts:19
visualization/app/codeCharta/views/dependencyView/explorer/dependencyExplorerSelection.ts:10 · visualization/app/codeCharta/views/metricsView/explorer/metricsExplorerSelection.ts:9 — 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. — visualization/app/codeCharta/views/dependencyView/explorer/dependencyExplorerSelection.ts:10
visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:372 · visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:388 — 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. — visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:372
visualization/app/codeCharta/util/color/gradientCalculator.ts:51 · visualization/app/codeCharta/util/color/gradientCalculator.ts:83 — 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. — visualization/app/codeCharta/util/color/gradientCalculator.ts:51
visualization/app/codeCharta/util/nodeDecorator.ts:245 · visualization/app/codeCharta/util/nodeDecorator.ts:272 — 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. — visualization/app/codeCharta/util/nodeDecorator.ts:245
sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Dice.js:5 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:5 — the two spans are one implementation copied and then locally edited — 67 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. — sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Dice.js:5
visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:8 · visualization/app/codeCharta/features/shared/stores/resetSettingsButton.store.ts:8 — 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. — visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:8
visualization/app/codeCharta/stores/fileStore/store/fileStore.readWindow.ts:12 · visualization/app/codeCharta/stores/mapState/store/mapState.readWindow.ts:38 · visualization/app/codeCharta/stores/preferences/store/preferences.readWindow.ts:18 · visualization/app/codeCharta/stores/sharedView/store/sharedView.readWindow.ts:15 — the 4 copies are spread across 4 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. — visualization/app/codeCharta/stores/fileStore/store/fileStore.readWindow.ts:12
sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js:36 · sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:27 — the two spans are one implementation copied and then locally edited — 107 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. — sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js:36
visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/backPrintColorChangeStrategy.ts:9 · visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/frontPrintColorChangeStrategy.ts:5 — 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. — visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/backPrintColorChangeStrategy.ts:9
visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:4 · visualization/app/codeCharta/features/labelSettings/stores/labelSettings.write.store.ts:15 — 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. — visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:4
visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:75 · visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts:45 · visualization/app/codeCharta/renderer/wordCloud/components/wordCloud/wordCloudChartHost.ts:64 — the 3 copies are spread across 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:75
visualization/app/codeCharta/stores/dependencyLensSource/store/dependencyLensSource.readWindow.ts:6 · visualization/app/codeCharta/stores/domainLensSource/store/domainLensSource.readWindow.ts:6 · visualization/app/codeCharta/stores/domainState/store/domainState.readWindow.ts:6 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — visualization/app/codeCharta/stores/dependencyLensSource/store/dependencyLensSource.readWindow.ts:6
visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:170 · visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts: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. — visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:170
sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:10 · sample-projects/vue/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:9 — the two spans are one implementation copied and then locally edited — 97 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. — sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:10
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:6 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:6
visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:7 imports visualization/app/codeCharta/mocks/state.mocks.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:7
visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.mocks.ts:12 imports visualization/app/codeCharta/mocks/state.mocks.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.mocks.ts:12
visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:1 imports visualization/app/codeCharta/util/testUtils/domStubs.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:1
visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:3 imports visualization/app/codeCharta/util/testUtils/domStubs.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:3
visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapBuilding.mocks.ts:2 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapBuilding.mocks.ts:2
What to do
Fix the listed violations: move the shared test helper into a source directory production code may depend on (6 rows).
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.
provideExplorerPortsMock has cyclomatic complexity 13 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 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. — visualization/app/codeCharta/features/sidebarExplorer/explorerPorts.mocks.ts:132
getPrintColor has cyclomatic complexity 12 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. — visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/mapMesh.ts:62
decorateNode has cyclomatic complexity 12 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. — visualization/app/codeCharta/util/nodeDecorator.ts:88
drawConnectors has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — visualization/app/codeCharta/features/labelSettings/services/connectorDrawing.service.ts:27
resolve 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. (×2) — sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:13, sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:14
buildPairingEdges 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. — visualization/app/codeCharta/features/codeMap/arrow/codeMap.arrow.service.ts:169
updateHighlight has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.ts:193
memberSlices 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. — visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/jsonBytes.ts:57
getColorByWeightedGradient has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — visualization/app/codeCharta/util/color/gradientCalculator.ts:92
resolveNodeMetricSelection has cyclomatic complexity 11 and cognitive complexity 9; 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. — visualization/app/codeCharta/load/effects/reconcileAfterLoad/resolveMetricSelection.ts:59
Do you agree with this assessment?
R3 · Large Files9.9 / 10Exemplary✓ 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 2429 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
visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts:1
visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.1 / 10Exemplary✓ 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.
sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts:2 imports './missing', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts: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. (×39) — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts:1, sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.js:1, sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · 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 root package declares the lint script `format` (`biome check --write --no-errors-on-unmatched`), 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 format` in `.` (or the workspace's task runner). — package.json:23
This repository declares test tooling, and the ✓ above records that declaration — but sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts:2
Do you agree with this assessment?
R7 · Dead Code9.1 / 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.
1 file(s) (~1 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. — sample-projects/regression/typescript/spec-workspace-subpath/src/packages/core
Unreachable from the 51 application, 29 tooling and 937 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 (51 application, 29 tooling, 937 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 (×23) — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts, sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue, sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js, …
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.vue
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCasesTsx.vue, sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/encounterReport.mts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/Repository.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/creatureEntityMapper.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Centaur.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/lairKeeper.mts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Zentaurenhöhle.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Stable.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCasesTsx.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/SpeedBadge.tsx
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/creatureEntityMapper.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/hoardLedger.cts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/ZentaurenhöhlePanel.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Zentaurenhöhle.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/NoSuchCreatureException.ts
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/ui/CreatureCard.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/ui/SpeedBadge.jsx
no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/decorators.ts
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — sample-projects/regression/angular/spec-ambiguous-selector/src/app/card.component.ts:1
Declared in the root 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. — package.json:32
Declared in analysis/node-wrapper/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) — analysis/node-wrapper/package.json:27, analysis/node-wrapper/package.json:28
Declared in sample-projects/angular/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. — sample-projects/angular/package.json:21
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports3.7 / 10Weak✓ 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.
sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js → sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.js → sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/index.js → sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js (one verified cycle inside a mutually-dependent group of 6 files) — sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js:10
sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts → sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts → sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/index.ts → sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts (one verified cycle inside a mutually-dependent group of 6 files) — sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:11
sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts → sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts → sample-projects/vue/src/de/sots/cellarsandcentaurs/application/index.ts → sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts (one verified cycle inside a mutually-dependent group of 6 files) — sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:10
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.6 `!` suppressions per 1k syntax nodes — 2 suppression(s) across the 3464 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. 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
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
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 — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:9001: page.addScriptTag: Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'sha25 rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:9000: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:9000/
Call log:
- navigating to "http://127.0.0.1:9000/", waiting until "load"
ran the repo's playwright suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics. This repository also has a user interface (226 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — JavaScript/TypeScript suite in sample-projects/typescript/ was not re-run
D12 Dependency Hygiene — Dependency hygiene not measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .bas, .c, .c++, .cc, .cpp, .cts, .cxx, .go, .java, .kt, .m, .mm, .mts, .pas, .php, .py, .rb, .rs, .swift, .ts, .tsx, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — None of 11 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .bas, .c, .c++, .cc, .cpp, .cts, .cxx, .go, .java, .m, .mm, .mts, .pas, .php, .py, .rb, .rs, .swift, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 44 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.
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the node:test suite in sample-projects/javascript/ ran and not one test passed (throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);), so the coverage would describe the failed run, not the code. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: 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.
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM8 Value-object opportunities — not scored — the deterministic rule found 1 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — IC1 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X1 Async correctness — X1 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — 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 async method does work a token could cancel
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — X21 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 45% of this repository's production lines — kotlin (49,863 lines), pascal (2,390 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — X28 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — X4 reached only 1% of this repository's production lines — kotlin (49,863 lines), typescript (49,166 lines), pascal (2,390 lines), javascript (2,341 lines), php (1,740 lines), rust (1,686 lines), c (1,495 lines), java (1,493 lines), cpp (1,376 lines), python (1,184 lines), go (1,050 lines), swift (918 lines), objectivec (908 lines), ruby (872 lines), vba (287 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
Orphaned knowledge visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts: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.
DM1 · Aggregate boundaries· Aggregate holds a reference to another aggregate · ×1
Aggregate holds a reference to another aggregate: EncounterEdgeCases.resolver sample-projects/rust/src/domain/service/encounter_edge_cases.rs:28— `EncounterEdgeCases` references the aggregate root `EncounterResolver` directly (via `resolver`) — hold its `EncounterResolverId` instead.
Unlisted import '@angular/core' sample-projects/regression/angular/spec-ambiguous-selector/src/app/card.component.ts:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 337 finding(s)
R4 · Test Coverage· No test reaches this file · ×39
No test reaches this file sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.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 sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.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 sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue: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 visualization/conf/dependencyCruiser/viewAndFeatureRules.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 visualization/conf/dependencyCruiser/storeRules.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 visualization/conf/dependencyCruiser/facadeRules.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 visualization/conf/dependencyCruiser/rendererRules.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 sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.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 sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.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 sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.vue: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 sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.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 visualization/conf/setupJestUnit.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 visualization/conf/dependencyCruiser/lensRules.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 visualization/conf/dependencyCruiser/loadRules.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 visualization/script/appDownload.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 visualization/electron/main.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 visualization/script/appMain.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 visualization/script/appBuild.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 visualization/script/appZip.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 visualization/script/lintComponentStyles.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 sample-projects/angular/src/app/app.component.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 sample-projects/javascript/src/de/sots/cellarsandcentaurs/adapter/persistence/Repository.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 sample-projects/javascript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.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 visualization/conf/dependencyCruiser/generalRules.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 sample-projects/angular/src/app/ui/encounter-edge-cases.component.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.
Repeated repair: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Node.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Node.kt:26— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Node.kt changed 12 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is Node.name at line 26), 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/dependency name resolution typescript bindings (#4626)”; “fix(analysis): look a C# name up in each enclosing namespace before its usings”; “fix(analysis): resolve a C# name to the nested type of the own or the base type first”; “fix(analysis): let a Kotlin private top-level declaration be seen in its file only”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Node.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/LogicalProjection.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/LogicalProjection.kt:86— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/LogicalProjection.kt changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is LogicalProjection.edgesBetween at line 86), 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(analysis): find cycles between declarations by file and logical path”; “Fix/dependency name resolution typescript bindings (#4626)”; “fix(analysis): resolve a name only within its language's name scope”; “fix(analysis): point a name declared in several files at the nearest copy”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/LogicalProjection.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/TypeImportResolver.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/TypeImportResolver.kt:93— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/TypeImportResolver.kt changed 9 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 3 (its worst body is TypeImportResolver.endsWithPackage at line 93), 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(analysis): look a C# name up in each enclosing namespace before its usings”; “fix(analysis): let a Kotlin private top-level declaration be seen in its file only”; “fix(analysis): resolve Java and Kotlin names only by their import rules”; “fix(analysis): resolve Java and Kotlin qualified names through their qualifier”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/TypeImportResolver.kt`: 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: analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LineClassifier.kt analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LineClassifier.kt:155— analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LineClassifier.kt 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 7 (its worst body is LineClassifier.scanRegion at line 155), 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(analysis): skip the byte order mark when the raw text parser counts lines”; “fix(analysis): read placeholders of javascript template literals as code”; “fix(analysis): count a python string as docstring only when it stands alone”; “fix(analysis): read ruby regex and percent literals in the raw text parser”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LineClassifier.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/FileLevelAggregator.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/FileLevelAggregator.kt:24— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/FileLevelAggregator.kt 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 2 (its worst body is FileLevelAggregator.aggregate at line 24), 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(analysis): find cycles between declarations by file and logical path”; “Fix/dependency name resolution typescript bindings (#4626)”; “fix(analysis): resolve a name only within its language's name scope”; “fix(analysis): point a name declared in several files at the nearest copy”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/FileLevelAggregator.kt`: 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: visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.ts visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.ts:92— visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.ts changed 6 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 4 (its worst body is BoxDragGesture.flush at line 92), 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(visualization): forget a right drag on the next press anywhere”; “fix(visualization): select a box on the first click after dragging”; “fix(visualization): keep the dependency graph from panning while a box is dragged”; “fix(visualization): see-through overlapping folders and a reachable dependency view”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.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: analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/ProjectScanner.kt analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/ProjectScanner.kt:166— analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/ProjectScanner.kt changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ProjectScanner.isParsableFile at line 166), 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(analysis): read VBA modules and Access queries in the Windows code page”; “fix(analysis): count the files the unified parser finished without losing any”; “fix(analysis): name the cause in the error of a run that analysed no file (#4596)”; “fix(analysis): analyse non-ascii file names under a non-utf-8 locale”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/ProjectScanner.kt`: 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: visualization/app/codeCharta/renderer/radialMap/util/radialTreemapLayout.ts visualization/app/codeCharta/renderer/radialMap/util/radialTreemapLayout.ts:46— visualization/app/codeCharta/renderer/radialMap/util/radialTreemapLayout.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is radialTreemapLayout.placeChildren at line 46), 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(visualization): put a radial folder's contents one band further out”; “fix(visualization): keep a radial folder's files in their own share”; “fix(visualization): draw the open folder's files as treemap cells”; “fix(visualization): keep radial treemap pieces and labels in place”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- visualization/app/codeCharta/renderer/radialMap/util/radialTreemapLayout.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: analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LanguageSyntax.kt analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LanguageSyntax.kt:27— analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LanguageSyntax.kt 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 1 (its worst body is MeasuredBlock.opensAt at line 27), 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(analysis): read placeholders of javascript template literals as code”; “fix(analysis): count a python string as docstring only when it stands alone”; “fix(analysis): read ruby regex and percent literals in the raw text parser”; “fix(analysis): end pascal and sql strings at the quote after a backslash”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/language/LanguageSyntax.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpAnalyzer.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpAnalyzer.kt:47— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpAnalyzer.kt changed 5 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 2 (its worst body is CSharpAnalyzer.namespaceOf at line 47), 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/dependency name resolution typescript bindings (#4626)”; “fix(analysis): look a C# name up in each enclosing namespace before its usings”; “fix(analysis): resolve a name written through a C# using alias to its target”; “fix(analysis): let a nested C# type see its namespace and its usings”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpAnalyzer.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/kotlin/KotlinAnalyzer.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/kotlin/KotlinAnalyzer.kt:22— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/kotlin/KotlinAnalyzer.kt changed 5 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 2 (its worst body is KotlinAnalyzer.convertImport at line 22), 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(analysis): let a Kotlin import alias stand for its class as a qualifier”; “fix(analysis): let a Kotlin import alias hide the imported name”; “fix(analysis): resolve a kotlin import alias through its full path”; “fix(analysis): find the kotlin dependencies the dependency parser missed”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/kotlin/KotlinAnalyzer.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/DeclaringFiles.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/DeclaringFiles.kt:23— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/DeclaringFiles.kt changed 4 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 6 (its worst body is DeclaringFiles.filesFor at line 23), 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/dependency name resolution typescript bindings (#4626)”; “fix(analysis): let a Kotlin private top-level declaration be seen in its file only”; “fix(analysis): keep the first declaring file for C# until its rules exist”; “fix(analysis): resolve a name only within its language's name scope”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/DeclaringFiles.kt`: 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: visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphElements.ts visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphElements.ts:15— visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphElements.ts changed 4 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 2 (its worst body is dependencyGraphElements.drawnItem at line 15), 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(visualization): forget a right drag on the next press anywhere”; “fix(visualization): remove a dependency graph box's name once it no longer fits”; “fix(visualization): keep the marks of a dependency graph box in place after zooming”; “fix(visualization): keep the dependency graph's paint order after boxes reappear”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphElements.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: analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/shared/domain/MetricCondition.kt analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/shared/domain/MetricCondition.kt:64— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/shared/domain/MetricCondition.kt 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 2 (its worst body is MetricCondition.hasType at line 64), 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(analysis): count a sql line of dashes alone as comment”; “fix(analysis): name the cause in the error of a run that analysed no file (#4596)”; “fix(analysis): count kotlin functions and nested functions in unifiedparser”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/shared/domain/MetricCondition.kt`: 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: analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/UsedTypeExtractor.kt analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/UsedTypeExtractor.kt:48— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/UsedTypeExtractor.kt 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 5 (its worst body is UsedTypeExtractor.extract at line 48), 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(analysis): update tree-sitter and seven grammars”; “Fix/dependency name resolution typescript bindings (#4626)”; “fix(analysis): match the old Go analyzer on broken Go code”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/UsedTypeExtractor.kt`: 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: analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaAccessObjects.kt analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaAccessObjects.kt:36— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaAccessObjects.kt 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 5 (its worst body is VbaAccessObjects.openedBy at line 36), 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(analysis): read the forms and reports VBA names in brackets”; “fix(analysis): point the domain functions, row sources and typed DoCmd calls at their object”; “fix(analysis): point a project's AllForms and AllReports at the form or report”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaAccessObjects.kt`: 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: analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/scan/SourceFileScanner.kt analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/scan/SourceFileScanner.kt:30— analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/scan/SourceFileScanner.kt 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 6 (its worst body is SourceFileScanner.scanProject at line 30), 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(analysis): read VBA modules and Access queries in the Windows code page”; “fix(analysis): name the cause in the error of a run that analysed no file (#4596)”; “fix(analysis): analyse non-ascii file names under a non-utf-8 locale”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/scan/SourceFileScanner.kt`: 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: analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/metrics/calculators/RealLinesOfCodeCalc.kt analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/metrics/calculators/RealLinesOfCodeCalc.kt:25— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/metrics/calculators/RealLinesOfCodeCalc.kt 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 12 (its worst body is RealLinesOfCodeCalc.calculateMetricForNode at line 25), 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(analysis): skip tokens the parser inserts when it counts real lines of code”; “fix(analysis): stop counting phantom lines in rloc of the unified parser”; “fix(analysis): count kotlin functions and nested functions in unifiedparser”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/metrics/calculators/RealLinesOfCodeCalc.kt`: 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: analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/BaseLanguageAnalyzer.kt analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/BaseLanguageAnalyzer.kt:22— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/BaseLanguageAnalyzer.kt 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 2 (its worst body is BaseLanguageAnalyzer.analyze at line 22), 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(analysis): let a Kotlin private top-level declaration be seen in its file only”; “fix(analysis): name the cause in the error of a run that analysed no file (#4596)”; “fix(analysis): find the kotlin dependencies the dependency parser missed”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/BaseLanguageAnalyzer.kt`: 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: visualization/app/codeCharta/features/localSource/components/sourceViewer/sourceViewer.component.ts visualization/app/codeCharta/features/localSource/components/sourceViewer/sourceViewer.component.ts:67— visualization/app/codeCharta/features/localSource/components/sourceViewer/sourceViewer.component.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 5 (its worst body is SourceViewerComponent.open at line 67), 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(visualization): keep the source viewer's code out of the Tab order”; “fix(visualization): resolve the review findings of the local source”; “fix(visualization): return to the map when going back from the source”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- visualization/app/codeCharta/features/localSource/components/sourceViewer/sourceViewer.component.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: analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/kotlin/extractors/ValueReferenceExtractor.kt analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/kotlin/extractors/ValueReferenceExtractor.kt:58— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/kotlin/extractors/ValueReferenceExtractor.kt 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 10 (its worst body is ValueReferenceExtractor.referencedName at line 58), 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(analysis): stop reporting the class a Kotlin call goes through as a use”; “fix(analysis): resolve Java and Kotlin member types by the name rules”; “fix(analysis): let a kotlin inner class depend on the class around it”. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 19:40:59 +01:00' --until='2026-11-10 19:40:59 +01:00' --full-history --no-merges -- analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/kotlin/extractors/ValueReferenceExtractor.kt`: 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 (4 corresponding lines) · ×8
Edited copy of a member (4 corresponding lines) sample-projects/tools/compare_dependency_builds.py:32— sample-projects/tools/compare_dependency_builds.py:32-35 | sample-projects/tools/dump_lenses.py:11-14 — 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) analysis/analysers/tools/GateTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/gate/config/AcceptedDependencyReader.kt:7— analysis/analysers/tools/GateTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/gate/config/AcceptedDependencyReader.kt:7-10 | analysis/analysers/tools/GateTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/gate/config/MetricRuleReader.kt:12-15 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/LocalNames.kt:52— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/LocalNames.kt:52-55 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/LocalScopes.kt:86-89 — 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) analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/CloverStrategy.kt:18— analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/CloverStrategy.kt:18-21 | analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/PHPUnitStrategy.kt:18-21 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/DeclarationExtractor.kt:103— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/DeclarationExtractor.kt:103-106 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/SqlNameCollector.kt:162-165 — 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) analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/DomainPathRemapper.kt:38— analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/DomainPathRemapper.kt:38-41 | analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeId.kt:41-44 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/NameCollector.kt:123— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/NameCollector.kt:123-126 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaNameCollector.kt:158-161 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/SpecifierNames.kt:7— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/SpecifierNames.kt:7-10 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/ForwardClassesExtractor.kt:8-12 — 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· Edited copy of a member (15 corresponding lines) · ×7
Edited copy of a member (15 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/accesslayout/AccessLayoutAnalyzer.kt:34— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/accesslayout/AccessLayoutAnalyzer.kt:34-50 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/accessmacro/AccessMacroAnalyzer.kt:29-43 — 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) analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/dataaccess/SonarMeasuresAPIDatasource.kt:83— analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/dataaccess/SonarMeasuresAPIDatasource.kt:83-98 | analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/dataaccess/SonarMetricsAPIDatasource.kt:64-78 — 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) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:43— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:43-57 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineCollector.kt:45-59 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/DelphiIdentifierExtractors.kt:14— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/DelphiIdentifierExtractors.kt:14-32 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/DelphiIdentifierExtractors.kt:34-48 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TyperefResolver.kt:88— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TyperefResolver.kt:88-102 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TyperefResolver.kt:104-121 — 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) analysis/analysers/tools/ConvertTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/convert/Dialog.kt:13— analysis/analysers/tools/ConvertTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/convert/Dialog.kt:13-27 | analysis/analysers/tools/InspectionTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/inspection/Dialog.kt:13-28 — 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) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/CommitCollector.kt:20— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/CommitCollector.kt:20-35 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/CommitCollector.kt:48-62 — 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.
Change coupling: DialogDrawing.kt ↔ DialogProvider.kt analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogDrawing.kt:1— `analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogDrawing.kt` and `analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt` change together 100% of the time (11 of the 11 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `7ba3da41` refactor(analysis): reduce parameter count in drawInput by merging su…; `eae530c9` feat(analysis): add review notes (#3923); `ef7fa989` feat(analysis): add console cleanup, enable case-sensitive completion… — run `git show` on any of them.
Change coupling: DialogDrawing.kt ↔ DirectoryNavigator.kt analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogDrawing.kt:1— `analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogDrawing.kt` and `analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DirectoryNavigator.kt` change together 64% of the time (7 of the 11 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `eae530c9` feat(analysis): add review notes (#3923); `fcc421ad` feat(analysis): include validation in Navigator, renaming, code clean…; `538749d4` feat(analysis): reformat code and wip cleanup (#3923) (at that commit the file was still `analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogDirectoryProvider.kt`) — run `git show` on any of them.
Change coupling: REDACTED ↔ dependencyGraph.model.ts REDACTED:1— `REDACTED` and `visualization/app/codeCharta/model/dependencyGraph.model.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 `447094bd` feat(visualization): let the dependency graph's hover highlight be sw…; `0906e1ac` feat(visualization): switch each badge of the dependency view on its own; `13348fbd` feat(visualization): let the hover respect the edges shown in the dep… — run `git show` on any of them.
Change coupling: CodeMaatImporter.kt ↔ TokeiImporter.kt analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt:1— `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt` and `analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/TokeiImporter.kt` change together 53% of the time (10 of the 19 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 10 shared commits counted here, the most recent 3 are `617c0743` refactor: move CodeChartaConstants to model util #4146; `05ae6f34` refactor(analysis): move the sync flag from the AnalyserInterfacer to…; `676f5fff` refactor(analysis): move callable interface reference from analysers … (at that commit the files were still `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/importer/codemaat/CodeMaatImporter.kt` and `analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/importer/tokeiimporter/TokeiImporter.kt`) — run `git show` on any of them.
Change coupling: CodeMaatImporter.kt ↔ SVNLogParser.kt analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt:1— `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/SVNLogParser.kt` change together 53% of the time (10 of the 19 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 10 shared commits counted here, the most recent 3 are `38dda5d7` refactor(analysis): replace if-throw patterns with require/check/requ…; `617c0743` refactor: move CodeChartaConstants to model util #4146; `05ae6f34` refactor(analysis): move the sync flag from the AnalyserInterfacer to… — run `git show` on any of them.
Change coupling: dependencyGraph.model.ts ↔ indexedDBWriter.ts visualization/app/codeCharta/model/dependencyGraph.model.ts:1— `visualization/app/codeCharta/model/dependencyGraph.model.ts` and `visualization/app/codeCharta/stores/rootStore/indexedDB/indexedDBWriter.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 5 shared commits counted here, the most recent 3 are `447094bd` feat(visualization): let the dependency graph's hover highlight be sw…; `0906e1ac` feat(visualization): switch each badge of the dependency view on its own; `42476276` refactor(visualization): finish the review follow-ups of the dependen… — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/SignatureTypeExtractor.kt:28— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/SignatureTypeExtractor.kt:28-38 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/UsedTypeExtractor.kt:84-92 — 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) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:180— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:180-188 | analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/DomainLanguageParser.kt:199-209 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/DeclarationExtractor.kt:91— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/DeclarationExtractor.kt:91-99 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/DeclarationPrepass.kt:35-43 — 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) analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVProjectBuilder.kt:45— analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVProjectBuilder.kt:45-53 | analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CSVProjectBuilder.kt:67-77 — 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) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:118— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:118-126 | analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/UnifiedParser.kt:92-100 — 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) analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/ProjectMetricsCollector.kt:162— analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/ProjectMetricsCollector.kt:162-172 | analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/ProjectScanner.kt:196-204 — 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) · ×6
Edited copy of a member (6 corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TypeNames.kt:20— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TypeNames.kt:20-26 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/TypeNames.kt:29-34 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/CommonJsExports.kt:18— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/CommonJsExports.kt:18-24 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/php/extractors/IncludePaths.kt:56-61 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/DeclarationExtractor.kt:96— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/DeclarationExtractor.kt:96-101 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/sql/extractors/SqlNameCollector.kt:111-116 — 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) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/delphi/DelphiProject.kt:51— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/delphi/DelphiProject.kt:51-56 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlProject.kt:116-121 — 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) analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/util/CommaSeparatedStringToListConverter.kt:6— analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/util/CommaSeparatedStringToListConverter.kt:6-11 | analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/util/FileExtensionConverter.kt:6-15 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/ReexportDeclarationExtractor.kt:31— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/ReexportDeclarationExtractor.kt:31-38 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/TopLevelCode.kt:58-63 — 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.
Off the main sequence: de.sots/dicebag — de.sots/dicebag: 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: codecharta:treeSitterExcavationSite — codecharta:treeSitterExcavationSite: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: codecharta:model — codecharta:model: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: codecharta:dialogProvider — codecharta:dialogProvider: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: CellarsAndCentaurs — CellarsAndCentaurs: abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: codecharta:analysers:AnalyserInterface — codecharta:analysers:AnalyserInterface: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:6— visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:6 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:7— visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.mocks.ts:7 imports visualization/app/codeCharta/mocks/state.mocks.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.mocks.ts:12— visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.mocks.ts:12 imports visualization/app/codeCharta/mocks/state.mocks.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:1— visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:1 imports visualization/app/codeCharta/util/testUtils/domStubs.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:3— visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:3 imports visualization/app/codeCharta/util/testUtils/domStubs.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapBuilding.mocks.ts:2— visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapBuilding.mocks.ts:2 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/federation/FederationConfigParser.kt:17— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/federation/FederationConfigParser.kt:17-30 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/tsconfig/TsConfigParser.kt:19-29 — 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) analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/DomainLens.kt:16— analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/DomainLens.kt:16-26 | analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/LensMerging.kt:3-13 — 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) analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeId.kt:46— analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeId.kt:46-61 | analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/PathFactory.kt:12-22 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/syntax/CppNamespaceWalker.kt:12— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/syntax/CppNamespaceWalker.kt:12-22 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/UsingDirectiveExtractor.kt:20-30 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/LambdaCapturesExtractor.kt:9— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/LambdaCapturesExtractor.kt:9-21 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/TuplePatternExtractor.kt:15-25 — 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.
Dead file (~7 LoC) sample-projects/angular/src/app/domain/model/centaur.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~7 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/ui/SpeedBadge.jsx— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/ui/CreatureCard.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/creatureEntityMapper.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/decorators.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/CreatureViewer.vue— no import path from any entry point (51 application, 29 tooling, 937 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
TooManyMethods: CodeMapMesh visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts:54— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ThreeSceneService visualization/app/codeCharta/renderer/threeViewer/threeSceneService.ts:25— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TreeSitterApi analysis/treeSitterExcavationSite/src/main/java/de/maibornwolff/treesitter/excavationsite/shared/infrastructure/ffm/TreeSitterApi.java:26— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MetricsBarWriteStore visualization/app/codeCharta/features/metricsBar/stores/metricsBar.write.store.ts:48— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: GitLogParser.kt → TokeiImporter.kt, RawTextParser.kt, SVNLogParser.kt analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/GitLogParser.kt— `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/GitLogParser.kt` changes together with 3 other files — `analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/TokeiImporter.kt`, `analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/RawTextParser.kt`, `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/SVNLogParser.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: ValidationTool.kt → EdgeFilter.kt, CSVImporter.kt, CodeMaatImporter.kt, SonarImporter.kt, SourceMonitorImporter.kt, TokeiImporter.kt, SVNLogParser.kt analysis/analysers/tools/ValidationTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/validation/ValidationTool.kt— `analysis/analysers/tools/ValidationTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/validation/ValidationTool.kt` changes together with 7 other files — `analysis/analysers/filters/EdgeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/edgefilter/EdgeFilter.kt`, `analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVImporter.kt`, `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt`, `analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarImporter.kt`, `analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/SourceMonitorImporter.kt`, `analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/TokeiImporter.kt`, `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/SVNLogParser.kt` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Change-coupling hub: CSVImporter.kt → CodeMaatImporter.kt, SonarImporter.kt, SourceMonitorImporter.kt, TokeiImporter.kt analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVImporter.kt— `analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVImporter.kt` changes together with 4 other files — `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt`, `analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarImporter.kt`, `analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/SourceMonitorImporter.kt`, `analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/TokeiImporter.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: dependencyMap.component.ts → dependencyEdgeLegend.component.ts, dependencyGraph.model.ts, dependencyGraphBoxes.ts, dependencyGraphOption.builder.ts, dependencyGraphTooltip.ts visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.ts— `visualization/app/codeCharta/features/dependencyMap/components/dependencyMap/dependencyMap.component.ts` changes together with 5 other files — `visualization/app/codeCharta/features/dependencyMap/components/dependencyEdgeLegend/dependencyEdgeLegend.component.ts`, `visualization/app/codeCharta/model/dependencyGraph.model.ts`, `visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphBoxes.ts`, `visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphOption.builder.ts`, `visualization/app/codeCharta/renderer/dependencyGraph/util/dependencyGraphTooltip.ts` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarComponentProjectBuilder.kt:89— analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarComponentProjectBuilder.kt:89-96 | analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarComponentProjectBuilder.kt:105-112 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/GoHelpers.kt:55— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/GoHelpers.kt:55-65 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/python/extractors/DecoratorExtractor.kt: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.
Edited copy of a member (8 corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterExtraction.kt:46— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterExtraction.kt:46-53 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterMetrics.kt:30-37 — 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) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Path.kt:49— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/Path.kt:49-56 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/processing/cycledetection/algorithms/StronglyConnectedComponentDetection.kt:94-101 — 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.
Duplicated block (7 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:44— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:44-50 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineCollector.kt:46-52 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineCollector.kt` 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 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 `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/bundler/BundlerConfigResolver.kt:37— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/bundler/BundlerConfigResolver.kt:37-43 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/tsconfig/TsConfigResolver.kt:31-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/SignatureTypeExtractor.kt:19— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/SignatureTypeExtractor.kt:19-25 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/UsedTypeExtractor.kt:129-135 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/ExpressionListExtractor.kt:13— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/ExpressionListExtractor.kt:13-19 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/go/extractors/ExpressionListMultiExtractor.kt:13-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:15— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:15-24 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/CalendarWeek.kt:12-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/MutableNode.kt:19— analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/MutableNode.kt:19-24 | analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/Node.kt:13-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/MutableNode.kt:17` calls `toMutableSet` and `analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/Node.kt:12` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/HotfixCommitRatio.kt:26— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/HotfixCommitRatio.kt:26-31 | analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/SemanticCommitRatio.kt:26-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterExtraction.kt:14— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterExtraction.kt:14-19 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/api/TreeSitterMetrics.kt:15-20 — 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.
Dead file (~9 LoC) sample-projects/angular/src/app/ui/pipes/legacy/roll.pipe.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~9 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Movement.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~9 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/encounterReport.mts— no import path from any entry point (51 application, 29 tooling, 937 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 (~9 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/CreatureNote.vue— no import path from any entry point (51 application, 29 tooling, 937 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 (~8 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/extensions/LairGate.jsx— no import path from any entry point (51 application, 29 tooling, 937 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 (~8 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/extensions/lairGate.mjs— no import path from any entry point (51 application, 29 tooling, 937 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 (~8 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Zentaurenhöhle.js— no import path from any entry point (51 application, 29 tooling, 937 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 (~8 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/NoSuchCreatureException.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×4
JavaScript dependencies are not locked sample-projects/angular/package.json:10— sample-projects/angular/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 sample-projects/javascript/package.json:9— sample-projects/javascript/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 sample-projects/typescript/package.json:8— sample-projects/typescript/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 sample-projects/vue/package.json:11— sample-projects/vue/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.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt:40— analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt:40-61 | analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt:119-150 — 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) analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/DomainLanguageParser.kt:114— analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/DomainLanguageParser.kt:114-135 | analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/UnifiedParser.kt:61-88 — 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) analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/StructureModifier.kt:200— analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/StructureModifier.kt:200-221 | analysis/analysers/tools/InspectionTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/inspection/InspectionTool.kt:63-84 — 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 (1 corresponding lines) · ×3
Edited copy of a member (1 corresponding lines) analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/UnionMergeResolver.kt:34— analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/UnionMergeResolver.kt:34-34 | analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeInserter.kt:45-45 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (1 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppIncludes.kt:60— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppIncludes.kt:60-60 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/CopyRules.kt:19-23 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (1 corresponding lines) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:26— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:26-36 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/CalendarWeek.kt:20-20 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:167— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/DependencyParser.kt:167-174 | analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/DomainLanguageParser.kt:157-164 — 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 (8 lines × 2) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/ForLoopVariableExtractor.kt:10— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/ForLoopVariableExtractor.kt:10-17 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/UsingVariableExtractor.kt:10-17 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/java/extractors/LambdaSingleParameterExtractor.kt:13— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/java/extractors/LambdaSingleParameterExtractor.kt:13-20 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/ArrowFunctionParameterExtractor.kt:12-19 — 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 (14 lines × 2 locations) visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:372— visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:372 · visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:388 — 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 locations) visualization/app/codeCharta/util/color/gradientCalculator.ts:51— visualization/app/codeCharta/util/color/gradientCalculator.ts:51 · visualization/app/codeCharta/util/color/gradientCalculator.ts:83 — 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 (14 lines × 2 locations) visualization/app/codeCharta/util/nodeDecorator.ts:245— visualization/app/codeCharta/util/nodeDecorator.ts:245 · visualization/app/codeCharta/util/nodeDecorator.ts:272 — 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 (12 lines × 2 locations) visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/backPrintColorChangeStrategy.ts:9— visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/backPrintColorChangeStrategy.ts:9 · visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/ColorChangeStrategies/frontPrintColorChangeStrategy.ts:5 — 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 (12 lines × 2 locations) visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:4— visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:4 · visualization/app/codeCharta/features/labelSettings/stores/labelSettings.write.store.ts:15 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (12 lines × 2 locations) visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:170— visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:170 · visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts: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.
Dead file (~12 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.js— no import path from any entry point (51 application, 29 tooling, 937 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 (~12 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/creatureEntityMapper.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~12 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/hoardLedger.cts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/ProjectConverter.kt:22— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/ProjectConverter.kt:22-42 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/ProjectConverter.kt:16-28 — 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) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/CppTypeHelper.kt:78— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/CppTypeHelper.kt:78-94 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/CSharpTypeHelper.kt:32-44 — 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· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/php/extractors/UsedTypeExtractor.kt:140— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/php/extractors/UsedTypeExtractor.kt:140-154 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/shared/domain/TreeTraversal.kt:34-47 — 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) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/ProjectConverter.kt:58— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/ProjectConverter.kt:58-76 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/ProjectConverter.kt:42-55 — 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.
Duplicated block (16 lines × 2) analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19— analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19-34 | analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/Dialog.kt:18-33 — 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 `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19` 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 (16 lines × 2) analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/StructureModifier.kt:206— analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/StructureModifier.kt:206-221 | analysis/analysers/tools/InspectionTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/inspection/InspectionTool.kt:69-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 `analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/StructureModifier.kt:206` 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 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) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:39— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/CalendarWeek.kt:39-49 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/CalendarWeek.kt:23-33 — 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) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineParser.kt:27— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineParser.kt:27-37 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineParser.kt:27-38 — 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 (9 lines × 2) analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/RawTextParser.kt:174— analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/RawTextParser.kt:174-182 | analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/UnifiedParser.kt:178-186 — 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 (9 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:8— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt:8-16 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineCollector.kt:8-16 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/parser/LogLineCollector.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/parser/LogLineCollector.kt` 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 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 (17 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeTypesFactory.kt:7— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeTypesFactory.kt:7-23 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/AttributeTypesFactory.kt:7-23 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeTypesFactory.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/AttributeTypesFactory.kt` 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. Note first that the copies are not typed on the same thing: `Metric` names `de.maibornwolff.codecharta.analysers.parsers.gitlog.input.metrics.Metric` in one and `de.maibornwolff.codecharta.analysers.parsers.svnlog.input.metrics.Metric` 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 (17 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/AverageCodeChurnPerCommit.kt:10— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/AverageCodeChurnPerCommit.kt:10-26 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/AverageCodeChurnPerCommit.kt:10-26 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/AverageCodeChurnPerCommit.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/AverageCodeChurnPerCommit.kt` 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. Note first that the copies are not typed on the same thing: `Modification` names `de.maibornwolff.codecharta.analysers.parsers.gitlog.input.Modification` in one and `de.maibornwolff.codecharta.analysers.parsers.svnlog.input.Modification` 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.
Low cohesion: EncounterEdgeCases (LCOM4 18) sample-projects/kotlin/src/main/kotlin/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.kt:21— EncounterEdgeCases's methods fall into 18 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 18 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: FrameworkDetector (LCOM4 5) analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/processing/FrameworkDetector.kt:13— FrameworkDetector'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.
DM11 · Constructible invalid state· Constructible in an invalid state · ×2
Constructible in an invalid state: CreatureEntity sample-projects/java/src/main/java/de/sots/cellarsandcentaurs/adapter/persistence/CreatureEntity.java:19— `CreatureEntity`'s public constructor takes `type` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CreatureEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Creature sample-projects/python/de/sots/cellarsandcentaurs/domain/model/creature.py:16— `Creature`'s public constructor takes `xp_value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Creature` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Duplicated block (26 lines × 2 locations) visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:271— visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:271 · visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts:131 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (26 lines × 2 locations) visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV6.ts:4— visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV6.ts:4 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV7.ts:4 — 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 (24 lines × 2 locations) visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV4.ts:10— visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV4.ts:10 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV5.ts:8 — 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 (24 lines × 2 locations) visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV8.ts:8— visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV8.ts:8 · visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV9.ts:8 — 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 (15 lines × 2 locations) visualization/app/codeCharta/features/dependencyMap/components/boxBadgesSegment/boxBadgesSegment.component.ts:19— visualization/app/codeCharta/features/dependencyMap/components/boxBadgesSegment/boxBadgesSegment.component.ts:19 · visualization/app/codeCharta/features/metricsBar/components/edgeSettingsPopover/edgeSettingsPopover.component.ts:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (15 lines × 2 locations) visualization/app/codeCharta/views/dependencyView/explorer/dependencyExplorerSelection.ts:10— visualization/app/codeCharta/views/dependencyView/explorer/dependencyExplorerSelection.ts:10 · visualization/app/codeCharta/views/metricsView/explorer/metricsExplorerSelection.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 3 locations) visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:75— visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:75 · visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts:45 · visualization/app/codeCharta/renderer/wordCloud/components/wordCloud/wordCloudChartHost.ts:64 — the 3 copies are spread across 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (12 lines × 3 locations) visualization/app/codeCharta/stores/dependencyLensSource/store/dependencyLensSource.readWindow.ts:6— visualization/app/codeCharta/stores/dependencyLensSource/store/dependencyLensSource.readWindow.ts:6 · visualization/app/codeCharta/stores/domainLensSource/store/domainLensSource.readWindow.ts:6 · visualization/app/codeCharta/stores/domainState/store/domainState.readWindow.ts:6 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function resolve (cyclomatic 12, cognitive 11) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:13— resolve 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.
Complex function resolve (cyclomatic 12, cognitive 11) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:14— resolve 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.
Dead file (~91 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~91 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.vue— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~17 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/Repository.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~17 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/SpeedLimit.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~16 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/encounter.mjs— no import path from any entry point (51 application, 29 tooling, 937 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 (~16 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/CreatureRepository.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~15 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Centaur.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.ts, sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~15 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Zentaurenhöhle.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/lairKeeper.mts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~13 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Stable.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~13 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/SpeedBadge.tsx— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCasesTsx.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~10 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Zentaurenhöhle.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/ZentaurenhöhlePanel.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~10 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/ui/CreatureRoster.vue— no import path from any entry point (51 application, 29 tooling, 937 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
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×2
NuGet dependencies are not locked sample-projects/csharp/src/De.Sots.CellarsAndCentaurs/De.Sots.CellarsAndCentaurs.csproj:11— sample-projects/csharp/src/De.Sots.CellarsAndCentaurs/De.Sots.CellarsAndCentaurs.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample-projects/csharp/tests/De.Sots.CellarsAndCentaurs.Tests/De.Sots.CellarsAndCentaurs.Tests.csproj:10— sample-projects/csharp/tests/De.Sots.CellarsAndCentaurs.Tests/De.Sots.CellarsAndCentaurs.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
D11 · Test Reliability· Test reliability not measured · ×1
Test reliability not measured — test suite did not build — Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the .NET half could not be re-run — unit: not included — its runs surfaced no test; JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in sample-projects/javascript/ (1 tests); vitest via `npm ci --ignore-scripts` in sample-projects/typescript/; vitest via `npm ci --ignore-scripts` in sample-projects/vue/; jest via `npm ci --ignore-scripts` in visualization/ (0 tests)): measured (0 flaky). No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
TodoComment sample-projects/csharp/src/De.Sots.CellarsAndCentaurs/Domain/Service/EncounterEdgeCases.cs:150— // TODO: /* not a block comment */ still one line comment — 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.
Dialog.collectAnalyserArgs (cognitive 16) analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/Dialog.kt:17— Dialog.collectAnalyserArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LabelCollisionService.buildCollisionGroups (cognitive 16) visualization/app/codeCharta/features/labelSettings/services/labelCollision.service.ts:117— LabelCollisionService.buildCollisionGroups has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: AttributeDescriptorsKt.getAttributeDescriptors analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeDescriptors.kt:5— MethodTooLong — getAttributeDescriptors runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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 (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:16— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:16-59 | analysis/analysers/tools/AnalyseTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/analyse/Dialog.kt:15-61 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpNameRules.kt:17— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/csharp/CSharpNameRules.kt:17-39 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/java/JavaNameRules.kt:16-35 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 25+ corresponding lines) · ×1
Edited copies of one member (4 members, 25+ corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/Dialog.kt:14— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/Dialog.kt:14-38 | analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/Dialog.kt:17-49 | analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/Dialog.kt:14-53 | analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/Dialog.kt:13-47 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 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 copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/Dialog.kt:35— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/Dialog.kt:35-64 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/Dialog.kt:13-51 — 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/AttributeDescriptors.kt:5— analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/AttributeDescriptors.kt:5-39 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/output/AttributeDescriptors.kt:11-42 — 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 (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:14— analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:14-40 | analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/Dialog.kt:14-39 | analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/Dialog.kt:14-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiInnerStrategy.kt:53— analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiInnerStrategy.kt:53-71 | analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiTwelveStrategy.kt:49-68 — 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 (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/extraction/ExtractionFacade.kt:28— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/extraction/ExtractionFacade.kt:28-38 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/integration/metrics/MetricsFacade.kt:39-48 — 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 (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlLookup.kt:39— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlLookup.kt:39-44 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlLookup.kt:47-51 — 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 copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVImporter.kt:59— analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/CSVImporter.kt:59-71 | analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/CodeMaatImporter.kt:66-91 | analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/SourceMonitorImporter.kt:56-75 — 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 copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/SuccessiveWeeksWithCommits.kt:18— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/SuccessiveWeeksWithCommits.kt:18-34 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/SuccessiveWeeksWithCommits.kt:18-34 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 15+ corresponding lines) · ×1
Edited copies of one member (6 members, 15+ corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/DeclarationExtractor.kt:16— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/DeclarationExtractor.kt:16-36 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/FieldDeclarationExtractor.kt:13-31 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/TypedefExtractor.kt:15-34 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/ForRangeLoopExtractor.kt:13-33 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/FieldDeclarationExtractor.kt:12-27 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/ParameterDeclarationExtractor.kt:11-25 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/declarations/InClassDeclarationFinder.kt:48— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/declarations/InClassDeclarationFinder.kt:48-61 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/csharp/extractors/DeclarationExtractor.kt:53-66 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/DeclarationExtractor.kt:57-68 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/kotlin/extractors/DeclarationExtractor.kt:99-112 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/rust/extractors/DeclarationExtractor.kt:98-109 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/FieldDeclarationExtractor.kt:18— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/FieldDeclarationExtractor.kt:18-34 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/DeclarationExtractor.kt:13-29 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/MethodSelectorExtractor.kt:13-27 — 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· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiInnerStrategy.kt:25— analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiInnerStrategy.kt:25-36 | analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiInnerStrategy.kt:40-51 | analysis/analysers/importers/TokeiImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/tokei/strategy/TokeiTwelveStrategy.kt:36-47 — 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 copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/federation/FederationConfigResolver.kt:75— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/federation/FederationConfigResolver.kt:75-90 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/common/tsconfig/TsConfigResolver.kt:39-58 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/java/QualifiedNames.kt:34— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/java/QualifiedNames.kt:34-36 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/model/MemberTypeScopes.kt:39-41 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (112 lines × 2) analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/AttributeDescriptors.kt:8— analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/AttributeDescriptors.kt:8-119 | analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/AttributeDescriptors.kt:8-119 — before extracting anything, compare `analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/AttributeDescriptors.kt` and `analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/AttributeDescriptors.kt` 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. Read the line range as the matched WINDOW rather than a finished unit: at `analysis/analysers/importers/CSVImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/csv/AttributeDescriptors.kt:8` 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 (81 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeDescriptors.kt:8— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeDescriptors.kt:8-88 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/AttributeDescriptors.kt:8-88 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeDescriptors.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/converter/AttributeDescriptors.kt` 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. 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 `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/converter/AttributeDescriptors.kt:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–24 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/Dialog.kt:36— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/Dialog.kt:36-58 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/Dialog.kt:21-44 — 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 `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/Dialog.kt:36` 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 `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 (22–24 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:29— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:29-52 | analysis/analysers/tools/AnalyseTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/analyse/Dialog.kt:32-53 — 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 `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:29` 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 `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, `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:28` calls `commitQuestion`, `promptConfirm` and `analysis/analysers/tools/AnalyseTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/analyse/Dialog.kt:32` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 2) analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:25— analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:25-40 | analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/Dialog.kt:24-38 — before extracting anything, compare `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt` and `analysis/analysers/importers/SourceMonitorImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sourcemonitor/Dialog.kt` 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. Read the line range as the matched WINDOW rather than a finished unit: at `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:25` 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 (13 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/GitLogParser.kt:65— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/GitLogParser.kt:65-77 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/SVNLogParser.kt:96-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/DeclarationIdentifierExtractor.kt:16— analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/DeclarationIdentifierExtractor.kt:16-27 | analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/ForRangeLoopExtractor.kt:14-25 — 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 `analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/DeclarationIdentifierExtractor.kt:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/MedianCoupledFiles.kt:10— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/MedianCoupledFiles.kt:10-19 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/MedianCoupledFiles.kt:10-19 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/MedianCoupledFiles.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/MedianCoupledFiles.kt` 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. 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 (6 lines × 8) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppNameRules.kt:17— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppNameRules.kt:17-22 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/delphi/DelphiNameRules.kt:17-22 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/php/PhpNameRules.kt:17-22 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/python/PythonNameRules.kt:17-22 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/rust/RustNameRules.kt:16-21 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlNameRules.kt:17-22 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/typescript/TypescriptNameRules.kt:18-23 | analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/vba/VbaNameRules.kt:17-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times.
Duplicated block (29 lines × 2) analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/progress/ProgressTrackerReporter.kt:12— analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/progress/ProgressTrackerReporter.kt:12-40 | analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/progress/ProgressTrackerReporter.kt:12-40 — before extracting anything, compare `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/progress/ProgressTrackerReporter.kt` and `analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/progress/ProgressTrackerReporter.kt` 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.
Duplicated block (14 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/AgeInWeeks.kt:12— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/AgeInWeeks.kt:12-25 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/AgeInWeeks.kt:10-23 — 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: `Commit` names `de.maibornwolff.codecharta.analysers.parsers.gitlog.input.Commit` in one and `de.maibornwolff.codecharta.analysers.parsers.svnlog.input.Commit` 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 (15 lines × 2) analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/RangeOfWeeksWithCommits.kt:10— analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/RangeOfWeeksWithCommits.kt:10-24 | analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/RangeOfWeeksWithCommits.kt:10-24 — before extracting anything, compare `analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/input/metrics/RangeOfWeeksWithCommits.kt` and `analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/input/metrics/RangeOfWeeksWithCommits.kt` 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. Note first that the copies are not typed on the same thing: `Commit` names `de.maibornwolff.codecharta.analysers.parsers.gitlog.input.Commit` in one and `de.maibornwolff.codecharta.analysers.parsers.svnlog.input.Commit` 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 (5 lines × 2) analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/CoberturaStrategy.kt:18— analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/CoberturaStrategy.kt:18-22 | analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/strategies/JacocoStrategy.kt:18-22 — 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 (15 lines × 3) analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19— analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19-34 | analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/Dialog.kt:28-42 | analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/Dialog.kt:18-33 — 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 `analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt:19` 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.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the node:test suite in sample-projects/javascript/ ran and not one test passed (throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);), so the coverage would describe the failed run, not the code. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: 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.
Anemic entity: Creature sample-projects/ruby/lib/de/sots/cellars_and_centaurs/domain/model/creature.rb:16— `Creature` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Duplication concentrated across 22 sibling directories (33 clone groups) visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9— 33 duplicated blocks under visualization/app/codeCharta/features/ have copies in at least two of the sibling directories changelog, clusterExplorer, codeMap, dependencyMap, domainBar, domainToolbox (+16 more sibling(s) not listed) — 20 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 33 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (15 clone groups) visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.ts:64— 15 duplicated blocks under visualization/app/codeCharta/ have copies in at least two of the sibling directories features, load, renderer, stores, views — 4 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (14 clone groups) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13— 14 of the duplicated blocks reported below have copies in at least two of the sibling directories javascript, typescript, vue under sample-projects/. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (6 clone groups) visualization/app/codeCharta/stores/domainState/store/domainState.reducer.ts:18— 6 duplicated blocks under visualization/app/codeCharta/stores/ have copies in at least two of the sibling directories dependencyLensSource, domainLensSource, domainState, fileStore, mapState, metricsLensSource (+2 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (145 matched lines × 2 locations) · ×1
Duplicated block with local edits (145 matched lines × 2 locations) visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts:21— visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts:21 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:19 — the two spans are one implementation copied and then locally edited — 1175 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 (69 lines × 2 locations) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:11— sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:11 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.vue:12 — 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 (45 lines × 2 locations) visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/horizontalStrip.ts:7— visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/horizontalStrip.ts:7 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/strip/verticalStrip.ts:7 — 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 (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13— sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:13 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:14 — the two spans are one implementation copied and then locally edited — 200 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 (37 matched lines × 2 locations) · ×1
Duplicated block with local edits (37 matched lines × 2 locations) visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:97— visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:97 · visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts:159 — the two spans are one implementation copied and then locally edited — 278 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 with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:25— sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:25 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:25 — the two spans are one implementation copied and then locally edited — 137 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 (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Creature.js:29— sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Creature.js:29 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Creature.ts:23 — the two spans are one implementation copied and then locally edited — 106 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 (25 matched lines × 2 locations) · ×1
Duplicated block with local edits (25 matched lines × 2 locations) sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:13— sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:13 · sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:12 — the two spans are one implementation copied and then locally edited — 173 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) visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:98— visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:98 · visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/ccJson2/ccJson2ToCCFile.ts:217 — the two spans are one implementation copied and then locally edited — 134 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (19 lines × 2 locations) visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/qrCodeSettings/qrCodeSettings.component.ts:3— visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/qrCodeSettings/qrCodeSettings.component.ts:3 · visualization/app/codeCharta/features/3dPrint/components/export3DMapDialog/secondRowTextInput/secondRowTextInput.component.ts:3 — 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 (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6— sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/ArmorClass.ts:6 — the two spans are one implementation copied and then locally edited — 73 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 (18 lines × 2 locations) visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:403— visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:403 · visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:422 — 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 with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/backMWLogoMesh.ts:7— visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/backMWLogoMesh.ts:7 · visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/BackMeshModels/codeChartaLogoMesh.ts:9 — the two spans are one implementation copied and then locally edited — 83 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 (17 lines × 2 locations) visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:22— visualization/app/codeCharta/renderer/dependencyGraph/testing/dependencyGraph.stub.ts:22 · visualization/app/codeCharta/renderer/radialMap/testing/radialChart.stub.ts:23 — 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 (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9— visualization/app/codeCharta/features/dependencyMap/stores/dependencyMap.write.store.ts:9 · visualization/app/codeCharta/features/radialMap/stores/radialMap.write.store.ts:6 — the two spans are one implementation copied and then locally edited — 96 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 (16 lines × 2 locations) visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:50— visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:50 · visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts:86 — 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 with local edits (15 matched lines × 2 locations) · ×1
Duplicated block with local edits (15 matched lines × 2 locations) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1— sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1 · sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:1 — the two spans are one implementation copied and then locally edited — 90 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 (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Dice.js:5— sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/model/Dice.js:5 · sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/model/Dice.ts:5 — the two spans are one implementation copied and then locally edited — 67 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 (13 lines × 2 locations) visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:8— visualization/app/codeCharta/features/globalSettings/stores/resetSettings.store.ts:8 · visualization/app/codeCharta/features/shared/stores/resetSettingsButton.store.ts:8 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (13 lines × 4 locations) visualization/app/codeCharta/stores/fileStore/store/fileStore.readWindow.ts:12— visualization/app/codeCharta/stores/fileStore/store/fileStore.readWindow.ts:12 · visualization/app/codeCharta/stores/mapState/store/mapState.readWindow.ts:38 · visualization/app/codeCharta/stores/preferences/store/preferences.readWindow.ts:18 · visualization/app/codeCharta/stores/sharedView/store/sharedView.readWindow.ts:15 — the 4 copies are spread across 4 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 (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js:36— sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/CreatureFacade.js:36 · sample-projects/vue/src/de/sots/cellarsandcentaurs/application/CreatureFacade.ts:27 — the two spans are one implementation copied and then locally edited — 107 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 (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:10— sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:10 · sample-projects/vue/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts:9 — the two spans are one implementation copied and then locally edited — 97 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.
Complex function provideExplorerPortsMock (cyclomatic 13, cognitive 12) visualization/app/codeCharta/features/sidebarExplorer/explorerPorts.mocks.ts:132— provideExplorerPortsMock has cyclomatic complexity 13 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getPrintColor (cyclomatic 12, cognitive 15) visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/MeshModels/mapMesh.ts:62— getPrintColor has cyclomatic complexity 12 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.
Complex function decorateNode (cyclomatic 12, cognitive 14) visualization/app/codeCharta/util/nodeDecorator.ts:88— decorateNode has cyclomatic complexity 12 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.
Complex function drawConnectors (cyclomatic 12, cognitive 13) visualization/app/codeCharta/features/labelSettings/services/connectorDrawing.service.ts:27— drawConnectors has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildPairingEdges (cyclomatic 11, cognitive 14) visualization/app/codeCharta/features/codeMap/arrow/codeMap.arrow.service.ts:169— buildPairingEdges 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.
Complex function updateHighlight (cyclomatic 11, cognitive 13) visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.ts:193— updateHighlight has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function memberSlices (cyclomatic 11, cognitive 11) visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/jsonBytes.ts:57— memberSlices 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.
Complex function getColorByWeightedGradient (cyclomatic 11, cognitive 10) visualization/app/codeCharta/util/color/gradientCalculator.ts:92— getColorByWeightedGradient has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveNodeMetricSelection (cyclomatic 11, cognitive 9) visualization/app/codeCharta/load/effects/reconcileAfterLoad/resolveMetricSelection.ts:59— resolveNodeMetricSelection has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 2429 lines of code REDACTED:1— REDACTED has 2429 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· visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts · ×1
visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts: 482 lines of code visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts:1— visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts has 482 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· visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts · ×1
visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts: 479 lines of code visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts:1— visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/metricColorRangeDiagram.component.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage· This test file cannot be loaded · ×1
This test file cannot be loaded sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts:2— sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts:2 imports './missing', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job package.json:23— The root package declares the lint script `format` (`biome check --write --no-errors-on-unmatched`), 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 format` in `.` (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 sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts:2— This repository declares test tooling, and the ✓ above records that declaration — but sample-projects/regression/typescript/spec-unresolved-specifier/src/app.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~336 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~141 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.vue— no import path from any entry point (51 application, 29 tooling, 937 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 (~92 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js— no import path from any entry point (51 application, 29 tooling, 937 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 (~90 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCasesTsx.vue, sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/encounterReport.mts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~28 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/adapter/persistence/PersistedCreatures.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~24 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCasesTsx.vue— no import path from any entry point (51 application, 29 tooling, 937 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 (~22 LoC) sample-projects/javascript/src/de/sots/cellarsandcentaurs/application/ui/CreatureCard.jsx— no import path from any entry point (51 application, 29 tooling, 937 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/Centaur.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~14 LoC) sample-projects/typescript/src/de/sots/cellarsandcentaurs/application/CreatureLoader.ts— no import path from any entry point (51 application, 29 tooling, 937 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 (~11 LoC) sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/model/stableSize.cts— no import path from any entry point (51 application, 29 tooling, 937 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
Unused dependency 'badge-maker' package.json:32— Declared in the root 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 'makeshift' analysis/node-wrapper/package.json:27— Declared in analysis/node-wrapper/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 'shelljs' analysis/node-wrapper/package.json:28— Declared in analysis/node-wrapper/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 '@angular/compiler-cli' sample-projects/angular/package.json:21— Declared in sample-projects/angular/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.
SC1 · Supply-chain hygiene· Go module dependencies are not locked · ×1
Go module dependencies are not locked — There is a REDACTED but no go.sum — module versions aren't pinned to a verified hash, so builds aren't reproducible (SSDF PW.4.4). Run `go mod tidy` and commit go.sum; keep `GOFLAGS=-mod=readonly` in CI so a build fails rather than silently resolving a new version. Advisory — never scored.
Orphaned file visualization/app/codeCharta/resources/fixed-folders/fixed-folders-example.ts: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 analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt: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 analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/AttributeDescriptors.kt: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 visualization/app/codeCharta/features/3dPrint/3DExports/serialize3mf.service.ts: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 visualization/app/codeCharta/features/viewCube/viewCube.component.ts: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 visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts: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 visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts: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 visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts: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 visualization/app/codeCharta/stores/fileStore/loaders/gameObjects/gameObjectsImporter.ts: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 analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarImporter.kt: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 analysis/analysers/parsers/SVNLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/svnlog/SVNLogParser.kt: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 analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/Dialog.kt: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 visualization/app/codeCharta/util/fileExtension/fileExtensionCalculator.ts: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 visualization/app/codeCharta/features/viewCube/viewCube.mouseEvents.service.ts: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 analysis/analysers/filters/EdgeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/edgefilter/EdgeProjectBuilder.kt: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 analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/CoverageImporter.kt: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 visualization/app/codeCharta/util/color/gradientCalculator.ts: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 analysis/analysers/filters/StructureModifier/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/structuremodifier/Dialog.kt: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 visualization/app/codeCharta/stores/fileStore/loaders/ccJson/util/fileParser.ts: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 analysis/analysers/exporters/CSVExporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/exporters/csv/CSVExporter.kt: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 visualization/app/codeCharta/features/3dPrint/3DExports/3DPreview/preview3DPrintMesh.ts: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 analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/SonarComponentProjectBuilder.kt: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 visualization/app/codeCharta/util/color/colorConverter.ts: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 visualization/app/codeCharta/stores/fileStore/store/files.reducer.ts: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 visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/squarifiedTreeMap.ts: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.
Duplicated predicate visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV30.ts:11— `!dependencyGraph || typeof dependencyGraph !== "object"` appears character-identically in 3 files — visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV30.ts, visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV31.ts, visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/seedDefaults.ts. 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 visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.ts:111— `!event || !("button" in event) || event.button === PRIMARY_BUTTON` appears character-identically in 2 files — visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/boxDragGesture.ts, visualization/app/codeCharta/renderer/wordCloud/components/wordCloud/wordCloudPanZoom.ts. 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 visualization/app/codeCharta/features/codeMap/arrow/codeMap.arrow.service.ts:171— `!showIncomingEdges && !showOutgoingEdges` appears character-identically in 3 files — visualization/app/codeCharta/features/codeMap/arrow/codeMap.arrow.service.ts, visualization/app/codeCharta/renderer/renderModel/amountOfBuildingsWithSelectedEdgeMetric/amountOfBuildingsWithSelectedEdgeMetric.selector.ts, visualization/app/codeCharta/renderer/renderModel/edgeMetricData/sortedNodeEdgeMetricsMap.selector.ts. 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 visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/colorSettingsHeader.component.ts:30— `!this.isDeltaState() && this.colorMetric() !== "unary"` appears character-identically in 2 files — visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/colorSettingsHeader.component.ts, visualization/app/codeCharta/features/metricsBar/components/colorSettingsPopover/colorSettingsPopover.component.ts. 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 visualization/app/codeCharta/features/dependencyMap/selectors/dependencyMap.selectors.ts:17— `(focusedNodePath && pathToNode.get(focusedNodePath)) || unifiedMapNode` appears character-identically in 4 files — visualization/app/codeCharta/features/dependencyMap/selectors/dependencyMap.selectors.ts, visualization/app/codeCharta/features/mapExplorer/selectors/mapExplorerTree.selector.ts, visualization/app/codeCharta/features/metricsBar/selectors/topLevelNode.selector.ts, visualization/app/codeCharta/features/radialMap/selectors/radialMap.selectors.ts. 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 visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV10.ts:10— `appSettings && typeof appSettings === "object"` appears character-identically in 2 files — visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV10.ts, visualization/app/codeCharta/stores/rootStore/indexedDB/migrations/migrateToV11.ts. 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 visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:81— `this.chart && this.attachedContainer === container` appears character-identically in 3 files — visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts, visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts, visualization/app/codeCharta/renderer/wordCloud/components/wordCloud/wordCloudChartHost.ts. 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 visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts:284— `this.pathUnderPointer !== null && this.pointerLeaveTimeout === undefined` appears character-identically in 2 files — visualization/app/codeCharta/renderer/dependencyGraph/components/dependencyGraph/dependencyGraphHost.ts, visualization/app/codeCharta/renderer/radialMap/components/radialChart/radialChartHost.ts. 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 visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/streetViewHelper.ts:10— `totalSize === 0 && node.children && node.children.length > 0` appears character-identically in 2 files — visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/streetViewHelper.ts, visualization/app/codeCharta/renderer/threeViewer/algorithm/treeMapLayout/treeMapHelper.ts. 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 visualization/app/codeCharta/features/localSource/services/localSource.service.ts:192— `visibleFileStates.length > 1 && isPartialState(visibleFileStates)` appears character-identically in 2 files — visualization/app/codeCharta/features/localSource/services/localSource.service.ts, visualization/app/codeCharta/stores/fileStore/store/areMultipleMapsVisible.selector.ts. 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 analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/RawTextParser.kt:175— `!bypassGitignore && gitignoreExcludedCount > 0` appears character-identically in 2 files — analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/RawTextParser.kt, analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/UnifiedParser.kt. 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 analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/UnionMergeResolver.kt:34— `(first == NodeType.File && second == NodeType.Folder) || (first == NodeType.Folder && second == NodeType.File)` appears character-identically in 2 files — analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/UnionMergeResolver.kt, analysis/model/src/main/kotlin/de/maibornwolff/codecharta/model/NodeInserter.kt. 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 analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/Dialog.kt:71— `(outputFileName.isEmpty()) || session.promptConfirm( message = "Do you want to compress the output file?", onInputReady = testCallback() )` appears character-identically in 9 files — analysis/analysers/filters/MergeFilter/src/main/kotlin/de/maibornwolff/codecharta/analysers/filters/mergefilter/Dialog.kt, analysis/analysers/importers/CodeMaatImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/codemaat/Dialog.kt, analysis/analysers/importers/CoverageImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/coverage/Dialog.kt, analysis/analysers/importers/DependaChartaImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/dependacharta/Dialog.kt. 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 analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt:35— `authorOwnership && session.promptConfirm( message = "Write REAL author names into the map instead of invented ones? Anyone who gets the map …` appears character-identically in 2 files — analysis/analysers/parsers/GitLogParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/gitlog/RepoScanDialog.kt, analysis/analysers/tools/AnalyseTool/src/main/kotlin/de/maibornwolff/codecharta/analysers/tools/analyse/Dialog.kt. 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 analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/accesslayout/extractors/LayoutReader.kt:107— `index < lines.size && lines[index].startsWith(QUOTE)` appears character-identically in 2 files — analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/accesslayout/extractors/LayoutReader.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/accessmacro/extractors/MacroRows.kt. 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 analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/CDeclaratorParser.kt:55— `it.type == IDENTIFIER || it.type == TYPE_IDENTIFIER` appears character-identically in 4 files — analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/c/extractors/CDeclaratorParser.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/cpp/extractors/usedtypes/ClassScopeExtractor.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/UsedTypeExtractor.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/objectivec/extractors/ForwardClassesExtractor.kt. 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 analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/AngularDecoratorExtractor.kt:46— `it.type == STRING || it.type == TEMPLATE_STRING` appears character-identically in 2 files — analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/AngularDecoratorExtractor.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/javascript/extractors/ImportExtractor.kt. 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 analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/golang/GoModules.kt:86— `name.startsWith(HIDDEN_PREFIX) || name == NODE_MODULES` appears character-identically in 4 files — analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/golang/GoModules.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/typescript/GlobalDeclarations.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/typescript/WorkspacePackages.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/vue/ProjectFiles.kt. 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 analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppIncludes.kt:82— `name.startsWith(HIDDEN_PREFIX) || name in SKIPPED_FOLDERS` appears character-identically in 4 files — analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/cpp/CppIncludes.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/python/PythonModules.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/rust/RustCrates.kt, analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/rust/RustProject.kt. 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 analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/NameCollector.kt:77— `other != null && node.startByte == other.startByte && node.type == other.type` appears character-identically in 2 files — analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/delphi/extractors/NameCollector.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/vba/extractors/VbaNameCollector.kt. 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 analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/python/extractors/LocalScopes.kt:80— `other.startByte >= startByte && other.endByte <= endByte` appears character-identically in 2 files — analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/python/extractors/LocalScopes.kt, analysis/treeSitterExcavationSite/src/main/kotlin/de/maibornwolff/treesitter/excavationsite/languages/python/extractors/PythonUses.kt. 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 analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/Dialog.kt:18— `outputFileName.isEmpty() || compressedQuestion(session)` appears character-identically in 4 files — analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/Dialog.kt, analysis/analysers/parsers/DomainLanguageParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/domainlanguage/Dialog.kt, analysis/analysers/parsers/RawTextParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/rawtext/Dialog.kt, analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/Dialog.kt. 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.
D20 · ADR Quality· ADR has no Context section · ×10
ADR has no Context section dev_docs/adr/2017-01-02-ADR_1_decide_tech_stack.md:17— dev_docs/adr/2017-01-02-ADR_1_decide_tech_stack.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2017-01-02-ADR_2_pick_analysis_language.md:14— dev_docs/adr/2017-01-02-ADR_2_pick_analysis_language.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2017-01-02-ADR_3_pick_visualization_language.md:14— dev_docs/adr/2017-01-02-ADR_3_pick_visualization_language.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2017-01-02-ADR_4_decide_analysis_architecture.md:13— dev_docs/adr/2017-01-02-ADR_4_decide_analysis_architecture.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2017-01-02-ADR_6_filters_share_nothing.md:17— dev_docs/adr/2017-01-02-ADR_6_filters_share_nothing.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2017-09-03-ADR_7_pick_visualization_language.md:16— dev_docs/adr/2017-09-03-ADR_7_pick_visualization_language.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2022-09-16-ADR_8_angular_migration.md:35— dev_docs/adr/2022-09-16-ADR_8_angular_migration.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2023-08-03-ADR_9_ccsh_usage_via_npm.md:23— dev_docs/adr/2023-08-03-ADR_9_ccsh_usage_via_npm.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2025-21-03-ADR_11_change_module_structure.md:27— dev_docs/adr/2025-21-03-ADR_11_change_module_structure.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Context section dev_docs/adr/2026-06-25-ADR_12_separate_file_structure_from_analysis_lenses.md:24— dev_docs/adr/2026-06-25-ADR_12_separate_file_structure_from_analysis_lenses.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
Silent fallback default in catch sample-projects/csharp/src/De.Sots.CellarsAndCentaurs/Domain/Service/EncounterEdgeCases.cs:129— `ExceptionFilter` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch sample-projects/php/src/Domain/Service/EncounterEdgeCases.php:216— `unionCatch` swallows every exception into `return 0` — 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 docblock, and the row stops firing.
Silent fallback default in catch sample-projects/php/src/Domain/Service/EncounterEdgeCases.php:227— `multipleCatch` swallows every exception into `return 0` — 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 docblock, and the row stops firing.
Silent fallback default in catch sample-projects/php/src/Domain/Service/EncounterResolver.php:81— `safeRoll` swallows every exception into `return 1` — 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 docblock, and the row stops firing.
Silent fallback default in catch sample-projects/swift/Sources/CellarsAndCentaurs/Domain/Service/EncounterResolver.swift:68— `safeRoll` turns every thrown error into `1` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch sample-projects/swift/Sources/CellarsAndCentaurs/Domain/Service/EncounterEdgeCases.swift:137— `typedCatches` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch sample-projects/swift/Sources/CellarsAndCentaurs/Domain/Service/EncounterEdgeCases.swift:148— `catchWhere` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch sample-projects/javascript/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.js:71— `safeRoll` 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.
Silent fallback default in catch sample-projects/typescript/src/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.ts:258— `optionalCatchBinding` 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.
Silent fallback default in catch sample-projects/vue/src/de/sots/cellarsandcentaurs/domain/service/EncounterResolver.ts:69— `safeRoll` 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.
Silent fallback default on parse failure sample-projects/kotlin/src/main/kotlin/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.kt:231— `tryExpression` answers `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 KDoc, and the row stops firing.
Silent fallback default on parse failure sample-projects/kotlin/src/main/kotlin/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.kt:240— `multipleCatch` answers `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 KDoc, and the row stops firing.
Silent fallback default on parse failure sample-projects/java/src/main/java/de/sots/cellarsandcentaurs/domain/service/EncounterEdgeCases.java:136— `multiCatch` returns `0` when `NumberFormatException | NullPointerException` 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 sample-projects/python/de/sots/cellarsandcentaurs/domain/service/encounter_resolver.py:61— `safe_roll` returns `1` when `ValueError` is raised, with no log or raise — 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 on the handler or in the docstring, and the row stops firing.
Silent fallback default in rescue sample-projects/ruby/lib/de/sots/cellars_and_centaurs/domain/service/encounter_edge_cases.rb:159— `rescue_modifier` rescues every error into `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 rescue or above the method, and the row stops firing.
Silent fallback default in rescue sample-projects/ruby/lib/de/sots/cellars_and_centaurs/domain/service/encounter_edge_cases.rb:164— `method_level_rescue` rescues every error into `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 rescue or above the method, and the row stops firing.
Silent fallback default in rescue sample-projects/ruby/lib/de/sots/cellars_and_centaurs/domain/service/encounter_resolver.rb:71— `safe_roll` rescues every error into `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 rescue or above the method, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 251 significant file(s) lose their only recent owner: visualization/app/codeCharta/renderer/threeViewer/rendering/codeMapMesh.ts, visualization/app/codeCharta/renderer/threeViewer/threeSceneService.ts, visualization/app/codeCharta/features/dependencyMap/inspector/inspectorModel.ts, visualization/app/codeCharta/features/codeMap/codeMap.mouseEvent.service.ts, analysis/treeSitterExcavationSite/src/main/java/de/maibornwolff/treesitter/excavationsite/shared/infrastructure/ffm/TreeSitterApi.java, visualization/app/codeCharta/load/loadFiles.useCase.ts, visualization/app/codeCharta/features/scenarios/model/scenarioSettings.registry.ts, analysis/analysers/importers/SonarImporter/src/main/kotlin/de/maibornwolff/codecharta/analysers/importers/sonar/AttributeDescriptors.kt (+243 more). Pair on, review, or document these before any departure.
ADR declares no status dev_docs/adr/2017-01-01-ADR_0_write_adrs.md:19— `dev_docs/adr/2017-01-01-ADR_0_write_adrs.md` declares no status, while 12 of the 12 other records in `dev_docs/adr` do, so a reader cannot tell whether this decision is in force. Add a `Status:` line.
D20 · ADR Quality· ADR has no Context and Decision section · ×1
ADR has no Context and Decision section dev_docs/adr/2023-10-09-ADR_10_change_visualization_standalone.md:30— dev_docs/adr/2023-10-09-ADR_10_change_visualization_standalone.md has no Context and Decision section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D20 · ADR Quality· ADR links a record that does not exist · ×1
ADR links a record that does not exist dev_docs/adr/2017-01-02-ADR_3_pick_visualization_language.md:16— dev_docs/adr/2017-01-02-ADR_3_pick_visualization_language.md:16 names `ADR 7` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
redundant comment visualization/electron/main.js:11— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `const mainWindow = new BrowserWindow({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 82 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: visualization/app/codeCharta/resources/fixed-folders/fixed-folders-example.ts, analysis/dialogProvider/src/main/kotlin/de/maibornwolff/codecharta/dialogProvider/DialogProvider.kt, analysis/analysers/parsers/UnifiedParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/unified/AttributeDescriptors.kt, visualization/app/codeCharta/features/3dPrint/3DExports/serialize3mf.service.ts, visualization/app/codeCharta/features/viewCube/viewCube.component.ts, visualization/app/codeCharta/features/viewCube/viewCube.meshGenerator.ts, visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/verticalStreet.ts, visualization/app/codeCharta/renderer/threeViewer/algorithm/streetLayout/horizontalStreet.ts (and 74 more) (83 orphaned of 691 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; 691 of the 3633 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.
Mutable entity: Creature sample-projects/go/domain/model/creature.go:34— `Creature` exposes exported guard-free setter(s) (SetType, SetArmorClass, SetSpeeds, SetHitPoints) that rewrite business state without enforcing invariants.
DM9 · Scattered domain decisions· Rule about [x, y] decided in 4 places · ×1
Rule about [x, y] decided in 4 places — visualization.app.codeCharta.model.rectangle.Rectangle's [x, y] are judged in visualization.app.codeCharta.renderer.dependencyGraph.util.axisWindow, visualization.app.codeCharta.renderer.dependencyGraph.util.geometry, visualization.app.codeCharta.renderer.dependencyGraph.util.overlaps, visualization.app.codeCharta.renderer.dependencyGraph.util.paintOrder — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Rule about [declarationCount, kind] decided in 2 places · ×1
Rule about [declarationCount, kind] decided in 2 places — visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel.LayoutBox's [declarationCount, kind] are judged in visualization.app.codeCharta.renderer.dependencyGraph.util.dependencyGraphBoxes, visualization.app.codeCharta.renderer.dependencyGraph.util.layoutModel — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
README/code drift visualization/README.md:174— visualization/README.md links to `../DEV_START_GUIDE.md`, but `DEV_START_GUIDE.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.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety REDACTED:40— Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.6 `!` suppressions per 1k syntax nodes — 2 suppression(s) across the 3464 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. 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.
Silent fallback default on error sample-projects/go/domain/service/encounter_edge_cases.go:149— `ifWithInit` turns a non-nil `err` into `return 20` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Silent fallback default on Err sample-projects/rust/src/domain/service/encounter_resolver.rs:75— `safe_roll` turns every `Err` into `1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
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.
nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 44 file(s) — `analysis/analysers/AnalyserInterface/src/main/kotlin/de/maibornwolff/codecharta/analysers/analyserinterface/AnalyserDialogInterface.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/LanguageAnalyzer.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/delphi/UnitScope.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/sql/SqlAnalyzer.kt`, `analysis/analysers/parsers/DependencyParser/src/main/kotlin/de/maibornwolff/codecharta/analysers/parsers/dependency/analysis/analyzers/vba/VbaModuleFile.kt`, … (+39 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e70b-0bba-74fb-89ba-f21c0c782f91 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 149 · Warnings: 337 · Recommendations: 152 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 01:07 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.