Public report of microsoft/Analysis-Services, published 16 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, 16 November 2026, 12:33 UTC · Survey ID cd_83885829c3124548b6bd59adfd37fd78
microsoft/Analysis-Services
Measured 16 November 2026, 12:33 UTC, at code version d3ccb50
Code coverage is not measured: .NET and JavaScript/TypeScript suite (CouldNotMeasureRepoBuildError, CouldNotMeasureNoRunner).
Test reliability is not measured: No test run produced results.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreProvisional
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 35,083 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Production Readiness, 24.4
Findings by how serious they are
104 critical520 serious166 minor
5 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
16 November 2026, 12:33 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 code didn't build, so the score is provisional
We couldn't build the code: the build stopped with 118 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0234: The type or namespace name 'AnalysisServices' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'NamedMetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'MetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TranslatedProperty' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CultureCollection' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Partition' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Server' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Database' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Table' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Management' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0246: The type or namespace name 'TraceServer' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TraceTable' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'XEvent' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0234: The type or namespace name 'IdentityModel' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'PowerArgs' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonPropertyAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonProperty' could not be found (are you missing a using directive or an assembly reference?)
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 ▸
54of 54 dimensions measured by tools.
778of 790 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
54dimensions across 6 lenses, read from 35,083 lines of product code in 16 projects.
microsoft/Analysis-Services has a provisional result, because the code didn't build. Its score is held back because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 38.6 out of 100, and the ratings may change once the code builds. 65 of its 104 critical findings are security problems.
Production Readiness, at 24.4, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 12.3 points. Removing the unread values comes next, worth about 4.0 points. Raising Production Readiness to 70 would lift the score to about 50.6.
Fifty-five known security holes in the packages the code depends on can be used by attackers. Five passwords or keys in the code's history and two in the code are open to anyone who can read the repository, and thirty-four errors are caught and ignored, so failures can go unnoticed. Updating the vulnerable packages, replacing each exposed password or key and handling or logging the ignored errors would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code. The two data fields that are written but never read need removing.
The product code is 35,083 lines, about €180,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 Production Readiness rose from 24.4 to 70, the lowest score rated Strong, the score would rise from 38.6 to about 50.6.
Code composition: what the lines of code are
Business logic 54%Supporting code 28%Tests 0%Generated by tools 18%
Rebuild cost: about €180,000 · Estimate
Cost to rebuild
€58,000 to €300,000, for 969 to 3,191 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 35,083 lines of product code
Comment lines
The estimate prices 28,419 lines. Comment lines count towards the size of 35,083 lines but aren't priced as work.
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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Raises the score by about 12.3 points · Low effort · REDACTED Scanning
2
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ChromeDebugger.cs, CalcDependency.cs.
Raises the score by about 4.0 points · Low effort · Explicit Debt
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 6.1 points · Medium effort · CI/CD gates
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0234: The type or namespace name 'AnalysisServices' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'NamedMetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'MetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TranslatedProperty' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CultureCollection' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Partition' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Server' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Database' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Table' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Management' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0246: The type or namespace name 'TraceServer' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TraceTable' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'XEvent' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0234: The type or namespace name 'IdentityModel' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'PowerArgs' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonPropertyAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonProperty' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 24.4 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 15% on every change. The history of the code shows how much it changes: about 688 lines over the last 90 days, which is about 2,790 lines a year. At that pace, the extra work comes to an estimated 0.5 to 2.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
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.
42 modules, with 32 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 2 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.
ASJobGraphEvents uses ASJobGraphEvents.rebuild, so a change to ASJobGraphEvents.rebuild can break ASJobGraphEvents, while a change to ASJobGraphEvents can't break ASJobGraphEvents.rebuild.
Position
Below the diagonal: ASJobGraphEvents uses a module listed above it, which is the healthy direction.
ASJobGraphEvents.gantt uses ASJobGraphEvents.gantt.structures, so a change to ASJobGraphEvents.gantt.structures can break ASJobGraphEvents.gantt, while a change to ASJobGraphEvents.gantt can't break ASJobGraphEvents.gantt.structures.
Position
Below the diagonal: ASJobGraphEvents.gantt uses a module listed above it, which is the healthy direction.
23→29 AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service uses AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_servicepart of a loop✕
Connections
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service uses AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can break AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service can't break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-token-provider.
AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils uses AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-token-provider, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-token-provider can break AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils can't break AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-token-provider.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl_monaco_contributions uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-parser-manager.
AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl_monaco_contributions uses AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-parser-manager, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-parser-manager can break AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl_monaco_contributions, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl_monaco_contributions can't break AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl-parser-manager.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.tmdl-utils.tmdl_monaco_contributions uses a module listed above it, which is the healthy direction.
AsPartitionProcessing.SampleClient uses AsPartitionProcessing, so a change to AsPartitionProcessing can break AsPartitionProcessing.SampleClient, while a change to AsPartitionProcessing.SampleClient can't break AsPartitionProcessing.
Position
Below the diagonal: AsPartitionProcessing.SampleClient uses a module listed above it, which is the healthy direction.
27→31 BismNormalizer.TabularCompare uses BismNormalizer.TabularCompare.Corepart of a loop✕
Connections
3 pairs of types, where a type in BismNormalizer.TabularCompare uses a type in BismNormalizer.TabularCompare.Core.
BismNormalizer.TabularCompare uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break BismNormalizer.TabularCompare, while a change to BismNormalizer.TabularCompare can't break BismNormalizer.TabularCompare.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service can break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can't break AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service.
AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service can break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can't break AlmToolkit.AlmToolkit.html-resources.src.app.service.window-reference_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service uses a module listed above it, which is the healthy direction.
BismNormalizer uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer, while a change to BismNormalizer can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.Core uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer.TabularCompare.Core, while a change to BismNormalizer.TabularCompare.Core can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer.TabularCompare.Core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service can break AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component can't break AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.shared.model.comparison-node.
AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses AlmToolkit.AlmToolkit.html-resources.src.app.shared.model.comparison-node, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.shared.model.comparison-node can break AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component can't break AlmToolkit.AlmToolkit.html-resources.src.app.shared.model.comparison-node.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can break AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component can't break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.grid.grid_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.service uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
AlmToolkit.AlmToolkit.html-resources.src.app.service uses AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can break AlmToolkit.AlmToolkit.html-resources.src.app.service, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.service can't break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service can break AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component can't break AlmToolkit.AlmToolkit.html-resources.src.app.app-log.app-log_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses a type in AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service, so a change to AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service can break AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component, while a change to AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component can't break AlmToolkit.AlmToolkit.html-resources.src.app.service.grid-data_service.
Position
Below the diagonal: AlmToolkit.AlmToolkit.html-resources.src.app.tree-control-context-menu.tree-control-context-menu_component uses a module listed above it, which is the healthy direction.
AlmToolkit.Model uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break AlmToolkit.Model, while a change to AlmToolkit.Model can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: AlmToolkit.Model uses a module listed above it, which is the healthy direction.
BismNormalizer.CommandLine uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer.CommandLine, while a change to BismNormalizer.CommandLine can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer.CommandLine uses a module listed above it, which is the healthy direction.
BismNormalizer.CommandLine uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break BismNormalizer.CommandLine, while a change to BismNormalizer.CommandLine can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: BismNormalizer.CommandLine uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.MultidimensionalMetadata uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer.TabularCompare.MultidimensionalMetadata, while a change to BismNormalizer.TabularCompare.MultidimensionalMetadata can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer.TabularCompare.MultidimensionalMetadata uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.MultidimensionalMetadata uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break BismNormalizer.TabularCompare.MultidimensionalMetadata, while a change to BismNormalizer.TabularCompare.MultidimensionalMetadata can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: BismNormalizer.TabularCompare.MultidimensionalMetadata uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.TabularMetadata uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer.TabularCompare.TabularMetadata, while a change to BismNormalizer.TabularCompare.TabularMetadata can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer.TabularCompare.TabularMetadata uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.TabularMetadata uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break BismNormalizer.TabularCompare.TabularMetadata, while a change to BismNormalizer.TabularCompare.TabularMetadata can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: BismNormalizer.TabularCompare.TabularMetadata uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.UI uses BismNormalizer.TabularCompare.UI.DesktopInstances, so a change to BismNormalizer.TabularCompare.UI.DesktopInstances can break BismNormalizer.TabularCompare.UI, while a change to BismNormalizer.TabularCompare.UI can't break BismNormalizer.TabularCompare.UI.DesktopInstances.
Position
Below the diagonal: BismNormalizer.TabularCompare.UI uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.UI uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break BismNormalizer.TabularCompare.UI, while a change to BismNormalizer.TabularCompare.UI can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: BismNormalizer.TabularCompare.UI uses a module listed above it, which is the healthy direction.
BismNormalizer.TabularCompare.UI uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break BismNormalizer.TabularCompare.UI, while a change to BismNormalizer.TabularCompare.UI can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: BismNormalizer.TabularCompare.UI uses a module listed above it, which is the healthy direction.
AlmToolkit uses BismNormalizer.TabularCompare, so a change to BismNormalizer.TabularCompare can break AlmToolkit, while a change to AlmToolkit can't break BismNormalizer.TabularCompare.
Position
Below the diagonal: AlmToolkit uses a module listed above it, which is the healthy direction.
AlmToolkit uses BismNormalizer.TabularCompare.Core, so a change to BismNormalizer.TabularCompare.Core can break AlmToolkit, while a change to AlmToolkit can't break BismNormalizer.TabularCompare.Core.
Position
Below the diagonal: AlmToolkit uses a module listed above it, which is the healthy direction.
AlmToolkit uses BismNormalizer.TabularCompare.UI, so a change to BismNormalizer.TabularCompare.UI can break AlmToolkit, while a change to AlmToolkit can't break BismNormalizer.TabularCompare.UI.
Position
Below the diagonal: AlmToolkit uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 40.2 · Weak · gated by D2, D18, X1 ·
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
A03:2025 — Software Supply Chain Failures
84
High / Critical
A05:2025 — Injection
15
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED; Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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 — 104
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 520
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 166
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
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 54 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 — 54 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, 778 of 790 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 2 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 8 test source file(s) (.ts) 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 NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D12 Dependency Hygiene — not measured this run — 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: error: MsBuild was unable to open Project 'AlmToolkit/AlmToolkitSetup/AlmToolkitSetup.vdproj'.
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 C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'AlmToolkit/AlmToolkit/AlmToolkit.csproj' with message: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\chromiumembedded….
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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
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 (34,648 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.
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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to 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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
IC1 Incompleteness & stubs — 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. 315 further occurrence(s) are not listed individually; the score already reflects all 355.
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.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
+ 56 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Comparison.ValidateSelection (cyclomatic 136), Comparison.CompareTabularModels (cyclomatic 81), Comparison.ValidateSelection (cyclomatic 79). — 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 4 together lifts Cyclomatic Complexity from 4.6 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 93 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 18 bodies over 60 down to 60 or less in Cognitive Complexity — start with Comparison.CompareTabularModels (cognitive 279), Comparison.ValidateSelection (cognitive 259), Comparison.CompareTabularModels (cognitive 215). — 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 18 together lifts Cognitive Complexity from 2.0 to about 4.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.4 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 11 MethodTooLong finding(s) in God Classes — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with REDACTED (2), REDACTED (2), DiffMatchPatch.cs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 TooManyMethods finding(s) in God Classes — start with REDACTED (2), ComparisonControl.cs, ComparisonForm.cs. — One of this dimension's main actionable groups (7 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.
68 duplicated block group(s) detected. 11.0 % of the production lines (3,811 of 34,648) are in a reported copy. A further 54 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with TreeGridViewComparison.cs (2), Connections.cs (2), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), REDACTED, CalculationItem.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with TreeGridCell.cs (2), REDACTED, Measure.cs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 1 serious finding✓ 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.
Off the main sequence: Metadata TranslatorMetadataTranslator/Metadata Translator/Metadata Translator.csproj:1
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling — start with Metadata Translator.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with ConnectionsAlmt.cs, REDACTED, Connections.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test 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, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2 tests. Measured on the C# suite only — at least 8 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 198 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure.
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.
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.
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 86 of the 174 production source files in this repository: 72 are under the ~2,400-byte size floor this dimension measures over, and the remaining 16 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
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.
136 deducted debt markers + unmeasured dead symbols across 34648 LoC in the .NET projects (1.7/KLoC) → score 6.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Whole file has no live code — 4 debt markers inside itAlmToolkit/BismNormalizer/TabularCompare/Telemetry.cs:1
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 34 EmptyCatchBlock finding(s) in Explicit Debt — start with Service1.cs (12), REDACTED (8), PartitionProcessor.cs (3). — One of this dimension's main actionable groups (34 issue-level).
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ChromeDebugger.cs, CalcDependency.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 70 CommentedOutCode finding(s) in Explicit Debt — start with ComparisonControl.cs (20), REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (70 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
16 projects, 186 source files, 34739 hand-written lines of code (34648 production / 91 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 5984 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 4 inter-project edges (build failed). Measured across 11 solutions loaded as one workspace: `AlmToolkit/AlmToolkit.sln`, `MetadataTranslator/Metadata Translator.sln`, `AsPartitionProcessing/AsPartitionProcessing.sln`, `AsTrace/ASTrace CS - 2014/ASTrace.sln`, `AsTrace/ASTrace CS - 2014/ASTrace2014.sln`, `AsTrace/ASTrace CS - 2016/ASTrace.sln`, `AsTrace/ASTrace CS - 2016/ASTrace2016.sln`, `AsXEventSample/TracingSample.sln`, `RestApiSample/RestApiSample.sln`, `SetUpAggs/SetUpAggs.sln`, `AsPerfMon/ASPerfMon.sln`.
Build failed
Solution references a project that does not existAsPerfMon/ASPerfMon.sln
What to do
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Solution references a project that does not exist finding(s) in Solution Shape — start with ASPerfMon.sln. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 15 document(s) read across 14 unit(s).
Documentation: no build, run or usage example · ×2README.md:1
What to do
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with SetUpAggs.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×5AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:373
What to do
Resolve the 64 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (48), PartitionProcessor.cs (3), REDACTED (2). — One of this dimension's main actionable groups (64 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 16 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionAlmToolkit/BismNormalizer/BismNormalizer.csproj:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with BismNormalizer.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
15 finding(s): 0 critical, 3 high, 12 medium, 0 low. semgrep hit a parse error in 4 file(s) — `BestPracticeRules/BPARules.json`, `BestPracticeRules/Italian/BPARules.json`, `BestPracticeRules/Japanese/BPARules.json`, `BestPracticeRules/Spanish/BPARules.json` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
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.
84 finding(s): 6 critical, 49 high, 20 medium, 9 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: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 47 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (45), REDACTED (2). — One of this dimension's main actionable groups (47 issue-level).
Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
9 of 102 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is MetadataTranslator/Metadata Translator/Data/DataModel.cs. Counted over 102 of the 174 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with DataModel.cs, MainWindow.xaml.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with TranslatorService.cs, REDACTED, DAX Rest API REDACTED. — One of this dimension's main actionable groups (7 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.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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.
3 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 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.
Resolve the 7 End-of-life runtime finding(s) in Platform End-of-Life — start with ASTrace2014.csproj, ASTrace2016.csproj, AsPartitionProcessing.SampleClient.csproj. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`ComparisonJSInteraction` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (selectedNodes, comparisonList; e.g. `selectedNodes` at line 126). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:10
`Utils` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (PrimaryFudgeFactor, SecondaryFudgeFactor; e.g. `PrimaryFudgeFactor` at line 120). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:13
`CalcDependencyCollection` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (recursionCounter; e.g. `recursionCounter` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalcDependencyCollection.cs:21
`PartitionProcessor` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_modelConfiguration, _messageLogger, _retryAttempts; e.g. `_modelConfiguration` at line 48). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:29
What to do
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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.
The namespaces BismNormalizer.TabularCompare ↔ BismNormalizer.TabularCompare.Core depend on each other. The lightest dependency in the cycle is BismNormalizer.TabularCompare → BismNormalizer.TabularCompare.Core (BismNormalizer.TabularCompare.ComparisonFactory → BismNormalizer.TabularCompare.Core.Comparison, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — AlmToolkit/BismNormalizer/TabularCompare/ComparisonFactory.cs:6
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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.
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.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×5) — MetadataTranslator/Metadata Translator/Converters/CollectionEmptyTrueFalseConverter.cs:20, MetadataTranslator/Metadata Translator/Converters/TranslationPropertyToolTipConverter.cs:31, MetadataTranslator/Metadata Translator/Converters/PercentageConverter.cs:22, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×3) — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:112, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:403, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:456
`CopyTo` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×2) — AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:116, AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:165
`IsSynchronized` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:199
`SyncRoot` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:206
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×33) — AlmToolkit/AlmToolkit/ComparisonForm.cs:106, AlmToolkit/AlmToolkit/ComparisonForm.cs:107, AlmToolkit/AlmToolkit/ComparisonForm.cs:184, …
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:3
What to do
Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. (×2) — MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:134, RestApiSample/RestApiSample/Program.cs:20
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:147, MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:148
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — RestApiSample/RestApiSample/Program.cs:18
`Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. — RestApiSample/RestApiSample/Program.cs:61
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`folderDlg` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 78). Every use of it in `OnExportButton_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderDlg = …;`), which releases it at the end of the scope on every path including a throw. — MetadataTranslator/Metadata Translator/UI/ImportExportPanel.xaml.cs:78
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 250). Every use of it in `PreserveSQLHistory` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cmd = …;`), which releases it at the end of the scope on every path including a throw. (×2) — AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:250, AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:250
`connForm` is a `Connect`, which implements `IDisposable`, and it is created here (line 328). Every use of it in `Connect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var connForm = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:328
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/3 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×3) — AlmToolkit/AlmToolkit/ComparisonForm.cs:123, RestApiSample/RestApiSample/Program.cs:18, RestApiSample/RestApiSample/Program.cs:65
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×34) — AlmToolkit/AlmToolkit/ComparisonForm.cs:152, AlmToolkit/AlmToolkit/ComparisonForm.cs:799, AlmToolkit/AlmToolkit/Program.cs:46, …
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:416, AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:543, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:640
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:175
`throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — REDACTED:396
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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.
SC1 Supply-chain hygiene — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 26 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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 — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Dependency hygiene not measured
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 10 candidate(s) found and not reported.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
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 — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: 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 JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — AlmToolkit/AlmToolkit/html-resources/ (karma) — a gap in the analyzer, not something this repository is missing. 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.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
P8 Schema migrations — no EF Core usage detected
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.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X5 Nullable reference types — no NRT-eligible projects
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.
EmptyCatchBlock AlmToolkit/AlmToolkit/ComparisonForm.cs:152— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AlmToolkit/AlmToolkit/ComparisonForm.cs:799— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AlmToolkit/AlmToolkit/Program.cs:46— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2585— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2677— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2792— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:396— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2462— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2530— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2595— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2605— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:86— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:138— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:157— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:255— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:387— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:461— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:149— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:381— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/ProjectInstaller.cs:40— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:372— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:377— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:410— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:422— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:425— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
WriteOnlyPrivateField AlmToolkit/AlmToolkit/ChromeDebugger.cs:11— private ComparisonForm _instanceMainForm — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalcDependency.cs:11— private TabularModel _parentTabularModel — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
Orphaned knowledge MetadataTranslator/Metadata Translator/Data/DataModel.cs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge MetadataTranslator/Metadata Translator/UI/MainWindow.xaml.cs: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.
Namespace dependency cycle AlmToolkit/BismNormalizer/TabularCompare/ComparisonFactory.cs:6— The namespaces BismNormalizer.TabularCompare ↔ BismNormalizer.TabularCompare.Core depend on each other. The lightest dependency in the cycle is BismNormalizer.TabularCompare → BismNormalizer.TabularCompare.Core (BismNormalizer.TabularCompare.ComparisonFactory → BismNormalizer.TabularCompare.Core.Comparison, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Swallowed exception (empty catch) AlmToolkit/AlmToolkit/ComparisonForm.cs:152— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AlmToolkit/AlmToolkit/ComparisonForm.cs:799— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AlmToolkit/AlmToolkit/Program.cs:46— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2585— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2677— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2792— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:396— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2462— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2530— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2595— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2605— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:86— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:138— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:157— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) MetadataTranslator/Metadata Translator/UI/ImportExportPanel.xaml.cs:63— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:255— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:387— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:461— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/ProjectInstaller.cs:40— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:372— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:377— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:410— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:422— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:425— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:437— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 9 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×18
TodoComment AlmToolkit/AlmToolkit/ComparisonForm.cs:290— //todo: delete extra info once Oren's fix — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AlmToolkit/AlmToolkit/ComparisonForm.cs:565— //Todo: not firing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:596— //Todo: proper xml lookup — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:726— //Todo: see if Tabular helper classes for this once documentation available after CTP — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2013— // 6/9/2025: No longer needed various calls are commented out. TODO: Search for DesktopHardened to clean up. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AlmToolkit/BismNormalizer/Utils.cs:13— //Todo: create an option setting for this so customers can set to share debug error messages — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:144— //todo safer invoke look up bism — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:153— //Todo delete this once http stability fix is done — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:242— //todo: delete global condition — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsXEventSample/TracingSample/Program.cs:133— //TODO stop the trace ! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsXEventSample/TracingSample/Program.cs:162— //TODO: handle exceptions :-) — 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.
MethodTooLong: Comparison.CompareTabularModels AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:81— MethodTooLong — CompareTabularModels runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Comparison.CompareTabularModels AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:80— MethodTooLong — CompareTabularModels runs 249 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 149 over it, 2.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Comparison.ValidateSelection AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:664— MethodTooLong — ValidateSelection runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Program.Main REDACTED:18— MethodTooLong — Main runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TreeGridViewComparison.PopulateNode AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:182— MethodTooLong — PopulateNode runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TabularModel.PopulateMeasures REDACTED:131— MethodTooLong — PopulateMeasures runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConnectionInfo.InitializeCompatibilityLevel REDACTED:499— MethodTooLong — InitializeCompatibilityLevel runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Comparison.ValidateSelection AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:699— MethodTooLong — ValidateSelection runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TabularModel.SyncCultures REDACTED:1701— MethodTooLong — SyncCultures runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Comparison.PopulateExcelRow REDACTED:363— MethodTooLong — PopulateExcelRow runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PartitionProcessor.PerformProcessing AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:55— MethodTooLong — PerformProcessing runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×11
NuGet dependencies are not locked REDACTED:3— REDACTED 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 AlmToolkit/BismNormalizer.CommandLine/packages.config:3— AlmToolkit/BismNormalizer.CommandLine/packages.config 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 AlmToolkit/BismNormalizer.Tests/packages.config:3— AlmToolkit/BismNormalizer.Tests/packages.config 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 AlmToolkit/BismNormalizer/packages.config:3— AlmToolkit/BismNormalizer/packages.config 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 AsPartitionProcessing/AsPartitionProcessing.SampleClient/packages.config:3— AsPartitionProcessing/AsPartitionProcessing.SampleClient/packages.config 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 AsPartitionProcessing/AsPartitionProcessing/packages.config:3— AsPartitionProcessing/AsPartitionProcessing/packages.config 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 AsPerfMon/AsPerfMon/packages.config:3— AsPerfMon/AsPerfMon/packages.config 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 MetadataTranslator/MTCmd/packages.config:3— MetadataTranslator/MTCmd/packages.config 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 MetadataTranslator/Metadata Translator/packages.config:3— MetadataTranslator/Metadata Translator/packages.config 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 REDACTED:3— REDACTED 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 REDACTED:3— REDACTED 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 1204 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 704 over it, 2.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1189 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 689 over it, 2.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/DiffMatchPatch.cs AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs— FileTooLong — 1125 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 625 over it, 2.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TabularMetadata/Comparison.cs AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs— FileTooLong — 895 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 395 over it, 1.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/TreeGridViewComparison.cs AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/ComparisonControl.cs AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs— FileTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 54 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: AlmToolkit/ComparisonForm.cs AlmToolkit/AlmToolkit/ComparisonForm.cs— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: MultidimensionalMetadata/Comparison.cs AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: TabularModel REDACTED— TooManyMethods — 1156 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TabularModel REDACTED— TooManyMethods — 1182 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: ComparisonControl AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs— TooManyMethods — 538 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: ComparisonForm AlmToolkit/AlmToolkit/ComparisonForm.cs— TooManyMethods — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: DiffMatchPatch AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs— TooManyMethods — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), 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: Comparison AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs— TooManyMethods — 890 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× 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: TreeGridViewComparison AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs— TooManyMethods — 559 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) REDACTED:1022— REDACTED:1022-1028 | REDACTED:1344-1350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1022` 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) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:592— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:592-598 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:698-704 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:592` 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) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:301— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:301-307 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:339-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:301` 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) REDACTED:150— REDACTED:150-156 | REDACTED:158-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) AlmToolkit/AlmToolkit/Utils.cs:55— AlmToolkit/AlmToolkit/Utils.cs:55-61 | AlmToolkit/BismNormalizer/Utils.cs:57-63 — `AlmToolkit/AlmToolkit/Utils.cs` and `AlmToolkit/BismNormalizer/Utils.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 25 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (7 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:497— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:497-503 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:585-591 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:507— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:507-513 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:595-601 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.
End-of-life runtime: .NET Framework net40 AsTrace/ASTrace CS - 2014/ASTrace/ASTrace2014.csproj:13— AsTrace/ASTrace CS - 2014/ASTrace/ASTrace2014.csproj declares .NET Framework net40 as this project's target framework version, and .NET Framework 4.0, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net40 AsTrace/ASTrace CS - 2016/ASTrace/ASTrace2016.csproj:13— AsTrace/ASTrace CS - 2016/ASTrace/ASTrace2016.csproj declares .NET Framework net40 as this project's target framework version, and .NET Framework 4.0, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net452 AsPartitionProcessing/AsPartitionProcessing.SampleClient/AsPartitionProcessing.SampleClient.csproj:12— AsPartitionProcessing/AsPartitionProcessing.SampleClient/AsPartitionProcessing.SampleClient.csproj declares .NET Framework net452 as this project's target framework version, and .NET Framework 4.5.2, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net452 AsPartitionProcessing/AsPartitionProcessing/AsPartitionProcessing.csproj:12— AsPartitionProcessing/AsPartitionProcessing/AsPartitionProcessing.csproj declares .NET Framework net452 as this project's target framework version, and .NET Framework 4.5.2, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net452 AsPerfMon/AsPerfMon/ASPerfMon.csproj:12— AsPerfMon/AsPerfMon/ASPerfMon.csproj declares .NET Framework net452 as this project's target framework version, and .NET Framework 4.5.2, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net452 AsXEventSample/TracingSample/TracingSample.csproj:12— AsXEventSample/TracingSample/TracingSample.csproj declares .NET Framework net452 as this project's target framework version, and .NET Framework 4.5.2, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net461 SetUpAggs/SetUpAggs.csproj:11— SetUpAggs/SetUpAggs.csproj declares .NET Framework net461 as this project's target framework version, and .NET Framework 4.6.1, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Duplicated block (15 lines × 2) REDACTED:509— REDACTED:509-523 | REDACTED:533-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:509` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1210— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1210-1224 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2045-2059 — `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs` and `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 67 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1210` 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 (15 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:642— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:642-656 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:677-691 — `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs` and `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 67 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:79— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:79-93 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:92-106 — 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 `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:79` 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 (15 lines × 2) REDACTED:2768— REDACTED:2768-2782 | REDACTED:2506-2520 — 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 `REDACTED:2768` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) REDACTED:1219— REDACTED:1219-1223 | REDACTED:1240-1244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:194— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:194-198 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:209-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:194` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:182— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:182-186 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:203-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:56— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:56-60 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:65-69 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:429— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:429-433 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:438-442 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Unfinished stub — throws NotImplementedException MetadataTranslator/Metadata Translator/Converters/CollectionEmptyTrueFalseConverter.cs:20— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MetadataTranslator/Metadata Translator/Converters/TranslationPropertyToolTipConverter.cs:31— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MetadataTranslator/Metadata Translator/Converters/PercentageConverter.cs:22— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MetadataTranslator/Metadata Translator/Converters/TrueFalseVisibilityConverter.cs:25— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MetadataTranslator/Metadata Translator/Converters/TrueFalseVisibilityConverter.cs:43— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
AX2 · Stateful singletons· Process-global static state · ×4
Process-global static state: ComparisonJSInteraction AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:10— `ComparisonJSInteraction` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (selectedNodes, comparisonList; e.g. `selectedNodes` at line 126). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Utils AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:13— `Utils` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (PrimaryFudgeFactor, SecondaryFudgeFactor; e.g. `PrimaryFudgeFactor` at line 120). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: CalcDependencyCollection AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalcDependencyCollection.cs:21— `CalcDependencyCollection` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (recursionCounter; e.g. `recursionCounter` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: PartitionProcessor AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:29— `PartitionProcessor` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_modelConfiguration, _messageLogger, _retryAttempts; e.g. `_modelConfiguration` at line 48). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Duplicated block (14 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:85— AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:85-98 | AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:82-95 — 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 `AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) REDACTED:445— REDACTED:445-458 | REDACTED:489-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:445` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:168— AlmToolkit/AlmToolkit/ComparisonForm.cs:168-181 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:318-331 — 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 what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (14 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:192— AlmToolkit/AlmToolkit/ComparisonForm.cs:192-205 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:343-356 — 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 what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AlmToolkit/AlmToolkit/ComparisonForm.cs:212` calls `SetGridState` and `AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:357` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:410— AlmToolkit/AlmToolkit/ComparisonForm.cs:410-420 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:266-276 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:426— AlmToolkit/AlmToolkit/ComparisonForm.cs:426-436 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:282-292 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:293` calls `GetFromAutoCompleteTarget` and `AlmToolkit/AlmToolkit/ComparisonForm.cs:438` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) AlmToolkit/AlmToolkit/Utils.cs:30— AlmToolkit/AlmToolkit/Utils.cs:30-40 | AlmToolkit/BismNormalizer/Utils.cs:32-42 — `AlmToolkit/AlmToolkit/Utils.cs` and `AlmToolkit/BismNormalizer/Utils.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 25 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:57— AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:57-67 | AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:401-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:562— REDACTED:562-571 | REDACTED:263-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:128— AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:128-137 | AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:164-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:2611— REDACTED:2611-2620 | REDACTED:2311-2320 — 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 `REDACTED:2611` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:2814— REDACTED:2814-2823 | REDACTED:2552-2561 — 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.
Unfinished stub — throws a "not implemented" exception AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:116— `CopyTo` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:165— `CopyTo` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:199— `IsSynchronized` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNodeCollection.cs:206— `SyncRoot` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×4
Disposable created and abandoned in the method that made it MetadataTranslator/Metadata Translator/UI/ImportExportPanel.xaml.cs:78— `folderDlg` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 78). Every use of it in `OnExportButton_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderDlg = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:250— `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 250). Every use of it in `PreserveSQLHistory` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:250— `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 250). Every use of it in `PreserveSQLHistory` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:328— `connForm` is a `Connect`, which implements `IDisposable`, and it is created here (line 328). Every use of it in `Connect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var connForm = …;`), which releases it at the end of the scope on every path including a throw.
Swallowed exception (caught, then discarded) AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:416— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:543— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:640— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:175— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1836— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1836-1854 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1857-1875 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:632— AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:632-651 | AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:677-695 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:224— AlmToolkit/AlmToolkit/ComparisonForm.cs:224-242 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:207-226 — 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 (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:193— AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:193-217 | AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:220-242 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:223— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:223-247 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:254-276 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:525— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:525-547 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:621-644 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:852— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:852-869 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:871-885 — 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) AlmToolkit/AlmToolkit/ComparisonForm.cs:856— AlmToolkit/AlmToolkit/ComparisonForm.cs:856-872 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:149-163 — 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) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1235— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1235-1249 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2070-2084 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1935— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1935-1946 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1997-2007 — 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) AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1115— AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1115-1125 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1128-1138 — 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) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/TableCollection.cs:88— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/TableCollection.cs:88-98 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/TableCollection.cs:53-63 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) AlmToolkit/AlmToolkit/Utils.cs:54— AlmToolkit/AlmToolkit/Utils.cs:54-61 | AlmToolkit/BismNormalizer/Utils.cs:56-63 — 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) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:496— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:496-503 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:584-591 — 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) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:506— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:506-513 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:594-601 — 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 (17 lines × 2) REDACTED:2740— REDACTED:2740-2756 | REDACTED:2478-2494 — 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 `REDACTED:2740` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:511— AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:511-527 | AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:557-573 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:511` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1276— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1276-1292 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2111-2127 — `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs` and `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 67 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:59— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:59-66 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:70-77 — 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 `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:551— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:551-558 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:527-534 — `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs` and `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 67 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:551` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:750— AlmToolkit/AlmToolkit/ComparisonForm.cs:750-757 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1159-1166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Low cohesion: ConnectionsAlmt (LCOM4 13) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:13— ConnectionsAlmt's methods fall into 13 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 13 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: Comparison (LCOM4 9) REDACTED:13— Comparison's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Connections (LCOM4 9) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:10— Connections's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs· Both branches open with the same statements · ×3
Both branches open with the same statements — the condition does not decide them AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:112— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:403— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:456— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
X2 · Cancellation propagation· Async method without CancellationToken · ×3
Async method without CancellationToken: CheckForNewVersion AlmToolkit/AlmToolkit/ComparisonForm.cs:123— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CallRefreshAsync RestApiSample/RestApiSample/Program.cs:18— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateToken RestApiSample/RestApiSample/Program.cs:65— No CancellationToken parameter — this work can't be stopped early once started.
Trace.DoWork (cognitive 33) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:311— Trace.DoWork has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Trace.DoWork (cognitive 33) AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:311— Trace.DoWork has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.Trace_OnEvent (cognitive 18) REDACTED:2758— TabularModel.Trace_OnEvent has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.Trace_OnEvent (cognitive 18) REDACTED:2496— TabularModel.Trace_OnEvent has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:407— AlmToolkit/AlmToolkit/ComparisonForm.cs:407-439 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:263-295 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (33 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1524— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1524-1556 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1559-1591 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (52 corresponding lines) · ×2
Edited copy of a member (52 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:166— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:166-217 | AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:220-273 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (52 corresponding lines) REDACTED:2759— REDACTED:2759-2810 | REDACTED:2497-2548 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) REDACTED:558— REDACTED:558-579 | REDACTED:259-274 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:517— AlmToolkit/AlmToolkit/ComparisonForm.cs:517-538 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1037-1052 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1209— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1209-1232 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2044-2067 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:308— AlmToolkit/AlmToolkit/ComparisonForm.cs:308-331 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:734-762 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1816— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1816-1833 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1882-1900 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:818— AlmToolkit/AlmToolkit/ComparisonForm.cs:818-835 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:126-146 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Kpi.cs:64— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Kpi.cs:64-73 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Kpi.cs:96-105 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Kpi.cs:128-137 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItemCollection.cs:51— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItemCollection.cs:51-60 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/MeasureCollection.cs:51-60 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:567-576 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×2
Edited copies of one member (4 members, 11+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItemCollection.cs:86— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItemCollection.cs:86-96 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/DataSourceCollection.cs:54-64 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/MeasureCollection.cs:86-96 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/TableCollection.cs:95-105 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 11+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/KpiCollection.cs:87— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/KpiCollection.cs:87-97 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/MeasureCollection.cs:87-97 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItemCollection.cs:68-78 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/MeasureCollection.cs:68-78 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (6 lines × 2) REDACTED:127— REDACTED:127-132 | REDACTED:144-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:315— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:315-320 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:394-399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1238— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1238-1249 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:2073-2084 — `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs` and `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 67 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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) AlmToolkit/AlmToolkit/ComparisonForm.cs:393— AlmToolkit/AlmToolkit/ComparisonForm.cs:393-404 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:249-260 — 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 (6 lines × 3) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:681— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:681-686 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:731-736 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:791-796 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:681` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) MetadataTranslator/Metadata Translator/Data/DataModel.cs:163— MetadataTranslator/Metadata Translator/Data/DataModel.cs:163-168 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:174-179 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:184-189 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) REDACTED:98— REDACTED:98-102 | REDACTED:152-156 | REDACTED:160-164 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:98` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) REDACTED:150— REDACTED:150-154 | REDACTED:158-162 | REDACTED:166-170 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Outbound HTTP without resilience MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:134— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience RestApiSample/RestApiSample/Program.cs:20— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Sync-over-async (deadlock risk) through `.Result` MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:147— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs:148— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Comparison.ValidateSelection (cyclomatic 136) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:664— Comparison.ValidateSelection has cyclomatic complexity 136 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.CompareTabularModels (cyclomatic 81) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:81— Comparison.CompareTabularModels has cyclomatic complexity 81 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.ValidateSelection (cyclomatic 79) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:699— Comparison.ValidateSelection has cyclomatic complexity 79 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Comparison.CompareTabularModels (cyclomatic 72) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:80— Comparison.CompareTabularModels has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.SyncCultures (cyclomatic 56) REDACTED:1701— TabularModel.SyncCultures has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ConnectionInfo.InitializeCompatibilityLevel (cyclomatic 55) REDACTED:499— ConnectionInfo.InitializeCompatibilityLevel has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Program.Main (cyclomatic 55) REDACTED:18— Program.Main has cyclomatic complexity 55 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TreeGridViewComparison.PopulateNode (cyclomatic 46) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:182— TreeGridViewComparison.PopulateNode has cyclomatic complexity 46 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ComparisonFactory.CreateComparisonInitialized (cyclomatic 44) AlmToolkit/BismNormalizer/TabularCompare/ComparisonFactory.cs:64— ComparisonFactory.CreateComparisonInitialized has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.CleanUpAggregations (cyclomatic 41) REDACTED:1141— TabularModel.CleanUpAggregations has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Perspective.ContainsOtherPerspectiveSelections (cyclomatic 39) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Perspective.cs:236— Perspective.ContainsOtherPerspectiveSelections has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.PopulateMeasures (cyclomatic 38) REDACTED:131— TabularModel.PopulateMeasures has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.UpdatePerspective (cyclomatic 38) REDACTED:1919— TabularModel.UpdatePerspective has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Table.SetColumnFormatAndVisibility (cyclomatic 36) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:417— Table.SetColumnFormatAndVisibility has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Comparison.PopulateExcelRow (cyclomatic 35) REDACTED:363— Comparison.PopulateExcelRow has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table.PopulateProperties (cyclomatic 35) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:143— Table.PopulateProperties has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Table.CreateRelationship (cyclomatic 35) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:591— Table.CreateRelationship has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.CreateTable (cyclomatic 35) REDACTED:1091— TabularModel.CreateTable has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComparisonJSInteraction.PopulateComparisonData (cyclomatic 32) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:188— ComparisonJSInteraction.PopulateComparisonData has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Comparison.HasBlockingFromDependenciesInSource (cyclomatic 32) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1148— Comparison.HasBlockingFromDependenciesInSource has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiffMatchPatch.diff_bisect (cyclomatic 32) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:477— DiffMatchPatch.diff_bisect has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Perspective.Perspective.ctor (cyclomatic 28) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Perspective.cs:23— Perspective.Perspective.ctor has cyclomatic complexity 28 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PartitionProcessor.PerformProcessing (cyclomatic 27) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:55— PartitionProcessor.PerformProcessing has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Measure.PopulateObjectDefinition (cyclomatic 26) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:41— Measure.PopulateObjectDefinition has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TabularModel.InitializeCalcDependenciesFromM (cyclomatic 26) REDACTED:254— TabularModel.InitializeCalcDependenciesFromM has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreeGridViewValidationOutput.ShowStatusMessage (cyclomatic 26) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewValidationOutput.cs:87— TreeGridViewValidationOutput.ShowStatusMessage has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DiffMatchPatch.diff_cleanupMerge (cyclomatic 25) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1308— DiffMatchPatch.diff_cleanupMerge has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.Connect (cyclomatic 24) REDACTED:59— TabularModel.Connect has cyclomatic complexity 24 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TabularModel.UpdateRelationshipsForChildrenOfUpdatedTables (cyclomatic 23) REDACTED:1431— TabularModel.UpdateRelationshipsForChildrenOfUpdatedTables has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiffMatchPatch.diff_cleanupEfficiency (cyclomatic 23) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1211— DiffMatchPatch.diff_cleanupEfficiency has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Action.Action.ctor (cyclomatic 22) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Action.cs:24— Action.Action.ctor has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.UpdateTable (cyclomatic 22) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1733— Comparison.UpdateTable has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.UpdateTable (cyclomatic 21) REDACTED:1305— TabularModel.UpdateTable has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.SyncPerspectives (cyclomatic 21) REDACTED:1514— TabularModel.SyncPerspectives has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PartitionProcessor.MergePartitions (cyclomatic 21) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:267— PartitionProcessor.MergePartitions has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TabularModel.CreateRole (cyclomatic 20) REDACTED:2182— TabularModel.CreateRole has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.DeleteExpression (cyclomatic 20) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1459— Comparison.DeleteExpression has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiffMatchPatch.diff_cleanupSemanticScore (cyclomatic 20) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1150— DiffMatchPatch.diff_cleanupSemanticScore has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Measure.FindMissingCalculationDependencies (cyclomatic 19) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:223— Measure.FindMissingCalculationDependencies has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.CreatePerspective (cyclomatic 19) REDACTED:1810— TabularModel.CreatePerspective has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Table.PopulateProperties (cyclomatic 19) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:82— Table.PopulateProperties has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiffMatchPatch.patch_splitMax (cyclomatic 19) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2369— DiffMatchPatch.patch_splitMax has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AggConfigurationUtility.ApplyConfigurationOfTable (cyclomatic 19) REDACTED:200— AggConfigurationUtility.ApplyConfigurationOfTable has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 218, 223, 255, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ComparisonJSInteraction.ShowHideSkipNodes (cyclomatic 18) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:395— ComparisonJSInteraction.ShowHideSkipNodes has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.HasBlockingToDependenciesInTarget (cyclomatic 18) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1072— Comparison.HasBlockingToDependenciesInTarget has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Perspective.ContainsOtherPerspectiveSelections (cyclomatic 18) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Perspective.cs:43— Perspective.ContainsOtherPerspectiveSelections has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.DatabaseDeployAndProcess (cyclomatic 18) REDACTED:2179— TabularModel.DatabaseDeployAndProcess has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DiffMatchPatch.diff_cleanupSemantic (cyclomatic 18) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:937— DiffMatchPatch.diff_cleanupSemantic has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Comparison.DeleteDataSource (cyclomatic 17) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1350— Comparison.DeleteDataSource has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Measure.FindMissingMeasureDependencies (cyclomatic 17) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:64— Measure.FindMissingMeasureDependencies has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.CanRetainPartitions (cyclomatic 17) REDACTED:741— TabularModel.CanRetainPartitions has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ComparisonControl.PopulateObjectDefinitions (cyclomatic 17) AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:407— ComparisonControl.PopulateObjectDefinitions has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiffMatchPatch.patch_apply (cyclomatic 17) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2171— DiffMatchPatch.patch_apply has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreeGridCell.Paint (cyclomatic 17) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:123— TreeGridCell.Paint has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.PopulateReferenceDimension (cyclomatic 16) REDACTED:767— TabularModel.PopulateReferenceDimension has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TabularModel.Process (cyclomatic 16) REDACTED:2351— TabularModel.Process has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ConnectionsAlmt.BindSourceConnectionInfo (cyclomatic 16) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:116— ConnectionsAlmt.BindSourceConnectionInfo has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ConnectionsAlmt.BindTargetConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ConnectionsAlmt.BindTargetConnectionInfo (cyclomatic 16) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:207— ConnectionsAlmt.BindTargetConnectionInfo has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ConnectionsAlmt.BindSourceConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DiffMatchPatch.patch_make (cyclomatic 16) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2051— DiffMatchPatch.patch_make has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataModel.LoadNamedObjectCollections (cyclomatic 16) MetadataTranslator/Metadata Translator/Data/DataModel.cs:142— DataModel.LoadNamedObjectCollections has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AggConfigurationUtility.ValidateConfigurationOfTable (cyclomatic 16) REDACTED:138— AggConfigurationUtility.ValidateConfigurationOfTable has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt· Whole file has no live code · ×1
Whole file has no live code — 4 debt markers inside it AlmToolkit/BismNormalizer/TabularCompare/Telemetry.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
HackComment AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:175— // HACK: only add first row that is in a Listening state — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D17 · Explicit Debt· BareSuppressMessage repeated 14 times in 4 files · ×1
BareSuppressMessage repeated 14 times in 4 files AlmToolkit/BismNormalizer/TabularCompare/UI/SynchronizedScrollRichTextBox.cs:8— The identical BareSuppressMessage (`System.Diagnostics.CodeAnalysis.SuppressMessage`) appears 14 times in 4 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 14 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
Build failed — The target solution did not build cleanly (errors: 118), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0234: The type or namespace name 'AnalysisServices' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'NamedMetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'MetadataObject' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TranslatedProperty' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CultureCollection' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Partition' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Server' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Database' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Table' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Management' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0246: The type or namespace name 'TraceServer' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TraceTable' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'XEvent' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?); CS0234: The type or namespace name 'IdentityModel' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'PowerArgs' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonPropertyAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JsonProperty' could not be found (are you missing a using directive or an assembly reference?).
D18 · Solution Shape· Solution references a project that does not exist · ×1
Solution references a project that does not exist AsPerfMon/ASPerfMon.sln— `AsPerfMon/ASPerfMon.sln` declares 1 project file(s) that are missing from the tree (`AsPerfMon/ASPerfMon/ASPerfMon.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
Comparison.CompareTabularModels (cognitive 279) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:80— Comparison.CompareTabularModels has cognitive complexity 279 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Comparison.ValidateSelection (cognitive 259) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:664— Comparison.ValidateSelection has cognitive complexity 259 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.CompareTabularModels (cognitive 215) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:81— Comparison.CompareTabularModels has cognitive complexity 215 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.SyncCultures (cognitive 202) REDACTED:1701— TabularModel.SyncCultures has cognitive complexity 202 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.PopulateMeasures (cognitive 175) REDACTED:131— TabularModel.PopulateMeasures has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.CleanUpAggregations (cognitive 146) REDACTED:1141— TabularModel.CleanUpAggregations has cognitive complexity 146 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.UpdateRelationshipsForChildrenOfUpdatedTables (cognitive 136) REDACTED:1431— TabularModel.UpdateRelationshipsForChildrenOfUpdatedTables has cognitive complexity 136 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.UpdatePerspective (cognitive 136) REDACTED:1919— TabularModel.UpdatePerspective has cognitive complexity 136 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Perspective.ContainsOtherPerspectiveSelections (cognitive 117) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Perspective.cs:236— Perspective.ContainsOtherPerspectiveSelections has cognitive complexity 117 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.ValidateSelection (cognitive 105) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:699— Comparison.ValidateSelection has cognitive complexity 105 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectionInfo.InitializeCompatibilityLevel (cognitive 92) REDACTED:499— ConnectionInfo.InitializeCompatibilityLevel has cognitive complexity 92 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Table.CreateRelationship (cognitive 92) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:591— Table.CreateRelationship has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.SyncPerspectives (cognitive 82) REDACTED:1514— TabularModel.SyncPerspectives has cognitive complexity 82 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.UpdateTable (cognitive 72) REDACTED:1305— TabularModel.UpdateTable has cognitive complexity 72 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PartitionProcessor.PerformProcessing (cognitive 72) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:55— PartitionProcessor.PerformProcessing has cognitive complexity 72 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Perspective.ContainsOtherPerspectiveSelections (cognitive 71) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Perspective.cs:43— Perspective.ContainsOtherPerspectiveSelections has cognitive complexity 71 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.Main (cognitive 70) REDACTED:18— Program.Main has cognitive complexity 70 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TabularModel.CreateTable (cognitive 64) REDACTED:1091— TabularModel.CreateTable has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.CreatePerspective (cognitive 58) REDACTED:1810— TabularModel.CreatePerspective has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiffMatchPatch.diff_bisect (cognitive 58) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:477— DiffMatchPatch.diff_bisect has cognitive complexity 58 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.CreateRole (cognitive 56) REDACTED:2182— TabularModel.CreateRole has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table.PopulateProperties (cognitive 55) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Table.cs:143— Table.PopulateProperties has cognitive complexity 55 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffMatchPatch.patch_apply (cognitive 55) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2171— DiffMatchPatch.patch_apply has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Perspective.Perspective.ctor (cognitive 54) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Perspective.cs:23— Perspective.Perspective.ctor has cognitive complexity 54 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Comparison.UpdateTable (cognitive 53) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1733— Comparison.UpdateTable has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.CleanUpVariations (cognitive 49) REDACTED:1058— TabularModel.CleanUpVariations has cognitive complexity 49 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComparisonFactory.CreateComparisonInitialized (cognitive 48) AlmToolkit/BismNormalizer/TabularCompare/ComparisonFactory.cs:64— ComparisonFactory.CreateComparisonInitialized has cognitive complexity 48 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.PopulateReferenceDimension (cognitive 48) REDACTED:767— TabularModel.PopulateReferenceDimension has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.CheckRelationshipValidity (cognitive 48) REDACTED:1527— TabularModel.CheckRelationshipValidity has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.DatabaseDeployAndProcess (cognitive 48) REDACTED:2179— TabularModel.DatabaseDeployAndProcess has cognitive complexity 48 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DiffMatchPatch.diff_cleanupMerge (cognitive 48) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1308— DiffMatchPatch.diff_cleanupMerge has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Measure.FindMissingCalculationDependencies (cognitive 47) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:223— Measure.FindMissingCalculationDependencies has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffMatchPatch.patch_splitMax (cognitive 47) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2369— DiffMatchPatch.patch_splitMax has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.HasBlockingFromDependenciesInSource (cognitive 46) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1148— Comparison.HasBlockingFromDependenciesInSource has cognitive complexity 46 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.ParseMdxScript (cognitive 45) REDACTED:425— TabularModel.ParseMdxScript has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.InitializeCalcDependenciesFromM (cognitive 45) REDACTED:254— TabularModel.InitializeCalcDependenciesFromM has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Action.Action.ctor (cognitive 43) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Action.cs:24— Action.Action.ctor has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.DeleteExpression (cognitive 43) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1459— Comparison.DeleteExpression has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ComparisonJSInteraction.PopulateComparisonData (cognitive 42) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:188— ComparisonJSInteraction.PopulateComparisonData has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionsAlmt.BindSourceConnectionInfo (cognitive 42) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:116— ConnectionsAlmt.BindSourceConnectionInfo has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ConnectionsAlmt.BindTargetConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ConnectionsAlmt.BindTargetConnectionInfo (cognitive 42) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:207— ConnectionsAlmt.BindTargetConnectionInfo has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ConnectionsAlmt.BindSourceConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DataModel.LoadNamedObjectCollections (cognitive 40) MetadataTranslator/Metadata Translator/Data/DataModel.cs:142— DataModel.LoadNamedObjectCollections has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.Connect (cognitive 39) REDACTED:59— TabularModel.Connect has cognitive complexity 39 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TabularModel.InitializeCalcDependenciesFromServer (cognitive 39) REDACTED:182— TabularModel.InitializeCalcDependenciesFromServer has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffMatchPatch.diff_cleanupSemantic (cognitive 39) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:937— DiffMatchPatch.diff_cleanupSemantic has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.DeleteDataSource (cognitive 38) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1350— Comparison.DeleteDataSource has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiffMatchPatch.diff_cleanupEfficiency (cognitive 38) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1211— DiffMatchPatch.diff_cleanupEfficiency has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.FlushReferenceDimensions (cognitive 37) REDACTED:690— TabularModel.FlushReferenceDimensions has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.CreateTable (cognitive 36) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1666— Comparison.CreateTable has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiffMatchPatch.match_bitap (cognitive 36) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1783— DiffMatchPatch.match_bitap has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.HasBlockingToDependenciesInTarget (cognitive 31) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1072— Comparison.HasBlockingToDependenciesInTarget has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Table.PopulateProperties (cognitive 31) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:82— Table.PopulateProperties has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeGridCell.Paint (cognitive 31) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridCell.cs:123— TreeGridCell.Paint has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AggConfigurationUtility.ValidateConfigurationOfTable (cognitive 31) REDACTED:138— AggConfigurationUtility.ValidateConfigurationOfTable has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.PopulateMdxScript (cognitive 29) REDACTED:2333— TabularModel.PopulateMdxScript has cognitive complexity 29 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TabularObject.TabularObject.ctor (cognitive 28) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/TabularObject.cs:27— TabularObject.TabularObject.ctor has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Connections.Connections_Load (cognitive 28) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:24— Connections.Connections_Load has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffMatchPatch.diff_cleanupSemanticLossless (cognitive 28) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1066— DiffMatchPatch.diff_cleanupSemanticLossless has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComparisonJSInteraction.ShowHideSkipNodes (cognitive 27) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:395— ComparisonJSInteraction.ShowHideSkipNodes has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.Process (cognitive 27) REDACTED:2625— TabularModel.Process has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CalculationItem.FindMissingCalculationItemDependencies (cognitive 27) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:53— CalculationItem.FindMissingCalculationItemDependencies has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Measure.FindMissingMeasureDependencies (cognitive 27) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:64— Measure.FindMissingMeasureDependencies has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeGridViewComparison.PopulateNode (cognitive 26) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:182— TreeGridViewComparison.PopulateNode has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabularModel.Process (cognitive 25) REDACTED:2351— TabularModel.Process has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlobCredentials.BlobCredentials_Load (cognitive 25) AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:47— BlobCredentials.BlobCredentials_Load has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ImpersonationCredentials.ImpersonationCredentials_FormClosing (cognitive 25) AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:122— ImpersonationCredentials.ImpersonationCredentials_FormClosing has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeGridView.SiteNode (cognitive 25) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridView.cs:309— TreeGridView.SiteNode has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeGridViewComparison.ShowHideNodes (cognitive 25) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:812— TreeGridViewComparison.ShowHideNodes has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableConfiguration.ValidatePartitioningConfigurations (cognitive 25) AsPartitionProcessing/AsPartitionProcessing/TableConfiguration.cs:54— TableConfiguration.ValidatePartitioningConfigurations has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.ScriptDatabase (cognitive 24) REDACTED:2832— TabularModel.ScriptDatabase has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PartitionProcessor.MergePartitions (cognitive 24) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:267— PartitionProcessor.MergePartitions has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PowerBIHelper.GetLocalInstances (cognitive 23) AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/PowerBIHelper.cs:74— PowerBIHelper.GetLocalInstances has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffMatchPatch.patch_make (cognitive 23) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:2051— DiffMatchPatch.patch_make has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ASPerfMon.GetNewXAxisMarkerPointsFromAs (cognitive 23) REDACTED:211— ASPerfMon.GetNewXAxisMarkerPointsFromAs has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.DeleteRole (cognitive 22) REDACTED:2110— TabularModel.DeleteRole has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.DatabaseDeployAndProcess (cognitive 22) REDACTED:2548— TabularModel.DatabaseDeployAndProcess has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ParseArgs (cognitive 22) AsPartitionProcessing/AsPartitionProcessing.SampleClient/Program.cs:221— Program.ParseArgs has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeGridViewComparison.CheckToSkipChildren (cognitive 21) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:589— TreeGridViewComparison.CheckToSkipChildren has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComparisonJSInteraction.NodeContainsEditableChildren (cognitive 20) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:456— ComparisonJSInteraction.NodeContainsEditableChildren has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.PopulateExcelRow (cognitive 20) REDACTED:363— Comparison.PopulateExcelRow has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Role.Role.ctor (cognitive 20) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Role.cs:23— Role.Role.ctor has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionsAlmt.Connections_Load (cognitive 20) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:30— ConnectionsAlmt.Connections_Load has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Comparison.UpdateModel (cognitive 19) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1301— Comparison.UpdateModel has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.UpdateTable (cognitive 19) REDACTED:666— TabularModel.UpdateTable has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComparisonControl.PopulateObjectDefinitions (cognitive 19) AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:407— ComparisonControl.PopulateObjectDefinitions has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionInfo.IsPbiCompatibilityMode (cognitive 18) REDACTED:801— ConnectionInfo.IsPbiCompatibilityMode has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabularModel.DeleteTable (cognitive 18) REDACTED:1037— TabularModel.DeleteTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Connections.BindSourceConnectionInfo (cognitive 18) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:165— Connections.BindSourceConnectionInfo has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (Connections.BindTargetConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Connections.BindTargetConnectionInfo (cognitive 18) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:219— Connections.BindTargetConnectionInfo has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (Connections.BindSourceConnectionInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DiffMatchPatch.diff_cleanupSemanticScore (cognitive 18) AlmToolkit/BismNormalizer/TabularCompare/UI/DiffMatchPatch.cs:1150— DiffMatchPatch.diff_cleanupSemanticScore has cognitive complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AggConfigurationUtility.ApplyConfigurationOfTable (cognitive 18) REDACTED:200— AggConfigurationUtility.ApplyConfigurationOfTable has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 218, 255, 205, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ASPerfMon.OnTimedEvent (cognitive 18) REDACTED:137— ASPerfMon.OnTimedEvent has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ManagedIpHelper.GetExtendedTcpDictionary (cognitive 17) AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:155— ManagedIpHelper.GetExtendedTcpDictionary has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ImpersonationCredentials.ImpersonationCredentials_Load (cognitive 17) AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:53— ImpersonationCredentials.ImpersonationCredentials_Load has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.Import (cognitive 17) MetadataTranslator/MTCmd/Program.cs:80— Program.Import has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
rebuild.make_row_from_xml (cognitive 16) REDACTED:66— rebuild.make_row_from_xml has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: Comparison AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs— ClassTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 122 over it, 1.31× 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.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:113— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:113-166 | AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:233-309 | AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:312-400 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:113-166 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:233-309 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:312-400 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (84 corresponding lines) · ×1
Edited copy of a member (84 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:25— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:25-143 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:31-114 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (89 corresponding lines) · ×1
Edited copy of a member (89 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:117— AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:117-205 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:208-296 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:54— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:54-114 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:65-127 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:48— AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:48-105 | AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:54-120 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:120— AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:120-153 | AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ManagedIpHelper.cs:156-195 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:311— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:311-355 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:366-417 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) REDACTED:582— REDACTED:582-658 | REDACTED:277-317 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridView.cs:271— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridView.cs:271-307 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridView.cs:399-439 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:484— AlmToolkit/AlmToolkit/ComparisonForm.cs:484-514 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:946-1000 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:680— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:680-694 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:727-747 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:785-806 — 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 copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:640— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:640-653 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:765-778 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:580— AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:580-599 | AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:709-728 — 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 copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) REDACTED:2732— REDACTED:2732-2756 | REDACTED:2470-2494 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:191— AlmToolkit/AlmToolkit/ComparisonForm.cs:191-213 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:341-357 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) REDACTED:1486— REDACTED:1486-1512 | REDACTED:1673-1699 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:516— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:516-522 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:612-618 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:549— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:549-560 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:667-678 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) AlmToolkit/AlmToolkit/ComparisonForm.cs:749— AlmToolkit/AlmToolkit/ComparisonForm.cs:749-757 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:1158-1166 — 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) REDACTED:900— REDACTED:900-920 | REDACTED:479-499 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) AlmToolkit/AlmToolkit/Utils.cs:73— AlmToolkit/AlmToolkit/Utils.cs:73-78 | AlmToolkit/BismNormalizer/Utils.cs:67-72 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) AlmToolkit/AlmToolkit/Utils.cs:16— AlmToolkit/AlmToolkit/Utils.cs:16-23 | AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:18-25 | AlmToolkit/BismNormalizer/Utils.cs:18-25 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 11+ corresponding lines) · ×1
Edited copies of one member (8 members, 11+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/ActionCollection.cs:63— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/ActionCollection.cs:63-73 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/DataSourceCollection.cs:88-98 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/KpiCollection.cs:105-115 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/MeasureCollection.cs:105-115 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/PerspectiveCollection.cs:88-98 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/RelationshipCollection.cs:106-116 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/RoleCollection.cs:88-98 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/TableCollection.cs:106-116 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CultureCollection.cs:71— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CultureCollection.cs:71-81 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/ExpressionCollection.cs:71-81 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/FunctionCollection.cs:71-81 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/PerspectiveCollection.cs:71-81 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/RelationshipCollection.cs:88-98 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/RoleCollection.cs:71-81 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:55— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:55-58 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:58-61 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (88 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:313— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:313-400 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:313-400 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (76 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:234— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:234-309 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:234-309 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:234` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (61 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:170— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:170-230 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:170-230 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (52 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:115— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:115-166 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:115-166 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (38 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:26— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:26-63 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:35-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:33` calls `ToInt32` and `AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:25` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (33 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:48— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:48-80 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:48-80 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:85— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:85-109 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:85-109 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:404— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:404-426 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:404-426 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1675— AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1675-1695 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1750-1770 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:1675` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–19 lines × 2) AlmToolkit/AlmToolkit/ComparisonForm.cs:1056— AlmToolkit/AlmToolkit/ComparisonForm.cs:1056-1065 | AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:70-88 — 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 (19 lines × 2) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:371— AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:371-389 | AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:445-463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:371` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:48— AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:48-64 | AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:54-71 — 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 `AlmToolkit/BismNormalizer/TabularCompare/UI/BlobCredentials.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–17 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:230— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:230-243 | AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:62-78 — 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 `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:62` calls `TrimStart`, `Substring` and `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Measure.cs:230` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 6) AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:150— AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:150-162 | AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:295-307 | AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:352-364 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:150-162 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:295-307 | AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs:352-364 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 371 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) REDACTED:2562— REDACTED:2562-2574 | REDACTED:2208-2220 | REDACTED:2229-2241 | REDACTED:2251-2263 | REDACTED:2281-2293 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:225— AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:225-236 | AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:366-377 | AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:440-451 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsPartitionProcessing/AsPartitionProcessing/PartitionProcessor.cs:225` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:727— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:727-737 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:785-797 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:727` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:359— AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:359-369 | AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:405-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:359` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:359` calls `FilterByTableName`, `ContainsName` and `AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:405` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:198— AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:198-206 | AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:224-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/Deployment.cs:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:34— AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:34-41 | AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs:43-50 | AlmToolkit/BismNormalizer/TabularCompare/UI/Options.cs:35-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:594— AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:594-599 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:607-612 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:700-705 | AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:753-758 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs:594` 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–8 lines × 2) REDACTED:991— REDACTED:991-997 | REDACTED:1000-1007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:991` 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 (5 lines × 5) MetadataTranslator/Metadata Translator/Data/DataModel.cs:154— MetadataTranslator/Metadata Translator/Data/DataModel.cs:154-158 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:161-166 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:172-177 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:182-187 | MetadataTranslator/Metadata Translator/Data/DataModel.cs:191-196 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `MetadataTranslator/Metadata Translator/Data/DataModel.cs:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `MetadataTranslator/Metadata Translator/Data/DataModel.cs:178` calls `IsNullOrEmpty`, `AddDisplayFolder` and `MetadataTranslator/Metadata Translator/Data/DataModel.cs:159` 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 (27 lines × 2) AsTrace/ASTrace CS - 2014/ASTrace/ProjectInstaller.cs:16— AsTrace/ASTrace CS - 2014/ASTrace/ProjectInstaller.cs:16-42 | AsTrace/ASTrace CS - 2016/ASTrace/ProjectInstaller.cs:16-42 — before extracting anything, compare `AsTrace/ASTrace CS - 2014/ASTrace/ProjectInstaller.cs` and `AsTrace/ASTrace CS - 2016/ASTrace/ProjectInstaller.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) AlmToolkit/AlmToolkit/Utils.cs:17— AlmToolkit/AlmToolkit/Utils.cs:17-23 | AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:19-25 | AlmToolkit/BismNormalizer/Utils.cs:19-25 — `AlmToolkit/AlmToolkit/Utils.cs` and `AlmToolkit/BismNormalizer/Utils.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 25 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Off the main sequence: Metadata Translator MetadataTranslator/Metadata Translator/Metadata Translator.csproj:1— Metadata Translator: abstractness 0.00, instability 0.00, distance 1.00 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
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 JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — AlmToolkit/AlmToolkit/html-resources/ (karma) — a gap in the analyzer, not something this repository is missing. 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.
async void method: CallRefreshAsync RestApiSample/RestApiSample/Program.cs:18— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Blocking `Thread.Sleep` inside an `async` method RestApiSample/RestApiSample/Program.cs:61— `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.
Rethrow loses stack trace (`throw ex;`) REDACTED:396— `throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
redundant comment AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:503— 8 comments in this file only repeat the code they sit on (lines 503, 603, 610, 619, 626, 644, 671, 688), for example "Set node to skip depending on comparison object status". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/AlmToolkit/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/AlmToolkit/Properties/AssemblyInfo.cs:17— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/AlmToolkit/Properties/AssemblyInfo.cs:22— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.CommandLine/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.CommandLine/Properties/AssemblyInfo.cs:17— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.CommandLine/Properties/AssemblyInfo.cs:22— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.Tests/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.Tests/Properties/AssemblyInfo.cs:17— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.Tests/Properties/AssemblyInfo.cs:22— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer.Tests/Properties/AssemblyInfo.cs:25— "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/Properties/AssemblyInfo.cs:17— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/Properties/AssemblyInfo.cs:22— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:141— 9 comments in this file only repeat the code they sit on (lines 141, 211, 299, 343, 491, 499, 545, 601, 609), for example "there is a datasource in the target with the same name at least". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:71— "direct query check" repeats the code it sits on: 3 of its 3 words (direct, query, check) are already in `if (_amoDatabase.DirectQueryMode == DirectQueryMode.DirectQuery || _amoDatabase.DirectQueryMode == DirectQueryMode.InMem …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/CalculationItem.cs:99— "Check if another calculationItem or column has same name" repeats the code it sits on: 5 of its 5 words (check, calculation, item, column, name) are already in `if (table.CalculationItems.ContainsNameCaseInsensitive(dependency) || table.ColumnsContainsNameCaseInsensitive(dependenc …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs:121— 15 comments in this file only repeat the code they sit on (lines 121, 125, 206, 237, 291, 331, 338, 429, 433, 476, 480, 525, 577, 640, 644), for example "there is a DataSource in the target with the same name at least". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Measure.cs:112— "Check if another measure or column has same name" repeats the code it sits on: 4 of its 4 words (check, measure, column, name) are already in `if (table.Measures.ContainsNameCaseInsensitive(dependency) || table.ColumnsContainsNameCaseInsensitive(dependency))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Table.cs:428— "check if there is an existing relationship with same internal name" repeats the code it sits on: 4 of its 5 words (check, relationship, internal, name) are already in `if (_parentTabularModel.ContainsRelationshipByInternalName(tomRelationshipTarget.Name))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:703— 5 comments in this file only repeat the code they sit on (lines 703, 1212, 1213, 1233, 1234), for example "add back measures". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs:93— "set up splitter distance/widths/visibility" repeats the code it sits on: 4 of its 5 words (set, splitter, distance, widths) are already in `spltSourceTarget.SplitterDistance = Convert.ToInt32(Convert.ToDouble(spltSourceTarget.Width) * 0.5);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridNode.cs:115— "Represents the index of this row in the Grid" repeats the code it sits on: 4 of its 4 words (represents, index, row, grid) are already in `[System.ComponentModel.Description("Represents the index of this row in the Grid. Advanced usage."),`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:196— "Get child Controls in a specified Control." repeats the code it sits on: 4 of its 5 words (get, child, controls, control) are already in `internal static List<Control> GetChildInControl(Control parent)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AlmToolkit/VersionInfo.cs:3— "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:106— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:107— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:184— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:207— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:280— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:314— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:315— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:322— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:323— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:324— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:421— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:437— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:525— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:528— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:529— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:589— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:597— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:605— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:613— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:622— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:623— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:633— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:642— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:643— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AlmToolkit/AlmToolkit/ComparisonForm.cs:653— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:202— `!String.IsNullOrEmpty(_comparisonInfo.ConnectionInfoSource.ServerName) && !String.IsNullOrEmpty(_comparisonInfo.ConnectionInfoSource.Databas…` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:257— `!String.IsNullOrEmpty(_comparisonInfo.ConnectionInfoTarget.ServerName) && !String.IsNullOrEmpty(_comparisonInfo.ConnectionInfoTarget.Databas…` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:471— `!_sourceDatabaseBound && cboSourceServer.Text != ""` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:480— `!_targetDatabaseBound && cboTargetServer.Text != ""` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:555— `(_comparisonInfo.OptionsInfo.OptionMergePerspectives && perspectiveTarget.ContainsOtherPerspectiveSelections(perspectiveSource)) || (!_compa…` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:85— `Properties.Settings.Default.AppendDateToSQLTable && Properties.Settings.Default.PreserveHistory` appears character-identically in 2 files — AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs, AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs. 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 AlmToolkit/AlmToolkit/ComparisonForm.cs:718— `_compareState != CompareState.NotCompared && _comparison != null` appears character-identically in 2 files — AlmToolkit/AlmToolkit/ComparisonForm.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ComparisonControl.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:2786— `_stopProcessing && !_comparisonInfo.OptionsInfo.OptionTransaction` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs:319— `bFirstLoop || _RetryCounter < Properties.Settings.Default.RestartRetries` appears character-identically in 2 files — AsTrace/ASTrace CS - 2014/ASTrace/Service1.cs, AsTrace/ASTrace CS - 2016/ASTrace/Service1.cs. 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 AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:332— `comparisonObject.ChildComparisonObjects != null && comparisonObject.ChildComparisonObjects.Count > 0` appears character-identically in 2 files — AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/TreeGridViewComparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:709— `comparisonObject.ComparisonObjectType == ComparisonObjectType.DataSource && comparisonObject.MergeAction == MergeAction.Create` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:701— `comparisonObject.ComparisonObjectType == ComparisonObjectType.DataSource && comparisonObject.MergeAction == MergeAction.Delete` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:717— `comparisonObject.ComparisonObjectType == ComparisonObjectType.DataSource && comparisonObject.MergeAction == MergeAction.Update` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1073— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Perspective && comparisonObject.MergeAction == MergeAction.Create` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1065— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Perspective && comparisonObject.MergeAction == MergeAction.Delete` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1088— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Perspective && comparisonObject.MergeAction == MergeAction.Update` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1110— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Role && comparisonObject.MergeAction == MergeAction.Create` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1102— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Role && comparisonObject.MergeAction == MergeAction.Delete` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1125— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Role && comparisonObject.MergeAction == MergeAction.Update` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs:1238— `comparisonObject.ComparisonObjectType == ComparisonObjectType.Table && (comparisonObject.MergeAction == MergeAction.Create || comparisonObje…` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/MultidimensionalMetadata/Comparison.cs, AlmToolkit/BismNormalizer/TabularCompare/TabularMetadata/Comparison.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:36— `control is GroupBox || control is Button` appears character-identically in 3 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/Options.cs. 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 AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs:42— `control is GroupBox || control.Name == "btnSwitch"` appears character-identically in 2 files — AlmToolkit/BismNormalizer/TabularCompare/UI/Connections.cs, AlmToolkit/BismNormalizer/TabularCompare/UI/ConnectionsAlmt.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:2760— `e.ObjectName != null && e.ObjectReference != null && e.SessionID == _sessionId` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:2745— `exc is NullReferenceException || exc is InvalidOperationException` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate AlmToolkit/AlmToolkit/html-resources/src/app/grid/grid.component.ts:447— `event.which === 38 || event.which === 40` appears character-identically in 2 files — AlmToolkit/AlmToolkit/html-resources/src/app/grid/grid.component.ts, AlmToolkit/AlmToolkit/html-resources/src/app/tree-control-context-menu/tree-control-context-menu.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.
Orphaned file MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs: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 MetadataTranslator/MTCmd/Program.cs: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 BlogArticleUploads/DAX Rest API REDACTED: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 MetadataTranslator/Metadata Translator/Helpers/ObservableCollectionExtensions.cs: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 MetadataTranslator/Metadata Translator/UI/ImportExportPanel.xaml.cs: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 MetadataTranslator/Metadata Translator/UI/LanguagePanel.xaml.cs: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 MetadataTranslator/Metadata Translator/Properties/AssemblyInfo.cs: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.
Hand-rolled JSON/XML parsing via string slicing REDACTED:392— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing REDACTED:393— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing REDACTED:404— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing REDACTED:405— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Silent fallback default in catch AlmToolkit/BismNormalizer/TabularCompare/DesktopInstances/ProcessExtensions.cs:26— `GetParent` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AlmToolkit/BismNormalizer/TabularCompare/UI/ImpersonationCredentials.cs:158— `ImpersonationCredentials_FormClosing` swallows `System.IO.FileNotFoundException` and sets `valid = true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:138— `GetDpiFactor` swallows every exception and returns `factor` still holding `1.0F` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AlmToolkit/BismNormalizer/TabularCompare/UI/Utils.cs:157— `GetDpiWindowMonitor` swallows every exception and returns `dpi` still holding `0` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Documentation: no build, run or usage example README.md:1— the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example AlmToolkit/AlmToolkit/README.md:1— `AlmToolkit` is an executable (`OutputType WinExe`) and neither `AlmToolkit/AlmToolkit/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: REDACTED. Pair on, review, or document these before any departure.
No ADRs found SetUpAggs/SetUpAggs.csproj:8— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `SetUpAggs/SetUpAggs.csproj` makes this repository a deployable product (line 8).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion AlmToolkit/BismNormalizer/BismNormalizer.csproj:1— `BismNormalizer` overshoots its size bounds (26058 LoC, 133 public types across 7 namespaces). 1 of 16 project(s) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 7 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: MetadataTranslator/Metadata Translator/Translations/TranslatorService.cs, MetadataTranslator/MTCmd/Program.cs, BlogArticleUploads/DAX Rest API REDACTED, MetadataTranslator/Metadata Translator/Helpers/ObservableCollectionExtensions.cs, MetadataTranslator/Metadata Translator/UI/ImportExportPanel.xaml.cs, MetadataTranslator/Metadata Translator/UI/LanguagePanel.xaml.cs, MetadataTranslator/Metadata Translator/Properties/AssemblyInfo.cs (9 orphaned of 102 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; 102 of the 174 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Logging is not universal — Only 2/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:3— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 0/3 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
doc comments repeat the names AlmToolkit/AlmToolkit/ComparisonJSInteraction.cs:373— 0 of 29 documented parameters and 4 of 36 summaries in `AlmToolkit` only repeat the member or parameter name (e.g. "Show or Hide skip nodes" for `ShowHideSkipNodes`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names AsPartitionProcessing/AsPartitionProcessing/TableConfiguration.cs:11— 1 of 42 documented parameters and 1 of 53 summaries in `AsPartitionProcessing` only repeat the member or parameter name (e.g. "ID of the TableConfiguration table." for `TableConfigurationID`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names AlmToolkit/BismNormalizer/TabularCompare/BlobKeyEventArgs.cs:10— 18 of 330 documented parameters and 27 of 683 summaries in `BismNormalizer` only repeat the member or parameter name (e.g. "Gets or sets the authentication kind." for `AuthenticationKind`). 137 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names MetadataTranslator/Metadata Translator/UI/MainWindow.xaml.cs:251— 0 of 57 documented parameters and 8 of 54 summaries in `Metadata Translator` only repeat the member or parameter name (e.g. "DataModel object" for `DataModelProperty`). 58 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:137— 0 of 3 documented parameters and 0 of 3 summaries in `SetUpAggs` only repeat the member or parameter name (e.g. "" for `tableConfig`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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 01a1e459-0bed-7b7f-9259-26c48b432b96 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Name — 1 field(s)
ParsedCommand.FullName REDACTED:128
Issues: 104 · Warnings: 520 · Recommendations: 161 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 12:33 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.