Public report of alexiosus/KOTfor1C, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 04:43 UTC · Survey ID cd_aa274ce318b14d5fae386429014d9ae3
alexiosus/KOTfor1C
Measured 17 November 2026, 04:42 UTC, at code version 0e56421
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 115,122 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 47.5
Findings by how serious they are
14 critical1521 serious116 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 04:42 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
70of 70 dimensions measured by tools.
1635of 1651 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 115,122 lines of product code in 1 project.
alexiosus/KOTfor1C falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 50.0 out of 100 and is rated Weak, and eight of its 14 critical findings are security problems.
Production Readiness, at 47.5, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is replacing each deprecated dependency, worth about 1.1 points. Adopting a logging library would lift Production Readiness itself, worth about 1.9 points.
Four known security holes in the packages the code depends on can be used by attackers. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two form fields can't be read by a screen reader. Updating the vulnerable packages, pinning each tool to an exact version and labelling the form fields would close these risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the two places where passwords are scrambled with a fast general-purpose hash. The two pages that don't say their language need their language set.
The product code is 115,122 lines, about €160,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.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 69%Tests 31%
Rebuild cost: about €160,000 · Estimate
Cost to rebuild
€51,000 to €260,000, for 858 to 2,722 hours of work, about 1.1 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 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 115,122 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED.
Adopt pino (or winston) and log at meaningful points in the services you run.
Raises the score by about 1.9 points · Medium effort · Observability
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 47.5 (Weak). 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.
If you do one thing first · First action
Resolve the 1 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 1.1 points for low effort, because it clears the 1 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 4.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 173,542 lines over the last 90 days, which is about 703,809 lines a year. At that pace, the extra work comes to an estimated 148.9 to 893.5 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 · 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: 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.
229 modules, with 353 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 189 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.
activeYamlParametersProfile uses vanessaLaunchJson, so a change to vanessaLaunchJson can break activeYamlParametersProfile, while a change to activeYamlParametersProfile can't break vanessaLaunchJson.
Position
Below the diagonal: activeYamlParametersProfile uses a module listed above it, which is the healthy direction.
gherkinAnnotations uses gherkinDefinitionKeywords, so a change to gherkinDefinitionKeywords can break gherkinAnnotations, while a change to gherkinAnnotations can't break gherkinDefinitionKeywords.
Position
Below the diagonal: gherkinAnnotations uses a module listed above it, which is the healthy direction.
projectDefinitionIndexService uses projectDefinition, so a change to projectDefinition can break projectDefinitionIndexService, while a change to projectDefinitionIndexService can't break projectDefinition.
Position
Below the diagonal: projectDefinitionIndexService uses a module listed above it, which is the healthy direction.
scenarioPropertiesSession uses scenarioYamlDocument, so a change to scenarioYamlDocument can break scenarioPropertiesSession, while a change to scenarioPropertiesSession can't break scenarioYamlDocument.
Position
Below the diagonal: scenarioPropertiesSession uses a module listed above it, which is the healthy direction.
stepCatalogService uses stepCatalog, so a change to stepCatalog can break stepCatalogService, while a change to stepCatalogService can't break stepCatalog.
Position
Below the diagonal: stepCatalogService uses a module listed above it, which is the healthy direction.
stepLibraryModel uses projectDefinition, so a change to projectDefinition can break stepLibraryModel, while a change to stepLibraryModel can't break projectDefinition.
Position
Below the diagonal: stepLibraryModel uses a module listed above it, which is the healthy direction.
formExplorerPanel uses formExplorerTypes, so a change to formExplorerTypes can break formExplorerPanel, while a change to formExplorerPanel can't break formExplorerTypes.
Position
Below the diagonal: formExplorerPanel uses a module listed above it, which is the healthy direction.
formExplorerPanel uses gherkinDefinitionKeywords, so a change to gherkinDefinitionKeywords can break formExplorerPanel, while a change to formExplorerPanel can't break gherkinDefinitionKeywords.
Position
Below the diagonal: formExplorerPanel uses a module listed above it, which is the healthy direction.
formExplorerPanel uses stepCatalogService, so a change to stepCatalogService can break formExplorerPanel, while a change to formExplorerPanel can't break stepCatalogService.
Position
Below the diagonal: formExplorerPanel uses a module listed above it, which is the healthy direction.
managedInfobaseService uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break managedInfobaseService, while a change to managedInfobaseService can't break projectDefinitionIndexService.
Position
Below the diagonal: managedInfobaseService uses a module listed above it, which is the healthy direction.
projectDefinitionResolver uses projectDefinition, so a change to projectDefinition can break projectDefinitionResolver, while a change to projectDefinitionResolver can't break projectDefinition.
Position
Below the diagonal: projectDefinitionResolver uses a module listed above it, which is the healthy direction.
projectDefinitionResolver uses stepCatalog, so a change to stepCatalog can break projectDefinitionResolver, while a change to projectDefinitionResolver can't break stepCatalog.
Position
Below the diagonal: projectDefinitionResolver uses a module listed above it, which is the healthy direction.
projectDefinitionResolver uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break projectDefinitionResolver, while a change to projectDefinitionResolver can't break projectDefinitionIndexService.
Position
Below the diagonal: projectDefinitionResolver uses a module listed above it, which is the healthy direction.
projectDefinitionResolver uses scenarioCatalog, so a change to scenarioCatalog can break projectDefinitionResolver, while a change to projectDefinitionResolver can't break scenarioCatalog.
Position
Below the diagonal: projectDefinitionResolver uses a module listed above it, which is the healthy direction.
projectDefinitionResolver uses stepCatalogService, so a change to stepCatalogService can break projectDefinitionResolver, while a change to projectDefinitionResolver can't break stepCatalogService.
Position
Below the diagonal: projectDefinitionResolver uses a module listed above it, which is the healthy direction.
scenarioFilesService uses stepLibraryModel, so a change to stepLibraryModel can break scenarioFilesService, while a change to scenarioFilesService can't break stepLibraryModel.
Position
Below the diagonal: scenarioFilesService uses a module listed above it, which is the healthy direction.
scenarioRelationshipService uses projectDefinition, so a change to projectDefinition can break scenarioRelationshipService, while a change to scenarioRelationshipService can't break projectDefinition.
Position
Below the diagonal: scenarioRelationshipService uses a module listed above it, which is the healthy direction.
scenarioRelationshipService uses scenarioCatalog, so a change to scenarioCatalog can break scenarioRelationshipService, while a change to scenarioRelationshipService can't break scenarioCatalog.
Position
Below the diagonal: scenarioRelationshipService uses a module listed above it, which is the healthy direction.
standaloneFeatureService uses projectLibraryStore, so a change to projectLibraryStore can break standaloneFeatureService, while a change to standaloneFeatureService can't break projectLibraryStore.
Position
Below the diagonal: standaloneFeatureService uses a module listed above it, which is the healthy direction.
standaloneFeatureService uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break standaloneFeatureService, while a change to standaloneFeatureService can't break projectDefinitionIndexService.
Position
Below the diagonal: standaloneFeatureService uses a module listed above it, which is the healthy direction.
completionProvider uses formExplorerTypes, so a change to formExplorerTypes can break completionProvider, while a change to completionProvider can't break formExplorerTypes.
Position
Below the diagonal: completionProvider uses a module listed above it, which is the healthy direction.
completionProvider uses gherkinDefinitionKeywords, so a change to gherkinDefinitionKeywords can break completionProvider, while a change to completionProvider can't break gherkinDefinitionKeywords.
Position
Below the diagonal: completionProvider uses a module listed above it, which is the healthy direction.
completionProvider uses projectDefinition, so a change to projectDefinition can break completionProvider, while a change to completionProvider can't break projectDefinition.
Position
Below the diagonal: completionProvider uses a module listed above it, which is the healthy direction.
completionProvider uses gherkinAnnotations, so a change to gherkinAnnotations can break completionProvider, while a change to completionProvider can't break gherkinAnnotations.
Position
Below the diagonal: completionProvider uses a module listed above it, which is the healthy direction.
completionProvider uses projectDefinitionResolver, so a change to projectDefinitionResolver can break completionProvider, while a change to completionProvider can't break projectDefinitionResolver.
Position
Below the diagonal: completionProvider uses a module listed above it, which is the healthy direction.
hoverProvider uses projectDefinition, so a change to projectDefinition can break hoverProvider, while a change to hoverProvider can't break projectDefinition.
Position
Below the diagonal: hoverProvider uses a module listed above it, which is the healthy direction.
hoverProvider uses projectDefinitionResolver, so a change to projectDefinitionResolver can break hoverProvider, while a change to hoverProvider can't break projectDefinitionResolver.
Position
Below the diagonal: hoverProvider uses a module listed above it, which is the healthy direction.
infobaseSidebarProvider uses vanessaInfobaseClients, so a change to vanessaInfobaseClients can break infobaseSidebarProvider, while a change to infobaseSidebarProvider can't break vanessaInfobaseClients.
Position
Below the diagonal: infobaseSidebarProvider uses a module listed above it, which is the healthy direction.
infobaseSidebarProvider uses managedInfobaseService, so a change to managedInfobaseService can break infobaseSidebarProvider, while a change to infobaseSidebarProvider can't break managedInfobaseService.
Position
Below the diagonal: infobaseSidebarProvider uses a module listed above it, which is the healthy direction.
projectDefinitionReferences uses projectDefinition, so a change to projectDefinition can break projectDefinitionReferences, while a change to projectDefinitionReferences can't break projectDefinition.
Position
Below the diagonal: projectDefinitionReferences uses a module listed above it, which is the healthy direction.
projectDefinitionReferences uses projectDefinitionResolver, so a change to projectDefinitionResolver can break projectDefinitionReferences, while a change to projectDefinitionReferences can't break projectDefinitionResolver.
Position
Below the diagonal: projectDefinitionReferences uses a module listed above it, which is the healthy direction.
scenarioPropertiesAttachments uses stepLibraryModel, so a change to stepLibraryModel can break scenarioPropertiesAttachments, while a change to scenarioPropertiesAttachments can't break stepLibraryModel.
Position
Below the diagonal: scenarioPropertiesAttachments uses a module listed above it, which is the healthy direction.
scenarioPropertiesAttachments uses scenarioFilesService, so a change to scenarioFilesService can break scenarioPropertiesAttachments, while a change to scenarioPropertiesAttachments can't break scenarioFilesService.
Position
Below the diagonal: scenarioPropertiesAttachments uses a module listed above it, which is the healthy direction.
scenarioPropertiesLibrarySupport uses featurePropertiesController, so a change to featurePropertiesController can break scenarioPropertiesLibrarySupport, while a change to scenarioPropertiesLibrarySupport can't break featurePropertiesController.
Position
Below the diagonal: scenarioPropertiesLibrarySupport uses a module listed above it, which is the healthy direction.
scenarioPropertiesLibrarySupport uses standaloneFeatureService, so a change to standaloneFeatureService can break scenarioPropertiesLibrarySupport, while a change to scenarioPropertiesLibrarySupport can't break standaloneFeatureService.
Position
Below the diagonal: scenarioPropertiesLibrarySupport uses a module listed above it, which is the healthy direction.
stepLibraryActions uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break stepLibraryActions, while a change to stepLibraryActions can't break projectDefinitionIndexService.
Position
Below the diagonal: stepLibraryActions uses a module listed above it, which is the healthy direction.
stepLibraryActions uses stepLibraryModel, so a change to stepLibraryModel can break stepLibraryActions, while a change to stepLibraryActions can't break stepLibraryModel.
Position
Below the diagonal: stepLibraryActions uses a module listed above it, which is the healthy direction.
stepLibraryActions uses projectDefinitionResolver, so a change to projectDefinitionResolver can break stepLibraryActions, while a change to stepLibraryActions can't break projectDefinitionResolver.
Position
Below the diagonal: stepLibraryActions uses a module listed above it, which is the healthy direction.
stepLibrarySnapshotService uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break stepLibrarySnapshotService, while a change to stepLibrarySnapshotService can't break projectDefinitionIndexService.
Position
Below the diagonal: stepLibrarySnapshotService uses a module listed above it, which is the healthy direction.
stepLibrarySnapshotService uses stepLibraryModel, so a change to stepLibraryModel can break stepLibrarySnapshotService, while a change to stepLibrarySnapshotService can't break stepLibraryModel.
Position
Below the diagonal: stepLibrarySnapshotService uses a module listed above it, which is the healthy direction.
stepLibrarySnapshotService uses projectDefinitionResolver, so a change to projectDefinitionResolver can break stepLibrarySnapshotService, while a change to stepLibrarySnapshotService can't break projectDefinitionResolver.
Position
Below the diagonal: stepLibrarySnapshotService uses a module listed above it, which is the healthy direction.
stepLibrarySnapshotService uses scenarioFilesService, so a change to scenarioFilesService can break stepLibrarySnapshotService, while a change to stepLibrarySnapshotService can't break scenarioFilesService.
Position
Below the diagonal: stepLibrarySnapshotService uses a module listed above it, which is the healthy direction.
stepLibrarySnapshotService uses standaloneFeatureService, so a change to standaloneFeatureService can break stepLibrarySnapshotService, while a change to stepLibrarySnapshotService can't break standaloneFeatureService.
Position
Below the diagonal: stepLibrarySnapshotService uses a module listed above it, which is the healthy direction.
projectDefinitionDeletion uses projectDefinition, so a change to projectDefinition can break projectDefinitionDeletion, while a change to projectDefinitionDeletion can't break projectDefinition.
Position
Below the diagonal: projectDefinitionDeletion uses a module listed above it, which is the healthy direction.
projectDefinitionDeletion uses types, so a change to types can break projectDefinitionDeletion, while a change to projectDefinitionDeletion can't break types.
Position
Below the diagonal: projectDefinitionDeletion uses a module listed above it, which is the healthy direction.
projectDefinitionDeletion uses projectDefinitionResolver, so a change to projectDefinitionResolver can break projectDefinitionDeletion, while a change to projectDefinitionDeletion can't break projectDefinitionResolver.
Position
Below the diagonal: projectDefinitionDeletion uses a module listed above it, which is the healthy direction.
projectDefinitionDeletion uses projectDefinitionReferences, so a change to projectDefinitionReferences can break projectDefinitionDeletion, while a change to projectDefinitionDeletion can't break projectDefinitionReferences.
Position
Below the diagonal: projectDefinitionDeletion uses a module listed above it, which is the healthy direction.
scenarioPropertiesPanel uses featurePropertiesController, so a change to featurePropertiesController can break scenarioPropertiesPanel, while a change to scenarioPropertiesPanel can't break featurePropertiesController.
Position
Below the diagonal: scenarioPropertiesPanel uses a module listed above it, which is the healthy direction.
scenarioPropertiesPanel uses scenarioPropertiesSession, so a change to scenarioPropertiesSession can break scenarioPropertiesPanel, while a change to scenarioPropertiesPanel can't break scenarioPropertiesSession.
Position
Below the diagonal: scenarioPropertiesPanel uses a module listed above it, which is the healthy direction.
scenarioPropertiesPanel uses scenarioFilesService, so a change to scenarioFilesService can break scenarioPropertiesPanel, while a change to scenarioPropertiesPanel can't break scenarioFilesService.
Position
Below the diagonal: scenarioPropertiesPanel uses a module listed above it, which is the healthy direction.
scenarioPropertiesPanel uses scenarioPropertiesAttachments, so a change to scenarioPropertiesAttachments can break scenarioPropertiesPanel, while a change to scenarioPropertiesPanel can't break scenarioPropertiesAttachments.
Position
Below the diagonal: scenarioPropertiesPanel uses a module listed above it, which is the healthy direction.
scenarioPropertiesPanel uses scenarioPropertiesLibrarySupport, so a change to scenarioPropertiesLibrarySupport can break scenarioPropertiesPanel, while a change to scenarioPropertiesPanel can't break scenarioPropertiesLibrarySupport.
Position
Below the diagonal: scenarioPropertiesPanel uses a module listed above it, which is the healthy direction.
stepLibraryPanel uses standaloneFeatureController, so a change to standaloneFeatureController can break stepLibraryPanel, while a change to stepLibraryPanel can't break standaloneFeatureController.
Position
Below the diagonal: stepLibraryPanel uses a module listed above it, which is the healthy direction.
stepLibraryPanel uses stepLibraryModel, so a change to stepLibraryModel can break stepLibraryPanel, while a change to stepLibraryPanel can't break stepLibraryModel.
Position
Below the diagonal: stepLibraryPanel uses a module listed above it, which is the healthy direction.
stepLibraryPanel uses scenarioFilesService, so a change to scenarioFilesService can break stepLibraryPanel, while a change to stepLibraryPanel can't break scenarioFilesService.
Position
Below the diagonal: stepLibraryPanel uses a module listed above it, which is the healthy direction.
stepLibraryPanel uses stepLibraryActions, so a change to stepLibraryActions can break stepLibraryPanel, while a change to stepLibraryPanel can't break stepLibraryActions.
Position
Below the diagonal: stepLibraryPanel uses a module listed above it, which is the healthy direction.
stepLibraryPanel uses stepLibrarySnapshotService, so a change to stepLibrarySnapshotService can break stepLibraryPanel, while a change to stepLibraryPanel can't break stepLibrarySnapshotService.
Position
Below the diagonal: stepLibraryPanel uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses standaloneFeatureController, so a change to standaloneFeatureController can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break standaloneFeatureController.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses stepLibraryModel, so a change to stepLibraryModel can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break stepLibraryModel.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses scenarioFilesService, so a change to scenarioFilesService can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break scenarioFilesService.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses scenarioRelationshipService, so a change to scenarioRelationshipService can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break scenarioRelationshipService.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses stepLibraryActions, so a change to stepLibraryActions can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break stepLibraryActions.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
stepLibrarySidebarProvider uses stepLibrarySnapshotService, so a change to stepLibrarySnapshotService can break stepLibrarySidebarProvider, while a change to stepLibrarySidebarProvider can't break stepLibrarySnapshotService.
Position
Below the diagonal: stepLibrarySidebarProvider uses a module listed above it, which is the healthy direction.
phaseSwitcher uses projectLibraryStore, so a change to projectLibraryStore can break phaseSwitcher, while a change to phaseSwitcher can't break projectLibraryStore.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses standaloneFeatureController, so a change to standaloneFeatureController can break phaseSwitcher, while a change to phaseSwitcher can't break standaloneFeatureController.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses vanessaControlSession, so a change to vanessaControlSession can break phaseSwitcher, while a change to phaseSwitcher can't break vanessaControlSession.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses vanessaLaunchJson, so a change to vanessaLaunchJson can break phaseSwitcher, while a change to phaseSwitcher can't break vanessaLaunchJson.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses activeYamlParametersProfile, so a change to activeYamlParametersProfile can break phaseSwitcher, while a change to phaseSwitcher can't break activeYamlParametersProfile.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses scenarioCatalog, so a change to scenarioCatalog can break phaseSwitcher, while a change to phaseSwitcher can't break scenarioCatalog.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses stepLibraryModel, so a change to stepLibraryModel can break phaseSwitcher, while a change to phaseSwitcher can't break stepLibraryModel.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses scenarioRelationshipService, so a change to scenarioRelationshipService can break phaseSwitcher, while a change to phaseSwitcher can't break scenarioRelationshipService.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses standaloneFeatureService, so a change to standaloneFeatureService can break phaseSwitcher, while a change to phaseSwitcher can't break standaloneFeatureService.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
phaseSwitcher uses projectDefinitionDeletion, so a change to projectDefinitionDeletion can break phaseSwitcher, while a change to phaseSwitcher can't break projectDefinitionDeletion.
Position
Below the diagonal: phaseSwitcher uses a module listed above it, which is the healthy direction.
src uses featurePropertiesController, so a change to featurePropertiesController can break src, while a change to src can't break featurePropertiesController.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses gherkinDefinitionKeywords, so a change to gherkinDefinitionKeywords can break src, while a change to src can't break gherkinDefinitionKeywords.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in src uses a type in projectDefinition. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
src uses activeYamlParametersProfile, so a change to activeYamlParametersProfile can break src, while a change to src can't break activeYamlParametersProfile.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses projectDefinitionIndexService, so a change to projectDefinitionIndexService can break src, while a change to src can't break projectDefinitionIndexService.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses scenarioPropertiesSession, so a change to scenarioPropertiesSession can break src, while a change to src can't break scenarioPropertiesSession.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses projectDefinitionResolver, so a change to projectDefinitionResolver can break src, while a change to src can't break projectDefinitionResolver.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses scenarioRelationshipService, so a change to scenarioRelationshipService can break src, while a change to src can't break scenarioRelationshipService.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses projectDefinitionReferences, so a change to projectDefinitionReferences can break src, while a change to src can't break projectDefinitionReferences.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses scenarioPropertiesLibrarySupport, so a change to scenarioPropertiesLibrarySupport can break src, while a change to src can't break scenarioPropertiesLibrarySupport.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
src uses projectDefinitionDeletion, so a change to projectDefinitionDeletion can break src, while a change to src can't break projectDefinitionDeletion.
Position
Below the diagonal: src uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
61
High / Critical
A03:2025 — Software Supply Chain Failures
11
High / Critical
A02:2025 — Security Misconfiguration
1
Medium
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 — 14
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 — 1521
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 — 116
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.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 — 70 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1635 of 1651 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.
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 JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the node:test run in the repository root produced no per-test report ([PhaseSwitcherProvider:_handleRunAssembleScriptTypeScript] Error: Error: SPPR preflight failed with 1 error(s). See KOT output.). This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in the repository root was NOT MEASURED: the node:test run in the repository root produced no per-test report ([PhaseSwitcherProvider:_handleRunAssembleScriptTypeScript] Error: Error: SPPR preflight failed with 1 error(s). See KOT output.). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 317 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a REDACTED `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `REDACTED`.
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.
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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D26 Project Cohesion — 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. `(repository root)` (115110 LoC, 932 module-visible types across 5 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/compilerArtifacts.ts`, `src/compilerYamlBlockEditor.ts`, `REDACTED`, `REDACTED`, `src/phaseSwitcher.ts`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 15 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
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.
PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 383 further occurrence(s) are not listed individually; the score already reflects all 423.
R2 Cyclomatic Complexity — 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. 662 further occurrence(s) are not listed individually; the score already reflects all 702.
R3 Large Files — 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. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
X10 Duplicated predicate — 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. 79 further occurrence(s) are not listed individually; the score already reflects all 119.
X3 Exception handling — 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. 56 further occurrence(s) are not listed individually; the score already reflects all 96.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
526 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was VanessaControlSession.run at 162. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DriveHoverProvider.getYamlFieldHoverDescription at 47 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/gherkinTableEditing.ts (gherkinTableEditing.registerGherkinTableColumnDeletion::onChange at 16), src/stepLibraryActions.ts (StepLibraryActionService.editProcessSteps at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 450 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 23 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with VanessaControlSession.run (cyclomatic 162), phaseSwitcher.window.addEventListener("message") (cyclomatic 112), (anonymous) (cyclomatic 112). — 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 23 together lifts Cyclomatic Complexity from 2.0 to about 3.2/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.
+ 540 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 46 bodies over 60 down to 60 or less in Cognitive Complexity — start with ScenarioDiagnosticsProvider.validateDocument (cognitive 203), VanessaControlSession.run (cognitive 174), (anonymous) (cognitive 172). — 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 46 together lifts Cognitive Complexity from 2.0 to about 3.2/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 Classes7.6 / 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 43 FunctionTooLong finding(s) in God Classes — start with REDACTED (7), phaseSwitcher.js (4), stepLibrary.js (4). — One of this dimension's main actionable groups (43 warning-level).
Resolve the 34 FileTooLong finding(s) in God Classes — start with phaseSwitcher.ts, REDACTED, REDACTED. — One of this dimension's main actionable groups (34 warning-level).
Resolve the 17 MethodTooLong finding(s) in God Classes — start with formExplorerPanel.ts (2), infobaseManagerPanel.ts (2), REDACTED (2). — One of this dimension's main actionable groups (17 warning-level).
Detailed fixes: d3_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 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 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 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
3 skipped (3 with a documented reason), 0 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2708 tests.
Fixed-sleep synchronisation: the first wizard prompt opens before slow scenario discovery completestest/scenarioCreator.test.ts:284
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with scenarioCreator.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
6 outdated direct production npm dependency(ies) of 7 graded, 0 pinning defect(s), across 1 REDACTED (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: eslintREDACTED:3164
Outdated (npm): uuidREDACTED:3174
Outdated (npm): @cucumber/gherkin · ×5
What to do
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 41 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 41 package(s) this repository's committed lockfile installs for a consumer — its 7 production, optional and peer dependency(ies), across 1 product REDACTED manifest(s), and everything those install in turn. Its 11 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 56 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, phaseSwitcher.ts, phaseSwitcher.js. — One of this dimension's main actionable groups (56 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with stepCatalogService.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 96296 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
64 finding(s): 0 critical, 2 high, 54 medium, 8 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 16 file(s) — `media/formExplorer.js`, `media/phaseSwitcher.js`, `media/stepLibrary.js`, `src/compilerArtifacts.ts` (lines 219–220), `src/compilerYamlBlockEditor.ts` (line 31), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 27 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (27 warning-level).
Resolve the 26 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (7), REDACTED (2). — One of this dimension's main actionable groups (26 warning-level).
No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 261 of the 310 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with REDACTED (2), REDACTED, phaseSwitcher.js. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with phaseSwitcher.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (REDACTED 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 REDACTED (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.
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d37_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels7.5 / 10Strong✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — media/kotWorkspace.js:242
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — media/phaseSwitcher.js:1183
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — media/yamlParameters.js:943
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The lang value isn't a well-formed BCP-47 language tag (use e.g. "en" or "en-US", not "english"/"en_US"), so assistive tech may apply the wrong language. Use a valid language subtag. (×2) — media/phaseSwitcher.html:2, media/yamlParameters.html:3
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — media/phaseSwitcher.html:2, media/yamlParameters.html:3
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". — media/stepLibrary.js:460
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`#cancelAssembleBtn` sets color: #ffffff on background-color: #ff7f50 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — media/phaseSwitcher.css:752
`.kot-search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — media/kotSidebar.css:58
`.kot-search-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — media/kotSidebar.css:67
`.scenario-search-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — media/phaseSwitcher.css:1637
`.search-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — media/stepLibrary.css:124
`.search-field input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — media/stepLibrary.css:130
`.codicon-sync.codicon-modifier-spin` moves (`animation: codicon-spin 1.5s steps(30) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/codicon.css:39
`.section-toggle-icon` moves (`transition: transform 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — media/formExplorer.css:1235, media/infobaseManager.css:870
`.section-card-body` moves (`transition: max-height 0.22s ease, opacity 0.18s ease, padding 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — media/formExplorer.css:1252, media/infobaseManager.css:825
`.infobase-actions` moves (`transition: max-width 0.12s ease, opacity 0.12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/infobaseSidebar.css:121
`.kot-tree-row:hover .kot-tree-label.is-overflowing .kot-scroll-content` moves (`transition: transform var(--kot-overflow-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/kotSidebar.css:151
`.kot-pane-resizer::before` moves (`transition: background-color 80ms ease, inset 80ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/kotWebviewSplit.css:2
`.kot-text-overflow:hover > .kot-text-track` moves (`transition: transform var(--kot-text-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/kotWebviewText.css:13
`.phase-toggle-icon` moves (`transition: transform 0.15s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/phaseSwitcher.css:214
`.phase-tests-list` moves (`transition: max-height 0.2s ease,
opacity 0.16s ease,
padding-top 0.18s ease,
padding-bottom 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/phaseSwitcher.css:271
`.scenario-resource-tree` moves (`transition: max-height 0.2s ease,
opacity 0.16s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/phaseSwitcher.css:1811
`label.checkbox-item .kot-row-actions` moves (`transition: max-width 0.12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/phaseSwitcher.css:2016
`.properties-scroll-title.is-overflowing:hover > span` moves (`transition: transform var(--properties-scroll-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/scenarioProperties.css:117
`.pane-resizer::before` moves (`transition: background-color 80ms ease, inset 80ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/stepLibrary.css:209
`.details-scroll-label.is-overflowing:hover .kot-scroll-content` moves (`transition: transform var(--kot-overflow-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — media/stepLibrary.css:910
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`InfobaseSidebarOperations` declares 19 required operations: `createInfobase`, `openEnterprise`, `openDesigner`, `openFormExplorer`, `copy`, `recreate`, `updateConfiguration`, `updateFromSources`, `updateFromTemplate`, `edit`, `addToLauncher`, `removeFromLauncher`, `reveal`, `logs`, `exportDt`, `importDt`, `restoreFromTemplate`, `exportCf`, `importCf`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/infobaseSidebarProvider.ts:39
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`buildAdapterStateHeaderTextRussian` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — REDACTED:2299
`buildAdapterStateHeaderTextEnglish` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — REDACTED:2303
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×3) — REDACTED:1970, REDACTED:1983, REDACTED:2745
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates6.5 / 10Adequate✓ 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.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 301 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 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:3155
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — 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 · 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.
`fs.existsSync` in `openMxlWithFileWorkshop` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:170
`fs.existsSync` in `resolveConfiguredConfigurationSourceDirectory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:277
`fs.existsSync` in `callback to dialogPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/infobaseManager.ts:1508
`fs.statSync` in `callback to dialogPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/infobaseManager.ts:1508
`fs.existsSync` in `resolveConfiguredOneCDesignerExePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/infobaseManager.ts:1670, src/infobaseManager.ts:1675
`fs.existsSync` in `resolveConfiguredOneCClientExePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/infobaseManager.ts:1696
`fs.existsSync` in `openInfobaseInEnterprise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/infobaseManager.ts:3133
`fs.existsSync` in `openInfobaseInDesigner` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/infobaseManager.ts:3182, src/infobaseManager.ts:3187
`fs.existsSync` in `pickManagedInfobasePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/infobaseManager.ts:3312
`fs.existsSync` in `pickTargetInfobasePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:544
`fs.existsSync` in `validateInput` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:586
`fs.existsSync` in `callback to configuredPlatforms.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/oneCPlatform.ts:487
`fs.existsSync` in `pollVanessaRuntimeLogMonitor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:2678
`fs.existsSync` in `buildFavoriteEntryFromScenarioUri` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:4452
`fs.existsSync` in `synchronizeFavoriteEntriesWithCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:4662
`fs.existsSync` in `changeNestedScenarioCodeForActiveEditor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:5036
`fs.existsSync` in `runStandaloneFeature` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/phaseSwitcher.ts:5664, src/phaseSwitcher.ts:5681
`fs.existsSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — src/phaseSwitcher.ts:6006, src/phaseSwitcher.ts:6045, src/phaseSwitcher.ts:6056
`fs.statSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:6006
`fs.readdirSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:6007
`fs.existsSync` in `openVanessaStandaloneDebug` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/phaseSwitcher.ts:6858, src/phaseSwitcher.ts:6894
`fs.existsSync` in `openCompilerBuildReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:8326
`fs.existsSync` in `callback to window.withProgress` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — src/phaseSwitcher.ts:8576, src/phaseSwitcher.ts:8829, src/phaseSwitcher.ts:8842
`fs.existsSync` in `updateScenarioBuildArtifacts` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:10302
`fs.existsSync` in `createCombinedScenarioJsonArtifact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:10382
`fs.existsSync` in `ensureCombinedScenarioJsonArtifacts` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:10428
`fs.existsSync` in `ensureUniqueVanessaRuntimePathsForArtifacts` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:10720
`fs.existsSync` in `child.on("close")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:11069
`fs.existsSync` in `callback to dialogDefaultPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:11188
`fs.statSync` in `callback to dialogDefaultPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:11192
`fs.existsSync` in `canReuseInfobaseReference` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:11479
`fs.existsSync` in `promptVanessaInfobasePreparationPlan` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/phaseSwitcher.ts:11558
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.5 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
18 duplicated blocks under the repository root have copies in at least two of the sibling directories media, src, tools — 16 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — media/formExplorer.js:2046
src/stepLibraryPanel.ts:604 · src/stepLibrarySidebarProvider.ts:718 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/stepLibraryPanel.ts:604
src/exportScenarioCommand.ts:34 · src/userStepCommands.ts:40 — the two spans are one implementation copied and then locally edited — 991 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/exportScenarioCommand.ts:34
media/stepLibrary.js:854 · media/stepLibrarySidebar.js:64 — the two spans are one implementation copied and then locally edited — 774 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — media/stepLibrary.js:854
src/formExplorerBridgeGenerator.ts:141 · REDACTED:7101 — the two spans are one implementation copied and then locally edited — 729 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/formExplorerBridgeGenerator.ts:141
media/phaseSwitcher.js:2440 · media/stepLibrary.js:681 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — media/phaseSwitcher.js:2440
src/completionProvider.ts:1941 · REDACTED:655 — the two spans are one implementation copied and then locally edited — 494 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/completionProvider.ts:1941
REDACTED:317 · src/testReviewAiReport.ts:135 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:317
src/exportScenarioMetadataCodeLens.ts:82 · src/scenarioCategoryCodeLens.ts:49 — the two spans are one implementation copied and then locally edited — 403 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/exportScenarioMetadataCodeLens.ts:82
src/infobaseManager.ts:2145 · src/infobaseManager.ts:2213 — 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. — src/infobaseManager.ts:2145
src/phaseSwitcher.ts:6480 · src/phaseSwitcher.ts:6716 — 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. — src/phaseSwitcher.ts:6480
src/formExplorerBuilder.ts:186 · src/infobaseManager.ts:1710 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/formExplorerBuilder.ts:186
media/formExplorer.js:2046 · src/formExplorerStepSuggestions.ts:396 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — media/formExplorer.js:2046
REDACTED:405 · src/infobaseManager.ts:1567 — the two spans are one implementation copied and then locally edited — 301 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:405
src/kotMetadataDescription.ts:9 · src/scenarioDiagnostics.ts:256 — the two spans are one implementation copied and then locally edited — 384 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/kotMetadataDescription.ts:9
src/stepCatalogClient.ts:193 · src/stepCatalogClient.ts:278 — the two spans are one implementation copied and then locally edited — 329 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/stepCatalogClient.ts:193
src/formExplorerLiveSnapshot.ts:58 · src/formExplorerPanel.ts:1017 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/formExplorerLiveSnapshot.ts:58
src/phaseSwitcher.ts:4967 · src/phaseSwitcher.ts:5177 — 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. — src/phaseSwitcher.ts:4967
REDACTED:6156 · REDACTED:6211 · REDACTED:6267 · REDACTED:6320 — 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. — REDACTED:6156
REDACTED:1372 · src/testReviewAiReport.ts:439 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:1372
REDACTED:1807 · src/testReviewAiReport.ts:981 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1807
src/scenarioDiagnostics.ts:1832 · src/scenarioDiagnostics.ts:2011 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/scenarioDiagnostics.ts:1832
src/scenarioYamlMutations.ts:144 · src/scenarioYamlMutations.ts:215 — the two spans are one implementation copied and then locally edited — 206 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/scenarioYamlMutations.ts:144
src/testReviewAiReport.ts:763 · src/testReviewAiReport.ts:858 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/testReviewAiReport.ts:763
src/exportScenarioCreator.ts:85 · src/userStepCreator.ts:179 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/exportScenarioCreator.ts:85
REDACTED:1459 · REDACTED:1586 — 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. — REDACTED:1459
src/exportScenarioMetadata.ts:16 · src/scenarioCategory.ts:16 — the two spans are one implementation copied and then locally edited — 222 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/exportScenarioMetadata.ts:16
src/phaseSwitcher.ts:2168 · REDACTED:123 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/phaseSwitcher.ts:2168
src/stepLibraryPanel.ts:524 · src/stepLibrarySidebarProvider.ts:387 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/stepLibraryPanel.ts:524
REDACTED:118 · REDACTED:277 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:118
REDACTED:1502 · src/testReviewAiReport.ts:626 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:1502
REDACTED:5914 · REDACTED:5951 — 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. — REDACTED:5914
REDACTED:157 · src/testReviewAiReport.ts:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:157
media/formExplorer.js:1778 · src/formExplorerStepSuggestions.ts:646 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — media/formExplorer.js:1778
REDACTED:1290 · src/testReviewAiReport.ts:318 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1290
media/standaloneFeatures.js:218 · media/stepLibraryFeatureProtocol.js:109 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — media/standaloneFeatures.js:218
src/infobaseManager.ts:2439 · src/infobaseManager.ts:2595 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/infobaseManager.ts:2439
REDACTED:383 · REDACTED:452 — the two spans are one implementation copied and then locally edited — 194 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:383
REDACTED:326 · REDACTED:374 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:326
REDACTED:1370 · REDACTED:1460 · REDACTED:1524 — 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. — REDACTED:1370
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 148 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/vanessaControlSession.ts:369
validateDocument has cyclomatic complexity 111 and cognitive complexity 187; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioDiagnostics.ts:1540
handleConvertCallableScenario has cyclomatic complexity 108 and cognitive complexity 185; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioCallableCommands.ts:83
(anonymous) has cyclomatic complexity 91 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:7424
(anonymous) has cyclomatic complexity 90 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/phaseSwitcher.js:3201
renderDetails has cyclomatic complexity 90 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/infobaseManager.js:597
perform has cyclomatic complexity 82 and cognitive complexity 141; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioPropertiesSession.ts:387
buildScenarioViewState has cyclomatic complexity 81 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/phaseSwitcher.js:1056
(anonymous) has cyclomatic complexity 79 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:8499
(anonymous) has cyclomatic complexity 78 and cognitive complexity 117; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/stepLibrarySidebar.js:1008
parseVanessaControlReply has cyclomatic complexity 77 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/vanessaControlProtocol.ts:111
writeCompilerBuildReport has cyclomatic complexity 67 and cognitive complexity 119; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/compilerBuildReport.ts:131
renderStaticFrame has cyclomatic complexity 61 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/formExplorer.js:698
(anonymous) has cyclomatic complexity 59 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1278
handleScenarioContextMenu has cyclomatic complexity 58 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/phaseSwitcher.js:2843
(anonymous) has cyclomatic complexity 57 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioPropertiesActions.ts:277
(anonymous) has cyclomatic complexity 56 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/stepLibrary.js:2136
planFeatureEditorEdit has cyclomatic complexity 56 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/featureEditorActions.ts:184
(anonymous) has cyclomatic complexity 56 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/yamlParameters.js:4
handleMessage has cyclomatic complexity 54 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/infobaseManagerPanel.ts:418
makeRow has cyclomatic complexity 53 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/stepLibrarySidebar.js:286
applyYamlMapField has cyclomatic complexity 52 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioPropertiesModel.ts:366
renameScenario has cyclomatic complexity 51 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:5936
records has cyclomatic complexity 50 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/scenarioProperties.js:436
collectCompilerBuildPreflightIssues has cyclomatic complexity 50 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/compilerBuildPreflight.ts:107
updateScenarioBuildArtifacts has cyclomatic complexity 50 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:10172
changeScenarioIdentityField has cyclomatic complexity 50 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:5360
load has cyclomatic complexity 49 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioPropertiesSession.ts:131
(anonymous) has cyclomatic complexity 49 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/vanessaInfobaseClients.ts:289
handleGenerateFormExplorerExtensionCore has cyclomatic complexity 47 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:6621
load has cyclomatic complexity 46 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/projectLibraryStore.ts:343
provideInlayHints has cyclomatic complexity 46 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioHeaderInlayHintsProvider.ts:36
performAction has cyclomatic complexity 46 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/standaloneFeatureController.ts:191
readSchema has cyclomatic complexity 46 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/vanessaControlFormTools.ts:50
provideCodeActions has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioDiagnostics.ts:855
runScenarioInVanessaBuiltIn has cyclomatic complexity 45 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/phaseSwitcher.ts:12050
(anonymous) has cyclomatic complexity 45 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — media/yamlParameters.js:1451
buildTokens has cyclomatic complexity 44 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/scenarioSyntaxHighlightProvider.ts:185
parseStandaloneFeatureMessage has cyclomatic complexity 44 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/standaloneFeatureController.ts:69
loadProjectScenarioMetadata has cyclomatic complexity 43 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/projectLibraryMetadata.ts:152
Do you agree with this assessment?
R3 · Large Files2.5 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
src/phaseSwitcher.ts has 12379 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/phaseSwitcher.ts:1
REDACTED has 6136 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 4094 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 3665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
media/phaseSwitcher.js has 3547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/phaseSwitcher.js:1
src/infobaseManager.ts has 3021 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/infobaseManager.ts:1
media/formExplorer.js has 2667 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/formExplorer.js:1
src/completionProvider.ts has 2626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/completionProvider.ts:1
src/scenarioCreator.ts has 2385 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scenarioCreator.ts:1
media/stepLibrary.js has 2225 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/stepLibrary.js:1
REDACTED has 2026 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 1878 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
src/scenarioDiagnostics.ts has 1861 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scenarioDiagnostics.ts:1
src/formExplorerPanel.ts has 1798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/formExplorerPanel.ts:1
REDACTED has 1464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
media/yamlParameters.js has 1460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/yamlParameters.js:1
REDACTED has 1189 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
media/stepLibrarySidebar.js has 1149 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/stepLibrarySidebar.js:1
src/testReviewAiReport.ts has 1128 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/testReviewAiReport.ts:1
src/stepLibraryPanel.ts has 1011 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/stepLibraryPanel.ts:1
src/formExplorerStepSuggestions.ts has 1006 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/formExplorerStepSuggestions.ts:1
src/scenarioFilesService.ts has 988 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scenarioFilesService.ts:1
src/projectDefinitionIndexService.ts has 955 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/projectDefinitionIndexService.ts:1
src/infobaseManagerPanel.ts has 953 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/infobaseManagerPanel.ts:1
media/infobaseManager.js has 951 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/infobaseManager.js:1
src/stepLibrarySidebarProvider.ts has 916 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/stepLibrarySidebarProvider.ts:1
src/projectLibraryStore.ts has 908 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/projectLibraryStore.ts:1
src/bslStepSourceParser.ts has 894 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/bslStepSourceParser.ts:1
src/standaloneFeatureService.ts has 802 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/standaloneFeatureService.ts:1
REDACTED has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
src/scenarioPropertiesPanel.ts has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scenarioPropertiesPanel.ts:1
media/scenarioProperties.js has 745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/scenarioProperties.js:1
src/vanessaControlSession.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/vanessaControlSession.ts:1
media/standaloneFeatures.js has 721 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/standaloneFeatures.js:1
src/scenarioYamlDocument.ts has 693 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scenarioYamlDocument.ts:1
src/phaseSwitcherMetadata.ts has 606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/phaseSwitcherMetadata.ts:1
src/oneCPlatform.ts has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/oneCPlatform.ts:1
src/stepCatalogService.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/stepCatalogService.ts:1
src/vanessaLaunchJson.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/vanessaLaunchJson.ts:1
media/stepLibraryProtocol.js has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — media/stepLibraryProtocol.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.9 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — media/standaloneFeatures.js:1, media/scenarioProperties.js:1, media/featureProperties.js:1
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
The root package declares the lint script `lint` (`eslint src test tools/step-catalog --max-warnings 0`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner). — REDACTED:3144
Do you agree with this assessment?
R7 · Dead Code7.4 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 99 application, 4 tooling and 300 test entry point(s) detected in this repo. Gate removals on `npm run compile` — an undetected custom entry would make these reachable.
no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×9) — media/formExplorer.js, media/yamlParameters.js, media/scenarioProperties.js, …
Nothing imports this binding — it is safe to review for removal. — src/formExplorerPaths.ts:52
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×16) — src/formExplorerBuilder.ts:102, REDACTED:530, REDACTED:1085, …
Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. (×6) — REDACTED:228, REDACTED:312, REDACTED:322, …
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — src/phaseSwitcher.ts:478
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — REDACTED:3161
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — REDACTED:391
`left.password === right.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. — REDACTED:493
`actual.password === expected.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. — src/vanessaInfobaseClients.ts:64
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `REDACTED:493`.
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.
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.
Do you agree with this assessment?
X13 · Undrained process stream6.1 / 10Adequate✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
`spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `killer.stdout`, while `killer.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`killer.stdout.on('data', …)`, or `killer.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — src/phaseSwitcher.ts:6326
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.0 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`fingerprintCompilerBuildInputs` is exported, takes a document from its caller (line 47) and hands it to `canonicalJson`, which calls itself at line 32 (`canonicalJson`) with a piece of `value` (and at line 34) — and nowhere in `canonicalJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/compilerBuildManifest.ts:32
`validateSetting` is exported and takes `value: unknown` from its caller, and it calls itself at line 36 (`validateSetting`) with a piece of `value` (and at line 41) — and nowhere in `validateSetting` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validateSetting` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:36
`setJsonValueAtPointer` is exported, takes a document from its caller (line 238) and hands it to `cloneJsonValue`, which calls itself at line 131 (`cloneJsonValue`) with a piece of `value` (and at line 135) — and nowhere in `cloneJsonValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cloneJsonValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/vanessaLaunchJson.ts:131
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped7.1 / 10Strong✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`attrs.join(' ')` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — media/formExplorer.js:2502
`t('Project setup')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — media/kotWorkspace.js:58, media/kotWorkspace.js:175
`section.id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:61
`section.id` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:65
`t('Open VS Code Settings')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:106
`t('This setting applies to the whole window. Choose Workspace or User scope.')` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:159
`t('Back to start')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:174
`t('Where shall we start?')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:177
`t('Inspect the project')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:181
`t('Prepare the editor')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:190
`t('Build profiles currently apply to one project window. Open this folder separately to continue setup.')` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:195
`t('Connect execution?')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:197
`t('Where to find tools')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — media/kotWorkspace.js:199, media/kotWorkspace.js:272
`t('Review changes')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:201
`t('Ready to start')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:205
`t('Project settings are applied. Preparing 1C and Vanessa…')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:225
`t('Vanessa connected.')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:226
`t('The editor is ready. Vanessa preparation was not completed; execution is still disconnected.')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:227
`t(label)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:253
`t('Check environment')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:257
`t('Step catalog version')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:263
`t('Files to create')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/kotWorkspace.js:266
`html.trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/phaseSwitcher.js:1249
`desiredButton.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/phaseSwitcher.js:1398
`txt` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — media/phaseSwitcher.js:1858, media/phaseSwitcher.js:1867
`window.__loc?.phaseSwitcherDisabled||'Test Manager is disabled in settings.'` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — media/phaseSwitcher.js:3364
`typed&¶m.valueKind?`data-value-kind="${escapeHtml(param.valueKind)}" data-original-key="${escapeHtml(param.key)}"…` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — media/yamlParameters.js:513
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
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. (×33) — REDACTED:102, src/compilerBuildErrorLocation.ts:42, src/compilerBuildRuntime.ts:81, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×7) — REDACTED:1961, REDACTED:2057, REDACTED:522, …
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.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.8 `!` null assertions per 1k TypeScript source lines — 288 assertion(s) across the 103692 source line(s) of the 269 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/phaseSwitcher.ts (32), REDACTED (11), src/gherkinAnnotations.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 19 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 — 54 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — Repository kind not determined
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 1 exposed TypeScript types.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in the repository root ran and not one test passed ([PhaseSwitcherProvider:_handleRunAssembleScriptTypeScript] Error: Error: SPPR preflight failed with 1 error(s). See KOT output.), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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 — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label media/phaseSwitcher.js:1183— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label media/yamlParameters.js:943— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
Malformed <html lang> value "${localeHtmlLang}" media/phaseSwitcher.html:2— The lang value isn't a well-formed BCP-47 language tag (use e.g. "en" or "en-US", not "english"/"en_US"), so assistive tech may apply the wrong language. Use a valid language subtag.
Malformed <html lang> value "${localeHtmlLang}" media/yamlParameters.html:3— The lang value isn't a well-formed BCP-47 language tag (use e.g. "en" or "en-US", not "english"/"en_US"), so assistive tech may apply the wrong language. Use a valid language subtag.
S1 · Web-Security Posture· Password hashing without a KDF · ×2
Password hashing without a KDF REDACTED:493— `left.password === right.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account.
Password hashing without a KDF src/vanessaInfobaseClients.ts:64— `actual.password === expected.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account.
AC2 · Forms & labels· <label> that labels no control · ×1
<label> that labels no control media/kotWorkspace.js:242— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> media/stepLibrary.js:460— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Hotspot: REDACTED REDACTED:838— REDACTED changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 333 in extension.activate at line 838. 9 of those changes were fix/bug commits, and the other 31 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/phaseSwitcher.ts src/phaseSwitcher.ts:7251— src/phaseSwitcher.ts changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 104 in PhaseSwitcherProvider.resolveWebviewView at line 7251. 12 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/phaseSwitcher.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/phaseSwitcher.js media/phaseSwitcher.js:3201— media/phaseSwitcher.js changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 112 in phaseSwitcher.window.addEventListener("message") at line 3201. 4 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/phaseSwitcher.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/completionProvider.ts src/completionProvider.ts:717— src/completionProvider.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in DriveCompletionProvider.provideCompletionItems at line 717. 5 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/completionProvider.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioDiagnostics.ts src/scenarioDiagnostics.ts:1540— src/scenarioDiagnostics.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 108 in ScenarioDiagnosticsProvider.validateDocument at line 1540. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioDiagnostics.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/stepLibrary.js media/stepLibrary.js:2136— media/stepLibrary.js changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in stepLibrary.window.addEventListener("message") at line 2136. 6 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/stepLibrary.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/stepLibraryPanel.ts src/stepLibraryPanel.ts:408— src/stepLibraryPanel.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in StepLibraryPanel.handleMessage at line 408. 5 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepLibraryPanel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/vanessaControlSession.ts src/vanessaControlSession.ts:351— src/vanessaControlSession.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 162 in VanessaControlSession.run at line 351. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/vanessaControlSession.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/stepLibrarySidebar.js media/stepLibrarySidebar.js:1008— media/stepLibrarySidebar.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in stepLibrarySidebar.window.addEventListener("message") at line 1008. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/stepLibrarySidebar.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/infobaseManagerPanel.ts src/infobaseManagerPanel.ts:418— src/infobaseManagerPanel.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in InfobaseManagerPanel.handleMessage at line 418. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/infobaseManagerPanel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/stepLibraryFeatureProtocol.js media/stepLibraryFeatureProtocol.js:21— media/stepLibraryFeatureProtocol.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 122 in stepLibraryFeatureProtocol.createController at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/stepLibraryFeatureProtocol.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1235— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in YamlParametersManager.openYamlParametersPanel at line 1235. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1194— REDACTED changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in DriveHoverProvider.provideHover at line 1194. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/stepLibraryProtocol.js media/stepLibraryProtocol.js:378— media/stepLibraryProtocol.js changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in stepLibraryProtocol.buildCategoryTree at line 378. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/stepLibraryProtocol.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioPropertiesActions.ts src/scenarioPropertiesActions.ts:96— src/scenarioPropertiesActions.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in scenarioPropertiesActions.createScenarioPropertiesActions at line 96. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioPropertiesActions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioPropertiesSession.ts src/scenarioPropertiesSession.ts:387— src/scenarioPropertiesSession.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in ScenarioPropertiesSession.perform at line 387. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioPropertiesSession.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/stepLibraryModel.ts src/stepLibraryModel.ts:305— src/stepLibraryModel.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in stepLibraryModel.buildStepLibrarySnapshot at line 305. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepLibraryModel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioCatalog.ts src/scenarioCatalog.ts:159— src/scenarioCatalog.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in scenarioCatalog.areScenarioCatalogEntriesEqual at line 159. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioCatalog.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: media/infobaseManager.js media/infobaseManager.js:597— media/infobaseManager.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 96 in infobaseManager.renderDetails at line 597. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- media/infobaseManager.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/stepLibrarySidebarProvider.ts src/stepLibrarySidebarProvider.ts:299— src/stepLibrarySidebarProvider.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in StepLibrarySidebarProvider.handleMessage at line 299. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepLibrarySidebarProvider.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1109— REDACTED changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in commandHandlers.clearAndFillNestedScenarios at line 1109. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioCreator.ts src/scenarioCreator.ts:1728— src/scenarioCreator.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in scenarioCreator.handleManageEtalonBases at line 1728. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioCreator.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/stepLibrarySidebarModel.ts src/stepLibrarySidebarModel.ts:247— src/stepLibrarySidebarModel.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in StepLibrarySidebarIndex.constructor at line 247. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepLibrarySidebarModel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/scenarioYamlDocument.ts src/scenarioYamlDocument.ts:158— src/scenarioYamlDocument.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in scenarioYamlDocument.buildStructuralShadow at line 158. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/scenarioYamlDocument.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/stepCatalogTemplateXml.ts src/stepCatalogTemplateXml.ts:378— src/stepCatalogTemplateXml.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in stepCatalogTemplateXml.writeCatalogPublication at line 378. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepCatalogTemplateXml.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: extension.activate REDACTED:838— FunctionTooLong — activate runs 2064 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1964 over it, 20.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.buildAdapterSupportTextEnglish REDACTED:3421— FunctionTooLong — buildAdapterSupportTextEnglish runs 798 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 698 over it, 7.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.buildAdapterSupportTextRussian REDACTED:2307— FunctionTooLong — buildAdapterSupportTextRussian runs 786 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 686 over it, 7.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: standaloneFeatures.create media/standaloneFeatures.js:6— FunctionTooLong — create runs 617 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 517 over it, 6.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: phaseSwitcher.window.addEventListener("message") media/phaseSwitcher.js:3201— FunctionTooLong — window.addEventListener("message") runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vanessaControlConnection.registerVanessaControl src/vanessaControlConnection.ts:15— FunctionTooLong — registerVanessaControl runs 274 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.generateExtensionProjectFiles REDACTED:5351— FunctionTooLong — generateExtensionProjectFiles runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.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.
FunctionTooLong: scenarioPropertiesActions.createScenarioPropertiesActions src/scenarioPropertiesActions.ts:96— FunctionTooLong — createScenarioPropertiesActions runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorer.bindStaticEvents media/formExplorer.js:290— FunctionTooLong — bindStaticEvents runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: infobaseManager.collectManagedInfobases src/infobaseManager.ts:1121— FunctionTooLong — collectManagedInfobases runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.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.
FunctionTooLong: formExplorerExtensionGenerator.buildSettingsFormLayoutXml REDACTED:1760— FunctionTooLong — buildSettingsFormLayoutXml runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.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.
FunctionTooLong: configurationDiffAiReport.finalizeTestingFocusAreaRussian REDACTED:823— FunctionTooLong — finalizeTestingFocusAreaRussian runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: phaseSwitcher.renderPhaseTree media/phaseSwitcher.js:1683— FunctionTooLong — renderPhaseTree runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: exportScenarioCommand.createExportScenarioCommand src/exportScenarioCommand.ts:83— FunctionTooLong — createExportScenarioCommand runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: phaseSwitcher.buildScenarioViewState media/phaseSwitcher.js:1056— FunctionTooLong — buildScenarioViewState runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.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.
FunctionTooLong: exportScenarioParser.parseExportScenarios src/exportScenarioParser.ts:317— FunctionTooLong — parseExportScenarios runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nativeProjectCatalogSettings.registerNativeProjectCatalogSettings src/nativeProjectCatalogSettings.ts:86— FunctionTooLong — registerNativeProjectCatalogSettings runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: stepLibrary.createDefinitionRow media/stepLibrary.js:1157— FunctionTooLong — createDefinitionRow runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: stepLibrarySidebar.makeRow media/stepLibrarySidebar.js:286— FunctionTooLong — makeRow runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.buildCommandModuleTextEnglish REDACTED:4768— FunctionTooLong — buildCommandModuleTextEnglish 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.
FunctionTooLong: stepLibrarySidebar.window.addEventListener("message") media/stepLibrarySidebar.js:1008— FunctionTooLong — window.addEventListener("message") runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.handleStartFormExplorerInfobase REDACTED:7104— FunctionTooLong — handleStartFormExplorerInfobase runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: stepLibraryFeatureProtocol.createController media/stepLibraryFeatureProtocol.js:21— FunctionTooLong — createController runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerExtensionGenerator.buildCommandModuleTextRussian REDACTED:4579— FunctionTooLong — buildCommandModuleTextRussian runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: formExplorerBridgeGenerator.handleStartFormExplorerBridge src/formExplorerBridgeGenerator.ts:146— FunctionTooLong — handleStartFormExplorerBridge runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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.
Sync-over-async blocking REDACTED:170— `fs.existsSync` in `openMxlWithFileWorkshop` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:277— `fs.existsSync` in `resolveConfiguredConfigurationSourceDirectory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:1508— `fs.existsSync` in `callback to dialogPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:1508— `fs.statSync` in `callback to dialogPathCandidates.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:1670— `fs.existsSync` in `resolveConfiguredOneCDesignerExePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:1675— `fs.existsSync` in `resolveConfiguredOneCDesignerExePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:1696— `fs.existsSync` in `resolveConfiguredOneCClientExePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:3133— `fs.existsSync` in `openInfobaseInEnterprise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:3182— `fs.existsSync` in `openInfobaseInDesigner` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:3187— `fs.existsSync` in `openInfobaseInDesigner` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/infobaseManager.ts:3312— `fs.existsSync` in `pickManagedInfobasePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:544— `fs.existsSync` in `pickTargetInfobasePath` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:586— `fs.existsSync` in `validateInput` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/oneCPlatform.ts:487— `fs.existsSync` in `callback to configuredPlatforms.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:2678— `fs.existsSync` in `pollVanessaRuntimeLogMonitor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:4452— `fs.existsSync` in `buildFavoriteEntryFromScenarioUri` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:4662— `fs.existsSync` in `synchronizeFavoriteEntriesWithCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:5036— `fs.existsSync` in `changeNestedScenarioCodeForActiveEditor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:5664— `fs.existsSync` in `runStandaloneFeature` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:5681— `fs.existsSync` in `runStandaloneFeature` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:6006— `fs.existsSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:6006— `fs.statSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:6007— `fs.readdirSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:6045— `fs.existsSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/phaseSwitcher.ts:6056— `fs.existsSync` in `renameScenario` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
FileTooLong: src/phaseSwitcher.ts src/phaseSwitcher.ts— FileTooLong — 9782 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9282 over it, 19.56× 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 — 5357 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4857 over it, 10.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 3341 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2841 over it, 6.68× 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 — 2854 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: activate (838-3675). The bar is 500 significant lines; this is 2354 over it, 5.71× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: media/phaseSwitcher.js media/phaseSwitcher.js— FileTooLong — 2830 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 1330 over it, 1.89× 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: src/infobaseManager.ts src/infobaseManager.ts— FileTooLong — 2391 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1891 over it, 4.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: media/formExplorer.js media/formExplorer.js— FileTooLong — 2126 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 626 over it, 1.42× 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: src/completionProvider.ts src/completionProvider.ts— FileTooLong — 2090 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1590 over it, 4.18× 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: media/stepLibrary.js media/stepLibrary.js— FileTooLong — 1830 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 330 over it, 1.22× 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: src/scenarioCreator.ts src/scenarioCreator.ts— FileTooLong — 1825 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1325 over it, 3.65× 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 — 1568 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1068 over it, 3.14× 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: src/formExplorerPanel.ts src/formExplorerPanel.ts— FileTooLong — 1529 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: DEFAULT_ADAPTER_SETTINGS_FILE_NAME (99-1975). The bar is 500 significant lines; this is 1029 over it, 3.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1514 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: YamlParametersManager (100-2212). The bar is 500 significant lines; this is 1014 over it, 3.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/scenarioDiagnostics.ts src/scenarioDiagnostics.ts— FileTooLong — 1469 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 969 over it, 2.94× 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: media/yamlParameters.js media/yamlParameters.js— FileTooLong — 1201 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 701 over it, 2.40× 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 — 1029 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 529 over it, 2.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: REDACTED REDACTED— FileTooLong — 951 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: DriveHoverProvider (69-1361). The bar is 500 significant lines; this is 451 over it, 1.90× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: media/stepLibrarySidebar.js media/stepLibrarySidebar.js— FileTooLong — 927 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 427 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/stepLibraryPanel.ts src/stepLibraryPanel.ts— FileTooLong — 873 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: StepLibraryPanel (147-1046). The bar is 500 significant lines; this is 373 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/infobaseManagerPanel.ts src/infobaseManagerPanel.ts— FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: InfobaseManagerPanel (83-1023). The bar is 500 significant lines; this is 337 over it, 1.67× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/formExplorerStepSuggestions.ts src/formExplorerStepSuggestions.ts— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 293 over it, 1.59× 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: src/scenarioFilesService.ts src/scenarioFilesService.ts— FileTooLong — 782 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 282 over it, 1.56× 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: src/stepLibrarySidebarProvider.ts src/stepLibrarySidebarProvider.ts— FileTooLong — 759 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: StepLibrarySidebarProvider (161-958). The bar is 500 significant lines; this is 259 over it, 1.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/projectDefinitionIndexService.ts src/projectDefinitionIndexService.ts— FileTooLong — 753 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: ProjectDefinitionIndexService (274-1034). The bar is 500 significant lines; this is 253 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/projectLibraryStore.ts src/projectLibraryStore.ts— FileTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: ProjectLibraryStore (221-914). The bar is 500 significant lines; this is 239 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Swallowed exception (empty catch) REDACTED:102— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/compilerBuildErrorLocation.ts:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/compilerBuildRuntime.ts:81— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/compilerBuildRuntime.ts:142— 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:1356— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/exportScenarioCommand.ts:226— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/exportScenarioMetadataCodeLens.ts:101— 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:338— 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:386— 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:1132— 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:2267— 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:2972— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/featurePropertiesController.ts:85— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerBuilder.ts:231— 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:5798— 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:5849— 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:6110— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerLiveSnapshot.ts:68— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerLiveSnapshot.ts:85— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:299— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:306— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:949— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:958— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:1025— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/formExplorerPanel.ts:1042— 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.
+ 8 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×30
Untrusted text written into markup unescaped media/formExplorer.js:2502— `attrs.join(' ')` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
Untrusted text written into markup unescaped media/kotWorkspace.js:58— `t('Project setup')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:61— `section.id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:65— `section.id` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:106— `t('Open VS Code Settings')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:159— `t('This setting applies to the whole window. Choose Workspace or User scope.')` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:174— `t('Back to start')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:175— `t('Project setup')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:177— `t('Where shall we start?')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:181— `t('Inspect the project')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:190— `t('Prepare the editor')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:195— `t('Build profiles currently apply to one project window. Open this folder separately to continue setup.')` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:197— `t('Connect execution?')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:199— `t('Where to find tools')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:201— `t('Review changes')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:205— `t('Ready to start')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:225— `t('Project settings are applied. Preparing 1C and Vanessa…')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:226— `t('Vanessa connected.')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:227— `t('The editor is ready. Vanessa preparation was not completed; execution is still disconnected.')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:253— `t(label)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:257— `t('Check environment')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:263— `t('Step catalog version')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:266— `t('Files to create')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/kotWorkspace.js:272— `t('Where to find tools')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped media/phaseSwitcher.js:1249— `html.trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
MethodTooLong: FormExplorerPanel.getWebviewHtml src/formExplorerPanel.ts:1600— MethodTooLong — getWebviewHtml runs 363 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 263 over it, 3.63× 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: InfobaseManagerPanel.getWebviewHtml src/infobaseManagerPanel.ts:660— MethodTooLong — getWebviewHtml runs 348 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 248 over it, 3.48× 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: YamlParametersManager.openYamlParametersPanel REDACTED:1235— MethodTooLong — openYamlParametersPanel runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.62× 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: StepLibraryPanel.getWebviewHtml src/stepLibraryPanel.ts:795— MethodTooLong — getWebviewHtml runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InfobaseManagerPanel.handleMessage src/infobaseManagerPanel.ts:418— MethodTooLong — handleMessage runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: VanessaControlSession.run src/vanessaControlSession.ts:351— MethodTooLong — run runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: YamlParametersManager.getWebviewContent REDACTED:1959— MethodTooLong — getWebviewContent runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: StepLibrarySidebarIndex.constructor src/stepLibrarySidebarModel.ts:247— MethodTooLong — constructor runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.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: ScenarioPropertiesSession.load src/scenarioPropertiesSession.ts:131— MethodTooLong — load runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: StepLibraryPanel.handleMessage src/stepLibraryPanel.ts:408— MethodTooLong — handleMessage runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: ScenarioSyntaxHighlightProvider.buildTokens src/scenarioSyntaxHighlightProvider.ts:185— MethodTooLong — buildTokens runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: StepLibrarySidebarProvider.handleMessage src/stepLibrarySidebarProvider.ts:299— MethodTooLong — handleMessage runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: FormExplorerPanel.refreshSnapshot src/formExplorerPanel.ts:1430— MethodTooLong — refreshSnapshot runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScenarioPropertiesSession.perform src/scenarioPropertiesSession.ts:387— MethodTooLong — perform 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.
MethodTooLong: ProjectLibraryStore.load src/projectLibraryStore.ts:343— MethodTooLong — load runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: ScenarioHeaderInlayHintsProvider.provideInlayHints src/scenarioHeaderInlayHintsProvider.ts:36— MethodTooLong — provideInlayHints runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: StandaloneFeatureController.performAction src/standaloneFeatureController.ts:191— MethodTooLong — performAction runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×16
Animation without a prefers-reduced-motion guard media/codicon.css:39— `.codicon-sync.codicon-modifier-spin` moves (`animation: codicon-spin 1.5s steps(30) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/formExplorer.css:1235— `.section-toggle-icon` moves (`transition: transform 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/formExplorer.css:1252— `.section-card-body` moves (`transition: max-height 0.22s ease, opacity 0.18s ease, padding 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/infobaseManager.css:825— `.section-card-body` moves (`transition: max-height 0.22s ease, opacity 0.18s ease, padding 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/infobaseManager.css:870— `.section-toggle-icon` moves (`transition: transform 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/infobaseSidebar.css:121— `.infobase-actions` moves (`transition: max-width 0.12s ease, opacity 0.12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/kotSidebar.css:151— `.kot-tree-row:hover .kot-tree-label.is-overflowing .kot-scroll-content` moves (`transition: transform var(--kot-overflow-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/kotWebviewSplit.css:2— `.kot-pane-resizer::before` moves (`transition: background-color 80ms ease, inset 80ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/kotWebviewText.css:13— `.kot-text-overflow:hover > .kot-text-track` moves (`transition: transform var(--kot-text-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/phaseSwitcher.css:214— `.phase-toggle-icon` moves (`transition: transform 0.15s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/phaseSwitcher.css:271— `.phase-tests-list` moves (`transition: max-height 0.2s ease,
opacity 0.16s ease,
padding-top 0.18s ease,
padding-bottom 0.18s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/phaseSwitcher.css:1811— `.scenario-resource-tree` moves (`transition: max-height 0.2s ease,
opacity 0.16s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/phaseSwitcher.css:2016— `label.checkbox-item .kot-row-actions` moves (`transition: max-width 0.12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/scenarioProperties.css:117— `.properties-scroll-title.is-overflowing:hover > span` moves (`transition: transform var(--properties-scroll-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/stepLibrary.css:209— `.pane-resizer::before` moves (`transition: background-color 80ms ease, inset 80ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard media/stepLibrary.css:910— `.details-scroll-label.is-overflowing:hover .kot-scroll-content` moves (`transition: transform var(--kot-overflow-duration, 1.2s) ease-in-out 350ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
TooManyMethods: PhaseSwitcherProvider src/phaseSwitcher.ts:466— TooManyMethods — 392 methods. The bar is 30 methods; this is 362 over it, 13.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: YamlParametersManager REDACTED:100— TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DriveCompletionProvider src/completionProvider.ts:568— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FormExplorerPanel src/formExplorerPanel.ts:105— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StandaloneFeatureService src/standaloneFeatureService.ts:110— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DriveHoverProvider REDACTED:69— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: ScenarioFilesService src/scenarioFilesService.ts:170— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProjectDefinitionIndexService src/projectDefinitionIndexService.ts:274— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProjectLibraryStore src/projectLibraryStore.ts:221— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StepLibrarySidebarProvider src/stepLibrarySidebarProvider.ts:161— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: YamlParametersManager REDACTED:100— ClassTooLong — 1440 significant lines (blank, comment-only and punctuation-only lines excluded), 79 methods. The bar is 400 significant lines; this is 1040 over it, 3.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DriveHoverProvider REDACTED:69— ClassTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 497 over it, 2.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InfobaseManagerPanel src/infobaseManagerPanel.ts:83— ClassTooLong — 769 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 369 over it, 1.92× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StepLibraryPanel src/stepLibraryPanel.ts:147— ClassTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 350 over it, 1.88× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StepLibrarySidebarProvider src/stepLibrarySidebarProvider.ts:161— ClassTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 231 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ProjectLibraryStore src/projectLibraryStore.ts:221— ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 169 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StandaloneFeatureService src/standaloneFeatureService.ts:110— ClassTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 162 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ProjectDefinitionIndexService src/projectDefinitionIndexService.ts:274— ClassTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 156 over it, 1.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: VanessaControlSession src/vanessaControlSession.ts:71— ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 144 over it, 1.36× 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.
Swallowed exception (caught, then discarded) REDACTED:1961— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:2057— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:522— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:259— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:395— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:464— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) src/kotWorkspacePanel.ts:109— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×5
Focus outline removed in CSS without a :focus replacement media/kotSidebar.css:58— `.kot-search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement media/kotSidebar.css:67— `.kot-search-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement media/phaseSwitcher.css:1637— `.scenario-search-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement media/stepLibrary.css:124— `.search-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement media/stepLibrary.css:130— `.search-field input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Change coupling: REDACTED ↔ scenarioCreator.ts REDACTED:1— `REDACTED` and `src/scenarioCreator.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6b4468c2` build: enforce warning-free quality checks; `ccfdcf3c` new features and fixes; `ba615b55` new features — run `git show` on any of them.
Change coupling: REDACTED ↔ scenarioDiagnostics.ts REDACTED:1— `REDACTED` and `src/scenarioDiagnostics.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `11e81d8a` refactor: share versioned step catalogs; `13b72015` perf: keep step diagnostics responsive; `7b18f788` fix: surface ambiguous scenario definitions — run `git show` on any of them.
Change coupling: REDACTED ↔ scenarioDiagnostics.ts REDACTED:1— `REDACTED` and `src/scenarioDiagnostics.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7b18f788` fix: surface ambiguous scenario definitions; `a800c625` new features; `ccfdcf3c` new features and fixes — run `git show` on any of them.
Change coupling: phaseSwitcher.js ↔ scenarioCreator.ts media/phaseSwitcher.js:1— `media/phaseSwitcher.js` and `src/scenarioCreator.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b5671763` fix web bases detection, add context menu items, test header setup; `ccfdcf3c` new features and fixes; `ba615b55` new features — run `git show` on any of them.
IC1 · Incompleteness & stubs· Both branches are identical · ×3
Both branches are identical — the condition decides nothing REDACTED:1970— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing REDACTED:1983— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing REDACTED:2745— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
R4 · Test Coverage· No test reaches this file · ×3
No test reaches this file media/standaloneFeatures.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file media/scenarioProperties.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file media/featureProperties.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap src/compilerBuildManifest.ts:32— `fingerprintCompilerBuildInputs` is exported, takes a document from its caller (line 47) and hands it to `canonicalJson`, which calls itself at line 32 (`canonicalJson`) with a piece of `value` (and at line 34) — and nowhere in `canonicalJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap REDACTED:36— `validateSetting` is exported and takes `value: unknown` from its caller, and it calls itself at line 36 (`validateSetting`) with a piece of `value` (and at line 41) — and nowhere in `validateSetting` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validateSetting` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/vanessaLaunchJson.ts:131— `setJsonValueAtPointer` is exported, takes a document from its caller (line 238) and hands it to `cloneJsonValue`, which calls itself at line 131 (`cloneJsonValue`) with a piece of `value` (and at line 135) — and nowhere in `cloneJsonValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cloneJsonValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark media/phaseSwitcher.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark media/yamlParameters.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
(anonymous) (cyclomatic 56) media/stepLibrary.js:2136— (anonymous) 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.
(anonymous) (cyclomatic 56) media/yamlParameters.js:4— (anonymous) has cyclomatic complexity 56 (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.
(anonymous) (cyclomatic 20) media/kotWorkspace.js:275— (anonymous) has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 20) media/yamlParameters.js:1188— (anonymous) 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.
stepLibraryFeatureProtocol.createController::actions (cyclomatic 17) media/stepLibraryFeatureProtocol.js:73— stepLibraryFeatureProtocol.createController::actions 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. This shape REPEATS in the file: one other method here (stepLibraryFeatureProtocol.createController::send) 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.
stepLibraryFeatureProtocol.createController::send (cyclomatic 16) media/stepLibraryFeatureProtocol.js:40— stepLibraryFeatureProtocol.createController::send has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (stepLibraryFeatureProtocol.createController::actions) 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.
scenarioPropertiesActions.createScenarioPropertiesActions::catalogChoice (cognitive 31) src/scenarioPropertiesActions.ts:128— scenarioPropertiesActions.createScenarioPropertiesActions::catalogChoice has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 8 (9 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (scenarioPropertiesActions.createScenarioPropertiesActions::openReference) 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.
scenarioPropertiesActions.createScenarioPropertiesActions::openReference (cognitive 16) src/scenarioPropertiesActions.ts:233— scenarioPropertiesActions.createScenarioPropertiesActions::openReference has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 5, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (scenarioPropertiesActions.createScenarioPropertiesActions::catalogChoice) 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.
vanessaControlCommands.registerVanessaControlCommands::update (cognitive 26) src/vanessaControlCommands.ts:42— vanessaControlCommands.registerVanessaControlCommands::update has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (9 pts), ternaries 2 (4 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. This shape REPEATS in the file: one other method here (vanessaControlCommands.registerVanessaControlCommands::run) 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.
vanessaControlCommands.registerVanessaControlCommands::run (cognitive 18) src/vanessaControlCommands.ts:125— vanessaControlCommands.registerVanessaControlCommands::run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (vanessaControlCommands.registerVanessaControlCommands::update) 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.
stepLibraryFeatureProtocol.createController::send (cognitive 18) media/stepLibraryFeatureProtocol.js:40— stepLibraryFeatureProtocol.createController::send has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (stepLibraryFeatureProtocol.createController::actions) 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.
stepLibraryFeatureProtocol.createController::actions (cognitive 18) media/stepLibraryFeatureProtocol.js:73— stepLibraryFeatureProtocol.createController::actions has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 5, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (stepLibraryFeatureProtocol.createController::send) 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.
Hollow method — returns a constant without doing the work REDACTED:2299— `buildAdapterStateHeaderTextRussian` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work REDACTED:2303— `buildAdapterStateHeaderTextEnglish` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Duplicated block (49 lines × 2 locations) src/formExplorerLiveSnapshot.ts:58— src/formExplorerLiveSnapshot.ts:58 · src/formExplorerPanel.ts:1017 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (49 lines × 2 locations) src/phaseSwitcher.ts:4967— src/phaseSwitcher.ts:4967 · src/phaseSwitcher.ts:5177 — 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 (36 lines × 2 locations) src/phaseSwitcher.ts:2168— src/phaseSwitcher.ts:2168 · REDACTED:123 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (36 lines × 2 locations) src/stepLibraryPanel.ts:524— src/stepLibraryPanel.ts:524 · src/stepLibrarySidebarProvider.ts:387 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) REDACTED:1502— REDACTED:1502 · src/testReviewAiReport.ts:626 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (34 lines × 2 locations) REDACTED:5914— REDACTED:5914 · REDACTED:5951 — 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 (31 lines × 2 locations) media/formExplorer.js:1778— media/formExplorer.js:1778 · src/formExplorerStepSuggestions.ts:646 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (31 lines × 2 locations) REDACTED:1290— REDACTED:1290 · src/testReviewAiReport.ts:318 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×2
Duplicated block with local edits (30 matched lines × 2 locations) media/standaloneFeatures.js:218— media/standaloneFeatures.js:218 · media/stepLibraryFeatureProtocol.js:109 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (30 matched lines × 2 locations) REDACTED:383— REDACTED:383 · REDACTED:452 — the two spans are one implementation copied and then locally edited — 194 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Low contrast colour pair in CSS (2.5:1) media/phaseSwitcher.css:752— `#cancelAssembleBtn` sets color: #ffffff on background-color: #ff7f50 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
VanessaControlSession.run (cyclomatic 162) src/vanessaControlSession.ts:351— VanessaControlSession.run has cyclomatic complexity 162 (threshold 15). Of this number, 24 points are the body's own statements and 138 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phaseSwitcher.window.addEventListener("message") (cyclomatic 112) media/phaseSwitcher.js:3201— phaseSwitcher.window.addEventListener("message") has cyclomatic complexity 112 (threshold 15). Of this number, 93 points are the body's own statements and 19 belong to 8 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 112) media/phaseSwitcher.js:3201— (anonymous) has cyclomatic complexity 112 (threshold 15). Of this number, 90 points are the body's own statements and 22 belong to 9 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScenarioDiagnosticsProvider.validateDocument (cyclomatic 108) src/scenarioDiagnostics.ts:1540— ScenarioDiagnosticsProvider.validateDocument has cyclomatic complexity 108 (threshold 15). Of this number, 106 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
scenarioCallableCommands.handleConvertCallableScenario (cyclomatic 106) src/scenarioCallableCommands.ts:83— scenarioCallableCommands.handleConvertCallableScenario has cyclomatic complexity 106 (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 (scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls) 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.
PhaseSwitcherProvider.resolveWebviewView (cyclomatic 104) src/phaseSwitcher.ts:7251— PhaseSwitcherProvider.resolveWebviewView has cyclomatic complexity 104 (threshold 15). Most of this is not in the body itself: 8 of the 104 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 7424, 7431, 7638). 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.
PhaseSwitcherProvider._handleRunAssembleScriptTypeScript (cyclomatic 101) src/phaseSwitcher.ts:8443— PhaseSwitcherProvider._handleRunAssembleScriptTypeScript has cyclomatic complexity 101 (threshold 15). Most of this is not in the body itself: 7 of the 101 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 8499, a function literal at line 8870, a function literal at line 8900, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
infobaseManager.renderDetails (cyclomatic 96) media/infobaseManager.js:597— infobaseManager.renderDetails has cyclomatic complexity 96 (threshold 15). Of this number, 90 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
formExplorerExtensionGenerator.handleGenerateFormExplorerExtensionCore (cyclomatic 88) REDACTED:6621— formExplorerExtensionGenerator.handleGenerateFormExplorerExtensionCore has cyclomatic complexity 88 (threshold 15). Of this number, 47 points are the body's own statements and 41 belong to 8 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phaseSwitcher.buildScenarioViewState (cyclomatic 81) media/phaseSwitcher.js:1056— phaseSwitcher.buildScenarioViewState has cyclomatic complexity 81 (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.
stepLibrarySidebar.window.addEventListener("message") (cyclomatic 79) media/stepLibrarySidebar.js:1008— stepLibrarySidebar.window.addEventListener("message") has cyclomatic complexity 79 (threshold 15). Of this number, 78 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
(anonymous) (cyclomatic 79) media/stepLibrarySidebar.js:1008— (anonymous) has cyclomatic complexity 79 (threshold 15). Of this number, 78 points are the body's own statements and 1 belongs to 7 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScenarioPropertiesSession.perform (cyclomatic 78) src/scenarioPropertiesSession.ts:387— ScenarioPropertiesSession.perform has cyclomatic complexity 78 (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.
vanessaControlProtocol.parseVanessaControlReply (cyclomatic 77) src/vanessaControlProtocol.ts:111— vanessaControlProtocol.parseVanessaControlReply has cyclomatic complexity 77 (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.
compilerBuildReport.writeCompilerBuildReport (cyclomatic 74) src/compilerBuildReport.ts:131— compilerBuildReport.writeCompilerBuildReport has cyclomatic complexity 74 (threshold 15). Of this number, 66 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VanessaInfobaseClients.operate (cyclomatic 74) src/vanessaInfobaseClients.ts:269— VanessaInfobaseClients.operate has cyclomatic complexity 74 (threshold 15). Most of this is not in the body itself: 6 of the 74 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 289, 271, 280, …). 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.
scenarioProperties.records (cyclomatic 71) media/scenarioProperties.js:436— scenarioProperties.records has cyclomatic complexity 71 (threshold 15). Of this number, 50 points are the body's own statements and 21 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
formExplorer.bindStaticEvents (cyclomatic 69) media/formExplorer.js:290— formExplorer.bindStaticEvents has cyclomatic complexity 69 (threshold 15). Most of this is not in the body itself: 7 of the 69 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 449, 593, 291, …). 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.
InfobaseManagerPanel.handleMessage (cyclomatic 64) src/infobaseManagerPanel.ts:418— InfobaseManagerPanel.handleMessage has cyclomatic complexity 64 (threshold 15). Of this number, 54 points are the body's own statements and 10 belong to 8 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
stepLibrarySidebar.makeRow (cyclomatic 62) media/stepLibrarySidebar.js:286— stepLibrarySidebar.makeRow has cyclomatic complexity 62 (threshold 15). Of this number, 53 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
formExplorer.renderStaticFrame (cyclomatic 61) media/formExplorer.js:698— formExplorer.renderStaticFrame has cyclomatic complexity 61 (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.
PhaseSwitcherProvider.changeScenarioIdentityField (cyclomatic 61) src/phaseSwitcher.ts:5360— PhaseSwitcherProvider.changeScenarioIdentityField has cyclomatic complexity 61 (threshold 15). Of this number, 52 points are the body's own statements and 9 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.renameScenario (cyclomatic 61) src/phaseSwitcher.ts:5936— PhaseSwitcherProvider.renameScenario has cyclomatic complexity 61 (threshold 15). Of this number, 50 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
featureEditorActions.planFeatureEditorEdit (cyclomatic 60) src/featureEditorActions.ts:184— featureEditorActions.planFeatureEditorEdit has cyclomatic complexity 60 (threshold 15). Of this number, 53 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phaseSwitcher.handleScenarioContextMenu (cyclomatic 58) media/phaseSwitcher.js:2843— phaseSwitcher.handleScenarioContextMenu has cyclomatic complexity 58 (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.
YamlParametersManager.openYamlParametersPanel (cyclomatic 58) REDACTED:1235— YamlParametersManager.openYamlParametersPanel has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 1 of the 58 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 1278, watchModelDbFile). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DriveCompletionProvider.provideCompletionItems (cyclomatic 58) src/completionProvider.ts:717— DriveCompletionProvider.provideCompletionItems has cyclomatic complexity 58 (threshold 15). Of this number, 40 points are the body's own statements and 18 belong to one function literal inside it that branches. 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.
scenarioPropertiesActions.createScenarioPropertiesActions.<returned closure> (cyclomatic 58) src/scenarioPropertiesActions.ts:277— scenarioPropertiesActions.createScenarioPropertiesActions.<returned closure> has cyclomatic complexity 58 (threshold 15). Of this number, 57 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
stepLibrary.renderProcessSteps (cyclomatic 57) media/stepLibrary.js:1672— stepLibrary.renderProcessSteps has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 12 of the 57 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 1763, a function literal at line 1723, readDrag, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
scenarioPropertiesModel.applyYamlMapField (cyclomatic 57) src/scenarioPropertiesModel.ts:366— scenarioPropertiesModel.applyYamlMapField has cyclomatic complexity 57 (threshold 15). Of this number, 51 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
renderPhaseTree (cyclomatic 56) media/phaseSwitcher.js:1683— renderPhaseTree has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 11 of the 56 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 1718, 1710, 1690, …). 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.
stepLibrary.window.addEventListener("message") (cyclomatic 55) media/stepLibrary.js:2136— stepLibrary.window.addEventListener("message") 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.
compilerBuildPreflight.collectCompilerBuildPreflightIssues (cyclomatic 54) src/compilerBuildPreflight.ts:107— compilerBuildPreflight.collectCompilerBuildPreflightIssues has cyclomatic complexity 54 (threshold 15). Of this number, 47 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioIdentityFiles.prepareScenarioIdentityFileChanges (cyclomatic 54) src/scenarioIdentityFiles.ts:46— scenarioIdentityFiles.prepareScenarioIdentityFileChanges has cyclomatic complexity 54 (threshold 15). Of this number, 44 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
standaloneFeatures.create.render (cyclomatic 53) media/standaloneFeatures.js:578— standaloneFeatures.create.render has cyclomatic complexity 53 (threshold 15). Of this number, 30 points are the body's own statements and 23 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
processEditorCommands.changeProcessIdentityFromEditor (cyclomatic 53) src/processEditorCommands.ts:50— processEditorCommands.changeProcessIdentityFromEditor has cyclomatic complexity 53 (threshold 15). Of this number, 38 points are the body's own statements and 15 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.updateScenarioBuildArtifacts (cyclomatic 53) src/phaseSwitcher.ts:10172— PhaseSwitcherProvider.updateScenarioBuildArtifacts has cyclomatic complexity 53 (threshold 15). Of this number, 47 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create.render (cyclomatic 53) media/standaloneFeatures.js:578— create.render has cyclomatic complexity 53 (threshold 15). Of this number, 30 points are the body's own statements and 23 belong to 15 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gherkinAnnotations.buildGherkinAnnotationCompletions (cyclomatic 50) src/gherkinAnnotations.ts:234— gherkinAnnotations.buildGherkinAnnotationCompletions has cyclomatic complexity 50 (threshold 15). Of this number, 32 points are the body's own statements and 18 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
vanessaControlFormTools.readSchema (cyclomatic 50) src/vanessaControlFormTools.ts:50— vanessaControlFormTools.readSchema has cyclomatic complexity 50 (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.
vanessaControlDiagnosticsCommands.registerVanessaDiagnosticsCommands (cyclomatic 49) src/vanessaControlDiagnosticsCommands.ts:10— vanessaControlDiagnosticsCommands.registerVanessaDiagnosticsCommands has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 15 function items inside it that branch (a function literal at line 90, run, a function literal at line 110, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ScenarioDiagnosticsProvider.provideCodeActions (cyclomatic 49) src/scenarioDiagnostics.ts:855— ScenarioDiagnosticsProvider.provideCodeActions has cyclomatic complexity 49 (threshold 15). Of this number, 44 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlStepResults.mapVanessaStepResults (cyclomatic 48) src/vanessaControlStepResults.ts:10— vanessaControlStepResults.mapVanessaStepResults has cyclomatic complexity 48 (threshold 15). Of this number, 25 points are the body's own statements and 23 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioProperties.render (cyclomatic 47) media/scenarioProperties.js:624— scenarioProperties.render has cyclomatic complexity 47 (threshold 15). Of this number, 39 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StandaloneFeatureController.performAction (cyclomatic 47) src/standaloneFeatureController.ts:191— StandaloneFeatureController.performAction has cyclomatic complexity 47 (threshold 15). Of this number, 46 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
compilerBuildErrorLocation.resolveCompilerBuildErrorLocation (cyclomatic 47) src/compilerBuildErrorLocation.ts:12— compilerBuildErrorLocation.resolveCompilerBuildErrorLocation has cyclomatic complexity 47 (threshold 15). Of this number, 28 points are the body's own statements and 19 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioProperties.fieldControl (cyclomatic 46) media/scenarioProperties.js:304— scenarioProperties.fieldControl has cyclomatic complexity 46 (threshold 15). Of this number, 30 points are the body's own statements and 16 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProjectLibraryStore.load (cyclomatic 46) src/projectLibraryStore.ts:343— ProjectLibraryStore.load has cyclomatic complexity 46 (threshold 15). Of this number, 43 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.runScenarioInVanessaBuiltIn (cyclomatic 46) src/phaseSwitcher.ts:12050— PhaseSwitcherProvider.runScenarioInVanessaBuiltIn has cyclomatic complexity 46 (threshold 15). Of this number, 44 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StepLibraryPanel.handleMessage (cyclomatic 46) src/stepLibraryPanel.ts:408— StepLibraryPanel.handleMessage has cyclomatic complexity 46 (threshold 15). Of this number, 37 points are the body's own statements and 9 belong to 3 function literals inside it that branch. 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.
kotWorkspace.setup (cyclomatic 45) media/kotWorkspace.js:172— kotWorkspace.setup has cyclomatic complexity 45 (threshold 15). Of this number, 32 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
standaloneFeatureController.parseStandaloneFeatureMessage (cyclomatic 45) src/standaloneFeatureController.ts:69— standaloneFeatureController.parseStandaloneFeatureMessage has cyclomatic complexity 45 (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.
(anonymous) (cyclomatic 45) media/yamlParameters.js:1451— (anonymous) has cyclomatic complexity 45 (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.
yamlParameters.window.addEventListener("message") (cyclomatic 44) media/yamlParameters.js:1451— yamlParameters.window.addEventListener("message") 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.
stepLibraryModel.buildStepLibrarySnapshot (cyclomatic 44) src/stepLibraryModel.ts:305— stepLibraryModel.buildStepLibrarySnapshot has cyclomatic complexity 44 (threshold 15). Of this number, 17 points are the body's own statements and 27 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioPropertiesCatalogs.runScenarioPropertiesCatalogAction (cyclomatic 44) src/scenarioPropertiesCatalogs.ts:199— scenarioPropertiesCatalogs.runScenarioPropertiesCatalogAction has cyclomatic complexity 44 (threshold 15). Of this number, 36 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.promptVanessaInfobasePreparationPlan (cyclomatic 44) src/phaseSwitcher.ts:11454— PhaseSwitcherProvider.promptVanessaInfobasePreparationPlan has cyclomatic complexity 44 (threshold 15). Of this number, 40 points are the body's own statements and 4 belong to one function item inside it that branches. 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.
ScenarioHeaderInlayHintsProvider.provideInlayHints (cyclomatic 44) src/scenarioHeaderInlayHintsProvider.ts:36— ScenarioHeaderInlayHintsProvider.provideInlayHints has cyclomatic complexity 44 (threshold 15). Of this number, 43 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
FeaturePropertiesController.handle (cyclomatic 43) src/featurePropertiesController.ts:43— FeaturePropertiesController.handle has cyclomatic complexity 43 (threshold 15). Of this number, 42 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
ScenarioSyntaxHighlightProvider.buildTokens (cyclomatic 43) src/scenarioSyntaxHighlightProvider.ts:185— ScenarioSyntaxHighlightProvider.buildTokens has cyclomatic complexity 43 (threshold 15). Of this number, 37 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
kotWebviewSplit.attach (cyclomatic 42) media/kotWebviewSplit.js:11— kotWebviewSplit.attach has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 5 of the 42 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 77, update, geometry, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
projectDefinitionDeletion.deleteScenarioDefinition.prepare (cyclomatic 42) src/projectDefinitionDeletion.ts:133— projectDefinitionDeletion.deleteScenarioDefinition.prepare has cyclomatic complexity 42 (threshold 15). Of this number, 35 points are the body's own statements and 7 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
infobaseManager.collectManagedInfobases (cyclomatic 42) src/infobaseManager.ts:1121— infobaseManager.collectManagedInfobases has cyclomatic complexity 42 (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. This shape REPEATS in the file: one other method here (infobaseManager.collectManagedInfobases::observeInfobase) 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.
(anonymous) (cyclomatic 42) media/phaseSwitcher.js:4— (anonymous) has cyclomatic complexity 42 (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.
projectLibraryMetadata.loadProjectScenarioMetadata (cyclomatic 41) src/projectLibraryMetadata.ts:152— projectLibraryMetadata.loadProjectScenarioMetadata has cyclomatic complexity 41 (threshold 15). Of this number, 40 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
gherkinAnnotations.scan (cyclomatic 41) src/gherkinAnnotations.ts:60— gherkinAnnotations.scan has cyclomatic complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
PhaseSwitcherProvider.execute1CProcess (cyclomatic 41) src/phaseSwitcher.ts:9003— PhaseSwitcherProvider.execute1CProcess has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 8 of the 41 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 9121, 9094, 9031, …). 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.
PhaseSwitcherProvider.runScenarioInVanessa (cyclomatic 41) src/phaseSwitcher.ts:13433— PhaseSwitcherProvider.runScenarioInVanessa has cyclomatic complexity 41 (threshold 15). Of this number, 40 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
kotProjectSetup.inspectSetupProject (cyclomatic 41) src/kotProjectSetup.ts:35— kotProjectSetup.inspectSetupProject has cyclomatic complexity 41 (threshold 15). Of this number, 40 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
app.fieldHtml (cyclomatic 40) docs/ux/first-run/app.js:152— app.fieldHtml has cyclomatic complexity 40 (threshold 15). Of this number, 38 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
standaloneFeatures.create.dropTarget (cyclomatic 40) media/standaloneFeatures.js:279— standaloneFeatures.create.dropTarget has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 304, a function literal at line 286, valid, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
compilerBuildPreflight.settingSelected (cyclomatic 40) src/compilerBuildPreflight.ts:43— compilerBuildPreflight.settingSelected has cyclomatic complexity 40 (threshold 15). Of this number, 25 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FormExplorerPanel.refreshSnapshot (cyclomatic 40) src/formExplorerPanel.ts:1430— FormExplorerPanel.refreshSnapshot has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
create.dropTarget (cyclomatic 40) media/standaloneFeatures.js:279— create.dropTarget has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 304, a function literal at line 286, valid, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
stepLibrary.createDefinitionRow (cyclomatic 39) media/stepLibrary.js:1157— stepLibrary.createDefinitionRow has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
ProjectLibraryStore.moveEntity (cyclomatic 39) src/projectLibraryStore.ts:718— ProjectLibraryStore.moveEntity has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 720, 747, 748). 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.
scenarioFilesWebviewProtocol.parseScenarioFilesMessage (cyclomatic 39) src/scenarioFilesWebviewProtocol.ts:80— scenarioFilesWebviewProtocol.parseScenarioFilesMessage 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.
KotWorkspacePanel.dispatch (cyclomatic 39) src/kotWorkspacePanel.ts:116— KotWorkspacePanel.dispatch has cyclomatic complexity 39 (threshold 15). Of this number, 35 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
StepLibrarySidebarProvider.handleMessage (cyclomatic 39) src/stepLibrarySidebarProvider.ts:299— StepLibrarySidebarProvider.handleMessage has cyclomatic complexity 39 (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.
stepLibraryPanel.parseStepLibraryInboundMessage (cyclomatic 39) src/stepLibraryPanel.ts:95— stepLibraryPanel.parseStepLibraryInboundMessage has cyclomatic complexity 39 (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.
scenarioPropertiesProtocol.createClient::setState (cyclomatic 38) media/scenarioPropertiesProtocol.js:145— scenarioPropertiesProtocol.createClient::setState 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.
stepLibrary.renderDetails (cyclomatic 38) media/stepLibrary.js:1783— stepLibrary.renderDetails has cyclomatic complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
configurationDiffAiReport.analyzeConfigurationPath (cyclomatic 38) REDACTED:522— configurationDiffAiReport.analyzeConfigurationPath has cyclomatic complexity 38 (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.
projectMetadataMerge.mergeProjectMetadata::combine (cyclomatic 38) src/projectMetadataMerge.ts:72— projectMetadataMerge.mergeProjectMetadata::combine 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.
vanessaControlYamlTrial.prepareVanessaYamlTrial (cyclomatic 38) src/vanessaControlYamlTrial.ts:33— vanessaControlYamlTrial.prepareVanessaYamlTrial has cyclomatic complexity 38 (threshold 15). Of this number, 36 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand (cyclomatic 38) src/vanessaControlYamlTrialCommands.ts:15— vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 99, 63, 87, …). 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.
standaloneFeatures.create.syncManagerFeature (cyclomatic 37) media/standaloneFeatures.js:368— standaloneFeatures.create.syncManagerFeature has cyclomatic complexity 37 (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.
scenarioCatalog.areScenarioCatalogEntriesEqual (cyclomatic 37) src/scenarioCatalog.ts:159— scenarioCatalog.areScenarioCatalogEntriesEqual has cyclomatic complexity 37 (threshold 15). Of this number, 30 points are the body's own statements and 7 belong to one function literal inside it that branches. 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.
gherkinAnnotations.completionContext (cyclomatic 37) src/gherkinAnnotations.ts:173— gherkinAnnotations.completionContext has cyclomatic complexity 37 (threshold 15). Of this number, 30 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
exportScenarioParser.parseExportScenarios (cyclomatic 37) src/exportScenarioParser.ts:317— exportScenarioParser.parseExportScenarios has cyclomatic complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
ScenarioPropertiesPanel.receive (cyclomatic 37) src/scenarioPropertiesPanel.ts:658— ScenarioPropertiesPanel.receive has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
kotSettingsSession.validateSetting (cyclomatic 37) REDACTED:27— kotSettingsSession.validateSetting has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlClientWorkflow.manageVanessaClients (cyclomatic 37) src/vanessaControlClientWorkflow.ts:27— vanessaControlClientWorkflow.manageVanessaClients has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create.syncManagerFeature (cyclomatic 37) media/standaloneFeatures.js:368— create.syncManagerFeature has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
standaloneFeatures.create.featureRow (cyclomatic 36) media/standaloneFeatures.js:501— standaloneFeatures.create.featureRow has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
stepLibraryProtocol.buildCategoryTree (cyclomatic 36) media/stepLibraryProtocol.js:378— stepLibraryProtocol.buildCategoryTree has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProjectLibraryStore.commit (cyclomatic 36) src/projectLibraryStore.ts:514— ProjectLibraryStore.commit has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 515, guard, a function literal at line 559, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
scenarioPropertyIdentity.applyScenarioPropertyIdentity (cyclomatic 36) src/scenarioPropertyIdentity.ts:11— scenarioPropertyIdentity.applyScenarioPropertyIdentity has cyclomatic complexity 36 (threshold 15). Of this number, 31 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScenarioPropertiesSession.load (cyclomatic 36) src/scenarioPropertiesSession.ts:131— ScenarioPropertiesSession.load has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ScenarioPropertiesSession.load::enrich) 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.
PhaseSwitcherProvider.applyRunningFeatureStepDecorations (cyclomatic 36) src/phaseSwitcher.ts:3264— PhaseSwitcherProvider.applyRunningFeatureStepDecorations has cyclomatic complexity 36 (threshold 15). Of this number, 33 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioAiDescription.buildDeterministicParameterizedUtilityScenarioDescription (cyclomatic 36) REDACTED:3395— scenarioAiDescription.buildDeterministicParameterizedUtilityScenarioDescription has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create.featureRow (cyclomatic 36) media/standaloneFeatures.js:501— create.featureRow has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 8 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VanessaFormExplorerSource.perform (cyclomatic 35) src/vanessaControlFormSource.ts:99— VanessaFormExplorerSource.perform has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 107, sameSession, current, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
StepLibrarySidebarIndex.constructor (cyclomatic 35) src/stepLibrarySidebarModel.ts:247— StepLibrarySidebarIndex.constructor has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScenarioPropertiesAttachments.handle (cyclomatic 34) src/scenarioPropertiesAttachments.ts:73— ScenarioPropertiesAttachments.handle has cyclomatic complexity 34 (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.
PhaseSwitcherProvider.pollVanessaRuntimeLogMonitor (cyclomatic 34) src/phaseSwitcher.ts:2661— PhaseSwitcherProvider.pollVanessaRuntimeLogMonitor has cyclomatic complexity 34 (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.
scenarioAiDescription.buildDeterministicScenarioChunkSummary (cyclomatic 34) REDACTED:3153— scenarioAiDescription.buildDeterministicScenarioChunkSummary has cyclomatic complexity 34 (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.
vanessaControlVariableCommands.registerVanessaVariableCommands (cyclomatic 34) src/vanessaControlVariableCommands.ts:11— vanessaControlVariableCommands.registerVanessaVariableCommands has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 28, write, a function literal at line 88, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
vanessaControlYamlCommands.createVanessaYamlControl::render (cyclomatic 34) src/vanessaControlYamlCommands.ts:33— vanessaControlYamlCommands.createVanessaYamlControl::render has cyclomatic complexity 34 (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.
formExplorerExtensionGenerator.handleStartFormExplorerInfobase (cyclomatic 34) REDACTED:7104— formExplorerExtensionGenerator.handleStartFormExplorerInfobase has cyclomatic complexity 34 (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.
ProjectCatalogSettings.run (cyclomatic 34) src/projectCatalogSettings.ts:70— ProjectCatalogSettings.run has cyclomatic complexity 34 (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.
scenarioPropertiesProtocol.validateMessage (cyclomatic 33) media/scenarioPropertiesProtocol.js:66— scenarioPropertiesProtocol.validateMessage has cyclomatic complexity 33 (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.
scenarioPropertiesModel.applyScenarioPropertyEdit (cyclomatic 33) src/scenarioPropertiesModel.ts:220— scenarioPropertiesModel.applyScenarioPropertyEdit has cyclomatic complexity 33 (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.
VanessaControlSession.refreshState (cyclomatic 33) src/vanessaControlSession.ts:289— VanessaControlSession.refreshState has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 4 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 294, 299). 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.
StandaloneFeatureService.readProjectOrganization (cyclomatic 33) src/standaloneFeatureService.ts:686— StandaloneFeatureService.readProjectOrganization has cyclomatic complexity 33 (threshold 15). Of this number, 28 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KotWorkspacePanel.reviewSetup (cyclomatic 33) src/kotWorkspacePanel.ts:202— KotWorkspacePanel.reviewSetup has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KotWorkspacePanel.applySetup (cyclomatic 33) src/kotWorkspacePanel.ts:238— KotWorkspacePanel.applySetup has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 4 of the 33 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 244, 246, 256). 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.
projectDefinitionCache.isDefinition (cyclomatic 33) src/projectDefinitionCache.ts:54— projectDefinitionCache.isDefinition has cyclomatic complexity 33 (threshold 15). Of this number, 28 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
FormExplorerPanel.handleMessage (cyclomatic 33) src/formExplorerPanel.ts:342— FormExplorerPanel.handleMessage has cyclomatic complexity 33 (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.
nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.rebuild (cyclomatic 33) src/nativeProjectCatalogSettings.ts:177— nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.rebuild has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaLaunchJson.parseAdditionalParameterValue (cyclomatic 32) src/vanessaLaunchJson.ts:437— vanessaLaunchJson.parseAdditionalParameterValue has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
VanessaBreakpointReconciler.reconcile (cyclomatic 32) src/vanessaControlBreakpoints.ts:39— VanessaBreakpointReconciler.reconcile has cyclomatic complexity 32 (threshold 15). Of this number, 23 points are the body's own statements and 9 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VanessaYamlControl.run (cyclomatic 32) src/vanessaControlYaml.ts:60— VanessaYamlControl.run has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
PhaseSwitcherProvider.changeNestedScenarioCodeForActiveEditor (cyclomatic 32) src/phaseSwitcher.ts:4948— PhaseSwitcherProvider.changeNestedScenarioCodeForActiveEditor has cyclomatic complexity 32 (threshold 15). Of this number, 26 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DriveCompletionProvider.buildFormExplorerQuotedArgumentCompletionList (cyclomatic 32) src/completionProvider.ts:1675— DriveCompletionProvider.buildFormExplorerQuotedArgumentCompletionList has cyclomatic complexity 32 (threshold 15). Of this number, 24 points are the body's own statements and 8 belong to 7 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DriveCompletionProvider.buildControlFlowCompletions (cyclomatic 32) src/completionProvider.ts:2737— DriveCompletionProvider.buildControlFlowCompletions 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.
exportScenarioCommand.createExportScenarioCommand (cyclomatic 32) src/exportScenarioCommand.ts:83— exportScenarioCommand.createExportScenarioCommand has cyclomatic complexity 32 (threshold 15). Of this number, 29 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioSyntaxHighlightProvider.collectScenarioPlainTextRanges (cyclomatic 32) src/scenarioSyntaxHighlightProvider.ts:352— scenarioSyntaxHighlightProvider.collectScenarioPlainTextRanges 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.
buildRowHtml (cyclomatic 32) media/yamlParameters.js:375— buildRowHtml has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
kotWorkspace.controls (cyclomatic 31) media/kotWorkspace.js:80— kotWorkspace.controls has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
stepLibrarySidebar.render (cyclomatic 31) media/stepLibrarySidebar.js:614— stepLibrarySidebar.render has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
scenarioCompilerSyntax.validateCompilerBlocks (cyclomatic 31) src/scenarioCompilerSyntax.ts:105— scenarioCompilerSyntax.validateCompilerBlocks has cyclomatic complexity 31 (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.
DriveCompletionProvider.collectFormExplorerTableCompletionCandidates (cyclomatic 31) src/completionProvider.ts:1057— DriveCompletionProvider.collectFormExplorerTableCompletionCandidates has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (append, a function literal at line 1060, append::collect, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
vanessaControlConnection.registerVanessaControl.autoConnect (cyclomatic 31) src/vanessaControlConnection.ts:105— vanessaControlConnection.registerVanessaControl.autoConnect has cyclomatic complexity 31 (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.
vanessaInfobaseClientCommands.handleVanessaInfobaseClientMessage (cyclomatic 31) src/vanessaInfobaseClientCommands.ts:12— vanessaInfobaseClientCommands.handleVanessaInfobaseClientMessage has cyclomatic complexity 31 (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.
extension.activate::runScenarioRepairBatch (cyclomatic 31) REDACTED:2929— extension.activate::runScenarioRepairBatch has cyclomatic complexity 31 (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.
infobaseVanessaClients.create.render (cyclomatic 30) media/infobaseVanessaClients.js:63— infobaseVanessaClients.create.render has cyclomatic complexity 30 (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.
infobaseManager.collectManagedInfobases::observeInfobase (cyclomatic 30) src/infobaseManager.ts:1131— infobaseManager.collectManagedInfobases::observeInfobase has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (infobaseManager.collectManagedInfobases) 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.
DriveCompletionProvider.calculateSemanticVectorScores (cyclomatic 30) src/completionProvider.ts:2350— DriveCompletionProvider.calculateSemanticVectorScores has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2368, 2401, 2424). 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.
scenarioAiDescription.extractScenarioFieldAssignments (cyclomatic 30) REDACTED:2963— scenarioAiDescription.extractScenarioFieldAssignments has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
featureEditorCodeLens.editFeatureStructureCommand (cyclomatic 30) src/featureEditorCodeLens.ts:91— featureEditorCodeLens.editFeatureStructureCommand has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create.render (cyclomatic 30) media/infobaseVanessaClients.js:63— create.render has cyclomatic complexity 30 (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.
relationshipDecorationForNode (cyclomatic 30) media/stepLibrarySidebarProtocol.js:175— relationshipDecorationForNode has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phaseSwitcher.renderScenarioFileNode (cyclomatic 29) media/phaseSwitcher.js:946— phaseSwitcher.renderScenarioFileNode has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stepLibrary.renderDetailsResourceNode (cyclomatic 29) media/stepLibrary.js:1470— stepLibrary.renderDetailsResourceNode has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phaseSwitcherMetadata.migrateLegacyPhaseSwitcherMetadata (cyclomatic 29) src/phaseSwitcherMetadata.ts:611— phaseSwitcherMetadata.migrateLegacyPhaseSwitcherMetadata has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlForms.parseVanessaFormTree (cyclomatic 29) src/vanessaControlForms.ts:36— vanessaControlForms.parseVanessaFormTree has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
standaloneFeatureLaunch.buildStandaloneFeatureLaunchJson (cyclomatic 29) src/standaloneFeatureLaunch.ts:172— standaloneFeatureLaunch.buildStandaloneFeatureLaunchJson has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
infobaseManager.updateManagedInfobaseMetadata (cyclomatic 29) src/infobaseManager.ts:789— infobaseManager.updateManagedInfobaseMetadata has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScenarioPropertiesSession.load::enrich (cyclomatic 29) src/scenarioPropertiesSession.ts:215— ScenarioPropertiesSession.load::enrich has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ScenarioPropertiesSession.load) 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.
ScenarioPropertiesPanel.follow (cyclomatic 29) src/scenarioPropertiesPanel.ts:555— ScenarioPropertiesPanel.follow has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.constructor (cyclomatic 29) src/phaseSwitcher.ts:1987— PhaseSwitcherProvider.constructor has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 1997, a function literal at line 2079, a function literal at line 2045, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PhaseSwitcherProvider.changeNestedScenarioName (cyclomatic 29) src/phaseSwitcher.ts:5169— PhaseSwitcherProvider.changeNestedScenarioName has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.prepareVanessaLaunchContext (cyclomatic 29) src/phaseSwitcher.ts:11879— PhaseSwitcherProvider.prepareVanessaLaunchContext has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
formExplorerBridgeGenerator.handleStartFormExplorerBridge (cyclomatic 29) src/formExplorerBridgeGenerator.ts:146— formExplorerBridgeGenerator.handleStartFormExplorerBridge has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
userStepCommands.buildUserStepLibraryCommand (cyclomatic 29) src/userStepCommands.ts:411— userStepCommands.buildUserStepLibraryCommand has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
formExplorer.initialize (cyclomatic 28) media/formExplorer.js:226— formExplorer.initialize has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 232). 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.
phaseSwitcher.applyCheckboxStatesToVisible (cyclomatic 28) media/phaseSwitcher.js:2987— phaseSwitcher.applyCheckboxStatesToVisible has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2994, 3075, 3026). 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.
aiClient.extractResponseText (cyclomatic 28) src/aiClient.ts:107— aiClient.extractResponseText has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
scenarioYamlDocument.buildStructuralShadow (cyclomatic 28) src/scenarioYamlDocument.ts:158— scenarioYamlDocument.buildStructuralShadow has cyclomatic complexity 28 (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.
scenarioPropertiesModel.propertyField (cyclomatic 28) src/scenarioPropertiesModel.ts:77— scenarioPropertiesModel.propertyField has cyclomatic complexity 28 (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.
compilerBuildValueValidation.collectCompilerBuildValueIssues (cyclomatic 28) src/compilerBuildValueValidation.ts:64— compilerBuildValueValidation.collectCompilerBuildValueIssues has cyclomatic complexity 28 (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.
compilerArtifacts.readXml (cyclomatic 28) src/compilerArtifacts.ts:214— compilerArtifacts.readXml has cyclomatic complexity 28 (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.
gherkinTableUtils.planGherkinHeaderColumnDeletion (cyclomatic 28) src/gherkinTableUtils.ts:153— gherkinTableUtils.planGherkinHeaderColumnDeletion has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
PhaseSwitcherProvider.pollTrackedRunLogWatcher (cyclomatic 28) src/phaseSwitcher.ts:3812— PhaseSwitcherProvider.pollTrackedRunLogWatcher has cyclomatic complexity 28 (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.
PhaseSwitcherProvider.reorderProjectLibrary (cyclomatic 28) src/phaseSwitcher.ts:5798— PhaseSwitcherProvider.reorderProjectLibrary has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.prepareTargetInfobaseForVanessa (cyclomatic 28) src/phaseSwitcher.ts:11624— PhaseSwitcherProvider.prepareTargetInfobaseForVanessa has cyclomatic complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
commandHandlers.handleCreateFirstLaunchZip (cyclomatic 28) REDACTED:931— commandHandlers.handleCreateFirstLaunchZip has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 999, 1002, 969, …). 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.
gherkinInsertionContext.featureContext (cyclomatic 28) src/gherkinInsertionContext.ts:81— gherkinInsertionContext.featureContext has cyclomatic complexity 28 (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.
configurationDiffAiReport.finalizeTestingFocusAreaRussian (cyclomatic 28) REDACTED:823— configurationDiffAiReport.finalizeTestingFocusAreaRussian has cyclomatic complexity 28 (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.
scenarioPropertiesActions.createScenarioPropertiesActions::catalogChoice (cyclomatic 28) src/scenarioPropertiesActions.ts:128— scenarioPropertiesActions.createScenarioPropertiesActions::catalogChoice has cyclomatic complexity 28 (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.
VanessaInfobaseClients.refresh (cyclomatic 28) src/vanessaInfobaseClients.ts:133— VanessaInfobaseClients.refresh has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 139, 147). 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.
stepLibrarySidebarProvider.parseStepLibrarySidebarMessage (cyclomatic 28) src/stepLibrarySidebarProvider.ts:105— stepLibrarySidebarProvider.parseStepLibrarySidebarMessage has cyclomatic complexity 28 (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.
scenarioCallableFiles.applyCallableFileConversion (cyclomatic 28) src/scenarioCallableFiles.ts:27— scenarioCallableFiles.applyCallableFileConversion has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
stepLibraryProtocol.searchItems (cyclomatic 27) media/stepLibraryProtocol.js:215— stepLibraryProtocol.searchItems has cyclomatic complexity 27 (threshold 15). Of this number, 16 points are the body's own statements and 11 belong to one function literal inside it that branches. 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.
scenarioDescriptor.parseScenarioDescriptor (cyclomatic 27) src/scenarioDescriptor.ts:122— scenarioDescriptor.parseScenarioDescriptor has cyclomatic complexity 27 (threshold 15). Of this number, 18 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProjectLibraryStore.setMetadata (cyclomatic 27) src/projectLibraryStore.ts:674— ProjectLibraryStore.setMetadata has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 675, 698, 708). 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.
vanessaControlFormTools.validateValue (cyclomatic 27) src/vanessaControlFormTools.ts:126— vanessaControlFormTools.validateValue has cyclomatic complexity 27 (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.
standaloneFeatureService.readOrganization (cyclomatic 27) src/standaloneFeatureService.ts:82— standaloneFeatureService.readOrganization 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.
scenarioCreator.handleManageEtalonBases (cyclomatic 27) src/scenarioCreator.ts:1728— scenarioCreator.handleManageEtalonBases has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlCommands.registerVanessaControlCommands::update (cyclomatic 27) src/vanessaControlCommands.ts:42— vanessaControlCommands.registerVanessaControlCommands::update has cyclomatic complexity 27 (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.
ScenarioDiagnosticsProvider.validateFeatureDocument (cyclomatic 27) src/scenarioDiagnostics.ts:1935— ScenarioDiagnosticsProvider.validateFeatureDocument 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.
bslStepSourceParser.scanBslTokens (cyclomatic 26) src/bslStepSourceParser.ts:146— bslStepSourceParser.scanBslTokens 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.
scenarioYamlDocument.readOriginalScalar (cyclomatic 26) src/scenarioYamlDocument.ts:262— scenarioYamlDocument.readOriginalScalar has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
compilerProcesses.updateCompilerProcessIdentity (cyclomatic 26) src/compilerProcesses.ts:327— compilerProcesses.updateCompilerProcessIdentity has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlClients.parseVanessaClientProfiles (cyclomatic 26) src/vanessaControlClients.ts:51— vanessaControlClients.parseVanessaClientProfiles has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 64, 68). 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.
compilerBuildValueValidation.isXmlDateTime (cyclomatic 26) src/compilerBuildValueValidation.ts:47— compilerBuildValueValidation.isXmlDateTime has cyclomatic complexity 26 (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.
compilerBuildSourceSelection.selectCompilerBuildSources (cyclomatic 26) src/compilerBuildSourceSelection.ts:6— compilerBuildSourceSelection.selectCompilerBuildSources 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.
scenarioCreator.handleCreateMainScenario (cyclomatic 26) src/scenarioCreator.ts:2461— scenarioCreator.handleCreateMainScenario has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerEnrichment.enrichElementTree (cyclomatic 26) REDACTED:771— formExplorerEnrichment.enrichElementTree has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 775). 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.
scenarioAiDescription.humanizeScenarioParameterOrBranch (cyclomatic 26) REDACTED:2477— scenarioAiDescription.humanizeScenarioParameterOrBranch 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.
app.setup (cyclomatic 25) docs/ux/first-run/app.js:86— app.setup has cyclomatic complexity 25 (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.
phaseSwitcher.applyScenarioVisibility (cyclomatic 25) media/phaseSwitcher.js:479— phaseSwitcher.applyScenarioVisibility has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 525, 502, 562, …). 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.
bslStepSourceParser.parseStaticBslStepRegistrations (cyclomatic 25) src/bslStepSourceParser.ts:764— bslStepSourceParser.parseStaticBslStepRegistrations has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
VanessaFeatureControl.run (cyclomatic 25) src/vanessaControlFeature.ts:45— VanessaFeatureControl.run 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.
oneCInfobaseTemplates.discoverInfobaseTemplates (cyclomatic 25) src/oneCInfobaseTemplates.ts:20— oneCInfobaseTemplates.discoverInfobaseTemplates has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 27, 22, 24, …). 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.
infobaseManager.pickManagedInfobasePath (cyclomatic 25) src/infobaseManager.ts:3254— infobaseManager.pickManagedInfobasePath has cyclomatic complexity 25 (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.
projectMetadataAudit.auditMetadataReferences (cyclomatic 25) src/projectMetadataAudit.ts:7— projectMetadataAudit.auditMetadataReferences has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
vanessaControlFormToolWorkflow.collectVanessaFormToolArguments (cyclomatic 25) src/vanessaControlFormToolWorkflow.ts:13— vanessaControlFormToolWorkflow.collectVanessaFormToolArguments has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
additionalValueHtml (cyclomatic 25) media/yamlParameters.js:466— additionalValueHtml has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
infobaseManager.renderList (cyclomatic 24) media/infobaseManager.js:377— infobaseManager.renderList has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
standaloneFeatures.create.updateRelationshipPresentation (cyclomatic 24) media/standaloneFeatures.js:463— standaloneFeatures.create.updateRelationshipPresentation has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
stepLibrary.renderScenarioResourceNode (cyclomatic 24) media/stepLibrary.js:962— stepLibrary.renderScenarioResourceNode has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compilerProcessSelection.adaptNestedProcessFilters (cyclomatic 24) src/compilerProcessSelection.ts:72— compilerProcessSelection.adaptNestedProcessFilters has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compilerBuildRuntime.mergeCompilerBuildOutputs (cyclomatic 24) src/compilerBuildRuntime.ts:105— compilerBuildRuntime.mergeCompilerBuildOutputs has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to one function item inside it that branches. 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.
spprScenarioFormat.convertSpprScenarioFiles (cyclomatic 24) src/spprScenarioFormat.ts:55— spprScenarioFormat.convertSpprScenarioFiles has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioIdentityFiles.prepareScenarioIdentityFileChanges.apply (cyclomatic 24) src/scenarioIdentityFiles.ts:157— scenarioIdentityFiles.prepareScenarioIdentityFileChanges.apply has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
featurePropertiesModel.planFeaturePropertiesEdit (cyclomatic 24) src/featurePropertiesModel.ts:40— featurePropertiesModel.planFeaturePropertiesEdit has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCreator.handleCreateNestedScenario (cyclomatic 24) src/scenarioCreator.ts:2269— scenarioCreator.handleCreateNestedScenario has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.runStandaloneFeature (cyclomatic 24) src/phaseSwitcher.ts:5649— PhaseSwitcherProvider.runStandaloneFeature has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.handleScenarioFilesMessage (cyclomatic 24) src/phaseSwitcher.ts:7065— PhaseSwitcherProvider.handleScenarioFilesMessage has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DriveCompletionProvider.buildGherkinCompletionState (cyclomatic 24) src/completionProvider.ts:589— DriveCompletionProvider.buildGherkinCompletionState has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FormExplorerPanel.doRefreshStartedInfobaseProcessState (cyclomatic 24) src/formExplorerPanel.ts:928— FormExplorerPanel.doRefreshStartedInfobaseProcessState has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaControlStepSources.prepareVanessaResultSources.expand (cyclomatic 24) src/vanessaControlStepSources.ts:21— vanessaControlStepSources.prepareVanessaResultSources.expand has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
processCreator.handleCreateProcess (cyclomatic 24) src/processCreator.ts:81— processCreator.handleCreateProcess has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls (cyclomatic 24) src/scenarioCallableCommands.ts:114— scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (scenarioCallableCommands.handleConvertCallableScenario) 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.
create.updateRelationshipPresentation (cyclomatic 24) media/standaloneFeatures.js:463— create.updateRelationshipPresentation has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
scenarioFilesProtocol.projectCompiledScenarioChildren (cyclomatic 23) media/scenarioFilesProtocol.js:277— scenarioFilesProtocol.projectCompiledScenarioChildren has cyclomatic complexity 23 (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.
yamlParameters.document.addEventListener("click") (cyclomatic 23) media/yamlParameters.js:1104— yamlParameters.document.addEventListener("click") has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
vanessaControlProtocol.assessVanessaControlCapabilities (cyclomatic 23) src/vanessaControlProtocol.ts:35— vanessaControlProtocol.assessVanessaControlCapabilities has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 75, 84). 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.
YamlParametersManager.manageProfiles (cyclomatic 23) REDACTED:1773— YamlParametersManager.manageProfiles has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
oneCPlatform.handleManagePlatforms (cyclomatic 23) src/oneCPlatform.ts:510— oneCPlatform.handleManagePlatforms has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stepLibraryModel.mainScenarioItems (cyclomatic 23) src/stepLibraryModel.ts:185— stepLibraryModel.mainScenarioItems has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 190, 194). 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.
processEditorCommands.changeProcessTestSettingsFromEditor (cyclomatic 23) src/processEditorCommands.ts:132— processEditorCommands.changeProcessTestSettingsFromEditor has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PhaseSwitcherProvider.handleScenarioFilesRenamed (cyclomatic 23) src/phaseSwitcher.ts:1860— PhaseSwitcherProvider.handleScenarioFilesRenamed has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
DriveCompletionProvider.buildSemanticStepCompletionList (cyclomatic 23) src/completionProvider.ts:2503— DriveCompletionProvider.buildSemanticStepCompletionList has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 2574, 2537, 2552, …). 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.
scenarioAiDescription.extractScenarioSemanticFactsFromValue (cyclomatic 23) REDACTED:1538— scenarioAiDescription.extractScenarioSemanticFactsFromValue has cyclomatic complexity 23 (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.
DriveHoverProvider.parseScenarioDescription (cyclomatic 23) REDACTED:364— DriveHoverProvider.parseScenarioDescription 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. This is NOT this file's highest cyclomatic complexity: DriveHoverProvider.getYamlFieldHoverDescription (cyclomatic 47) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
vanessaControlBreakpointCommands.registerVanessaBreakpointCommands::act (cyclomatic 23) src/vanessaControlBreakpointCommands.ts:48— vanessaControlBreakpointCommands.registerVanessaBreakpointCommands::act 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.
scenarioSyntaxHighlightProvider.collectScenarioReferenceRanges (cyclomatic 23) src/scenarioSyntaxHighlightProvider.ts:499— scenarioSyntaxHighlightProvider.collectScenarioReferenceRanges 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.
create.render (cyclomatic 23) media/featureProperties.js:57— create.render has cyclomatic complexity 23 (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.
(anonymous) (cyclomatic 23) media/yamlParameters.js:1104— (anonymous) has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
formExplorer.render (cyclomatic 22) media/formExplorer.js:628— formExplorer.render has cyclomatic complexity 22 (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.
phaseSwitcher.createScenarioTypeSection (cyclomatic 22) media/phaseSwitcher.js:1569— phaseSwitcher.createScenarioTypeSection has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 1662, 1601, 1617, …). 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.
scenarioProperties.renderSection (cyclomatic 22) media/scenarioProperties.js:541— scenarioProperties.renderSection 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.
standaloneFeatures.create.showMenu (cyclomatic 22) media/standaloneFeatures.js:164— standaloneFeatures.create.showMenu has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 178, 205, 194, …). 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.
kotMetadataDescription.findKotDescriptionSection (cyclomatic 22) src/kotMetadataDescription.ts:55— kotMetadataDescription.findKotDescriptionSection 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.
ProjectLibraryStore.importLegacy (cyclomatic 22) src/projectLibraryStore.ts:866— ProjectLibraryStore.importLegacy has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 867, 888, 890). 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.
projectDefinitionMatcher.compileProjectDefinitionMatcherInternal.matchPrepared (cyclomatic 22) src/projectDefinitionMatcher.ts:206— projectDefinitionMatcher.compileProjectDefinitionMatcherInternal.matchPrepared 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.
etalonBases.parseEtalonBasesYaml (cyclomatic 22) REDACTED:256— etalonBases.parseEtalonBasesYaml 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.
ScenarioFilesService.renameFile (cyclomatic 22) src/scenarioFilesService.ts:409— ScenarioFilesService.renameFile has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScenarioPropertiesAttachments.importUris (cyclomatic 22) src/scenarioPropertiesAttachments.ts:141— ScenarioPropertiesAttachments.importUris has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ScenarioPropertiesPanel.constructor (cyclomatic 22) src/scenarioPropertiesPanel.ts:333— ScenarioPropertiesPanel.constructor has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 373, 343, 358, …). 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.
vanessaControlRunLog.findManagedVanessaRunLog (cyclomatic 22) src/vanessaControlRunLog.ts:7— vanessaControlRunLog.findManagedVanessaRunLog has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PhaseSwitcherProvider.refreshScenarioHighlightsBySelectedRunSource (cyclomatic 22) src/phaseSwitcher.ts:3627— PhaseSwitcherProvider.refreshScenarioHighlightsBySelectedRunSource 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.
PhaseSwitcherProvider.openFeatureFromTrackedLogSession (cyclomatic 22) src/phaseSwitcher.ts:12839— PhaseSwitcherProvider.openFeatureFromTrackedLogSession has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProjectDefinitionProvider.provideDefinition (cyclomatic 22) src/projectDefinitionNavigation.ts:101— ProjectDefinitionProvider.provideDefinition has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioAiDescription.summarizeScenarioProcessStageTitle (cyclomatic 22) REDACTED:1922— scenarioAiDescription.summarizeScenarioProcessStageTitle 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.
DriveHoverProvider.provideHover (cyclomatic 22) REDACTED:1194— DriveHoverProvider.provideHover has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: DriveHoverProvider.getYamlFieldHoverDescription (cyclomatic 47) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
scenarioDiagnostics.getKotDescriptionState (cyclomatic 22) src/scenarioDiagnostics.ts:281— scenarioDiagnostics.getKotDescriptionState 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.
FormExplorerPanel.refreshNativeSteps (cyclomatic 22) src/formExplorerPanel.ts:632— FormExplorerPanel.refreshNativeSteps has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCallableConversion.rewriteCallableCall (cyclomatic 22) src/scenarioCallableConversion.ts:227— scenarioCallableConversion.rewriteCallableCall has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
stepCatalogTemplateXml.writeCatalogPublication (cyclomatic 22) src/stepCatalogTemplateXml.ts:378— stepCatalogTemplateXml.writeCatalogPublication has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
renderFields (cyclomatic 22) media/kotWorkspace.js:124— renderFields has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 39 function items inside it that branch ((anonymous)::onchange, a function literal at line 150, a function literal at line 127, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create.showMenu (cyclomatic 22) media/standaloneFeatures.js:164— create.showMenu has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 178, 205, 194, …). 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.
formExplorer.filterElementNode (cyclomatic 21) media/formExplorer.js:2603— formExplorer.filterElementNode has cyclomatic complexity 21 (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.
infobaseVanessaClients.renderClientRows (cyclomatic 21) media/infobaseVanessaClients.js:5— infobaseVanessaClients.renderClientRows has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 9, button). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
phaseSwitcher.enableAssembleControls (cyclomatic 21) media/phaseSwitcher.js:583— phaseSwitcher.enableAssembleControls 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.
phaseSwitcher.bindProjectOrderingTarget (cyclomatic 21) media/phaseSwitcher.js:1534— phaseSwitcher.bindProjectOrderingTarget has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 4 function items inside it that branch (a function literal at line 1549, valid, a function literal at line 1540, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
standaloneFeatures.create.row (cyclomatic 21) media/standaloneFeatures.js:240— standaloneFeatures.create.row has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 259, 250). 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.
stepLibraryProtocol.reconcileCategorySelection (cyclomatic 21) media/stepLibraryProtocol.js:475— stepLibraryProtocol.reconcileCategorySelection has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
vanessaControlVariables.parseVanessaVariables (cyclomatic 21) src/vanessaControlVariables.ts:22— vanessaControlVariables.parseVanessaVariables 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.
VanessaRuntimeDiagnostics.screenshot (cyclomatic 21) src/vanessaControlDiagnostics.ts:111— VanessaRuntimeDiagnostics.screenshot has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (capture). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ScenarioFilesService.prepareDrop (cyclomatic 21) src/scenarioFilesService.ts:453— ScenarioFilesService.prepareDrop has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StandaloneFeatureService.scanDirectory (cyclomatic 21) src/standaloneFeatureService.ts:483— StandaloneFeatureService.scanDirectory 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.
infobaseManager.mergeMetadataEntries (cyclomatic 21) src/infobaseManager.ts:576— infobaseManager.mergeMetadataEntries has cyclomatic complexity 21 (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.
scenarioPropertiesLibrarySupport.createPropertiesLibrarySupport.createFeatureController (cyclomatic 21) src/scenarioPropertiesLibrarySupport.ts:57— scenarioPropertiesLibrarySupport.createPropertiesLibrarySupport.createFeatureController has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 67, 59, 62). 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.
ScenarioPropertiesPanel.handleActiveEditor (cyclomatic 21) src/scenarioPropertiesPanel.ts:500— ScenarioPropertiesPanel.handleActiveEditor has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 501). 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.
PhaseSwitcherProvider.openVanessaStandaloneDebug (cyclomatic 21) src/phaseSwitcher.ts:6833— PhaseSwitcherProvider.openVanessaStandaloneDebug has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider._groupAndSortTestData (cyclomatic 21) src/phaseSwitcher.ts:9224— PhaseSwitcherProvider._groupAndSortTestData has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DriveCompletionProvider.buildFormExplorerElementReferenceCompletionList (cyclomatic 21) src/completionProvider.ts:1522— DriveCompletionProvider.buildFormExplorerElementReferenceCompletionList has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 1566, 1551, 1531, …). 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.
configurationDiffAiReport.buildConfigurationDiffPrompt (cyclomatic 21) REDACTED:1592— configurationDiffAiReport.buildConfigurationDiffPrompt has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
kotWorkspaceConfiguration.createWorkspaceSettingsSession (cyclomatic 21) src/kotWorkspaceConfiguration.ts:5— kotWorkspaceConfiguration.createWorkspaceSettingsSession has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 22, a function literal at line 30, folder, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
vanessaControlConnection.registerVanessaControl.startConfigured (cyclomatic 21) src/vanessaControlConnection.ts:156— vanessaControlConnection.registerVanessaControl.startConfigured has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
userStepLibraryBuilder.buildUserStepLibrary (cyclomatic 21) src/userStepLibraryBuilder.ts:55— userStepLibraryBuilder.buildUserStepLibrary has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
userStepCommands.createUserStepCommand (cyclomatic 21) src/userStepCommands.ts:140— userStepCommands.createUserStepCommand has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
FormExplorerPanel.refreshMcpSnapshot (cyclomatic 21) src/formExplorerPanel.ts:1408— FormExplorerPanel.refreshMcpSnapshot has cyclomatic complexity 21 (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.
scenarioCallableConversion.exportToNested (cyclomatic 21) src/scenarioCallableConversion.ts:166— scenarioCallableConversion.exportToNested has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extension.createProjectDefinitionIndexService (cyclomatic 21) REDACTED:231— extension.createProjectDefinitionIndexService has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 278, 285, 240, …). 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.
createTransferController (cyclomatic 21) media/scenarioFilesProtocol.js:339— createTransferController has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function items inside it that branch (handleMessage, beginDrop, startNextTransfer, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create.row (cyclomatic 21) media/standaloneFeatures.js:240— create.row has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 259, 250, 258). 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.
infobaseSidebar.makeRow (cyclomatic 20) media/infobaseSidebar.js:111— infobaseSidebar.makeRow has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
infobaseVanessaClients.create (cyclomatic 20) media/infobaseVanessaClients.js:15— infobaseVanessaClients.create has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 42, 54). 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.
kotWorkspace.window.addEventListener("message") (cyclomatic 20) media/kotWorkspace.js:275— kotWorkspace.window.addEventListener("message") has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 is NOT this file's highest cyclomatic complexity: kotWorkspace.renderFields (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
phaseSwitcher.enablePhaseControls (cyclomatic 20) media/phaseSwitcher.js:200— phaseSwitcher.enablePhaseControls has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 230, 214, 210). 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.
stepLibrary.createTreeNode (cyclomatic 20) media/stepLibrary.js:439— stepLibrary.createTreeNode has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
yamlParameters.document.addEventListener("input") (cyclomatic 20) media/yamlParameters.js:1188— yamlParameters.document.addEventListener("input") 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.
userStepLibraryState.inspectUserStepLibrary (cyclomatic 20) src/userStepLibraryState.ts:126— userStepLibraryState.inspectUserStepLibrary 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.
scenarioPropertiesModel.fieldEdit (cyclomatic 20) src/scenarioPropertiesModel.ts:178— scenarioPropertiesModel.fieldEdit 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.
VanessaControlSession.readResults (cyclomatic 20) src/vanessaControlSession.ts:715— VanessaControlSession.readResults has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaDebugClientConfiguration.advancedClient (cyclomatic 20) src/vanessaDebugClientConfiguration.ts:91— vanessaDebugClientConfiguration.advancedClient has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gherkinSyntaxValidator.maskVanessaSections (cyclomatic 20) src/gherkinSyntaxValidator.js:9— gherkinSyntaxValidator.maskVanessaSections has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 13, 24). 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.
ProjectDefinitionReferenceService.#readReferenceFile (cyclomatic 20) src/projectDefinitionReferences.ts:384— ProjectDefinitionReferenceService.#readReferenceFile 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.
scenarioCreator.handleManageSystemFunctions (cyclomatic 20) src/scenarioCreator.ts:1330— scenarioCreator.handleManageSystemFunctions has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.pollLiveRunLogWatcher (cyclomatic 20) src/phaseSwitcher.ts:4147— PhaseSwitcherProvider.pollLiveRunLogWatcher 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.
commandHandlers.findFileFromText (cyclomatic 20) REDACTED:41— commandHandlers.findFileFromText 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.
commandHandlers.alignNestedScenarioCallParametersInText (cyclomatic 20) REDACTED:1495— commandHandlers.alignNestedScenarioCallParametersInText 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.
DriveCompletionProvider.fuzzyMatch (cyclomatic 20) src/completionProvider.ts:2650— DriveCompletionProvider.fuzzyMatch 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.
vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand.render (cyclomatic 20) src/vanessaControlYamlTrialCommands.ts:35— vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand.render 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.
formExplorerStepSuggestions.buildVanessaMultilineSuggestions (cyclomatic 20) src/formExplorerStepSuggestions.ts:943— formExplorerStepSuggestions.buildVanessaMultilineSuggestions 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.
infobaseManager.document.body.addEventListener("click") (cyclomatic 19) media/infobaseManager.js:976— infobaseManager.document.body.addEventListener("click") has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
yamlParameters.additionalRowHtml (cyclomatic 19) media/yamlParameters.js:500— yamlParameters.additionalRowHtml has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
phaseSwitcherMetadata.findKotMetadataStructure (cyclomatic 19) src/phaseSwitcherMetadata.ts:179— phaseSwitcherMetadata.findKotMetadataStructure 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.
scenarioParameterUtils.parseScenarioParameterDefinitions (cyclomatic 19) src/scenarioParameterUtils.ts:102— scenarioParameterUtils.parseScenarioParameterDefinitions has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 106, 127). 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.
VanessaDebugClientStore.read (cyclomatic 19) src/vanessaDebugClients.ts:65— VanessaDebugClientStore.read has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
VanessaControlSession.mutate (cyclomatic 19) src/vanessaControlSession.ts:659— VanessaControlSession.mutate has cyclomatic complexity 19 (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.
vanessaDebugClientConfiguration.configureVanessaDebugClientSelection (cyclomatic 19) src/vanessaDebugClientConfiguration.ts:135— vanessaDebugClientConfiguration.configureVanessaDebugClientSelection has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
etalonBases.parseEtalonBaseUserProfiles (cyclomatic 19) REDACTED:99— etalonBases.parseEtalonBaseUserProfiles 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.
compilerFormatDiagnostics.collectCompilerFormatIssues::inspect (cyclomatic 19) src/compilerFormatDiagnostics.ts:61— compilerFormatDiagnostics.collectCompilerFormatIssues::inspect 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.
vanessaControlSourceMapping.mapYamlLineToFeatures (cyclomatic 19) src/vanessaControlSourceMapping.ts:81— vanessaControlSourceMapping.mapYamlLineToFeatures has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ScenarioRelationshipService.buildEnrichedStateValue (cyclomatic 19) src/scenarioRelationshipService.ts:240— ScenarioRelationshipService.buildEnrichedStateValue has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
featureRenameCommands.renameExportScenario (cyclomatic 19) src/featureRenameCommands.ts:98— featureRenameCommands.renameExportScenario has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scenarioCreator.handleSyncTestSettingsFromScenario (cyclomatic 19) src/scenarioCreator.ts:1231— scenarioCreator.handleSyncTestSettingsFromScenario has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScenarioPropertiesPanel.post (cyclomatic 19) src/scenarioPropertiesPanel.ts:705— ScenarioPropertiesPanel.post 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.
PhaseSwitcherProvider.applyTrackedRunStepSyncLogLine (cyclomatic 19) src/phaseSwitcher.ts:3732— PhaseSwitcherProvider.applyTrackedRunStepSyncLogLine 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.
PhaseSwitcherProvider.buildNestedScenarioCallInsertTextForUri (cyclomatic 19) src/phaseSwitcher.ts:4530— PhaseSwitcherProvider.buildNestedScenarioCallInsertTextForUri has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette (cyclomatic 19) src/phaseSwitcher.ts:6480— PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6508, 6495). 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. This shape REPEATS in the file: one other method here (PhaseSwitcherProvider.pickScenarioForVanessaRun) 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.
PhaseSwitcherProvider.pickScenarioForVanessaRun (cyclomatic 19) src/phaseSwitcher.ts:6716— PhaseSwitcherProvider.pickScenarioForVanessaRun has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6744, 6731). 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. This shape REPEATS in the file: one other method here (PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette) 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.
PhaseSwitcherProvider.resolveScenarioLaunchTarget (cyclomatic 19) src/phaseSwitcher.ts:9909— PhaseSwitcherProvider.resolveScenarioLaunchTarget 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.
gherkinInsertionContext.getGherkinInsertionContext (cyclomatic 19) src/gherkinInsertionContext.ts:190— gherkinInsertionContext.getGherkinInsertionContext has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
projectMetadataConflictCommand.registerMetadataConflictCommand (cyclomatic 19) src/projectMetadataConflictCommand.ts:9— projectMetadataConflictCommand.registerMetadataConflictCommand has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 14, 47, 58). 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.
VanessaInfobaseClients.stateFor (cyclomatic 19) src/vanessaInfobaseClients.ts:104— VanessaInfobaseClients.stateFor has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
userStepCommands.dumpUserStepLibraryCommand (cyclomatic 19) src/userStepCommands.ts:480— userStepCommands.dumpUserStepLibraryCommand has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCallableConversion.nestedToExport (cyclomatic 19) src/scenarioCallableConversion.ts:101— scenarioCallableConversion.nestedToExport has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 115, 107, 135). 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.
(anonymous) (cyclomatic 19) media/infobaseManager.js:976— (anonymous) has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
additionalValueError (cyclomatic 19) media/yamlParameters.js:449— additionalValueError 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.
formExplorer.renderSuggestedStepsBody (cyclomatic 18) media/formExplorer.js:1459— formExplorer.renderSuggestedStepsBody has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorer.collectFormTableEntries (cyclomatic 18) media/formExplorer.js:1691— formExplorer.collectFormTableEntries has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (tryAdd, collectFromElements, a function literal at line 1770). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
formExplorer.flattenElements (cyclomatic 18) media/formExplorer.js:2633— formExplorer.flattenElements has cyclomatic 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.
phaseSwitcher.showContextMenuAt (cyclomatic 18) media/phaseSwitcher.js:2755— phaseSwitcher.showContextMenuAt has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2773, 2795). 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.
scenarioProperties.window.addEventListener("message") (cyclomatic 18) media/scenarioProperties.js:724— scenarioProperties.window.addEventListener("message") has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaParameterParser.parseVanessaParameterSources (cyclomatic 18) REDACTED:18— vanessaParameterParser.parseVanessaParameterSources has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
compilerYamlBlocks.sectionsForEdit (cyclomatic 18) src/compilerYamlBlocks.ts:9— compilerYamlBlocks.sectionsForEdit 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.
oneCInfobaseConnection.parseInfobaseConnectionString (cyclomatic 18) src/oneCInfobaseConnection.ts:66— oneCInfobaseConnection.parseInfobaseConnectionString has cyclomatic 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.
vanessaDebugClientConfiguration.editClient (cyclomatic 18) src/vanessaDebugClientConfiguration.ts:40— vanessaDebugClientConfiguration.editClient has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProjectDefinitionReferenceService.findReferencesForDefinitions (cyclomatic 18) src/projectDefinitionReferences.ts:172— ProjectDefinitionReferenceService.findReferencesForDefinitions 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.
vanessaParameterCatalog.loadVanessaParameterCatalogSnapshot (cyclomatic 18) src/vanessaParameterCatalog.ts:39— vanessaParameterCatalog.loadVanessaParameterCatalogSnapshot has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compilerArtifacts.parseCompilerErrorXml (cyclomatic 18) src/compilerArtifacts.ts:359— compilerArtifacts.parseCompilerErrorXml has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
featureCreator.createFeature (cyclomatic 18) src/featureCreator.ts:54— featureCreator.createFeature has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
infobasePicker.updateInfobaseInLauncher (cyclomatic 18) REDACTED:431— infobasePicker.updateInfobaseInLauncher 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.
infobaseManager.promptNewInfobaseTarget (cyclomatic 18) src/infobaseManager.ts:1488— infobaseManager.promptNewInfobaseTarget has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
featureEditorActions.scanFeatureStructure (cyclomatic 18) src/featureEditorActions.ts:63— featureEditorActions.scanFeatureStructure has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
PhaseSwitcherProvider.applyFeatureStepSyncLogLine (cyclomatic 18) src/phaseSwitcher.ts:3415— PhaseSwitcherProvider.applyFeatureStepSyncLogLine has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.addScenarioToFavoritesByUri (cyclomatic 18) src/phaseSwitcher.ts:4690— PhaseSwitcherProvider.addScenarioToFavoritesByUri 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.
PhaseSwitcherProvider.changeScenarioGroup (cyclomatic 18) src/phaseSwitcher.ts:5852— PhaseSwitcherProvider.changeScenarioGroup has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
PhaseSwitcherProvider.buildRunArtifactsState (cyclomatic 18) src/phaseSwitcher.ts:9672— PhaseSwitcherProvider.buildRunArtifactsState has cyclomatic 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.
commandHandlers.clearAndFillNestedScenarios::progressHandler (cyclomatic 18) REDACTED:1116— commandHandlers.clearAndFillNestedScenarios::progressHandler has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VanessaFormExplorerSource.refresh (cyclomatic 18) src/vanessaControlFormSource.ts:53— VanessaFormExplorerSource.refresh has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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.
DriveCompletionProvider.collectScenarioVariableDefinitionsBeforeLine (cyclomatic 18) src/completionProvider.ts:1921— DriveCompletionProvider.collectScenarioVariableDefinitionsBeforeLine 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.
configurationDiffAiReport.compactPatchText (cyclomatic 18) REDACTED:1419— configurationDiffAiReport.compactPatchText has cyclomatic 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.
scenarioAiDescription.buildScenarioBodyChunks (cyclomatic 18) REDACTED:792— scenarioAiDescription.buildScenarioBodyChunks 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.
scenarioAiDescription.buildScenarioProcessStageFragments (cyclomatic 18) REDACTED:2145— scenarioAiDescription.buildScenarioProcessStageFragments 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.
scenarioAiDescription.buildDeterministicCheckedItems (cyclomatic 18) REDACTED:2351— scenarioAiDescription.buildDeterministicCheckedItems 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.
scenarioAiDescription.buildScenarioCoverageGroups (cyclomatic 18) REDACTED:2693— scenarioAiDescription.buildScenarioCoverageGroups has cyclomatic 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.
scenarioPropertiesActions.createScenarioLaunchSettings (cyclomatic 18) src/scenarioPropertiesActions.ts:43— scenarioPropertiesActions.createScenarioLaunchSettings has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
VanessaInfobaseClients.adoptObservedRenames (cyclomatic 18) src/vanessaInfobaseClients.ts:223— VanessaInfobaseClients.adoptObservedRenames has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StepLibrarySidebarIndex.children (cyclomatic 18) src/stepLibrarySidebarModel.ts:467— StepLibrarySidebarIndex.children has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
formExplorerStepSuggestions.buildElementContext (cyclomatic 18) src/formExplorerStepSuggestions.ts:682— formExplorerStepSuggestions.buildElementContext has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FormExplorerPanel.resolveActualSnapshotPath (cyclomatic 18) src/formExplorerPanel.ts:1004— FormExplorerPanel.resolveActualSnapshotPath has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
FormExplorerPanel.startBridge (cyclomatic 18) src/formExplorerPanel.ts:1265— FormExplorerPanel.startBridge 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.
extension.collectKotDescriptionContentRanges (cyclomatic 18) REDACTED:3734— extension.collectKotDescriptionContentRanges 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.
(anonymous) (cyclomatic 18) media/scenarioProperties.js:724— (anonymous) 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.
formExplorer.renderSectionCard (cyclomatic 17) media/formExplorer.js:2320— formExplorer.renderSectionCard has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
infobaseSidebar.clientRows (cyclomatic 17) media/infobaseSidebar.js:210— infobaseSidebar.clientRows has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
phaseSwitcherProtocol.parseRelationshipState (cyclomatic 17) media/phaseSwitcherProtocol.js:34— phaseSwitcherProtocol.parseRelationshipState has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 43, 73). 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.
scenarioProperties.rekey (cyclomatic 17) media/scenarioProperties.js:121— scenarioProperties.rekey 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.
stepLibrary.filteredItems (cyclomatic 17) media/stepLibrary.js:281— stepLibrary.filteredItems has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
stepLibrarySidebar.requestChildren (cyclomatic 17) media/stepLibrarySidebar.js:695— stepLibrarySidebar.requestChildren 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.
yamlParameters.inspectParameter (cyclomatic 17) media/yamlParameters.js:22— yamlParameters.inspectParameter 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.
bslStepSourceParser.evaluateStaticExpression (cyclomatic 17) src/bslStepSourceParser.ts:356— bslStepSourceParser.evaluateStaticExpression has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (primary, expression). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
phaseSwitcherMetadata.isLikelyValidKotMetadataBlockLines (cyclomatic 17) src/phaseSwitcherMetadata.ts:435— phaseSwitcherMetadata.isLikelyValidKotMetadataBlockLines 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.
projectFormat.projectFormat (cyclomatic 17) src/projectFormat.ts:26— projectFormat.projectFormat 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.
scenarioCompilerSyntax.validPreprocessorExpression (cyclomatic 17) src/scenarioCompilerSyntax.ts:86— scenarioCompilerSyntax.validPreprocessorExpression 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.
vanessaControlForms.parseVanessaFormElement (cyclomatic 17) src/vanessaControlForms.ts:77— vanessaControlForms.parseVanessaFormElement 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.
VanessaExecutionHighlighter.renderMany (cyclomatic 17) src/vanessaControlHighlighting.ts:38— VanessaExecutionHighlighter.renderMany 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.
VanessaRuntimeClients.apply (cyclomatic 17) src/vanessaControlClients.ts:105— VanessaRuntimeClients.apply 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.
VanessaControlSession.withTestClientControl (cyclomatic 17) src/vanessaControlSession.ts:167— VanessaControlSession.withTestClientControl has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 171, 170). 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.
VanessaControlSession.reloadSavedFeature (cyclomatic 17) src/vanessaControlSession.ts:613— VanessaControlSession.reloadSavedFeature has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
ProjectDefinitionIndexService.#enumerate (cyclomatic 17) src/projectDefinitionIndexService.ts:683— ProjectDefinitionIndexService.#enumerate has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
compilerArtifacts.decodeXmlText (cyclomatic 17) src/compilerArtifacts.ts:198— compilerArtifacts.decodeXmlText has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 200). 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.
scenarioYamlMutations.updateNestedScenarioNameReferencesInScenarioContent (cyclomatic 17) src/scenarioYamlMutations.ts:290— scenarioYamlMutations.updateNestedScenarioNameReferencesInScenarioContent 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.
projectDefinitionDeletion.deleteExportScenario (cyclomatic 17) src/projectDefinitionDeletion.ts:289— projectDefinitionDeletion.deleteExportScenario has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaRunLog.extractFailedStep (cyclomatic 17) REDACTED:23— vanessaRunLog.extractFailedStep 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.
ScenarioRelationshipIndex.fromCatalog (cyclomatic 17) src/scenarioRelationshipIndex.ts:35— ScenarioRelationshipIndex.fromCatalog has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScenarioFilesService.deleteFile (cyclomatic 17) src/scenarioFilesService.ts:351— ScenarioFilesService.deleteFile 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.
StandaloneFeatureService.moveFeature (cyclomatic 17) src/standaloneFeatureService.ts:347— StandaloneFeatureService.moveFeature has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 348, 373). 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.
infobaseManager.updateInfobaseConfigurationInteractive (cyclomatic 17) src/infobaseManager.ts:2469— infobaseManager.updateInfobaseConfigurationInteractive has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCreator.handleChangeTestSettingsUserProfileFromEditor (cyclomatic 17) src/scenarioCreator.ts:1149— scenarioCreator.handleChangeTestSettingsUserProfileFromEditor has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioPropertiesCatalogPresentation.applyPropertyCatalogPresentation (cyclomatic 17) src/scenarioPropertiesCatalogPresentation.ts:5— scenarioPropertiesCatalogPresentation.applyPropertyCatalogPresentation has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
PhaseSwitcherProvider.applyScenarioRuntimeRenamePlan (cyclomatic 17) src/phaseSwitcher.ts:1183— PhaseSwitcherProvider.applyScenarioRuntimeRenamePlan has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhaseSwitcherProvider.temporarilyMoveDisabledScenarioTestFilesForBuild (cyclomatic 17) src/phaseSwitcher.ts:1383— PhaseSwitcherProvider.temporarilyMoveDisabledScenarioTestFilesForBuild 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.
PhaseSwitcherProvider.handleScenarioSourceSaved (cyclomatic 17) src/phaseSwitcher.ts:1643— PhaseSwitcherProvider.handleScenarioSourceSaved has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.captureFailedStepHighlight (cyclomatic 17) src/phaseSwitcher.ts:2993— PhaseSwitcherProvider.captureFailedStepHighlight 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.
PhaseSwitcherProvider.pollFeatureStepTracker (cyclomatic 17) src/phaseSwitcher.ts:3524— PhaseSwitcherProvider.pollFeatureStepTracker has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.getScenarioDisplayedRunState (cyclomatic 17) src/phaseSwitcher.ts:4031— PhaseSwitcherProvider.getScenarioDisplayedRunState 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.
PhaseSwitcherProvider._sendInitialState (cyclomatic 17) src/phaseSwitcher.ts:7663— PhaseSwitcherProvider._sendInitialState has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.verifyCompilerBuildPreflight (cyclomatic 17) src/phaseSwitcher.ts:8388— PhaseSwitcherProvider.verifyCompilerBuildPreflight has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
compilerYamlBlockEditor.addCompilerYamlBlockCommand (cyclomatic 17) src/compilerYamlBlockEditor.ts:37— compilerYamlBlockEditor.addCompilerYamlBlockCommand has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerEnrichment.enrichFormExplorerSnapshot (cyclomatic 17) REDACTED:873— formExplorerEnrichment.enrichFormExplorerSnapshot 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.
exportScenarioCreator.planExportScenarioEdit (cyclomatic 17) src/exportScenarioCreator.ts:206— exportScenarioCreator.planExportScenarioEdit has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
kotWorkspaceProtocol.parseKotWorkspaceRequest (cyclomatic 17) src/kotWorkspaceProtocol.ts:14— kotWorkspaceProtocol.parseKotWorkspaceRequest 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.
kotProjectSetup.planNewProject (cyclomatic 17) src/kotProjectSetup.ts:95— kotProjectSetup.planNewProject 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.
kotProjectSetup.applySetupFiles (cyclomatic 17) src/kotProjectSetup.ts:118— kotProjectSetup.applySetupFiles has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vanessaControlFormToolCommands.registerVanessaFormToolCommands (cyclomatic 17) src/vanessaControlFormToolCommands.ts:6— vanessaControlFormToolCommands.registerVanessaFormToolCommands has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 10, 15, 31). 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.
vanessaControlAuthoringCommands.registerVanessaAuthoringCommands::captureTarget (cyclomatic 17) src/vanessaControlAuthoringCommands.ts:17— vanessaControlAuthoringCommands.registerVanessaAuthoringCommands::captureTarget has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
userStepCreator.ensureUserStepRuntimeContext (cyclomatic 17) src/userStepCreator.ts:67— userStepCreator.ensureUserStepRuntimeContext has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
infobaseSidebarProvider.parseInfobaseSidebarMessage (cyclomatic 17) src/infobaseSidebarProvider.ts:117— infobaseSidebarProvider.parseInfobaseSidebarMessage 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.
FormExplorerPanel.chooseClientWindow (cyclomatic 17) src/formExplorerPanel.ts:1381— FormExplorerPanel.chooseClientWindow has cyclomatic 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 2 function items inside it that branch (a function literal at line 1389, current). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
processCreator.handleEditProcessSteps (cyclomatic 17) src/processCreator.ts:218— processCreator.handleEditProcessSteps 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.
nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.importUserCatalogs (cyclomatic 17) src/nativeProjectCatalogSettings.ts:131— nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.importUserCatalogs has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
dropEmptyDuplicateDisplayColumns (cyclomatic 17) media/formExplorer.js:2038— dropEmptyDuplicateDisplayColumns has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 10 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
normalize (cyclomatic 17) media/yamlBuildParameterState.js:25— normalize has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
app.renderPickerOptions (cyclomatic 16) docs/ux/first-run/app.js:63— app.renderPickerOptions has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 is NOT this file's highest cyclomatic complexity: app.renderSettingFields (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
formExplorer.renderTabs (cyclomatic 16) media/formExplorer.js:1190— formExplorer.renderTabs has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
phaseSwitcher.applyScenarioSearch (cyclomatic 16) media/phaseSwitcher.js:846— phaseSwitcher.applyScenarioSearch has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 861, 882, 893). 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.
phaseSwitcher.handleScenarioRowClick (cyclomatic 16) media/phaseSwitcher.js:2311— phaseSwitcher.handleScenarioRowClick has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioPropertiesProtocol.normalizeState (cyclomatic 16) media/scenarioPropertiesProtocol.js:93— scenarioPropertiesProtocol.normalizeState has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
stepLibrarySidebar.appendNode (cyclomatic 16) media/stepLibrarySidebar.js:487— stepLibrarySidebar.appendNode has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
stepLibrarySidebarProtocol.parseRelationshipState (cyclomatic 16) media/stepLibrarySidebarProtocol.js:36— stepLibrarySidebarProtocol.parseRelationshipState has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (normalizeRelationships). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ScenarioYamlDocument.findRecordFieldsForEdit (cyclomatic 16) src/scenarioYamlDocument.ts:557— ScenarioYamlDocument.findRecordFieldsForEdit 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.
ProjectLibraryStore.discover::visit (cyclomatic 16) src/projectLibraryStore.ts:272— ProjectLibraryStore.discover::visit 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.
workspaceScanner.collectFilesFromScanDirectory (cyclomatic 16) src/workspaceScanner.ts:73— workspaceScanner.collectFilesFromScanDirectory has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 94). 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.
VanessaRuntimeForms.steps (cyclomatic 16) src/vanessaControlForms.ts:129— VanessaRuntimeForms.steps has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaDebugClients.validateVanessaDebugClientSelection (cyclomatic 16) src/vanessaDebugClients.ts:171— vanessaDebugClients.validateVanessaDebugClientSelection has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
stepCatalogHttp.requestHttpsBytes (cyclomatic 16) src/stepCatalogHttp.ts:53— stepCatalogHttp.requestHttpsBytes has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 83, 124, 67, …). 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.
compilerModelDbStatus.inspectCompilerModelDbStatus (cyclomatic 16) src/compilerModelDbStatus.ts:15— compilerModelDbStatus.inspectCompilerModelDbStatus has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
startupInfobase.ensureSharedStartupInfobaseReady::performEnsure (cyclomatic 16) src/startupInfobase.ts:385— startupInfobase.ensureSharedStartupInfobaseReady::performEnsure has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaRunLog.extractLastStepLocation (cyclomatic 16) REDACTED:377— vanessaRunLog.extractLastStepLocation 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.
featureCreator.generateFeatureJson (cyclomatic 16) src/featureCreator.ts:113— featureCreator.generateFeatureJson has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
infobasePicker.registerInfobaseInLauncher (cyclomatic 16) REDACTED:294— infobasePicker.registerInfobaseInLauncher 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.
SettingsInventory.discover::walk (cyclomatic 16) src/scenarioPropertiesPanel.ts:137— SettingsInventory.discover::walk 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.
ScenarioPropertiesPanel.bind (cyclomatic 16) src/scenarioPropertiesPanel.ts:527— ScenarioPropertiesPanel.bind 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.
PhaseSwitcherProvider.readStoredScenarioCustomInfobasePaths (cyclomatic 16) src/phaseSwitcher.ts:9741— PhaseSwitcherProvider.readStoredScenarioCustomInfobasePaths has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PhaseSwitcherProvider.removeScenarioCustomInfobasePathsForUris (cyclomatic 16) src/phaseSwitcher.ts:9853— PhaseSwitcherProvider.removeScenarioCustomInfobasePathsForUris has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
formExplorerLiveSnapshot.resolveActualLiveSnapshotPath (cyclomatic 16) src/formExplorerLiveSnapshot.ts:45— formExplorerLiveSnapshot.resolveActualLiveSnapshotPath has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
configurationDiffAiReport.describeConfigurationPath (cyclomatic 16) REDACTED:400— configurationDiffAiReport.describeConfigurationPath has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
projectMetadataConflicts.metadataKind (cyclomatic 16) src/projectMetadataConflicts.ts:14— projectMetadataConflicts.metadataKind has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
vanessaControlSelection.prepareVanessaSelection (cyclomatic 16) src/vanessaControlSelection.ts:7— vanessaControlSelection.prepareVanessaSelection has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerExtensionGenerator.pickFormExplorerLaunchAuthentication (cyclomatic 16) REDACTED:496— formExplorerExtensionGenerator.pickFormExplorerLaunchAuthentication has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerExtensionGenerator.collectManagedForms (cyclomatic 16) REDACTED:1315— formExplorerExtensionGenerator.collectManagedForms 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.
userStepLibraryDump.dumpUserStepLibrary (cyclomatic 16) src/userStepLibraryDump.ts:13— userStepLibraryDump.dumpUserStepLibrary has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
stepLibrarySidebarModel.definitionNode (cyclomatic 16) src/stepLibrarySidebarModel.ts:143— stepLibrarySidebarModel.definitionNode has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StepLibrarySidebarProvider.runItemAction (cyclomatic 16) src/stepLibrarySidebarProvider.ts:462— StepLibrarySidebarProvider.runItemAction 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.
InfobaseSidebarProvider.handleMessage (cyclomatic 16) src/infobaseSidebarProvider.ts:327— InfobaseSidebarProvider.handleMessage has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
InfobaseSidebarProvider.runAction (cyclomatic 16) src/infobaseSidebarProvider.ts:378— InfobaseSidebarProvider.runAction has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InfobaseSidebarProvider.load (cyclomatic 16) src/infobaseSidebarProvider.ts:422— InfobaseSidebarProvider.load has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerStepSuggestions.detectElementKind (cyclomatic 16) src/formExplorerStepSuggestions.ts:513— formExplorerStepSuggestions.detectElementKind has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FormExplorerPanel.constructor (cyclomatic 16) src/formExplorerPanel.ts:145— FormExplorerPanel.constructor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 154, 175, 183). 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.
vanessaControlFormLanguage.translateVanessaFormSteps (cyclomatic 16) REDACTED:33— vanessaControlFormLanguage.translateVanessaFormSteps has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 35, 50). 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.
create.accept (cyclomatic 16) media/featureProperties.js:125— create.accept 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.
fieldControl::commit (cyclomatic 16) media/scenarioProperties.js:338— fieldControl::commit has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
startStepLibraryClient (cyclomatic 16) media/stepLibrary.js:1— startStepLibraryClient has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: the first wizard prompt opens before slow scenario discovery completes test/scenarioCreator.test.ts:284— This test starts work it did not wait for (`running`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Deprecated: eslint REDACTED:3164— eslint 9.39.4, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Repeated repair: src/stepCatalogService.ts src/stepCatalogService.ts:149— src/stepCatalogService.ts changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is WorkspaceStepCatalogCoordinator.resolveCatalog at line 149), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: refine visual step library”; “fix: refresh catalogs for external resources”; “fix: exclude step categories from IntelliSense”; “fix: harden step catalog resolution and publication”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:33:17 +07:00' --until='2026-11-02 18:33:17 +07:00' --full-history --no-merges -- src/stepCatalogService.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
ScenarioDiagnosticsProvider.validateDocument (cognitive 203) src/scenarioDiagnostics.ts:1540— ScenarioDiagnosticsProvider.validateDocument has cognitive complexity 203 (threshold 15). Drivers by points: if/else 44 (93 pts), ternaries 26 (80 pts), boolean chains 20, loops 6 (8 pts), error handling 2 (nesting depth added 105). Of this number, 197 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
VanessaControlSession.run (cognitive 174) src/vanessaControlSession.ts:351— VanessaControlSession.run has cognitive complexity 174 (threshold 15). Drivers by points: if/else 47 (69 pts), boolean chains 49, ternaries 21 (44 pts), error handling 5 (8 pts), loops 2 (4 pts) (nesting depth added 50). Of this number, 20 points are the body's own statements and 154 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 172) media/phaseSwitcher.js:3201— (anonymous) has cognitive complexity 172 (threshold 15). Drivers by points: if/else 44 (97 pts), boolean chains 36, ternaries 13 (36 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 77). Of this number, 125 points are the body's own statements and 47 belong to 9 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
scenarioCallableCommands.handleConvertCallableScenario (cognitive 167) src/scenarioCallableCommands.ts:83— scenarioCallableCommands.handleConvertCallableScenario has cognitive complexity 167 (threshold 15). Drivers by points: if/else 62 (118 pts), boolean chains 43, ternaries 19 (38 pts), loops 11 (21 pts), error handling 4 (6 pts) (nesting depth added 87). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls) 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.
phaseSwitcher.window.addEventListener("message") (cognitive 148) media/phaseSwitcher.js:3201— phaseSwitcher.window.addEventListener("message") has cognitive complexity 148 (threshold 15). Drivers by points: if/else 44 (97 pts), boolean chains 34, ternaries 6 (14 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 62). Of this number, 117 points are the body's own statements and 31 belong to 8 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhaseSwitcherProvider._handleRunAssembleScriptTypeScript (cognitive 132) src/phaseSwitcher.ts:8443— PhaseSwitcherProvider._handleRunAssembleScriptTypeScript has cognitive complexity 132 (threshold 15). Drivers by points: if/else 65 (87 pts), boolean chains 24, ternaries 7 (11 pts), error handling 4 (5 pts), loops 3 (5 pts) (nesting depth added 29). Most of this is not in the body itself: 6 of the 132 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 8499, a function literal at line 8870, a function literal at line 8900, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
compilerBuildReport.writeCompilerBuildReport (cognitive 130) src/compilerBuildReport.ts:131— compilerBuildReport.writeCompilerBuildReport has cognitive complexity 130 (threshold 15). Drivers by points: if/else 20 (42 pts), ternaries 16 (42 pts), loops 11 (25 pts), boolean chains 21 (nesting depth added 62). Of this number, 124 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesSession.perform (cognitive 129) src/scenarioPropertiesSession.ts:387— ScenarioPropertiesSession.perform has cognitive complexity 129 (threshold 15). Drivers by points: if/else 44 (89 pts), boolean chains 17, ternaries 8 (17 pts), loops 2 (6 pts) (nesting depth added 58). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
formExplorerExtensionGenerator.handleGenerateFormExplorerExtensionCore (cognitive 123) REDACTED:6621— formExplorerExtensionGenerator.handleGenerateFormExplorerExtensionCore has cognitive complexity 123 (threshold 15). Drivers by points: if/else 47 (71 pts), boolean chains 26, ternaries 12 (21 pts), error handling 2 (5 pts) (nesting depth added 36). Of this number, 53 points are the body's own statements and 70 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.resolveWebviewView (cognitive 122) src/phaseSwitcher.ts:7251— PhaseSwitcherProvider.resolveWebviewView has cognitive complexity 122 (threshold 15). Drivers by points: if/else 35 (76 pts), boolean chains 24, ternaries 9 (16 pts), error handling 2 (4 pts), loops 1, match/switch 1 (nesting depth added 50). Most of this is not in the body itself: 7 of the 122 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 7424, 7431, 7638). 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.
(anonymous) (cognitive 121) media/stepLibrarySidebar.js:1008— (anonymous) has cognitive complexity 121 (threshold 15). Drivers by points: if/else 19 (48 pts), boolean chains 30, loops 9 (26 pts), ternaries 7 (16 pts), match/switch 1 (nesting depth added 55). Of this number, 117 points are the body's own statements and 4 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibrarySidebar.window.addEventListener("message") (cognitive 110) media/stepLibrarySidebar.js:1008— stepLibrarySidebar.window.addEventListener("message") has cognitive complexity 110 (threshold 15). Drivers by points: if/else 19 (48 pts), boolean chains 29, loops 9 (26 pts), ternaries 2 (6 pts), match/switch 1 (nesting depth added 50). Of this number, 106 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· records (cognitive 109) · ×1
records (cognitive 109) media/scenarioProperties.js:436— records has cognitive complexity 109 (threshold 15). Drivers by points: if/else 27 (53 pts), ternaries 13 (30 pts), boolean chains 20, loops 3 (5 pts), error handling 1 (nesting depth added 45). Of this number, 90 points are the body's own statements and 19 belong to 18 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectLibraryMetadata.loadProjectScenarioMetadata (cognitive 106) src/projectLibraryMetadata.ts:152— projectLibraryMetadata.loadProjectScenarioMetadata has cognitive complexity 106 (threshold 15). Drivers by points: ternaries 16 (60 pts), if/else 10 (27 pts), loops 6 (11 pts), boolean chains 8 (nesting depth added 66). Of this number, 104 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesModel.applyYamlMapField (cognitive 103) src/scenarioPropertiesModel.ts:366— scenarioPropertiesModel.applyYamlMapField has cognitive complexity 103 (threshold 15). Drivers by points: if/else 18 (45 pts), ternaries 11 (34 pts), boolean chains 19, loops 2 (5 pts) (nesting depth added 53). Of this number, 98 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
create.render (cognitive 96) media/standaloneFeatures.js:578— create.render has cognitive complexity 96 (threshold 15). Drivers by points: if/else 23 (47 pts), ternaries 10 (25 pts), boolean chains 16, loops 4 (8 pts) (nesting depth added 43). Of this number, 58 points are the body's own statements and 38 belong to 15 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlProtocol.parseVanessaControlReply (cognitive 91) src/vanessaControlProtocol.ts:111— vanessaControlProtocol.parseVanessaControlReply has cognitive complexity 91 (threshold 15). Drivers by points: if/else 22 (39 pts), ternaries 12 (29 pts), boolean chains 23 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderDetails (cognitive 90) media/infobaseManager.js:597— renderDetails has cognitive complexity 90 (threshold 15). Drivers by points: if/else 38 (39 pts), boolean chains 38, ternaries 7 (13 pts) (nesting depth added 7). Of this number, 84 points are the body's own statements and 6 belong to 3 function literals inside it that branch. 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.
standaloneFeatures.create.render (cognitive 88) media/standaloneFeatures.js:578— standaloneFeatures.create.render has cognitive complexity 88 (threshold 15). Drivers by points: if/else 23 (47 pts), ternaries 7 (17 pts), boolean chains 16, loops 4 (8 pts) (nesting depth added 38). Of this number, 53 points are the body's own statements and 35 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioSyntaxHighlightProvider.buildTokens (cognitive 87) src/scenarioSyntaxHighlightProvider.ts:185— ScenarioSyntaxHighlightProvider.buildTokens has cognitive complexity 87 (threshold 15). Drivers by points: if/else 26 (65 pts), ternaries 6 (13 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 47). Of this number, 75 points are the body's own statements and 12 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ScenarioDiagnosticsProvider.provideCodeActions (cognitive 86) src/scenarioDiagnostics.ts:855— ScenarioDiagnosticsProvider.provideCodeActions has cognitive complexity 86 (threshold 15). Drivers by points: if/else 21 (46 pts), loops 7 (17 pts), boolean chains 12, ternaries 6 (11 pts) (nesting depth added 40). Of this number, 80 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesActions.createScenarioPropertiesActions.<returned closure> (cognitive 83) src/scenarioPropertiesActions.ts:277— scenarioPropertiesActions.createScenarioPropertiesActions.<returned closure> has cognitive complexity 83 (threshold 15). Drivers by points: if/else 41 (56 pts), ternaries 6 (14 pts), boolean chains 13 (nesting depth added 23). Of this number, 81 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
setup (cognitive 83) media/kotWorkspace.js:172— setup has cognitive complexity 83 (threshold 15). Drivers by points: if/else 28 (51 pts), ternaries 13 (25 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 36). Of this number, 52 points are the body's own statements and 31 belong to 27 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibraryStore.load (cognitive 82) src/projectLibraryStore.ts:343— ProjectLibraryStore.load has cognitive complexity 82 (threshold 15). Drivers by points: if/else 28 (60 pts), loops 8 (12 pts), boolean chains 6, error handling 2 (3 pts), ternaries 1 (nesting depth added 37). Of this number, 78 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YamlParametersManager.openYamlParametersPanel (cognitive 82) REDACTED:1235— YamlParametersManager.openYamlParametersPanel has cognitive complexity 82 (threshold 15). Drivers by points: if/else 19 (38 pts), error handling 10 (20 pts), ternaries 7 (16 pts), boolean chains 7, match/switch 1 (nesting depth added 38). None of this is in the body itself: all 82 points belong to 2 function items inside it that branch (a function literal at line 1278, watchModelDbFile). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
featureEditorActions.planFeatureEditorEdit (cognitive 82) src/featureEditorActions.ts:184— featureEditorActions.planFeatureEditorEdit has cognitive complexity 82 (threshold 15). Drivers by points: ternaries 23 (53 pts), if/else 11 (18 pts), boolean chains 10, match/switch 1 (nesting depth added 37). Of this number, 76 points are the body's own statements and 6 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesCatalogs.runScenarioPropertiesCatalogAction (cognitive 82) src/scenarioPropertiesCatalogs.ts:199— scenarioPropertiesCatalogs.runScenarioPropertiesCatalogAction has cognitive complexity 82 (threshold 15). Drivers by points: if/else 27 (51 pts), ternaries 9 (19 pts), error handling 3 (8 pts), boolean chains 4 (nesting depth added 39). Of this number, 66 points are the body's own statements and 16 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioHeaderInlayHintsProvider.provideInlayHints (cognitive 81) src/scenarioHeaderInlayHintsProvider.ts:36— ScenarioHeaderInlayHintsProvider.provideInlayHints has cognitive complexity 81 (threshold 15). Drivers by points: ternaries 13 (39 pts), if/else 20 (34 pts), boolean chains 8 (nesting depth added 40). Of this number, 77 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
phaseSwitcher.buildScenarioViewState (cognitive 80) media/phaseSwitcher.js:1056— phaseSwitcher.buildScenarioViewState has cognitive complexity 80 (threshold 15). Drivers by points: ternaries 39 (43 pts), boolean chains 35, if/else 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
renderPhaseTree (cognitive 80) media/phaseSwitcher.js:1683— renderPhaseTree has cognitive complexity 80 (threshold 15). Drivers by points: if/else 19 (39 pts), boolean chains 20, ternaries 8 (15 pts), loops 3, other 3 (nesting depth added 27). Most of this is not in the body itself: 14 of the 80 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 1718, 1690, 1738, …). 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.
compilerBuildPreflight.collectCompilerBuildPreflightIssues (cognitive 79) src/compilerBuildPreflight.ts:107— compilerBuildPreflight.collectCompilerBuildPreflightIssues has cognitive complexity 79 (threshold 15). Drivers by points: if/else 20 (44 pts), ternaries 6 (15 pts), boolean chains 11, loops 7 (9 pts) (nesting depth added 35). Of this number, 76 points are the body's own statements and 3 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaInfobaseClients.operate (cognitive 79) src/vanessaInfobaseClients.ts:269— VanessaInfobaseClients.operate has cognitive complexity 79 (threshold 15). Drivers by points: if/else 24 (41 pts), boolean chains 31, loops 4 (7 pts) (nesting depth added 20). Most of this is not in the body itself: 2 of the 79 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 289, 271, 280, …). 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.
(anonymous) (cognitive 79) media/stepLibrary.js:2136— (anonymous) has cognitive complexity 79 (threshold 15). Drivers by points: if/else 25 (38 pts), ternaries 9 (18 pts), boolean chains 17, loops 2 (5 pts), other 1 (nesting depth added 25). 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.
PhaseSwitcherProvider.renameScenario (cognitive 78) src/phaseSwitcher.ts:5936— PhaseSwitcherProvider.renameScenario has cognitive complexity 78 (threshold 15). Drivers by points: if/else 30 (42 pts), boolean chains 15, ternaries 6 (9 pts), error handling 4 (8 pts), loops 3 (4 pts) (nesting depth added 20). Of this number, 67 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bindStaticEvents (cognitive 78) media/formExplorer.js:290— bindStaticEvents has cognitive complexity 78 (threshold 15). Drivers by points: if/else 34 (45 pts), boolean chains 26, ternaries 5 (6 pts), loops 1 (nesting depth added 12). Most of this is not in the body itself: 6 of the 78 points are its own statements and the rest belongs to 26 function literals inside it that branch (lines 449, 291, 593, …). 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.
makeRow (cognitive 78) media/stepLibrarySidebar.js:286— makeRow has cognitive complexity 78 (threshold 15). Drivers by points: if/else 29 (39 pts), ternaries 12 (22 pts), boolean chains 17 (nesting depth added 20). Of this number, 61 points are the body's own statements and 17 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.updateScenarioBuildArtifacts (cognitive 73) src/phaseSwitcher.ts:10172— PhaseSwitcherProvider.updateScenarioBuildArtifacts has cognitive complexity 73 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 16, loops 11 (13 pts), ternaries 2 (5 pts), error handling 2 (4 pts) (nesting depth added 24). Of this number, 70 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibrary.window.addEventListener("message") (cognitive 72) media/stepLibrary.js:2136— stepLibrary.window.addEventListener("message") has cognitive complexity 72 (threshold 15). Drivers by points: if/else 25 (38 pts), boolean chains 17, ternaries 6 (12 pts), loops 2 (5 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.changeScenarioIdentityField (cognitive 68) src/phaseSwitcher.ts:5360— PhaseSwitcherProvider.changeScenarioIdentityField has cognitive complexity 68 (threshold 15). Drivers by points: if/else 24 (37 pts), boolean chains 20, loops 6 (7 pts), ternaries 3 (4 pts) (nesting depth added 15). Of this number, 58 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.applyRunningFeatureStepDecorations (cognitive 67) src/phaseSwitcher.ts:3264— PhaseSwitcherProvider.applyRunningFeatureStepDecorations has cognitive complexity 67 (threshold 15). Drivers by points: if/else 17 (44 pts), loops 7 (11 pts), boolean chains 10, ternaries 1 (2 pts) (nesting depth added 32). Of this number, 63 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotProjectSetup.inspectSetupProject (cognitive 65) src/kotProjectSetup.ts:35— kotProjectSetup.inspectSetupProject has cognitive complexity 65 (threshold 15). Drivers by points: if/else 18 (40 pts), boolean chains 11, error handling 2 (6 pts), loops 3 (4 pts), ternaries 1 (4 pts) (nesting depth added 30). Of this number, 64 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.buildDeterministicScenarioChunkSummary (cognitive 65) REDACTED:3153— scenarioAiDescription.buildDeterministicScenarioChunkSummary has cognitive complexity 65 (threshold 15). Drivers by points: if/else 21 (46 pts), boolean chains 9, ternaries 3 (9 pts), loops 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlStepResults.mapVanessaStepResults (cognitive 64) src/vanessaControlStepResults.ts:10— vanessaControlStepResults.mapVanessaStepResults has cognitive complexity 64 (threshold 15). Drivers by points: ternaries 15 (33 pts), if/else 10 (14 pts), boolean chains 8, loops 6 (8 pts), error handling 1 (nesting depth added 24). Of this number, 37 points are the body's own statements and 27 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exportScenarioParser.parseExportScenarios (cognitive 63) src/exportScenarioParser.ts:317— exportScenarioParser.parseExportScenarios has cognitive complexity 63 (threshold 15). Drivers by points: if/else 22 (49 pts), boolean chains 10, ternaries 2 (3 pts), loops 1 (nesting depth added 28). Of this number, 58 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderStaticFrame (cognitive 63) media/formExplorer.js:698— renderStaticFrame has cognitive complexity 63 (threshold 15). Drivers by points: ternaries 18 (24 pts), if/else 22, boolean chains 17 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
vanessaControlAuthoringCommands.registerVanessaAuthoringCommands (cognitive 61) src/vanessaControlAuthoringCommands.ts:8— vanessaControlAuthoringCommands.registerVanessaAuthoringCommands has cognitive complexity 61 (threshold 15). Drivers by points: if/else 32 (35 pts), ternaries 11 (13 pts), boolean chains 10, error handling 3 (nesting depth added 5). None of this is in the body itself: all 61 points belong to 13 function items inside it that branch (captureTarget, a function literal at line 107, insert, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
projectDefinitionDeletion.deleteScenarioDefinition.prepare (cognitive 60) src/projectDefinitionDeletion.ts:133— projectDefinitionDeletion.deleteScenarioDefinition.prepare has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (35 pts), boolean chains 11, loops 3 (6 pts), ternaries 3 (6 pts), error handling 1 (2 pts) (nesting depth added 23). Of this number, 49 points are the body's own statements and 11 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.execute1CProcess (cognitive 60) src/phaseSwitcher.ts:9003— PhaseSwitcherProvider.execute1CProcess has cognitive complexity 60 (threshold 15). Drivers by points: if/else 27 (44 pts), boolean chains 12, error handling 2 (4 pts) (nesting depth added 19). Most of this is not in the body itself: 10 of the 60 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 9121, 9094, 9031, …). 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.
StepLibrarySidebarIndex.constructor (cognitive 59) src/stepLibrarySidebarModel.ts:247— StepLibrarySidebarIndex.constructor has cognitive complexity 59 (threshold 15). Drivers by points: if/else 13 (25 pts), ternaries 5 (14 pts), loops 8 (12 pts), boolean chains 8 (nesting depth added 25). Of this number, 48 points are the body's own statements and 11 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 59) media/scenarioProperties.js:624— render has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 18 (27 pts), if/else 14 (17 pts), boolean chains 8, loops 6 (7 pts) (nesting depth added 13). Of this number, 43 points are the body's own statements and 16 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StandaloneFeatureController.performAction (cognitive 58) src/standaloneFeatureController.ts:191— StandaloneFeatureController.performAction has cognitive complexity 58 (threshold 15). Drivers by points: if/else 26 (47 pts), boolean chains 8, ternaries 1 (2 pts), match/switch 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlYamlCommands.createVanessaYamlControl::render (cognitive 58) src/vanessaControlYamlCommands.ts:33— vanessaControlYamlCommands.createVanessaYamlControl::render has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 13 (32 pts), if/else 7 (16 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fieldControl (cognitive 58) media/scenarioProperties.js:304— fieldControl has cognitive complexity 58 (threshold 15). Drivers by points: if/else 20 (22 pts), ternaries 10 (19 pts), boolean chains 10, loops 2 (4 pts), other 3 (nesting depth added 13). Of this number, 41 points are the body's own statements and 17 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.syncManagerFeature (cognitive 57) media/standaloneFeatures.js:368— create.syncManagerFeature has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 13 (25 pts), if/else 15 (20 pts), boolean chains 12 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlFormTools.readSchema (cognitive 56) src/vanessaControlFormTools.ts:50— vanessaControlFormTools.readSchema has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (36 pts), boolean chains 14, loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 18). 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.
compilerBuildErrorLocation.resolveCompilerBuildErrorLocation (cognitive 56) src/compilerBuildErrorLocation.ts:12— compilerBuildErrorLocation.resolveCompilerBuildErrorLocation has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (38 pts), boolean chains 10, loops 4 (7 pts), ternaries 1 (nesting depth added 24). Of this number, 46 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.provideCompletionItems (cognitive 56) src/completionProvider.ts:717— DriveCompletionProvider.provideCompletionItems has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (24 pts), ternaries 15 (21 pts), boolean chains 11 (nesting depth added 12). Of this number, 39 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.handleScenarioContextMenu (cognitive 55) media/phaseSwitcher.js:2843— phaseSwitcher.handleScenarioContextMenu has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 42, ternaries 10, if/else 3. 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.
StandaloneFeatureService.readProjectOrganization (cognitive 55) src/standaloneFeatureService.ts:686— StandaloneFeatureService.readProjectOrganization has cognitive complexity 55 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 9 (13 pts), ternaries 4 (9 pts), boolean chains 8, error handling 1 (2 pts) (nesting depth added 24). Of this number, 48 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
processEditorCommands.changeProcessIdentityFromEditor (cognitive 55) src/processEditorCommands.ts:50— processEditorCommands.changeProcessIdentityFromEditor has cognitive complexity 55 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 19, ternaries 5 (8 pts), loops 4, error handling 1 (nesting depth added 9). Of this number, 41 points are the body's own statements and 14 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioSyntaxHighlightProvider.collectScenarioPlainTextRanges (cognitive 55) src/scenarioSyntaxHighlightProvider.ts:352— scenarioSyntaxHighlightProvider.collectScenarioPlainTextRanges has cognitive complexity 55 (threshold 15). Drivers by points: if/else 19 (45 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 28). 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.
stepLibraryProtocol.buildCategoryTree (cognitive 54) media/stepLibraryProtocol.js:378— stepLibraryProtocol.buildCategoryTree has cognitive complexity 54 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 17, loops 5 (8 pts), ternaries 2 (5 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.runScenarioInVanessa (cognitive 54) src/phaseSwitcher.ts:13433— PhaseSwitcherProvider.runScenarioInVanessa has cognitive complexity 54 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 12, ternaries 6 (10 pts), error handling 2 (3 pts) (nesting depth added 13). Of this number, 52 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 54) media/yamlParameters.js:4— (anonymous) has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 47, ternaries 6, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
gherkinAnnotations.completionContext (cognitive 53) src/gherkinAnnotations.ts:173— gherkinAnnotations.completionContext has cognitive complexity 53 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 4 (18 pts), boolean chains 14 (nesting depth added 22). Of this number, 50 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhaseSwitcherProvider.runScenarioInVanessaBuiltIn (cognitive 53) src/phaseSwitcher.ts:12050— PhaseSwitcherProvider.runScenarioInVanessaBuiltIn has cognitive complexity 53 (threshold 15). Drivers by points: if/else 27 (33 pts), boolean chains 10, ternaries 7 (8 pts), error handling 1 (2 pts) (nesting depth added 8). Of this number, 49 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
vanessaControlFormToolWorkflow.collectVanessaFormToolArguments (cognitive 53) src/vanessaControlFormToolWorkflow.ts:13— vanessaControlFormToolWorkflow.collectVanessaFormToolArguments has cognitive complexity 53 (threshold 15). Drivers by points: if/else 11 (27 pts), ternaries 6 (16 pts), error handling 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 29). Of this number, 46 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extension.activate::runScenarioRepairBatch (cognitive 53) REDACTED:2929— extension.activate::runScenarioRepairBatch has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 8 (11 pts), loops 4 (9 pts), error handling 2 (5 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (extension.activate) 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.
createDefinitionRow (cognitive 53) media/stepLibrary.js:1157— createDefinitionRow has cognitive complexity 53 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 9, ternaries 6 (9 pts), loops 3 (6 pts) (nesting depth added 14). Of this number, 51 points are the body's own statements and 2 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bslStepSourceParser.scanBslTokens (cognitive 52) src/bslStepSourceParser.ts:146— bslStepSourceParser.scanBslTokens has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (33 pts), loops 4 (10 pts), boolean chains 9 (nesting depth added 27). 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.
infobaseManager.updateManagedInfobaseMetadata (cognitive 52) src/infobaseManager.ts:789— infobaseManager.updateManagedInfobaseMetadata has cognitive complexity 52 (threshold 15). Drivers by points: if/else 38 (50 pts), boolean chains 2 (nesting depth added 12). 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.
scenarioAiDescription.buildDeterministicParameterizedUtilityScenarioDescription (cognitive 52) REDACTED:3395— scenarioAiDescription.buildDeterministicParameterizedUtilityScenarioDescription has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 34 (51 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.refreshSnapshot (cognitive 52) src/formExplorerPanel.ts:1430— FormExplorerPanel.refreshSnapshot has cognitive complexity 52 (threshold 15). Drivers by points: if/else 25 (38 pts), boolean chains 8, ternaries 2 (4 pts), error handling 2 (nesting depth added 15). Of this number, 51 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfobaseManagerPanel.handleMessage (cognitive 52) src/infobaseManagerPanel.ts:418— InfobaseManagerPanel.handleMessage has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 12, ternaries 3 (6 pts), error handling 1 (2 pts), match/switch 2 (nesting depth added 18). Of this number, 37 points are the body's own statements and 15 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectMetadataAudit.auditMetadataReferences (cognitive 51) src/projectMetadataAudit.ts:7— projectMetadataAudit.auditMetadataReferences has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (39 pts), boolean chains 5, loops 3 (5 pts), error handling 1 (2 pts) (nesting depth added 25). Of this number, 50 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StepLibrarySidebarProvider.runItemAction (cognitive 51) src/stepLibrarySidebarProvider.ts:462— StepLibrarySidebarProvider.runItemAction has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 9 (45 pts), boolean chains 4, error handling 1, if/else 1 (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
gherkinAnnotations.buildGherkinAnnotationCompletions (cognitive 50) src/gherkinAnnotations.ts:234— gherkinAnnotations.buildGherkinAnnotationCompletions has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 21, if/else 8 (12 pts), ternaries 6 (10 pts), loops 3 (7 pts) (nesting depth added 12). Of this number, 36 points are the body's own statements and 14 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesSession.load (cognitive 50) src/scenarioPropertiesSession.ts:131— ScenarioPropertiesSession.load has cognitive complexity 50 (threshold 15). Drivers by points: if/else 35 (56 pts), boolean chains 14, error handling 5 (10 pts), loops 4 (5 pts), ternaries 4 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ScenarioPropertiesSession.load::enrich) 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.
PhaseSwitcherProvider.promptVanessaInfobasePreparationPlan (cognitive 50) src/phaseSwitcher.ts:11454— PhaseSwitcherProvider.promptVanessaInfobasePreparationPlan has cognitive complexity 50 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 16, ternaries 1 (2 pts) (nesting depth added 11). Of this number, 46 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.dropTarget (cognitive 50) media/standaloneFeatures.js:279— create.dropTarget has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 11 (22 pts), if/else 11 (15 pts), boolean chains 13 (nesting depth added 15). None of this is in the body itself: all 50 points belong to 9 function items inside it that branch (a function literal at line 304, a function literal at line 286, valid, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
stepLibraryModel.buildStepLibrarySnapshot (cognitive 49) src/stepLibraryModel.ts:305— stepLibraryModel.buildStepLibrarySnapshot has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 24 (32 pts), boolean chains 11, if/else 2 (3 pts), loops 2 (3 pts) (nesting depth added 10). Of this number, 26 points are the body's own statements and 23 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.collectManagedInfobases (cognitive 49) src/infobaseManager.ts:1121— infobaseManager.collectManagedInfobases has cognitive complexity 49 (threshold 15). Drivers by points: if/else 30 (38 pts), boolean chains 25, loops 9 (10 pts), ternaries 3 (6 pts), error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (infobaseManager.collectManagedInfobases::observeInfobase) 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.
VanessaInfobaseClients.refresh (cognitive 49) src/vanessaInfobaseClients.ts:133— VanessaInfobaseClients.refresh has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (29 pts), error handling 4 (11 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 24). Most of this is not in the body itself: 6 of the 49 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 147, 139). 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.
(anonymous) (cognitive 49) media/yamlParameters.js:1451— (anonymous) has cognitive complexity 49 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 17, ternaries 1 (2 pts), match/switch 1, other 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
standaloneFeatures.create.dropTarget (cognitive 48) media/standaloneFeatures.js:279— standaloneFeatures.create.dropTarget has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 11 (15 pts), boolean chains 13 (nesting depth added 16). None of this is in the body itself: all 48 points belong to 5 function items inside it that branch (a function literal at line 304, a function literal at line 286, valid, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ProjectLibraryStore.commit (cognitive 48) src/projectLibraryStore.ts:514— ProjectLibraryStore.commit has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 10, error handling 2 (4 pts), loops 3 (4 pts), ternaries 2 (nesting depth added 10). Of this number, 23 points are the body's own statements and 25 belong to 8 function items inside it that branch. 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.
projectDefinitionMatcher.compileProjectDefinitionMatcherInternal.matchPrepared (cognitive 48) src/projectDefinitionMatcher.ts:206— projectDefinitionMatcher.compileProjectDefinitionMatcherInternal.matchPrepared has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (43 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 25). 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.
scenarioCreator.handleManageEtalonBases (cognitive 48) src/scenarioCreator.ts:1728— scenarioCreator.handleManageEtalonBases has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (39 pts), boolean chains 6, ternaries 1 (2 pts), loops 1 (nesting depth added 24). Of this number, 45 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectMetadataMerge.mergeProjectMetadata::combine (cognitive 48) src/projectMetadataMerge.ts:72— projectMetadataMerge.mergeProjectMetadata::combine has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 12, ternaries 3 (9 pts), loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerArtifacts.readXml (cognitive 47) src/compilerArtifacts.ts:214— compilerArtifacts.readXml has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 6, loops 2 (3 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yamlParameters.window.addEventListener("message") (cognitive 46) media/yamlParameters.js:1451— yamlParameters.window.addEventListener("message") has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 17, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
compilerBuildSourceSelection.selectCompilerBuildSources (cognitive 46) src/compilerBuildSourceSelection.ts:6— compilerBuildSourceSelection.selectCompilerBuildSources has cognitive complexity 46 (threshold 15). Drivers by points: loops 10 (17 pts), if/else 5 (14 pts), ternaries 6 (14 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerBuildPreflight.settingSelected (cognitive 46) src/compilerBuildPreflight.ts:43— compilerBuildPreflight.settingSelected has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 12, loops 3 (5 pts), ternaries 5 (nesting depth added 9). Of this number, 26 points are the body's own statements and 20 belong to 3 function items inside it that branch. 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.
oneCPlatform.handleManagePlatforms (cognitive 46) src/oneCPlatform.ts:510— oneCPlatform.handleManagePlatforms has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (41 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 26). 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.
scenarioIdentityFiles.prepareScenarioIdentityFileChanges (cognitive 46) src/scenarioIdentityFiles.ts:46— scenarioIdentityFiles.prepareScenarioIdentityFileChanges has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 18, ternaries 4 (5 pts), loops 3 (nesting depth added 10). Of this number, 45 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioIdentityFiles.prepareScenarioIdentityFileChanges.apply (cognitive 46) src/scenarioIdentityFiles.ts:157— scenarioIdentityFiles.prepareScenarioIdentityFileChanges.apply has cognitive complexity 46 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 3 (8 pts), loops 4 (8 pts), boolean chains 7 (nesting depth added 23). Of this number, 43 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.pollVanessaRuntimeLogMonitor (cognitive 46) src/phaseSwitcher.ts:2661— PhaseSwitcherProvider.pollVanessaRuntimeLogMonitor has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 9, error handling 2 (3 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlClientWorkflow.manageVanessaClients (cognitive 46) src/vanessaControlClientWorkflow.ts:27— vanessaControlClientWorkflow.manageVanessaClients has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 13, ternaries 6 (10 pts) (nesting depth added 13). Of this number, 42 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderDetailsResourceNode (cognitive 46) media/stepLibrary.js:1470— renderDetailsResourceNode has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 9, ternaries 5 (9 pts), loops 1 (3 pts) (nesting depth added 14). Of this number, 35 points are the body's own statements and 11 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcherMetadata.migrateLegacyPhaseSwitcherMetadata (cognitive 45) src/phaseSwitcherMetadata.ts:611— phaseSwitcherMetadata.migrateLegacyPhaseSwitcherMetadata has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 9, ternaries 4 (7 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCompilerSyntax.validateCompilerBlocks (cognitive 45) src/scenarioCompilerSyntax.ts:105— scenarioCompilerSyntax.validateCompilerBlocks has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 9, loops 1 (nesting depth added 18). 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.
exportScenarioCommand.createExportScenarioCommand (cognitive 45) src/exportScenarioCommand.ts:83— exportScenarioCommand.createExportScenarioCommand has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (33 pts), ternaries 4 (5 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 15). Of this number, 42 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.humanizeScenarioParameterOrBranch (cognitive 45) REDACTED:2477— scenarioAiDescription.humanizeScenarioParameterOrBranch has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 10 (25 pts), if/else 12 (17 pts), boolean chains 3 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.extractScenarioFieldAssignments (cognitive 45) REDACTED:2963— scenarioAiDescription.extractScenarioFieldAssignments has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 6 (17 pts), if/else 7 (14 pts), boolean chains 13, loops 1 (nesting depth added 18). 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.
scenarioCallableFiles.applyCallableFileConversion (cognitive 45) src/scenarioCallableFiles.ts:27— scenarioCallableFiles.applyCallableFileConversion has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 9 (13 pts), error handling 5 (9 pts), boolean chains 2 (nesting depth added 17). Of this number, 38 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinAnnotations.scan (cognitive 44) src/gherkinAnnotations.ts:60— gherkinAnnotations.scan has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 12, loops 3 (4 pts), ternaries 1 (nesting depth added 12). Of this number, 43 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaParameterCatalog.loadVanessaParameterCatalogSnapshot (cognitive 44) src/vanessaParameterCatalog.ts:39— vanessaParameterCatalog.loadVanessaParameterCatalogSnapshot has cognitive complexity 44 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 5 (16 pts), error handling 2 (6 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 27). Of this number, 37 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
standaloneFeatureLaunch.buildStandaloneFeatureLaunchJson (cognitive 44) src/standaloneFeatureLaunch.ts:172— standaloneFeatureLaunch.buildStandaloneFeatureLaunchJson has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 6 (13 pts), loops 6 (8 pts), boolean chains 4 (nesting depth added 18). Of this number, 35 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FeaturePropertiesController.handle (cognitive 44) src/featurePropertiesController.ts:43— FeaturePropertiesController.handle has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 13, error handling 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.buildGherkinCompletionState (cognitive 44) src/completionProvider.ts:589— DriveCompletionProvider.buildGherkinCompletionState has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 10 (23 pts), if/else 6 (14 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createClient::setState (cognitive 43) media/scenarioPropertiesProtocol.js:145— createClient::setState has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 11, loops 2 (5 pts), other 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
aiClient.extractResponseText (cognitive 42) src/aiClient.ts:107— aiClient.extractResponseText has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 9, ternaries 4 (7 pts), loops 2 (5 pts) (nesting depth added 15). Of this number, 38 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibraryStore.moveEntity (cognitive 42) src/projectLibraryStore.ts:718— ProjectLibraryStore.moveEntity has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 15, ternaries 3 (6 pts), loops 2 (3 pts), error handling 1 (nesting depth added 10). None of this is in the body itself: all 42 points belong to 3 function literals inside it that branch (lines 720, 747, 748). 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.
scenarioPropertyIdentity.applyScenarioPropertyIdentity (cognitive 42) src/scenarioPropertyIdentity.ts:11— scenarioPropertyIdentity.applyScenarioPropertyIdentity has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 10, ternaries 1 (4 pts), loops 1 (nesting depth added 13). Of this number, 38 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotSettingsSession.validateSetting (cognitive 42) REDACTED:27— kotSettingsSession.validateSetting has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 14, ternaries 4 (6 pts), loops 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlDiagnosticsCommands.registerVanessaDiagnosticsCommands (cognitive 42) src/vanessaControlDiagnosticsCommands.ts:10— vanessaControlDiagnosticsCommands.registerVanessaDiagnosticsCommands has cognitive complexity 42 (threshold 15). Drivers by points: if/else 25 (27 pts), boolean chains 13, error handling 1, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 42 points belong to 15 function items inside it that branch (a function literal at line 90, run, a function literal at line 110, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
userStepCommands.buildUserStepLibraryCommand (cognitive 42) src/userStepCommands.ts:411— userStepCommands.buildUserStepLibraryCommand has cognitive complexity 42 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 6, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 17). Of this number, 39 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extension.collectKotDescriptionContentRanges (cognitive 42) REDACTED:3734— extension.collectKotDescriptionContentRanges has cognitive complexity 42 (threshold 15). Drivers by points: if/else 7 (29 pts), loops 3 (7 pts), boolean chains 6 (nesting depth added 26). 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.
attach (cognitive 42) media/kotWebviewSplit.js:11— attach has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 24, if/else 11, boolean chains 6, loops 1. Most of this is not in the body itself: 4 of the 42 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 77, update, geometry, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
formExplorer.initialize (cognitive 41) media/formExplorer.js:226— formExplorer.initialize has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 14, ternaries 2 (5 pts) (nesting depth added 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to one function literal inside it that branches (line 232). 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.
stepLibrary.renderProcessSteps (cognitive 41) media/stepLibrary.js:1672— stepLibrary.renderProcessSteps has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 21, if/else 15, ternaries 3, loops 2. Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 1763, a function literal at line 1723, reorder, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VanessaBreakpointReconciler.reconcile (cognitive 41) src/vanessaControlBreakpoints.ts:39— VanessaBreakpointReconciler.reconcile has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 9, loops 3 (5 pts), error handling 2 (3 pts) (nesting depth added 11). Of this number, 33 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaDebugClientConfiguration.advancedClient (cognitive 41) src/vanessaDebugClientConfiguration.ts:91— vanessaDebugClientConfiguration.advancedClient has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (25 pts), ternaries 3 (12 pts), boolean chains 3, loops 1 (nesting depth added 24). Of this number, 26 points are the body's own statements and 15 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
commandHandlers.handleCreateFirstLaunchZip (cognitive 41) REDACTED:931— commandHandlers.handleCreateFirstLaunchZip has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 6, error handling 5 (6 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 11). Most of this is not in the body itself: 11 of the 41 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 999, 1002, 969, …). 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.
featureEditorCodeLens.editFeatureStructureCommand (cognitive 41) src/featureEditorCodeLens.ts:91— featureEditorCodeLens.editFeatureStructureCommand has cognitive complexity 41 (threshold 15). Drivers by points: if/else 20 (28 pts), ternaries 4 (8 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 13). Of this number, 39 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectCatalogSettings.run (cognitive 41) src/projectCatalogSettings.ts:70— ProjectCatalogSettings.run has cognitive complexity 41 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 14, ternaries 4 (8 pts), error handling 2 (3 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 41) media/phaseSwitcher.js:4— (anonymous) has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 21, if/else 17, ternaries 3. 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.
ScenarioDiagnosticsProvider.validateFeatureDocument (cognitive 40) src/scenarioDiagnostics.ts:1935— ScenarioDiagnosticsProvider.validateFeatureDocument has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (26 pts), ternaries 5 (9 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioDiagnostics.getKotDescriptionState (cognitive 40) src/scenarioDiagnostics.ts:281— scenarioDiagnostics.getKotDescriptionState has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (27 pts), boolean chains 7, loops 4 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderDetails (cognitive 40) media/stepLibrary.js:1783— renderDetails has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 17, if/else 11 (12 pts), ternaries 5 (7 pts), loops 2 (4 pts) (nesting depth added 5). Of this number, 38 points are the body's own statements and 2 belong to 3 function literals inside it that branch. 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.
yamlParameters.document.addEventListener("click") (cognitive 39) media/yamlParameters.js:1104— yamlParameters.document.addEventListener("click") has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (36 pts), boolean chains 3 (nesting depth added 18). Of this number, 36 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlForms.parseVanessaFormTree (cognitive 39) src/vanessaControlForms.ts:36— vanessaControlForms.parseVanessaFormTree has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 11, ternaries 2 (3 pts), loops 1 (nesting depth added 14). Of this number, 38 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
commandHandlers.alignNestedScenarioCallParametersInText (cognitive 39) REDACTED:1495— commandHandlers.alignNestedScenarioCallParametersInText has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.buildFormExplorerQuotedArgumentCompletionList (cognitive 39) src/completionProvider.ts:1675— DriveCompletionProvider.buildFormExplorerQuotedArgumentCompletionList has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 11 (nesting depth added 12). Of this number, 32 points are the body's own statements and 7 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveHoverProvider.parseScenarioDescription (cognitive 39) REDACTED:364— DriveHoverProvider.parseScenarioDescription has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 8, loops 4 (6 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerExtensionGenerator.handleStartFormExplorerInfobase (cognitive 39) REDACTED:7104— formExplorerExtensionGenerator.handleStartFormExplorerInfobase has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 10, ternaries 5 (9 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCallableConversion.rewriteCallableCall (cognitive 39) src/scenarioCallableConversion.ts:227— scenarioCallableConversion.rewriteCallableCall has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 19). Of this number, 37 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 39) media/yamlParameters.js:1104— (anonymous) has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (36 pts), boolean chains 3 (nesting depth added 18). Of this number, 36 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yamlParameters.buildRowHtml (cognitive 38) media/yamlParameters.js:375— yamlParameters.buildRowHtml has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 20 (29 pts), boolean chains 9 (nesting depth added 9). Of this number, 36 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
etalonBases.parseEtalonBasesYaml (cognitive 38) REDACTED:256— etalonBases.parseEtalonBasesYaml has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioFilesWebviewProtocol.parseScenarioFilesMessage (cognitive 38) src/scenarioFilesWebviewProtocol.ts:80— scenarioFilesWebviewProtocol.parseScenarioFilesMessage has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 11, if/else 10 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KotWorkspacePanel.applySetup (cognitive 38) src/kotWorkspacePanel.ts:238— KotWorkspacePanel.applySetup has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 8, error handling 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 9). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 244, 246, 256). 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.
scenarioAiDescription.buildScenarioBodyChunks (cognitive 38) REDACTED:792— scenarioAiDescription.buildScenarioBodyChunks has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 5 (11 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
controls (cognitive 38) media/kotWorkspace.js:80— controls has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 14 (22 pts), boolean chains 8, if/else 8 (nesting depth added 8). Of this number, 31 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaControlSession.refreshState (cognitive 37) src/vanessaControlSession.ts:289— VanessaControlSession.refreshState has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 5 (10 pts), boolean chains 7, error handling 1 (nesting depth added 14). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 294, 299). 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.
etalonBases.parseEtalonBaseUserProfiles (cognitive 37) REDACTED:99— etalonBases.parseEtalonBaseUserProfiles has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerBuildValueValidation.collectCompilerBuildValueIssues (cognitive 37) src/compilerBuildValueValidation.ts:64— compilerBuildValueValidation.collectCompilerBuildValueIssues has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 9, ternaries 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesPanel.receive (cognitive 37) src/scenarioPropertiesPanel.ts:658— ScenarioPropertiesPanel.receive has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 13, error handling 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.buildDeterministicProcessItems (cognitive 37) REDACTED:2246— scenarioAiDescription.buildDeterministicProcessItems has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 7 (16 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerStepSuggestions.buildVanessaMultilineSuggestions (cognitive 37) src/formExplorerStepSuggestions.ts:943— formExplorerStepSuggestions.buildVanessaMultilineSuggestions has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 5 (7 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
standaloneFeatures.create.syncManagerFeature (cognitive 36) media/standaloneFeatures.js:368— standaloneFeatures.create.syncManagerFeature has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 12, ternaries 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesModel.applyScenarioPropertyEdit (cognitive 36) src/scenarioPropertiesModel.ts:220— scenarioPropertiesModel.applyScenarioPropertyEdit has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 13, ternaries 4 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StandaloneFeatureService.scanDirectory (cognitive 36) src/standaloneFeatureService.ts:483— StandaloneFeatureService.scanDirectory has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 3 (7 pts), boolean chains 5, error handling 2 (3 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCreator.handleManageSystemFunctions (cognitive 36) src/scenarioCreator.ts:1330— scenarioCreator.handleManageSystemFunctions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (32 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 19). Of this number, 34 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.calculateSemanticVectorScores (cognitive 36) src/completionProvider.ts:2350— DriveCompletionProvider.calculateSemanticVectorScores has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 11, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 8). Most of this is not in the body itself: 8 of the 36 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2368, 2401, 2424). 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.
DriveCompletionProvider.buildControlFlowCompletions (cognitive 36) src/completionProvider.ts:2737— DriveCompletionProvider.buildControlFlowCompletions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 8, loops 4 (7 pts), ternaries 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.renderScenarioFileNode (cognitive 35) media/phaseSwitcher.js:946— phaseSwitcher.renderScenarioFileNode has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 11, if/else 4 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotMetadataDescription.findKotDescriptionSection (cognitive 35) src/kotMetadataDescription.ts:55— kotMetadataDescription.findKotDescriptionSection has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 8, loops 4 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioYamlDocument.buildStructuralShadow (cognitive 35) src/scenarioYamlDocument.ts:158— scenarioYamlDocument.buildStructuralShadow has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 10, loops 3 (6 pts), ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioDescriptor.parseScenarioDescriptor (cognitive 35) src/scenarioDescriptor.ts:122— scenarioDescriptor.parseScenarioDescriptor has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 15 (19 pts), if/else 4 (9 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 11). Of this number, 19 points are the body's own statements and 16 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerProcesses.updateCompilerProcessIdentity (cognitive 35) src/compilerProcesses.ts:327— compilerProcesses.updateCompilerProcessIdentity has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 7, ternaries 2 (4 pts), loops 1 (nesting depth added 11). Of this number, 30 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectDefinitionIndexService.#enumerate (cognitive 35) src/projectDefinitionIndexService.ts:683— ProjectDefinitionIndexService.#enumerate has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (20 pts), error handling 3 (7 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 18). Of this number, 18 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.changeNestedScenarioCodeForActiveEditor (cognitive 35) src/phaseSwitcher.ts:4948— PhaseSwitcherProvider.changeNestedScenarioCodeForActiveEditor has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 7, error handling 4 (6 pts), loops 1 (nesting depth added 4). Of this number, 29 points are the body's own statements and 6 belong to 3 function literals inside it that branch. 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.
PhaseSwitcherProvider._groupAndSortTestData (cognitive 35) src/phaseSwitcher.ts:9224— PhaseSwitcherProvider._groupAndSortTestData has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 4 (10 pts), loops 3, boolean chains 2 (nesting depth added 17). Of this number, 28 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioSyntaxHighlightProvider.collectScenarioReferenceRanges (cognitive 35) src/scenarioSyntaxHighlightProvider.ts:499— scenarioSyntaxHighlightProvider.collectScenarioReferenceRanges has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 3 (7 pts), boolean chains 4, ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls (cognitive 35) src/scenarioCallableCommands.ts:114— scenarioCallableCommands.handleConvertCallableScenario::expandNestedCalls has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 7, loops 3 (5 pts), ternaries 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (scenarioCallableCommands.handleConvertCallableScenario) 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.
create.featureRow (cognitive 35) media/standaloneFeatures.js:501— create.featureRow has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18, boolean chains 13, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 19 belong to 8 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
renderScenarioResourceNode (cognitive 35) media/stepLibrary.js:962— renderScenarioResourceNode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 7, ternaries 4 (7 pts), loops 1 (3 pts) (nesting depth added 9). Of this number, 30 points are the body's own statements and 5 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
relationshipDecorationForNode (cognitive 35) media/stepLibrarySidebarProtocol.js:175— relationshipDecorationForNode has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 11 (16 pts), boolean chains 11, if/else 6 (7 pts), other 1 (nesting depth added 6). Of this number, 33 points are the body's own statements and 2 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app.renderPickerOptions (cognitive 34) docs/ux/first-run/app.js:63— app.renderPickerOptions has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (33 pts), boolean chains 1 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
standaloneFeatures.create.featureRow (cognitive 34) media/standaloneFeatures.js:501— standaloneFeatures.create.featureRow has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18, boolean chains 14, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 552, 539, 562, …). 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.
scenarioPropertiesModel.propertyField (cognitive 34) src/scenarioPropertiesModel.ts:77— scenarioPropertiesModel.propertyField has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 13 (24 pts), boolean chains 10 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinTableUtils.planGherkinHeaderColumnDeletion (cognitive 34) src/gherkinTableUtils.ts:153— gherkinTableUtils.planGherkinHeaderColumnDeletion has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 11, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.handleScenarioFilesRenamed (cognitive 34) src/phaseSwitcher.ts:1860— PhaseSwitcherProvider.handleScenarioFilesRenamed has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (15 pts), error handling 4 (6 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 12). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.constructor (cognitive 34) src/phaseSwitcher.ts:1987— PhaseSwitcherProvider.constructor has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 6, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 34 points belong to 9 function items inside it that branch (a function literal at line 2079, a function literal at line 1997, a function literal at line 2045, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VanessaFormExplorerSource.perform (cognitive 34) src/vanessaControlFormSource.ts:99— VanessaFormExplorerSource.perform has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 12, if/else 7 (10 pts), ternaries 4 (9 pts), error handling 2 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 107, current, sameSession, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
KotWorkspacePanel.reviewSetup (cognitive 34) src/kotWorkspacePanel.ts:202— KotWorkspacePanel.reviewSetup has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 11, ternaries 6 (7 pts) (nesting depth added 4). Of this number, 29 points are the body's own statements and 5 belong to 2 function items inside it that branch. 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.
vanessaControlVariableCommands.registerVanessaVariableCommands (cognitive 34) src/vanessaControlVariableCommands.ts:11— vanessaControlVariableCommands.registerVanessaVariableCommands has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 7, ternaries 5 (6 pts), error handling 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 10 function items inside it that branch (write, a function literal at line 28, report, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
stepLibraryPanel.parseStepLibraryInboundMessage (cognitive 34) src/stepLibraryPanel.ts:95— stepLibraryPanel.parseStepLibraryInboundMessage has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 11, ternaries 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioProperties.renderSection (cognitive 33) media/scenarioProperties.js:541— scenarioProperties.renderSection has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 7, ternaries 2 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaLaunchJson.parseAdditionalParameterValue (cognitive 33) src/vanessaLaunchJson.ts:437— vanessaLaunchJson.parseAdditionalParameterValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 6, ternaries 2 (4 pts), error handling 1 (nesting depth added 11). Of this number, 32 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
spprScenarioFormat.convertSpprScenarioFiles (cognitive 33) src/spprScenarioFormat.ts:55— spprScenarioFormat.convertSpprScenarioFiles has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 8 (11 pts), ternaries 4 (5 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesPanel.follow (cognitive 33) src/scenarioPropertiesPanel.ts:555— ScenarioPropertiesPanel.follow has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 9, error handling 3 (5 pts) (nesting depth added 8). Of this number, 27 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.pollTrackedRunLogWatcher (cognitive 33) src/phaseSwitcher.ts:3812— PhaseSwitcherProvider.pollTrackedRunLogWatcher has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 7, loops 1 (2 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinInsertionContext.featureContext (cognitive 33) src/gherkinInsertionContext.ts:81— gherkinInsertionContext.featureContext has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.collectFormExplorerTableCompletionCandidates (cognitive 33) src/completionProvider.ts:1057— DriveCompletionProvider.collectFormExplorerTableCompletionCandidates has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 18, if/else 3 (7 pts), loops 2 (4 pts), ternaries 3 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (append, append::collect, a function literal at line 1060, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
formExplorerExtensionGenerator.collectManagedForms (cognitive 33) REDACTED:1315— formExplorerExtensionGenerator.collectManagedForms has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (23 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 18). 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.
userStepLibraryState.inspectUserStepLibrary (cognitive 32) src/userStepLibraryState.ts:126— userStepLibraryState.inspectUserStepLibrary has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 2 (6 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bslStepSourceParser.parseStaticBslStepRegistrations (cognitive 32) src/bslStepSourceParser.ts:764— bslStepSourceParser.parseStaticBslStepRegistrations has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 4 (7 pts), boolean chains 6, loops 1 (nesting depth added 11). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaDebugClientConfiguration.configureVanessaDebugClientSelection (cognitive 32) src/vanessaDebugClientConfiguration.ts:135— vanessaDebugClientConfiguration.configureVanessaDebugClientSelection has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (7 pts), ternaries 3 (7 pts), boolean chains 3 (nesting depth added 16). Of this number, 31 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectDefinitionReferenceService.#readReferenceFile (cognitive 32) src/projectDefinitionReferences.ts:384— ProjectDefinitionReferenceService.#readReferenceFile has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesSession.load::enrich (cognitive 32) src/scenarioPropertiesSession.ts:215— ScenarioPropertiesSession.load::enrich has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 4, loops 3 (4 pts), error handling 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ScenarioPropertiesSession.load) 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.
ScenarioPropertiesAttachments.handle (cognitive 32) src/scenarioPropertiesAttachments.ts:73— ScenarioPropertiesAttachments.handle has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 6, loops 1 (2 pts), error handling 1, match/switch 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.runStandaloneFeature (cognitive 32) src/phaseSwitcher.ts:5649— PhaseSwitcherProvider.runStandaloneFeature has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.prepareVanessaLaunchContext (cognitive 32) src/phaseSwitcher.ts:11879— PhaseSwitcherProvider.prepareVanessaLaunchContext has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 8, ternaries 4 (6 pts), loops 1 (2 pts), error handling 1 (nesting depth added 7). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.fuzzyMatch (cognitive 32) src/completionProvider.ts:2650— DriveCompletionProvider.fuzzyMatch has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand (cognitive 32) src/vanessaControlYamlTrialCommands.ts:15— vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 10, ternaries 2 (4 pts), error handling 2, loops 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 32 points belong to 5 function literals inside it that branch (lines 63, 99, 87, …). 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.
additionalValueHtml (cognitive 32) media/yamlParameters.js:466— additionalValueHtml has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 14 (21 pts), boolean chains 7, if/else 3, other 1 (nesting depth added 7). Of this number, 27 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
standaloneFeatureService.readOrganization (cognitive 31) src/standaloneFeatureService.ts:82— standaloneFeatureService.readOrganization has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (12 pts), boolean chains 7, if/else 3 (6 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.changeNestedScenarioName (cognitive 31) src/phaseSwitcher.ts:5169— PhaseSwitcherProvider.changeNestedScenarioName has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 6, loops 5 (6 pts), error handling 1 (nesting depth added 3). Of this number, 26 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
commandHandlers.findFileFromText (cognitive 31) REDACTED:41— commandHandlers.findFileFromText has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (9 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlConnection.registerVanessaControl.autoConnect (cognitive 31) src/vanessaControlConnection.ts:105— vanessaControlConnection.registerVanessaControl.autoConnect has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 8, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerBridgeGenerator.handleStartFormExplorerBridge (cognitive 31) src/formExplorerBridgeGenerator.ts:146— formExplorerBridgeGenerator.handleStartFormExplorerBridge has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 7, ternaries 3 (4 pts), error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
StepLibraryPanel.handleMessage (cognitive 31) src/stepLibraryPanel.ts:408— StepLibraryPanel.handleMessage has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 4 (11 pts), error handling 2 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 16). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 506, 481, 448). 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.
create.updateRelationshipPresentation (cognitive 31) media/standaloneFeatures.js:463— create.updateRelationshipPresentation has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 16, if/else 5 (10 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 8). Of this number, 23 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
phaseSwitcher.enablePhaseControls (cognitive 30) media/phaseSwitcher.js:200— phaseSwitcher.enablePhaseControls has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 7, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 230, 214, 210). 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.
phaseSwitcherMetadata.isLikelyValidKotMetadataBlockLines (cognitive 30) src/phaseSwitcherMetadata.ts:435— phaseSwitcherMetadata.isLikelyValidKotMetadataBlockLines has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioYamlDocument.readOriginalScalar (cognitive 30) src/scenarioYamlDocument.ts:262— scenarioYamlDocument.readOriginalScalar has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 11, loops 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibraryStore.importLegacy (cognitive 30) src/projectLibraryStore.ts:866— ProjectLibraryStore.importLegacy has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, ternaries 2 (4 pts), loops 3 (nesting depth added 9). None of this is in the body itself: all 30 points belong to 3 function literals inside it that branch (lines 867, 888, 890). 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.
VanessaExecutionHighlighter.renderMany (cognitive 30) src/vanessaControlHighlighting.ts:38— VanessaExecutionHighlighter.renderMany has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 2 (7 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioFilesService.prepareDrop (cognitive 30) src/scenarioFilesService.ts:453— ScenarioFilesService.prepareDrop has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, ternaries 2 (4 pts), loops 3, error handling 1 (nesting depth added 10). Of this number, 27 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.prepareTargetInfobaseForVanessa (cognitive 30) src/phaseSwitcher.ts:11624— PhaseSwitcherProvider.prepareTargetInfobaseForVanessa has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 11, loops 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 11679, 11663, 11797, …). 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.
commandHandlers.insertNestedScenarioRefHandler (cognitive 30) REDACTED:556— commandHandlers.insertNestedScenarioRefHandler has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), error handling 2 (5 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
commandHandlers.parseCalledScenariosFromScriptBody (cognitive 30) REDACTED:765— commandHandlers.parseCalledScenariosFromScriptBody has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (23 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
vanessaInfobaseClientCommands.handleVanessaInfobaseClientMessage (cognitive 30) src/vanessaInfobaseClientCommands.ts:12— vanessaInfobaseClientCommands.handleVanessaInfobaseClientMessage has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 6, ternaries 2 (4 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlYamlTrial.prepareVanessaYamlTrial (cognitive 30) src/vanessaControlYamlTrial.ts:33— vanessaControlYamlTrial.prepareVanessaYamlTrial has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 8, ternaries 6, loops 2 (nesting depth added 1). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
create.accept (cognitive 30) media/featureProperties.js:125— create.accept has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
(anonymous) (cognitive 30) media/kotWorkspace.js:275— (anonymous) has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 5 (11 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 11). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioYamlDocument.readRecords (cognitive 29) src/scenarioYamlDocument.ts:474— ScenarioYamlDocument.readRecords has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (5 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioRelationshipIndex.fromCatalog (cognitive 29) src/scenarioRelationshipIndex.ts:35— ScenarioRelationshipIndex.fromCatalog has cognitive complexity 29 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 6 (11 pts), ternaries 5 (7 pts) (nesting depth added 14). Of this number, 25 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobasePicker.updateInfobaseInLauncher (cognitive 29) REDACTED:431— infobasePicker.updateInfobaseInLauncher has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (5 pts), ternaries 3 (4 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.collectManagedInfobases::observeInfobase (cognitive 29) src/infobaseManager.ts:1131— infobaseManager.collectManagedInfobases::observeInfobase has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 8, loops 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (infobaseManager.collectManagedInfobases) 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.
PhaseSwitcherProvider.refreshScenarioHighlightsBySelectedRunSource (cognitive 29) src/phaseSwitcher.ts:3627— PhaseSwitcherProvider.refreshScenarioHighlightsBySelectedRunSource has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.summarizeScenarioProcessStageTitle (cognitive 29) REDACTED:1922— scenarioAiDescription.summarizeScenarioProcessStageTitle has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 8, boolean chains 5 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
userStepLibraryBuilder.buildUserStepLibrary (cognitive 29) src/userStepLibraryBuilder.ts:55— userStepLibraryBuilder.buildUserStepLibrary has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 4, ternaries 2 (3 pts), error handling 2 (nesting depth added 7). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.render (cognitive 29) media/infobaseVanessaClients.js:63— create.render has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (7 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 3). 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.
standaloneFeatures.create.updateRelationshipPresentation (cognitive 28) media/standaloneFeatures.js:463— standaloneFeatures.create.updateRelationshipPresentation has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 17, if/else 5 (10 pts), loops 1 (nesting depth added 5). Of this number, 20 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
yamlParameters.document.addEventListener("input") (cognitive 28) media/yamlParameters.js:1188— yamlParameters.document.addEventListener("input") has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaControlSession.withTestClientControl (cognitive 28) src/vanessaControlSession.ts:167— VanessaControlSession.withTestClientControl has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (23 pts), boolean chains 5 (nesting depth added 13). None of this is in the body itself: all 28 points belong to 2 function literals inside it that branch (lines 171, 170). 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.
oneCInfobaseTemplates.discoverInfobaseTemplates (cognitive 28) src/oneCInfobaseTemplates.ts:20— oneCInfobaseTemplates.discoverInfobaseTemplates has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 8, ternaries 3 (4 pts), loops 2 (nesting depth added 8). None of this is in the body itself: all 28 points belong to 6 function literals inside it that branch (lines 27, 22, 24, …). 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.
PhaseSwitcherProvider.handleScenarioFilesMessage (cognitive 28) src/phaseSwitcher.ts:7065— PhaseSwitcherProvider.handleScenarioFilesMessage has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (16 pts), error handling 3 (5 pts), ternaries 2 (4 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioDiagnosticsProvider.getRelatedScenarioUris (cognitive 28) src/scenarioDiagnostics.ts:1356— ScenarioDiagnosticsProvider.getRelatedScenarioUris has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
userStepCreator.ensureUserStepRuntimeContext (cognitive 28) src/userStepCreator.ts:67— userStepCreator.ensureUserStepRuntimeContext has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (6 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 12). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
userStepCommands.createUserStepCommand (cognitive 28) src/userStepCommands.ts:140— userStepCommands.createUserStepCommand has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 4 (6 pts), boolean chains 2, loops 2 (nesting depth added 8). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.importUserCatalogs (cognitive 28) src/nativeProjectCatalogSettings.ts:131— nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.importUserCatalogs has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (7 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 12). Of this number, 26 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.render (cognitive 28) media/featureProperties.js:57— create.render has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 5 (9 pts), ternaries 5, boolean chains 3 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
(anonymous) (cognitive 28) media/yamlParameters.js:1188— (anonymous) has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.applyCheckboxStatesToVisible (cognitive 27) media/phaseSwitcher.js:2987— phaseSwitcher.applyCheckboxStatesToVisible has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 11, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2994, 3075, 3026). 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.
stepLibraryProtocol.searchItems (cognitive 27) media/stepLibraryProtocol.js:215— stepLibraryProtocol.searchItems has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (12 pts), ternaries 2, loops 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerYamlBlocks.sectionsForEdit (cognitive 27) src/compilerYamlBlocks.ts:9— compilerYamlBlocks.sectionsForEdit has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, ternaries 3 (6 pts), loops 3 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectDefinitionReferenceService.findReferencesForDefinitions (cognitive 27) src/projectDefinitionReferences.ts:172— ProjectDefinitionReferenceService.findReferencesForDefinitions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 6 (10 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioRelationshipService.buildEnrichedStateValue (cognitive 27) src/scenarioRelationshipService.ts:240— ScenarioRelationshipService.buildEnrichedStateValue has cognitive complexity 27 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 6 (10 pts), boolean chains 3, ternaries 2 (nesting depth added 9). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinTableUtils.completeTableBlocks (cognitive 27) src/gherkinTableUtils.ts:122— gherkinTableUtils.completeTableBlocks has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerBuildRuntime.mergeCompilerBuildOutputs::copy (cognitive 27) src/compilerBuildRuntime.ts:116— compilerBuildRuntime.mergeCompilerBuildOutputs::copy has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), error handling 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (compilerBuildRuntime.mergeCompilerBuildOutputs) 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.
scenarioPropertiesLibrarySupport.createPropertiesLibrarySupport.createFeatureController (cognitive 27) src/scenarioPropertiesLibrarySupport.ts:57— scenarioPropertiesLibrarySupport.createPropertiesLibrarySupport.createFeatureController has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (22 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 6). None of this is in the body itself: all 27 points belong to 3 function literals inside it that branch (lines 67, 59, 62). 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.
PhaseSwitcherProvider.reorderProjectLibrary (cognitive 27) src/phaseSwitcher.ts:5798— PhaseSwitcherProvider.reorderProjectLibrary has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (8 pts), boolean chains 7, error handling 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.collectVanessaInfobaseCandidates (cognitive 27) src/phaseSwitcher.ts:10467— PhaseSwitcherProvider.collectVanessaInfobaseCandidates has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, ternaries 1 (4 pts), loops 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
formExplorerEnrichment.collectObjectAttributeLabels (cognitive 27) REDACTED:400— formExplorerEnrichment.collectObjectAttributeLabels has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.collectScenarioVariableDefinitionsBeforeLine (cognitive 27) src/completionProvider.ts:1921— DriveCompletionProvider.collectScenarioVariableDefinitionsBeforeLine has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 4 (8 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotProjectSetup.planNewProject (cognitive 27) src/kotProjectSetup.ts:95— kotProjectSetup.planNewProject has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 11 (21 pts), if/else 4 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderFields (cognitive 27) media/kotWorkspace.js:124— renderFields has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 7 (10 pts), boolean chains 4, error handling 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 39 function items inside it that branch ((anonymous)::onchange, a function literal at line 150, a function literal at line 127, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
app.fieldHtml (cognitive 26) docs/ux/first-run/app.js:152— app.fieldHtml has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 10, ternaries 2 (3 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
infobaseVanessaClients.create.render (cognitive 26) media/infobaseVanessaClients.js:63— infobaseVanessaClients.create.render has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (7 pts), loops 1 (nesting depth added 2). 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.
stepLibraryProtocol.reconcileCategorySelection (cognitive 26) media/stepLibraryProtocol.js:475— stepLibraryProtocol.reconcileCategorySelection has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 9, ternaries 5 (9 pts), if/else 5 (7 pts), loops 1 (nesting depth added 6). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcherMetadata.findKotMetadataStructure (cognitive 26) src/phaseSwitcherMetadata.ts:179— phaseSwitcherMetadata.findKotMetadataStructure has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibraryStore.setMetadata (cognitive 26) src/projectLibraryStore.ts:674— ProjectLibraryStore.setMetadata has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 11, error handling 1, loops 1, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 26 points belong to 3 function literals inside it that branch (lines 675, 698, 708). 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.
YamlParametersManager.flattenAdditionalParametersFromJson (cognitive 26) REDACTED:675— YamlParametersManager.flattenAdditionalParametersFromJson has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 4 (13 pts), if/else 7 (12 pts), boolean chains 1 (nesting depth added 14). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 699). 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.
standaloneFeatureController.parseStandaloneFeatureMessage (cognitive 26) src/standaloneFeatureController.ts:69— standaloneFeatureController.parseStandaloneFeatureMessage has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, ternaries 8, if/else 4. 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.
compilerBuildRuntime.mergeCompilerBuildOutputs (cognitive 26) src/compilerBuildRuntime.ts:105— compilerBuildRuntime.mergeCompilerBuildOutputs has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (32 pts), loops 5 (11 pts), error handling 2 (8 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (compilerBuildRuntime.mergeCompilerBuildOutputs::copy) 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.
scenarioCreator.handleCreateNestedScenario (cognitive 26) src/scenarioCreator.ts:2269— scenarioCreator.handleCreateNestedScenario has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (16 pts), error handling 3 (5 pts), boolean chains 3, ternaries 2 (nesting depth added 3). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DriveCompletionProvider.buildSemanticStepCompletionList (cognitive 26) src/completionProvider.ts:2503— DriveCompletionProvider.buildSemanticStepCompletionList has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 7, loops 2 (5 pts), ternaries 3 (nesting depth added 7). Of this number, 13 points are the body's own statements and 13 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configurationDiffAiReport.buildConfigurationDiffPrompt (cognitive 26) REDACTED:1592— configurationDiffAiReport.buildConfigurationDiffPrompt has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (18 pts), boolean chains 7, if/else 1 (nesting depth added 6). Of this number, 23 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlBreakpointCommands.registerVanessaBreakpointCommands::act (cognitive 26) src/vanessaControlBreakpointCommands.ts:48— vanessaControlBreakpointCommands.registerVanessaBreakpointCommands::act has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5, ternaries 2 (5 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
processCreator.handleCreateProcess (cognitive 26) src/processCreator.ts:81— processCreator.handleCreateProcess has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14, ternaries 5 (8 pts), boolean chains 3, error handling 1 (nesting depth added 3). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
processCreator.handleEditProcessSteps (cognitive 26) src/processCreator.ts:218— processCreator.handleEditProcessSteps has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 3 (8 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlFormTools.validateValue (cognitive 25) src/vanessaControlFormTools.ts:126— vanessaControlFormTools.validateValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 11 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaFeatureControl.run (cognitive 25) src/vanessaControlFeature.ts:45— VanessaFeatureControl.run has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioYamlMutations.updateNestedScenarioNameReferencesInScenarioContent (cognitive 25) src/scenarioYamlMutations.ts:290— scenarioYamlMutations.updateNestedScenarioNameReferencesInScenarioContent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCreator.handleCreateMainScenario (cognitive 25) src/scenarioCreator.ts:2461— scenarioCreator.handleCreateMainScenario has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16, boolean chains 4, ternaries 4, error handling 1. Of this number, 19 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.openFeatureFromTrackedLogSession (cognitive 25) src/phaseSwitcher.ts:12839— PhaseSwitcherProvider.openFeatureFromTrackedLogSession has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4, ternaries 2, error handling 1, loops 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 9 belong to 2 function items inside it that branch. 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.
formExplorerEnrichment.parseXml (cognitive 25) REDACTED:189— formExplorerEnrichment.parseXml has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configurationDiffAiReport.analyzeConfigurationPath (cognitive 25) REDACTED:522— configurationDiffAiReport.analyzeConfigurationPath has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14, boolean chains 10, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioAiDescription.normalizeStructuredSectionValue (cognitive 25) REDACTED:231— scenarioAiDescription.normalizeStructuredSectionValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.buildScenarioProcessStageFragments (cognitive 25) REDACTED:2145— scenarioAiDescription.buildScenarioProcessStageFragments has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 9 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.buildDeterministicCheckedItems (cognitive 25) REDACTED:2351— scenarioAiDescription.buildDeterministicCheckedItems has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 9 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand.render (cognitive 25) src/vanessaControlYamlTrialCommands.ts:35— vanessaControlYamlTrialCommands.registerVanessaYamlTrialCommand.render has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (18 pts), boolean chains 4, if/else 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.resolveActualSnapshotPath (cognitive 25) src/formExplorerPanel.ts:1004— FormExplorerPanel.resolveActualSnapshotPath has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 3 (5 pts), loops 1 (2 pts), ternaries 2, boolean chains 1 (nesting depth added 9). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.rebuild (cognitive 25) src/nativeProjectCatalogSettings.ts:177— nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.rebuild has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, if/else 5 (10 pts), loops 2 (nesting depth added 5). Of this number, 18 points are the body's own statements and 7 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
render (cognitive 25) media/stepLibrarySidebar.js:614— render has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10, loops 2, ternaries 2 (nesting depth added 3). Of this number, 22 points are the body's own statements and 3 belong to 7 function literals inside it that branch. 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.
vanessaLaunchJson.parseAdditionalParameterPointer (cognitive 24) src/vanessaLaunchJson.ts:256— vanessaLaunchJson.parseAdditionalParameterPointer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCompilerSyntax.validPreprocessorExpression (cognitive 24) src/scenarioCompilerSyntax.ts:86— scenarioCompilerSyntax.validPreprocessorExpression has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 4, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlForms.parseVanessaFormElement (cognitive 24) src/vanessaControlForms.ts:77— vanessaControlForms.parseVanessaFormElement has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerFormatDiagnostics.collectCompilerFormatIssues::inspect (cognitive 24) src/compilerFormatDiagnostics.ts:61— compilerFormatDiagnostics.collectCompilerFormatIssues::inspect has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaYamlControl.run (cognitive 24) src/vanessaControlYaml.ts:60— VanessaYamlControl.run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7, ternaries 1 (nesting depth added 3). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
StandaloneFeatureService.scanUntilCurrent (cognitive 24) src/standaloneFeatureService.ts:447— StandaloneFeatureService.scanUntilCurrent has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (7 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featureRenameCommands.renameExportScenario (cognitive 24) src/featureRenameCommands.ts:98— featureRenameCommands.renameExportScenario has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, error handling 1, loops 1, ternaries 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.pickManagedInfobasePath (cognitive 24) src/infobaseManager.ts:3254— infobaseManager.pickManagedInfobasePath has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10, boolean chains 8, ternaries 3 (5 pts), loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ScenarioPropertiesPanel.constructor (cognitive 24) src/scenarioPropertiesPanel.ts:333— ScenarioPropertiesPanel.constructor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, error handling 3 (4 pts), loops 3 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 373, 343, 358, …). 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.
PhaseSwitcherProvider.applyScenarioRuntimeRenamePlan (cognitive 24) src/phaseSwitcher.ts:1183— PhaseSwitcherProvider.applyScenarioRuntimeRenamePlan has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 6, loops 2 (nesting depth added 8). Of this number, 17 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.temporarilyMoveDisabledScenarioTestFilesForBuild (cognitive 24) src/phaseSwitcher.ts:1383— PhaseSwitcherProvider.temporarilyMoveDisabledScenarioTestFilesForBuild has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.terminateChildProcessTree (cognitive 24) src/phaseSwitcher.ts:6314— PhaseSwitcherProvider.terminateChildProcessTree has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 3 (6 pts), boolean chains 4 (nesting depth added 10). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider._sendInitialState (cognitive 24) src/phaseSwitcher.ts:7663— PhaseSwitcherProvider._sendInitialState has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, loops 2 (3 pts), ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 6). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.resolveScenarioLaunchTarget (cognitive 24) src/phaseSwitcher.ts:9909— PhaseSwitcherProvider.resolveScenarioLaunchTarget has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveCompletionProvider.buildFeatureStructureCompletions (cognitive 24) src/completionProvider.ts:2839— DriveCompletionProvider.buildFeatureStructureCompletions has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (22 pts), if/else 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StepSuggestionIndex.getSuggestions (cognitive 24) src/stepSuggestionIndex.ts:80— StepSuggestionIndex.getSuggestions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioDiagnostics.parseScenarioCallBlocks (cognitive 24) src/scenarioDiagnostics.ts:163— scenarioDiagnostics.parseScenarioCallBlocks has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepCatalogTemplateXml.writeCatalogPublication (cognitive 24) src/stepCatalogTemplateXml.ts:378— stepCatalogTemplateXml.writeCatalogPublication has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
enableAssembleControls (cognitive 24) media/phaseSwitcher.js:583— enableAssembleControls has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 8, boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.bindProjectOrderingTarget (cognitive 23) media/phaseSwitcher.js:1534— phaseSwitcher.bindProjectOrderingTarget has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 6, if/else 5 (nesting depth added 5). None of this is in the body itself: all 23 points belong to 4 function items inside it that branch (a function literal at line 1549, a function literal at line 1540, valid, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
scenarioPropertiesProtocol.validateMessage (cognitive 23) media/scenarioPropertiesProtocol.js:66— scenarioPropertiesProtocol.validateMessage has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 11. 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.
stepLibrary.renderDetailsResources (cognitive 23) media/stepLibrary.js:1612— stepLibrary.renderDetailsResources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectDefinitionReferenceService.#enumerateSources (cognitive 23) src/projectDefinitionReferences.ts:307— ProjectDefinitionReferenceService.#enumerateSources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (5 pts), ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 13). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 320). 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.
YamlParametersManager.manageProfiles (cognitive 23) REDACTED:1773— YamlParametersManager.manageProfiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, ternaries 2, match/switch 1 (nesting depth added 7). Of this number, 20 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaRunLog.extractFailedStep (cognitive 23) REDACTED:23— vanessaRunLog.extractFailedStep has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaRunLog.extractLastStepLocation (cognitive 23) REDACTED:377— vanessaRunLog.extractLastStepLocation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobasePicker.registerInfobaseInLauncher (cognitive 23) REDACTED:294— infobasePicker.registerInfobaseInLauncher has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (6 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.verifyCompilerBuildPreflight (cognitive 23) src/phaseSwitcher.ts:8388— PhaseSwitcherProvider.verifyCompilerBuildPreflight has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 6 (7 pts), ternaries 5 (7 pts), boolean chains 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerLiveSnapshot.resolveActualLiveSnapshotPath (cognitive 23) src/formExplorerLiveSnapshot.ts:45— formExplorerLiveSnapshot.resolveActualLiveSnapshotPath has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 3 (5 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 9). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configurationDiffAiReport.buildTestingFocusAreasMarkdown (cognitive 23) REDACTED:1210— configurationDiffAiReport.buildTestingFocusAreasMarkdown has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (19 pts), if/else 2 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotProjectSetup.applySetupFiles (cognitive 23) src/kotProjectSetup.ts:118— kotProjectSetup.applySetupFiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (6 pts), boolean chains 3, error handling 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.extractScenarioSemanticFactsFromValue (cognitive 23) REDACTED:1538— scenarioAiDescription.extractScenarioSemanticFactsFromValue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12, boolean chains 9, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StepLibrarySidebarIndex.children (cognitive 23) src/stepLibrarySidebarModel.ts:467— StepLibrarySidebarIndex.children has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 12 (19 pts), boolean chains 2, if/else 2 (nesting depth added 7). Of this number, 15 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlFormLanguage.translateVanessaFormSteps (cognitive 23) REDACTED:33— vanessaControlFormLanguage.translateVanessaFormSteps has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 8). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 35, 50). 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.
makeRow (cognitive 23) media/infobaseSidebar.js:111— makeRow has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8, ternaries 6 (8 pts), boolean chains 7 (nesting depth added 2). Of this number, 13 points are the body's own statements and 10 belong to 3 function literals inside it that branch. 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.
applyScenarioVisibility (cognitive 23) media/phaseSwitcher.js:479— applyScenarioVisibility has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (9 pts), ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 525, 502, 562, …). 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.
create.showMenu (cognitive 23) media/standaloneFeatures.js:164— create.showMenu has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 178, 205, 194, …). 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.
create.row (cognitive 23) media/standaloneFeatures.js:240— create.row has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 7, if/else 5, loops 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 259, 250, 258). 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.
maskVanessaSections (cognitive 23) src/gherkinSyntaxValidator.js:9— maskVanessaSections has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 13, 24). 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.
scenarioFilesProtocol.projectCompiledScenarioChildren (cognitive 22) media/scenarioFilesProtocol.js:277— scenarioFilesProtocol.projectCompiledScenarioChildren has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 9, if/else 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
yamlParameters.additionalRowHtml (cognitive 22) media/yamlParameters.js:500— yamlParameters.additionalRowHtml has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 6, if/else 1 (nesting depth added 4). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaParameterParser.parseVanessaParameterSources (cognitive 22) REDACTED:18— vanessaParameterParser.parseVanessaParameterSources has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3, boolean chains 2, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
scenarioPropertiesModel.fieldEdit (cognitive 22) src/scenarioPropertiesModel.ts:178— scenarioPropertiesModel.fieldEdit has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 6, if/else 5 (6 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesModel.addScenarioPropertyRecord (cognitive 22) src/scenarioPropertiesModel.ts:303— scenarioPropertiesModel.addScenarioPropertyRecord has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workspaceScanner.readScenarioDefinitions (cognitive 22) src/workspaceScanner.ts:215— workspaceScanner.readScenarioDefinitions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 2 (3 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlVariables.parseVanessaVariables (cognitive 22) src/vanessaControlVariables.ts:22— vanessaControlVariables.parseVanessaVariables has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 6, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectDefinitionSnippet.buildProjectDefinitionSnippetData (cognitive 22) src/projectDefinitionSnippet.ts:106— projectDefinitionSnippet.buildProjectDefinitionSnippetData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StandaloneFeatureService.moveFeature (cognitive 22) src/standaloneFeatureService.ts:347— StandaloneFeatureService.moveFeature has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 7). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 348, 373). 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.
scenarioCreator.promptForSelectedEtalonBaseValues (cognitive 22) src/scenarioCreator.ts:643— scenarioCreator.promptForSelectedEtalonBaseValues has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 3, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesPanel.post (cognitive 22) src/scenarioPropertiesPanel.ts:705— ScenarioPropertiesPanel.post has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 7, if/else 4, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
processEditorCommands.changeProcessTestSettingsFromEditor (cognitive 22) src/processEditorCommands.ts:132— processEditorCommands.changeProcessTestSettingsFromEditor has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 2). Of this number, 19 points are the body's own statements and 3 belong to 3 function literals inside it that branch. 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.
PhaseSwitcherProvider.pollLiveRunLogWatcher (cognitive 22) src/phaseSwitcher.ts:4147— PhaseSwitcherProvider.pollLiveRunLogWatcher has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, loops 1 (2 pts), error handling 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.
PhaseSwitcherProvider.openVanessaStandaloneDebug (cognitive 22) src/phaseSwitcher.ts:6833— PhaseSwitcherProvider.openVanessaStandaloneDebug has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 3, boolean chains 2, error handling 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
ProjectDefinitionProvider.provideDefinition (cognitive 22) src/projectDefinitionNavigation.ts:101— ProjectDefinitionProvider.provideDefinition has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9, ternaries 6 (8 pts), boolean chains 5 (nesting depth added 2). Of this number, 18 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
commandHandlers.parseExistingParameterData (cognitive 22) REDACTED:1287— commandHandlers.parseExistingParameterData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 11). Of this number, 20 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectMetadataConflictCommand.registerMetadataConflictCommand (cognitive 22) src/projectMetadataConflictCommand.ts:9— projectMetadataConflictCommand.registerMetadataConflictCommand has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, error handling 2 (3 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 22 points belong to 3 function literals inside it that branch (lines 14, 47, 58). 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.
spprScenarioBatchConversion.handleBatchScenarioFormatConversion (cognitive 22) src/spprScenarioBatchConversion.ts:95— spprScenarioBatchConversion.handleBatchScenarioFormatConversion has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (10 pts), error handling 3 (6 pts), if/else 5 (6 pts) (nesting depth added 10). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCallableConversion.exportToNested (cognitive 22) src/scenarioCallableConversion.ts:166— scenarioCallableConversion.exportToNested has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (14 pts), ternaries 3 (4 pts), boolean chains 3, loops 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 5 belong to 2 function literals inside it that branch. 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.
render (cognitive 22) media/formExplorer.js:628— render has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (6 pts), ternaries 3 (4 pts) (nesting depth added 2). 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.
(anonymous) (cognitive 22) media/scenarioProperties.js:724— (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 2 (5 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createTreeNode (cognitive 22) media/stepLibrary.js:439— createTreeNode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, ternaries 4, loops 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 6 belong to 4 function literals inside it that branch. 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.
formExplorer.normalizeSuggestedStepText (cognitive 21) media/formExplorer.js:1609— formExplorer.normalizeSuggestedStepText has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.document.body.addEventListener("click") (cognitive 21) media/infobaseManager.js:976— infobaseManager.document.body.addEventListener("click") has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
infobaseVanessaClients.renderClientRows (cognitive 21) media/infobaseVanessaClients.js:5— infobaseVanessaClients.renderClientRows has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (14 pts), boolean chains 7 (nesting depth added 2). None of this is in the body itself: all 21 points belong to 2 function items inside it that branch (a function literal at line 9, button). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
kotWorkspace.window.addEventListener("message") (cognitive 21) media/kotWorkspace.js:275— kotWorkspace.window.addEventListener("message") has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 6). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcherProtocol.parseRelationshipState (cognitive 21) media/phaseSwitcherProtocol.js:34— phaseSwitcherProtocol.parseRelationshipState has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 7, ternaries 3 (4 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 43, 73). 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.
stepLibrarySidebar.requestChildren (cognitive 21) media/stepLibrarySidebar.js:695— stepLibrarySidebar.requestChildren has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bslStepSourceParser.parseDeclarations (cognitive 21) src/bslStepSourceParser.ts:289— bslStepSourceParser.parseDeclarations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bslStepSourceParser.evaluateStaticExpression (cognitive 21) src/bslStepSourceParser.ts:356— bslStepSourceParser.evaluateStaticExpression has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (5 pts), boolean chains 4, loops 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (primary, expression). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ProjectLibraryStore.seedLegacyEntities (cognitive 21) src/projectLibraryStore.ts:826— ProjectLibraryStore.seedLegacyEntities has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, loops 1 (nesting depth added 8). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 828, 841, 845). 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.
exportScenarioParser.extractParameters (cognitive 21) src/exportScenarioParser.ts:272— exportScenarioParser.extractParameters has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerProcessSelection.readCompilerSettingsFiles::visit (cognitive 21) src/compilerProcessSelection.ts:20— compilerProcessSelection.readCompilerSettingsFiles::visit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (6 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibraryModel.mainScenarioItems (cognitive 21) src/stepLibraryModel.ts:185— stepLibraryModel.mainScenarioItems has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 4, if/else 2 (nesting depth added 2). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 190, 194). 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.
ScenarioFilesService.renameFile (cognitive 21) src/scenarioFilesService.ts:409— ScenarioFilesService.renameFile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, error handling 1 (2 pts), loops 1, ternaries 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
StandaloneFeatureService.updateWatches (cognitive 21) src/standaloneFeatureService.ts:528— StandaloneFeatureService.updateWatches has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 10). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 535). 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.
infobaseManager.promptNewInfobaseTarget (cognitive 21) src/infobaseManager.ts:1488— infobaseManager.promptNewInfobaseTarget has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 8, ternaries 1 (3 pts), loops 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCreator.manageEtalonBaseProfiles (cognitive 21) src/scenarioCreator.ts:1588— scenarioCreator.manageEtalonBaseProfiles has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 10). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesAttachments.importUris (cognitive 21) src/scenarioPropertiesAttachments.ts:141— ScenarioPropertiesAttachments.importUris has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 6). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsInventory.discover::walk (cognitive 21) src/scenarioPropertiesPanel.ts:137— SettingsInventory.discover::walk has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, error handling 1 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.applyTrackedRunStepSyncLogLine (cognitive 21) src/phaseSwitcher.ts:3732— PhaseSwitcherProvider.applyTrackedRunStepSyncLogLine has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.changeScenarioGroup (cognitive 21) src/phaseSwitcher.ts:5852— PhaseSwitcherProvider.changeScenarioGroup has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4 (6 pts), boolean chains 3 (nesting depth added 4). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette (cognitive 21) src/phaseSwitcher.ts:6480— PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 5, if/else 4 (nesting depth added 3). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6508, 6495). 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. This shape REPEATS in the file: one other method here (PhaseSwitcherProvider.pickScenarioForVanessaRun) 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.
PhaseSwitcherProvider.pickScenarioForVanessaRun (cognitive 21) src/phaseSwitcher.ts:6716— PhaseSwitcherProvider.pickScenarioForVanessaRun has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 5, if/else 4 (nesting depth added 3). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6744, 6731). 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. This shape REPEATS in the file: one other method here (PhaseSwitcherProvider.openScenarioInVanessaManualFromCommandPalette) 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.
PhaseSwitcherProvider.setSingleScenarioExecutionState (cognitive 21) src/phaseSwitcher.ts:9469— PhaseSwitcherProvider.setSingleScenarioExecutionState has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 2, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.findFirstStringByKeySet (cognitive 21) src/phaseSwitcher.ts:10818— PhaseSwitcherProvider.findFirstStringByKeySet has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KotWorkspacePanel.dispatch (cognitive 21) src/kotWorkspacePanel.ts:116— KotWorkspacePanel.dispatch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 7, ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vanessaControlStepSources.prepareVanessaResultSources.expand (cognitive 21) src/vanessaControlStepSources.ts:21— vanessaControlStepSources.prepareVanessaResultSources.expand has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 2 (3 pts), error handling 1, ternaries 1 (nesting depth added 4). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepCatalogCategories.enrichStepCatalogCategories (cognitive 21) src/stepCatalogCategories.ts:238— stepCatalogCategories.enrichStepCatalogCategories has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3, loops 2 (nesting depth added 7). Of this number, 14 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 21) media/infobaseManager.js:976— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
additionalValueError (cognitive 21) media/yamlParameters.js:449— additionalValueError has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 2 (5 pts), error handling 1 (2 pts), other 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.
scenarioProperties.window.addEventListener("message") (cognitive 20) media/scenarioProperties.js:724— scenarioProperties.window.addEventListener("message") has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 2 (5 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
vanessaLaunchJson.applyAdditionalVanessaParameters (cognitive 20) src/vanessaLaunchJson.ts:511— vanessaLaunchJson.applyAdditionalVanessaParameters has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotMetadataDescription.wrapNormalizedDescription (cognitive 20) src/kotMetadataDescription.ts:191— kotMetadataDescription.wrapNormalizedDescription has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioYamlDocument.findRecordFieldsForEdit (cognitive 20) src/scenarioYamlDocument.ts:557— ScenarioYamlDocument.findRecordFieldsForEdit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioParameterUtils.parseScenarioParameterDefinitions (cognitive 20) src/scenarioParameterUtils.ts:102— scenarioParameterUtils.parseScenarioParameterDefinitions has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 4, if/else 3 (nesting depth added 4). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 106, 127). 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.
ScenarioFilesService.deleteFile (cognitive 20) src/scenarioFilesService.ts:351— ScenarioFilesService.deleteFile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featureCreator.createFeature (cognitive 20) src/featureCreator.ts:54— featureCreator.createFeature has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (9 pts), boolean chains 1, error handling 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.
oneCInfobaseTemplatePicker.pickInstalledInfobaseTemplate (cognitive 20) src/oneCInfobaseTemplatePicker.ts:21— oneCInfobaseTemplatePicker.pickInstalledInfobaseTemplate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (9 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.updateInfobaseConfigurationInteractive (cognitive 20) src/infobaseManager.ts:2469— infobaseManager.updateInfobaseConfigurationInteractive has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
featureEditorActions.scanFeatureStructure (cognitive 20) src/featureEditorActions.ts:63— featureEditorActions.scanFeatureStructure has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, ternaries 3 (4 pts), loops 3 (nesting depth added 5). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesCatalogPresentation.applyPropertyCatalogPresentation (cognitive 20) src/scenarioPropertiesCatalogPresentation.ts:5— scenarioPropertiesCatalogPresentation.applyPropertyCatalogPresentation has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (8 pts), loops 1, ternaries 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
SettingsInventory.list (cognitive 20) src/scenarioPropertiesPanel.ts:108— SettingsInventory.list has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (nesting depth added 8). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioPropertiesPanel.bind (cognitive 20) src/scenarioPropertiesPanel.ts:527— ScenarioPropertiesPanel.bind has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (3 pts), boolean chains 2, error handling 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.
PhaseSwitcherProvider.addScenarioToFavoritesByUri (cognitive 20) src/phaseSwitcher.ts:4690— PhaseSwitcherProvider.addScenarioToFavoritesByUri has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.removeScenarioCustomInfobasePathsForUris (cognitive 20) src/phaseSwitcher.ts:9853— PhaseSwitcherProvider.removeScenarioCustomInfobasePathsForUris has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
commandHandlers.clearAndFillNestedScenarios::progressHandler (cognitive 20) REDACTED:1116— commandHandlers.clearAndFillNestedScenarios::progressHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, ternaries 2 (3 pts), error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
VanessaFormExplorerSource.refresh (cognitive 20) src/vanessaControlFormSource.ts:53— VanessaFormExplorerSource.refresh has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 3 (5 pts) (nesting depth added 4). Of this number, 14 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kotWorkspaceConfiguration.createWorkspaceSettingsSession (cognitive 20) src/kotWorkspaceConfiguration.ts:5— kotWorkspaceConfiguration.createWorkspaceSettingsSession has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 6, ternaries 4 (5 pts) (nesting depth added 1). None of this is in the body itself: all 20 points belong to 6 function items inside it that branch (a function literal at line 22, a function literal at line 30, folder, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DriveHoverProvider.provideHover (cognitive 20) REDACTED:1194— DriveHoverProvider.provideHover has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 7, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FormExplorerPanel.constructor (cognitive 20) src/formExplorerPanel.ts:145— FormExplorerPanel.constructor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4 (nesting depth added 7). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 154, 175, 183). 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.
nativeProjectCatalogSettings.mergeUserCatalog (cognitive 20) src/nativeProjectCatalogSettings.ts:40— nativeProjectCatalogSettings.mergeUserCatalog has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 7). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dropEmptyDuplicateDisplayColumns (cognitive 20) media/formExplorer.js:2038— dropEmptyDuplicateDisplayColumns has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (nesting depth added 6). Of this number, 13 points are the body's own statements and 7 belong to 10 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderList (cognitive 20) media/infobaseManager.js:377— renderList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9, boolean chains 7, if/else 4. Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 400). 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.
createScenarioTypeSection (cognitive 20) media/phaseSwitcher.js:1569— createScenarioTypeSection has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 1662, a function literal at line 1601, a function literal at line 1617, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
setPhaseListExpandedState (cognitive 20) media/phaseSwitcher.js:1980— setPhaseListExpandedState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 12 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorer.renderSectionCard (cognitive 19) media/formExplorer.js:2320— formExplorer.renderSectionCard has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 4, if/else 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
kotWebviewText.attach (cognitive 19) media/kotWebviewText.js:56— kotWebviewText.attach has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
standaloneFeatures.create.showMenu (cognitive 19) media/standaloneFeatures.js:164— standaloneFeatures.create.showMenu has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 3. Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 178, 194, 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.
standaloneFeatures.create.row (cognitive 19) media/standaloneFeatures.js:240— standaloneFeatures.create.row has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (6 pts), if/else 5, loops 1 (nesting depth added 2). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 259, 250). 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.
projectLibraryIntegration.persistProjectMetadata (cognitive 19) src/projectLibraryIntegration.ts:70— projectLibraryIntegration.persistProjectMetadata has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectLibraryIntegration.registerCreatedProjectScenario (cognitive 19) src/projectLibraryIntegration.ts:97— projectLibraryIntegration.registerCreatedProjectScenario has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workspaceScanner.collectFilesFromScanDirectory (cognitive 19) src/workspaceScanner.ts:73— workspaceScanner.collectFilesFromScanDirectory has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, error handling 2, loops 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 94). 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.
vanessaControlClients.parseVanessaClientProfiles (cognitive 19) src/vanessaControlClients.ts:51— vanessaControlClients.parseVanessaClientProfiles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, loops 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 64, 68). 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.
VanessaControlSession.withFormControl (cognitive 19) src/vanessaControlSession.ts:257— VanessaControlSession.withFormControl has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 5 (6 pts), boolean chains 3, loops 1 (nesting depth added 7). None of this is in the body itself: all 19 points belong to 5 function literals inside it that branch (lines 275, 262, 267, …). 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.
VanessaControlSession.readResults (cognitive 19) src/vanessaControlSession.ts:715— VanessaControlSession.readResults has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 7, error handling 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
compilerFormatDiagnostics.commentOffset (cognitive 19) src/compilerFormatDiagnostics.ts:12— compilerFormatDiagnostics.commentOffset has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featureCreator.generateFeatureJson (cognitive 19) src/featureCreator.ts:113— featureCreator.generateFeatureJson has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (4 pts), error handling 2, boolean chains 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCreator.promptForEtalonBaseChoice (cognitive 19) src/scenarioCreator.ts:731— scenarioCreator.promptForEtalonBaseChoice has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.resolveScenarioForAutoDetectedVanessaLog (cognitive 19) src/phaseSwitcher.ts:2552— PhaseSwitcherProvider.resolveScenarioForAutoDetectedVanessaLog has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (4 pts), boolean chains 3, 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.
PhaseSwitcherProvider.ensureCombinedScenarioJsonArtifacts (cognitive 19) src/phaseSwitcher.ts:10415— PhaseSwitcherProvider.ensureCombinedScenarioJsonArtifacts has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinInsertionContext.yamlScenarioBlockContext (cognitive 19) src/gherkinInsertionContext.ts:142— gherkinInsertionContext.yamlScenarioBlockContext has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configurationDiffAiReport.handleGenerateConfigurationDiffImpactReport (cognitive 19) REDACTED:1944— configurationDiffAiReport.handleGenerateConfigurationDiffImpactReport has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), boolean chains 3, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.humanizeScenarioHeadingFragment (cognitive 19) REDACTED:1785— scenarioAiDescription.humanizeScenarioHeadingFragment has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaInfobaseClients.stateFor (cognitive 19) src/vanessaInfobaseClients.ts:104— VanessaInfobaseClients.stateFor has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (6 pts), loops 3, if/else 1 (2 pts) (nesting depth added 3). Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioDiagnosticsProvider.rebuildDuplicateScenarioCodeDiagnosticsFromCache (cognitive 19) src/scenarioDiagnostics.ts:1226— ScenarioDiagnosticsProvider.rebuildDuplicateScenarioCodeDiagnosticsFromCache has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScenarioDiagnosticsProvider.rebuildDependencyGraphFromCacheIfNeeded (cognitive 19) src/scenarioDiagnostics.ts:1300— ScenarioDiagnosticsProvider.rebuildDependencyGraphFromCacheIfNeeded has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.doRefreshStartedInfobaseProcessState (cognitive 19) src/formExplorerPanel.ts:928— FormExplorerPanel.doRefreshStartedInfobaseProcessState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6, boolean chains 5, error handling 2 (4 pts), ternaries 4 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioCallableConversion.nestedToExport (cognitive 19) src/scenarioCallableConversion.ts:101— scenarioCallableConversion.nestedToExport has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, boolean chains 6, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 115, 107, 135). 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.
stepCatalogTemplateXml.parseVanessaStepTemplateXml (cognitive 19) src/stepCatalogTemplateXml.ts:178— stepCatalogTemplateXml.parseVanessaStepTemplateXml has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
clientRows (cognitive 19) media/infobaseSidebar.js:210— clientRows has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 7, if/else 2 (3 pts), loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseRelationshipState::normalizeRelationships (cognitive 19) media/stepLibrarySidebarProtocol.js:38— parseRelationshipState::normalizeRelationships has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorer.renderSuggestedStepsBody (cognitive 18) media/formExplorer.js:1459— formExplorer.renderSuggestedStepsBody has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, ternaries 6 (7 pts), if/else 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorer.collectFormTableEntries (cognitive 18) media/formExplorer.js:1691— formExplorer.collectFormTableEntries has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, ternaries 5 (6 pts), if/else 3 (4 pts), loops 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (tryAdd, collectFromElements, a function literal at line 1770). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
phaseSwitcher.patchScenarioRelationshipDecorations (cognitive 18) media/phaseSwitcher.js:318— phaseSwitcher.patchScenarioRelationshipDecorations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 321, 371, 374). 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.
scenarioFilesProtocol.createTransferController::handleMessage (cognitive 18) media/scenarioFilesProtocol.js:408— scenarioFilesProtocol.createTransferController::handleMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioProperties.rekey (cognitive 18) media/scenarioProperties.js:121— scenarioProperties.rekey has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, error handling 1 (2 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioPropertiesProtocol.createClient::flush (cognitive 18) media/scenarioPropertiesProtocol.js:117— scenarioPropertiesProtocol.createClient::flush has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bslStepSourceParser.descriptorCategory (cognitive 18) src/bslStepSourceParser.ts:633— bslStepSourceParser.descriptorCategory has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibraryStore.discover::visit (cognitive 18) src/projectLibraryStore.ts:272— ProjectLibraryStore.discover::visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerArtifacts.parseCompilerJUnit (cognitive 18) src/compilerArtifacts.ts:300— compilerArtifacts.parseCompilerJUnit has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (13 pts), loops 2 (3 pts), boolean chains 1, if/else 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featureNestedScenarioUtils.getFeatureNestedScenarioContextAtPosition (cognitive 18) src/featureNestedScenarioUtils.ts:77— featureNestedScenarioUtils.getFeatureNestedScenarioContextAtPosition has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (6 pts), boolean chains 2, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
startupInfobase.ensureSharedStartupInfobaseReady::performEnsure (cognitive 18) src/startupInfobase.ts:385— startupInfobase.ensureSharedStartupInfobaseReady::performEnsure has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (6 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
vanessaRunLog.formatFailedStepDetailsFromLogBlock (cognitive 18) REDACTED:269— vanessaRunLog.formatFailedStepDetailsFromLogBlock has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.collectSnapshotObservations (cognitive 18) src/infobaseManager.ts:929— infobaseManager.collectSnapshotObservations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (4 pts), error handling 2 (3 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featurePropertiesModel.planFeaturePropertiesEdit (cognitive 18) src/featurePropertiesModel.ts:40— featurePropertiesModel.planFeaturePropertiesEdit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8 (nesting depth added 2). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
scenarioCreator.handleSyncTestSettingsFromScenario (cognitive 18) src/scenarioCreator.ts:1231— scenarioCreator.handleSyncTestSettingsFromScenario has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 7, error handling 2, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
scenarioPropertiesCatalogs.loadScenarioPropertiesCatalogs (cognitive 18) src/scenarioPropertiesCatalogs.ts:136— scenarioPropertiesCatalogs.loadScenarioPropertiesCatalogs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (5 pts), error handling 2 (4 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.applyFeatureStepSyncLogLine (cognitive 18) src/phaseSwitcher.ts:3415— PhaseSwitcherProvider.applyFeatureStepSyncLogLine has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PhaseSwitcherProvider.getScenarioDisplayedRunState (cognitive 18) src/phaseSwitcher.ts:4031— PhaseSwitcherProvider.getScenarioDisplayedRunState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 8, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.synchronizeFavoriteEntriesWithCache (cognitive 18) src/phaseSwitcher.ts:4634— PhaseSwitcherProvider.synchronizeFavoriteEntriesWithCache has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 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.
compilerYamlBlockEditor.addCompilerYamlBlockCommand (cognitive 18) src/compilerYamlBlockEditor.ts:37— compilerYamlBlockEditor.addCompilerYamlBlockCommand has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 7, boolean chains 2, error handling 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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.
DriveCompletionProvider.getSemanticStepScore (cognitive 18) src/completionProvider.ts:2446— DriveCompletionProvider.getSemanticStepScore has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2465, 2483). 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.
scenarioAiDescription.tryNormalizeStructuredScenarioDescription (cognitive 18) REDACTED:422— scenarioAiDescription.tryNormalizeStructuredScenarioDescription has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioAiDescription.compactScenarioParameterAssignments (cognitive 18) REDACTED:2908— scenarioAiDescription.compactScenarioParameterAssignments has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (5 pts), boolean chains 4, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioDiagnostics.findClosestDefinitions (cognitive 18) src/scenarioDiagnostics.ts:451— scenarioDiagnostics.findClosestDefinitions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibrarySidebarProvider.parseStepLibrarySidebarMessage (cognitive 18) src/stepLibrarySidebarProvider.ts:105— stepLibrarySidebarProvider.parseStepLibrarySidebarMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
formExplorerStepSuggestions.dropEmptyDuplicateDisplayColumns (cognitive 18) src/formExplorerStepSuggestions.ts:385— formExplorerStepSuggestions.dropEmptyDuplicateDisplayColumns has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 6). Of this number, 12 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerStepSuggestions.parseCatalogRows (cognitive 18) src/formExplorerStepSuggestions.ts:464— formExplorerStepSuggestions.parseCatalogRows has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7, 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.
restoreSuggestedScrollState (cognitive 18) media/formExplorer.js:1579— restoreSuggestedScrollState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalize (cognitive 18) media/yamlBuildParameterState.js:25— normalize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), other 3, ternaries 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 1 belongs to 2 function items inside it that branch. 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.
inspectParameter (cognitive 18) media/yamlParameters.js:22— inspectParameter has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (7 pts), if/else 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
formExplorer.renderTabs (cognitive 17) media/formExplorer.js:1190— formExplorer.renderTabs has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 3 (4 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 2). 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.
formExplorer.getTableElementUiLabel (cognitive 17) media/formExplorer.js:1778— formExplorer.getTableElementUiLabel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorer.collectElementStateChips (cognitive 17) media/formExplorer.js:2532— formExplorer.collectElementStateChips has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 4, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorer.collectAttributeStateChips (cognitive 17) media/formExplorer.js:2558— formExplorer.collectAttributeStateChips has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseVanessaClients.create (cognitive 17) media/infobaseVanessaClients.js:15— infobaseVanessaClients.create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3 (nesting depth added 1). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 42, 54). 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.
yamlParameters.document.addEventListener("change") (cognitive 17) media/yamlParameters.js:1255— yamlParameters.document.addEventListener("change") has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerYamlBlocks.appendCompilerYamlBlock (cognitive 17) src/compilerYamlBlocks.ts:64— compilerYamlBlocks.appendCompilerYamlBlock has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 4). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.
projectLibraryMetadata.snapshotForDisplay (cognitive 17) src/projectLibraryMetadata.ts:15— projectLibraryMetadata.snapshotForDisplay has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, loops 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaRuntimeForms.steps (cognitive 17) src/vanessaControlForms.ts:129— VanessaRuntimeForms.steps has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
vanessaControlFormTools.getVanessaFormTools (cognitive 17) src/vanessaControlFormTools.ts:107— vanessaControlFormTools.getVanessaFormTools has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 5, error handling 1 (2 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaRuntimeDiagnostics.collect (cognitive 17) src/vanessaControlDiagnostics.ts:61— VanessaRuntimeDiagnostics.collect has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (10 pts), if/else 3 (4 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaRuntimeDiagnostics.screenshot (cognitive 17) src/vanessaControlDiagnostics.ts:111— VanessaRuntimeDiagnostics.screenshot has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 2 (nesting depth added 1). 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 item inside it that branches (capture). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
vanessaDebugClientConfiguration.editClient (cognitive 17) src/vanessaDebugClientConfiguration.ts:40— vanessaDebugClientConfiguration.editClient has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProjectDefinitionIndexService.#watchFile (cognitive 17) src/projectDefinitionIndexService.ts:570— ProjectDefinitionIndexService.#watchFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 2). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
stepCatalogHttp.requestHttpsBytes (cognitive 17) src/stepCatalogHttp.ts:53— stepCatalogHttp.requestHttpsBytes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, error handling 2 (3 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 83, 124, 67, …). 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.
compilerBuildValueValidation.isXmlDateTime (cognitive 17) src/compilerBuildValueValidation.ts:47— compilerBuildValueValidation.isXmlDateTime has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (7 pts), ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
YamlParametersManager.normalizeAdditionalVanessaParameters (cognitive 17) REDACTED:596— YamlParametersManager.normalizeAdditionalVanessaParameters has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (5 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioFilesWebviewProtocol.cleanManifest (cognitive 17) src/scenarioFilesWebviewProtocol.ts:50— scenarioFilesWebviewProtocol.cleanManifest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerBuildReport.absoluteReportLink (cognitive 17) src/compilerBuildReport.ts:49— compilerBuildReport.absoluteReportLink has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3, boolean chains 1, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.splitCommandLineArguments (cognitive 17) src/infobaseManager.ts:384— infobaseManager.splitCommandLineArguments has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCreator.handleChangeTestSettingsUserProfileFromEditor (cognitive 17) src/scenarioCreator.ts:1149— scenarioCreator.handleChangeTestSettingsUserProfileFromEditor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 5, ternaries 4 (5 pts), error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
compilerProcessDefaults.fillMissingCompilerProcessDefaults (cognitive 17) src/compilerProcessDefaults.ts:5— compilerProcessDefaults.fillMissingCompilerProcessDefaults has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.pollFeatureStepTracker (cognitive 17) src/phaseSwitcher.ts:3524— PhaseSwitcherProvider.pollFeatureStepTracker has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, loops 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PhaseSwitcherProvider.buildNestedScenarioCallInsertTextForUri (cognitive 17) src/phaseSwitcher.ts:4530— PhaseSwitcherProvider.buildNestedScenarioCallInsertTextForUri has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4, error handling 2 (3 pts), ternaries 3 (nesting depth added 1). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.checkBuildErrors (cognitive 17) src/phaseSwitcher.ts:8243— PhaseSwitcherProvider.checkBuildErrors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.buildRunArtifactsState (cognitive 17) src/phaseSwitcher.ts:9672— PhaseSwitcherProvider.buildRunArtifactsState has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 2 (4 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 4). 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.
gherkinInsertionContext.getGherkinInsertionContext (cognitive 17) src/gherkinInsertionContext.ts:190— gherkinInsertionContext.getGherkinInsertionContext has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, error handling 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
configurationDiffAiReport.buildTestingFocusAreas (cognitive 17) REDACTED:740— configurationDiffAiReport.buildTestingFocusAreas has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.
scenarioAiDescription.buildDeterministicParameterItems (cognitive 17) REDACTED:2550— scenarioAiDescription.buildDeterministicParameterItems has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 2 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.
scenarioAiDescription.buildScenarioCoverageGroups (cognitive 17) REDACTED:2693— scenarioAiDescription.buildScenarioCoverageGroups has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (5 pts), ternaries 2 (5 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.
vanessaControlConnection.registerVanessaControl.startConfigured (cognitive 17) src/vanessaControlConnection.ts:156— vanessaControlConnection.registerVanessaControl.startConfigured has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 2, error handling 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vanessaControlConnection.registerVanessaControl.menu (cognitive 17) src/vanessaControlConnection.ts:244— vanessaControlConnection.registerVanessaControl.menu has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 5, boolean chains 1 (nesting depth added 4). Of this number, 10 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaInfobaseClients.adoptObservedRenames (cognitive 17) src/vanessaInfobaseClients.ts:223— VanessaInfobaseClients.adoptObservedRenames has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectFeatureTagCatalog.getTags (cognitive 17) src/projectFeatureTags.ts:19— ProjectFeatureTagCatalog.getTags has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (5 pts), boolean chains 2, error handling 1 (nesting depth added 5). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StepLibrarySidebarProvider.handleMessage (cognitive 17) src/stepLibrarySidebarProvider.ts:299— StepLibrarySidebarProvider.handleMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
InfobaseSidebarProvider.runAction (cognitive 17) src/infobaseSidebarProvider.ts:378— InfobaseSidebarProvider.runAction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, error handling 1, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerStepSuggestions.getTableElementUiLabel (cognitive 17) src/formExplorerStepSuggestions.ts:642— formExplorerStepSuggestions.getTableElementUiLabel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.handleMessage (cognitive 17) src/formExplorerPanel.ts:342— FormExplorerPanel.handleMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, ternaries 1 (2 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FormExplorerPanel.startBridge (cognitive 17) src/formExplorerPanel.ts:1265— FormExplorerPanel.startBridge has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (7 pts), if/else 2, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioCallableCommands.chooseExistingFeature (cognitive 17) src/scenarioCallableCommands.ts:43— scenarioCallableCommands.chooseExistingFeature has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.
nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.discover (cognitive 17) src/nativeProjectCatalogSettings.ts:275— nativeProjectCatalogSettings.registerNativeProjectCatalogSettings.discover has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 275, 281, 283). 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.
NativeSpprScenarioSynchronizer.onSave (cognitive 17) src/spprScenarioSync.ts:21— NativeSpprScenarioSynchronizer.onSave has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extension.createProjectDefinitionIndexService (cognitive 17) REDACTED:231— extension.createProjectDefinitionIndexService has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3. None of this is in the body itself: all 17 points belong to 8 function literals inside it that branch (lines 278, 285, 240, …). 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.
scenarioYamlCorpusVerifier.validateScenarioYamlSource (cognitive 17) src/scenarioYamlCorpusVerifier.ts:52— scenarioYamlCorpusVerifier.validateScenarioYamlSource has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
visibleScenarioAggregate (cognitive 17) media/phaseSwitcherProtocol.js:310— visibleScenarioAggregate has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (6 pts), ternaries 3 (4 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 17) media/yamlParameters.js:1255— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorer.flattenElements (cognitive 16) media/formExplorer.js:2633— formExplorer.flattenElements has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 2 (4 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 3). 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.
infobaseManager.renderStatus (cognitive 16) media/infobaseManager.js:759— infobaseManager.renderStatus has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 3, if/else 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.syncScenarioLeadingControl (cognitive 16) media/phaseSwitcher.js:1274— phaseSwitcher.syncScenarioLeadingControl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, ternaries 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phaseSwitcher.handleScenarioRowClick (cognitive 16) media/phaseSwitcher.js:2311— phaseSwitcher.handleScenarioRowClick has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
phaseSwitcher.showContextMenuAt (cognitive 16) media/phaseSwitcher.js:2755— phaseSwitcher.showContextMenuAt has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 7. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2773, 2795). 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.
scenarioProperties.settingsSection (cognitive 16) media/scenarioProperties.js:584— scenarioProperties.settingsSection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 4). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibrary.filteredItems (cognitive 16) media/stepLibrary.js:281— stepLibrary.filteredItems has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 4, if/else 4 (nesting depth added 3). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stepLibrarySidebarProtocol.parseRelationshipState (cognitive 16) media/stepLibrarySidebarProtocol.js:36— stepLibrarySidebarProtocol.parseRelationshipState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (normalizeRelationships). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
boundedConcurrency.runWithConcurrencyLimit (cognitive 16) src/boundedConcurrency.ts:14— boundedConcurrency.runWithConcurrencyLimit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (runWorker). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
projectFormat.projectFormat (cognitive 16) src/projectFormat.ts:26— projectFormat.projectFormat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 3 (4 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
projectLegacyMetadata.editLegacyMetadata (cognitive 16) src/projectLegacyMetadata.ts:19— projectLegacyMetadata.editLegacyMetadata has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gherkinAnnotations.collectGherkinProjectTags (cognitive 16) src/gherkinAnnotations.ts:147— gherkinAnnotations.collectGherkinProjectTags has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 5). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VanessaControlSession.reloadSavedFeature (cognitive 16) src/vanessaControlSession.ts:613— VanessaControlSession.reloadSavedFeature has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7 (nesting depth added 2). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
exportScenarioParser.validateGherkinSyntax (cognitive 16) src/exportScenarioParser.ts:143— exportScenarioParser.validateGherkinSyntax has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 6, loops 1 (2 pts), if/else 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceStepCatalogCoordinator.resolveCatalog (cognitive 16) src/stepCatalogService.ts:149— WorkspaceStepCatalogCoordinator.resolveCatalog has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workspaceArtifactPath.resolveWorkspaceOwnedPath (cognitive 16) src/workspaceArtifactPath.ts:104— workspaceArtifactPath.resolveWorkspaceOwnedPath has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scenarioYamlMutations.updateScenarioGroupInMetadataContent (cognitive 16) src/scenarioYamlMutations.ts:138— scenarioYamlMutations.updateScenarioGroupInMetadataContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compilerProcessSelection.adaptNestedProcessFilters::includes (cognitive 16) src/compilerProcessSelection.ts:79— compilerProcessSelection.adaptNestedProcessFilters::includes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (compilerProcessSelection.adaptNestedProcessFilters) 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.
compilerProcessSelection.adaptNestedProcessFilters (cognitive 16) src/compilerProcessSelection.ts:72— compilerProcessSelection.adaptNestedProcessFilters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 7, loops 4 (5 pts), ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (compilerProcessSelection.adaptNestedProcessFilters::includes) 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.
infobaseManager.mergeMetadataEntries (cognitive 16) src/infobaseManager.ts:576— infobaseManager.mergeMetadataEntries has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 16. 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.
infobaseManager.runInfobaseDesignerCommandWithAuthRetry (cognitive 16) src/infobaseManager.ts:1772— infobaseManager.runInfobaseDesignerCommandWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
infobaseManager.moveInfobaseInteractive (cognitive 16) src/infobaseManager.ts:2737— infobaseManager.moveInfobaseInteractive has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 2). Of this number, 9 points are the body's own statements and 7 belong to 2 function literals inside it that branch. 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.
stepLibraryFavorites.legacyEntries (cognitive 16) src/stepLibraryFavorites.ts:31— stepLibraryFavorites.legacyEntries has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (5 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
featureEditorActions.buildFeatureEditorActions (cognitive 16) src/featureEditorActions.ts:107— featureEditorActions.buildFeatureEditorActions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhaseSwitcherProvider.handleScenarioSourceSaved (cognitive 16) src/phaseSwitcher.ts:1643— PhaseSwitcherProvider.handleScenarioSourceSaved has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, loops 1 (2 pts), ternaries 2 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PhaseSwitcherProvider.startTrackedRunLogWatcher (cognitive 16) src/phaseSwitcher.ts:3911— PhaseSwitcherProvider.startTrackedRunLogWatcher has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
formExplorerEnrichment.extractLocalizedPropertyValue (cognitive 16) REDACTED:368— formExplorerEnrichment.extractLocalizedPropertyValue has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (7 pts), loops 1 (nesting depth added 3). 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.
DriveCompletionProvider.buildFormExplorerElementReferenceCompletionList (cognitive 16) src/completionProvider.ts:1522— DriveCompletionProvider.buildFormExplorerElementReferenceCompletionList has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 5, ternaries 2. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 1566, 1551, 1531, …). 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.
configurationDiffAiReport.describeConfigurationPath (cognitive 16) REDACTED:400— configurationDiffAiReport.describeConfigurationPath has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 3 (5 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
scenarioAiDescription.splitStructuredSectionLine (cognitive 16) REDACTED:177— scenarioAiDescription.splitStructuredSectionLine has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 2 (nesting depth added 3). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
formExplorerExtensionGenerator.pickFormExplorerLaunchAuthentication (cognitive 16) REDACTED:496— formExplorerExtensionGenerator.pickFormExplorerLaunchAuthentication has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry (cognitive 16) REDACTED:6116— formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 4 other methods here (formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsInstallToInfobaseWithAuthRetry, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry (cognitive 16) REDACTED:6170— formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 4 other methods here (formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsInstallToInfobaseWithAuthRetry, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry (cognitive 16) REDACTED:6225— formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 4 other methods here (formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsInstallToInfobaseWithAuthRetry, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
formExplorerExtensionGenerator.runBuiltInWindowsInstallToInfobaseWithAuthRetry (cognitive 16) REDACTED:6281— formExplorerExtensionGenerator.runBuiltInWindowsInstallToInfobaseWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 4 other methods here (formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
formExplorerExtensionGenerator.runBuiltInWindowsDirectInstallToInfobaseWithAuthRetry (cognitive 16) REDACTED:6334— formExplorerExtensionGenerator.runBuiltInWindowsDirectInstallToInfobaseWithAuthRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 4 other methods here (formExplorerExtensionGenerator.probeExtensionInstalledInInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromInfobaseWithAuthRetry, formExplorerExtensionGenerator.runBuiltInWindowsDumpConfigurationFromFileInfobaseUsingIBCmdWithAuthRetry, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
userStepCommands.dumpUserStepLibraryCommand (cognitive 16) src/userStepCommands.ts:480— userStepCommands.dumpUserStepLibraryCommand has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 3, error handling 1 (2 pts), ternaries 2 (nesting depth added 1). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
infobaseSidebarProvider.parseInfobaseSidebarMessage (cognitive 16) src/infobaseSidebarProvider.ts:117— infobaseSidebarProvider.parseInfobaseSidebarMessage has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, if/else 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.readAdapterModeState (cognitive 16) src/formExplorerPanel.ts:1121— FormExplorerPanel.readAdapterModeState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), error handling 2 (4 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormExplorerPanel.refreshMcpSnapshot (cognitive 16) src/formExplorerPanel.ts:1408— FormExplorerPanel.refreshMcpSnapshot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 7. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extension.loadExportScenarioLibraryRoots (cognitive 16) REDACTED:329— extension.loadExportScenarioLibraryRoots has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (5 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (extension.loadUserStepLibraryRoots) 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.
extension.loadUserStepLibraryRoots (cognitive 16) REDACTED:377— extension.loadUserStepLibraryRoots has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (5 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (extension.loadExportScenarioLibraryRoots) 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.
extension.collectGitModifiedYamlUris (cognitive 16) REDACTED:649— extension.collectGitModifiedYamlUris has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extension.activate (cognitive 16) REDACTED:838— extension.activate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 164 (258 pts), ternaries 62 (93 pts), boolean chains 64, error handling 23 (39 pts), loops 9 (14 pts) (nesting depth added 146). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (extension.activate::runScenarioRepairBatch) 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.
(anonymous) (cognitive 16) media/scenarioProperties.js:92— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (sendUris, a function literal at line 101, a function literal at line 96, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversionMenu (cognitive 16) media/scenarioProperties.js:245— conversionMenu has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 268, open, a function literal at line 263, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Change-coupling hub: phaseSwitcher.ts → phaseSwitcher.js, REDACTED, scenarioCreator.ts src/phaseSwitcher.ts— `src/phaseSwitcher.ts` changes together with 3 other files — `media/phaseSwitcher.js`, `REDACTED`, `src/scenarioCreator.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Low cohesion: DriveHoverProvider (LCOM4 6) REDACTED:69— DriveHoverProvider's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in the repository root ran and not one test passed ([PhaseSwitcherProvider:_handleRunAssembleScriptTypeScript] Error: Error: SPPR preflight failed with 1 error(s). See KOT output.), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
No structured logging — No logging call was found in the 301 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 3 sibling directories (18 clone groups) media/formExplorer.js:2046— 18 duplicated blocks under the repository root have copies in at least two of the sibling directories media, src, tools — 16 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (185 lines × 2 locations) src/stepLibraryPanel.ts:604— src/stepLibraryPanel.ts:604 · src/stepLibrarySidebarProvider.ts:718 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (144 matched lines × 2 locations) · ×1
Duplicated block with local edits (144 matched lines × 2 locations) src/exportScenarioCommand.ts:34— src/exportScenarioCommand.ts:34 · src/userStepCommands.ts:40 — the two spans are one implementation copied and then locally edited — 991 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (117 matched lines × 2 locations) · ×1
Duplicated block with local edits (117 matched lines × 2 locations) media/stepLibrary.js:854— media/stepLibrary.js:854 · media/stepLibrarySidebar.js:64 — the two spans are one implementation copied and then locally edited — 774 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (116 matched lines × 2 locations) · ×1
Duplicated block with local edits (116 matched lines × 2 locations) src/formExplorerBridgeGenerator.ts:141— src/formExplorerBridgeGenerator.ts:141 · REDACTED:7101 — the two spans are one implementation copied and then locally edited — 729 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (83 lines × 2 locations) media/phaseSwitcher.js:2440— media/phaseSwitcher.js:2440 · media/stepLibrary.js:681 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) src/completionProvider.ts:1941— src/completionProvider.ts:1941 · REDACTED:655 — the two spans are one implementation copied and then locally edited — 494 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (73 lines × 2 locations) REDACTED:317— REDACTED:317 · src/testReviewAiReport.ts:135 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (73 matched lines × 2 locations) · ×1
Duplicated block with local edits (73 matched lines × 2 locations) src/exportScenarioMetadataCodeLens.ts:82— src/exportScenarioMetadataCodeLens.ts:82 · src/scenarioCategoryCodeLens.ts:49 — the two spans are one implementation copied and then locally edited — 403 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (67 lines × 2 locations) src/infobaseManager.ts:2145— src/infobaseManager.ts:2145 · src/infobaseManager.ts:2213 — 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 (66 lines × 2 locations) src/phaseSwitcher.ts:6480— src/phaseSwitcher.ts:6480 · src/phaseSwitcher.ts:6716 — 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 (61 lines × 2 locations) src/formExplorerBuilder.ts:186— src/formExplorerBuilder.ts:186 · src/infobaseManager.ts:1710 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (59 lines × 2 locations) media/formExplorer.js:2046— media/formExplorer.js:2046 · src/formExplorerStepSuggestions.ts:396 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) REDACTED:405— REDACTED:405 · src/infobaseManager.ts:1567 — the two spans are one implementation copied and then locally edited — 301 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) src/kotMetadataDescription.ts:9— src/kotMetadataDescription.ts:9 · src/scenarioDiagnostics.ts:256 — the two spans are one implementation copied and then locally edited — 384 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) src/stepCatalogClient.ts:193— src/stepCatalogClient.ts:193 · src/stepCatalogClient.ts:278 — the two spans are one implementation copied and then locally edited — 329 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (48 lines × 4 locations) REDACTED:6156— REDACTED:6156 · REDACTED:6211 · REDACTED:6267 · REDACTED:6320 — 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.
Duplicated block (46 lines × 2 locations) REDACTED:1372— REDACTED:1372 · src/testReviewAiReport.ts:439 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (41 lines × 2 locations) REDACTED:1807— REDACTED:1807 · src/testReviewAiReport.ts:981 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (40 lines × 2 locations) src/scenarioDiagnostics.ts:1832— src/scenarioDiagnostics.ts:1832 · src/scenarioDiagnostics.ts:2011 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) src/scenarioYamlMutations.ts:144— src/scenarioYamlMutations.ts:144 · src/scenarioYamlMutations.ts:215 — the two spans are one implementation copied and then locally edited — 206 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (39 lines × 2 locations) src/testReviewAiReport.ts:763— src/testReviewAiReport.ts:763 · src/testReviewAiReport.ts:858 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) src/exportScenarioCreator.ts:85— src/exportScenarioCreator.ts:85 · src/userStepCreator.ts:179 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (38 lines × 2 locations) REDACTED:1459— REDACTED:1459 · REDACTED:1586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) src/exportScenarioMetadata.ts:16— src/exportScenarioMetadata.ts:16 · src/scenarioCategory.ts:16 — the two spans are one implementation copied and then locally edited — 222 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (35 lines × 2 locations) REDACTED:118— REDACTED:118 · REDACTED:277 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) REDACTED:157— REDACTED:157 · src/testReviewAiReport.ts:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (30 lines × 2 locations) src/infobaseManager.ts:2439— src/infobaseManager.ts:2439 · src/infobaseManager.ts:2595 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (29 lines × 2 locations) REDACTED:326— REDACTED:326 · REDACTED:374 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (29 lines × 3 locations) REDACTED:1370— REDACTED:1370 · REDACTED:1460 · REDACTED:1524 — 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.
Complex function (anonymous) (cyclomatic 148, cognitive 155) src/vanessaControlSession.ts:369— (anonymous) has cyclomatic complexity 148 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateDocument (cyclomatic 111, cognitive 187) src/scenarioDiagnostics.ts:1540— validateDocument has cyclomatic complexity 111 and cognitive complexity 187; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleConvertCallableScenario (cyclomatic 108, cognitive 185) src/scenarioCallableCommands.ts:83— handleConvertCallableScenario has cyclomatic complexity 108 and cognitive complexity 185; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 91, cognitive 109) src/phaseSwitcher.ts:7424— (anonymous) has cyclomatic complexity 91 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 90, cognitive 125) media/phaseSwitcher.js:3201— (anonymous) has cyclomatic complexity 90 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderDetails (cyclomatic 90, cognitive 84) media/infobaseManager.js:597— renderDetails has cyclomatic complexity 90 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function perform (cyclomatic 82, cognitive 141) src/scenarioPropertiesSession.ts:387— perform has cyclomatic complexity 82 and cognitive complexity 141; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildScenarioViewState (cyclomatic 81, cognitive 77) media/phaseSwitcher.js:1056— buildScenarioViewState has cyclomatic complexity 81 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 79, cognitive 105) src/phaseSwitcher.ts:8499— (anonymous) has cyclomatic complexity 79 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 78, cognitive 117) media/stepLibrarySidebar.js:1008— (anonymous) has cyclomatic complexity 78 and cognitive complexity 117; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseVanessaControlReply (cyclomatic 77, cognitive 92) src/vanessaControlProtocol.ts:111— parseVanessaControlReply has cyclomatic complexity 77 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function writeCompilerBuildReport (cyclomatic 67, cognitive 119) src/compilerBuildReport.ts:131— writeCompilerBuildReport has cyclomatic complexity 67 and cognitive complexity 119; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderStaticFrame (cyclomatic 61, cognitive 63) media/formExplorer.js:698— renderStaticFrame has cyclomatic complexity 61 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 59, cognitive 82) REDACTED:1278— (anonymous) has cyclomatic complexity 59 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleScenarioContextMenu (cyclomatic 58, cognitive 55) media/phaseSwitcher.js:2843— handleScenarioContextMenu has cyclomatic complexity 58 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 57, cognitive 81) src/scenarioPropertiesActions.ts:277— (anonymous) has cyclomatic complexity 57 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 56, cognitive 79) media/stepLibrary.js:2136— (anonymous) has cyclomatic complexity 56 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function planFeatureEditorEdit (cyclomatic 56, cognitive 77) src/featureEditorActions.ts:184— planFeatureEditorEdit has cyclomatic complexity 56 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 56, cognitive 54) media/yamlParameters.js:4— (anonymous) has cyclomatic complexity 56 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleMessage (cyclomatic 54, cognitive 40) src/infobaseManagerPanel.ts:418— handleMessage has cyclomatic complexity 54 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function makeRow (cyclomatic 53, cognitive 61) media/stepLibrarySidebar.js:286— makeRow has cyclomatic complexity 53 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyYamlMapField (cyclomatic 52, cognitive 106) src/scenarioPropertiesModel.ts:366— applyYamlMapField has cyclomatic complexity 52 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renameScenario (cyclomatic 51, cognitive 70) src/phaseSwitcher.ts:5936— renameScenario has cyclomatic complexity 51 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function records (cyclomatic 50, cognitive 90) · ×1
Complex function records (cyclomatic 50, cognitive 90) media/scenarioProperties.js:436— records has cyclomatic complexity 50 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectCompilerBuildPreflightIssues (cyclomatic 50, cognitive 82) src/compilerBuildPreflight.ts:107— collectCompilerBuildPreflightIssues has cyclomatic complexity 50 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateScenarioBuildArtifacts (cyclomatic 50, cognitive 73) src/phaseSwitcher.ts:10172— updateScenarioBuildArtifacts has cyclomatic complexity 50 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function changeScenarioIdentityField (cyclomatic 50, cognitive 60) src/phaseSwitcher.ts:5360— changeScenarioIdentityField has cyclomatic complexity 50 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function load (cyclomatic 49, cognitive 73) src/scenarioPropertiesSession.ts:131— load has cyclomatic complexity 49 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 49, cognitive 56) src/vanessaInfobaseClients.ts:289— (anonymous) has cyclomatic complexity 49 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleGenerateFormExplorerExtensionCore (cyclomatic 47, cognitive 53) REDACTED:6621— handleGenerateFormExplorerExtensionCore has cyclomatic complexity 47 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function load (cyclomatic 46, cognitive 81) src/projectLibraryStore.ts:343— load has cyclomatic complexity 46 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function provideInlayHints (cyclomatic 46, cognitive 80) src/scenarioHeaderInlayHintsProvider.ts:36— provideInlayHints has cyclomatic complexity 46 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function performAction (cyclomatic 46, cognitive 58) src/standaloneFeatureController.ts:191— performAction has cyclomatic complexity 46 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function readSchema (cyclomatic 46, cognitive 57) src/vanessaControlFormTools.ts:50— readSchema has cyclomatic complexity 46 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function provideCodeActions (cyclomatic 45, cognitive 81) src/scenarioDiagnostics.ts:855— provideCodeActions has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runScenarioInVanessaBuiltIn (cyclomatic 45, cognitive 52) src/phaseSwitcher.ts:12050— runScenarioInVanessaBuiltIn has cyclomatic complexity 45 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 45, cognitive 49) media/yamlParameters.js:1451— (anonymous) has cyclomatic complexity 45 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildTokens (cyclomatic 44, cognitive 82) src/scenarioSyntaxHighlightProvider.ts:185— buildTokens has cyclomatic complexity 44 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseStandaloneFeatureMessage (cyclomatic 44, cognitive 29) src/standaloneFeatureController.ts:69— parseStandaloneFeatureMessage has cyclomatic complexity 44 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadProjectScenarioMetadata (cyclomatic 43, cognitive 104) src/projectLibraryMetadata.ts:152— loadProjectScenarioMetadata has cyclomatic complexity 43 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
src/phaseSwitcher.ts: 12379 lines of code src/phaseSwitcher.ts:1— src/phaseSwitcher.ts has 12379 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 6136 lines of code REDACTED:1— REDACTED has 6136 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 4094 lines of code REDACTED:1— REDACTED has 4094 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 3665 lines of code REDACTED:1— REDACTED has 3665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
media/phaseSwitcher.js: 3547 lines of code media/phaseSwitcher.js:1— media/phaseSwitcher.js has 3547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/infobaseManager.ts: 3021 lines of code src/infobaseManager.ts:1— src/infobaseManager.ts has 3021 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
media/formExplorer.js: 2667 lines of code media/formExplorer.js:1— media/formExplorer.js has 2667 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/completionProvider.ts: 2626 lines of code src/completionProvider.ts:1— src/completionProvider.ts has 2626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/scenarioCreator.ts: 2385 lines of code src/scenarioCreator.ts:1— src/scenarioCreator.ts has 2385 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
media/stepLibrary.js: 2225 lines of code media/stepLibrary.js:1— media/stepLibrary.js has 2225 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 2026 lines of code REDACTED:1— REDACTED has 2026 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1878 lines of code REDACTED:1— REDACTED has 1878 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/scenarioDiagnostics.ts: 1861 lines of code src/scenarioDiagnostics.ts:1— src/scenarioDiagnostics.ts has 1861 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/formExplorerPanel.ts: 1798 lines of code src/formExplorerPanel.ts:1— src/formExplorerPanel.ts has 1798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1464 lines of code REDACTED:1— REDACTED has 1464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
media/yamlParameters.js: 1460 lines of code media/yamlParameters.js:1— media/yamlParameters.js has 1460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1189 lines of code REDACTED:1— REDACTED has 1189 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· media/stepLibrarySidebar.js · ×1
media/stepLibrarySidebar.js: 1149 lines of code media/stepLibrarySidebar.js:1— media/stepLibrarySidebar.js has 1149 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/testReviewAiReport.ts: 1128 lines of code src/testReviewAiReport.ts:1— src/testReviewAiReport.ts has 1128 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/stepLibraryPanel.ts: 1011 lines of code src/stepLibraryPanel.ts:1— src/stepLibraryPanel.ts has 1011 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/formExplorerStepSuggestions.ts · ×1
src/formExplorerStepSuggestions.ts: 1006 lines of code src/formExplorerStepSuggestions.ts:1— src/formExplorerStepSuggestions.ts has 1006 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/scenarioFilesService.ts · ×1
src/scenarioFilesService.ts: 988 lines of code src/scenarioFilesService.ts:1— src/scenarioFilesService.ts has 988 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/projectDefinitionIndexService.ts · ×1
src/projectDefinitionIndexService.ts: 955 lines of code src/projectDefinitionIndexService.ts:1— src/projectDefinitionIndexService.ts has 955 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/infobaseManagerPanel.ts · ×1
src/infobaseManagerPanel.ts: 953 lines of code src/infobaseManagerPanel.ts:1— src/infobaseManagerPanel.ts has 953 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
media/infobaseManager.js: 951 lines of code media/infobaseManager.js:1— media/infobaseManager.js has 951 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/stepLibrarySidebarProvider.ts · ×1
src/stepLibrarySidebarProvider.ts: 916 lines of code src/stepLibrarySidebarProvider.ts:1— src/stepLibrarySidebarProvider.ts has 916 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/projectLibraryStore.ts: 908 lines of code src/projectLibraryStore.ts:1— src/projectLibraryStore.ts has 908 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/bslStepSourceParser.ts: 894 lines of code src/bslStepSourceParser.ts:1— src/bslStepSourceParser.ts has 894 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/standaloneFeatureService.ts · ×1
src/standaloneFeatureService.ts: 802 lines of code src/standaloneFeatureService.ts:1— src/standaloneFeatureService.ts has 802 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 795 lines of code REDACTED:1— REDACTED has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/scenarioPropertiesPanel.ts · ×1
src/scenarioPropertiesPanel.ts: 768 lines of code src/scenarioPropertiesPanel.ts:1— src/scenarioPropertiesPanel.ts has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· media/scenarioProperties.js · ×1
media/scenarioProperties.js: 745 lines of code media/scenarioProperties.js:1— media/scenarioProperties.js has 745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/vanessaControlSession.ts · ×1
src/vanessaControlSession.ts: 724 lines of code src/vanessaControlSession.ts:1— src/vanessaControlSession.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· media/standaloneFeatures.js · ×1
media/standaloneFeatures.js: 721 lines of code media/standaloneFeatures.js:1— media/standaloneFeatures.js has 721 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/scenarioYamlDocument.ts · ×1
src/scenarioYamlDocument.ts: 693 lines of code src/scenarioYamlDocument.ts:1— src/scenarioYamlDocument.ts has 693 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/phaseSwitcherMetadata.ts · ×1
src/phaseSwitcherMetadata.ts: 606 lines of code src/phaseSwitcherMetadata.ts:1— src/phaseSwitcherMetadata.ts has 606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/oneCPlatform.ts: 578 lines of code src/oneCPlatform.ts:1— src/oneCPlatform.ts has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/stepCatalogService.ts: 564 lines of code src/stepCatalogService.ts:1— src/stepCatalogService.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/vanessaLaunchJson.ts: 561 lines of code src/vanessaLaunchJson.ts:1— src/vanessaLaunchJson.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· media/stepLibraryProtocol.js · ×1
media/stepLibraryProtocol.js: 550 lines of code media/stepLibraryProtocol.js:1— media/stepLibraryProtocol.js has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job REDACTED:3144— The root package declares the lint script `lint` (`eslint src test tools/step-catalog --max-warnings 0`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner).
Dead file (~2983 LoC) media/formExplorer.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1598 LoC) media/yamlParameters.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~750 LoC) media/scenarioProperties.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~200 LoC) media/stepLibraryFeatureProtocol.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~151 LoC) media/featureProperties.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~131 LoC) media/kotWebviewText.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~96 LoC) media/kotWebviewSplit.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~93 LoC) media/infobaseVanessaClients.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~87 LoC) media/yamlBuildParameterState.js— no import path from any entry point (99 application, 4 tooling, 300 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@vscode/codicons' REDACTED:3161— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Weak hash algorithm REDACTED:391— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) src/phaseSwitcher.ts:6326— `spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `killer.stdout`, while `killer.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`killer.stdout.on('data', …)`, or `killer.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot.
Duplicated predicate src/compilerBuildManifest.ts:27— `!!value && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 3 files — src/compilerBuildManifest.ts, src/projectEntityDisplayOrder.ts, src/projectMetadataMerge.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate media/formExplorer.js:2039— `!Array.isArray(columns) || columns.length === 0 || !Array.isArray(rows) || rows.length === 0` appears character-identically in 2 files — media/formExplorer.js, src/formExplorerStepSuggestions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/vanessaControlLaunch.ts:26— `!Number.isInteger(port) || port < 1 || port > 65535` appears character-identically in 2 files — src/vanessaControlLaunch.ts, src/vanessaDebugClientConfiguration.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/processCreator.ts:187— `!await vscode.workspace.applyEdit(edit) || !await document.save()` appears character-identically in 2 files — src/processCreator.ts, src/processEditorCommands.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/scenarioFilesWebviewProtocol.ts:57— `!candidate || typeof candidate !== 'object'` appears character-identically in 2 files — src/scenarioFilesWebviewProtocol.ts, src/stepLibraryFavorites.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:277— `!configurationSourceDirectory || !fs.existsSync(configurationSourceDirectory)` appears character-identically in 2 files — REDACTED, src/testReviewAiReport.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/infobaseManager.ts:3187— `!designerExePath || !fs.existsSync(designerExePath)` appears character-identically in 2 files — src/infobaseManager.ts, src/startupInfobase.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/scenarioCallableCommands.ts:90— `!document.isClosed && document.uri.toString() === uri.toString()` appears character-identically in 2 files — src/scenarioCallableCommands.ts, src/spprScenarioFiles.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:241— `!document.isDirty || document.uri.scheme !== 'file'` appears character-identically in 2 files — REDACTED, src/projectLibraryIntegration.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate media/kotWebviewSplit.js:62— `!drag || event.pointerId !== drag.pointerId` appears character-identically in 2 files — media/kotWebviewSplit.js, media/stepLibrary.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/projectLegacyMetadataCleanup.ts:8— `!field || field.ambiguous || field.valueKind !== 'mapping'` appears character-identically in 2 files — src/projectLegacyMetadataCleanup.ts, src/scenarioPropertiesModel.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/phaseSwitcher.ts:5732— `!isScenarioYamlFile(document) && !isProcessYamlFile(document)` appears character-identically in 2 files — src/phaseSwitcher.ts, src/scenarioPropertiesEditorIntegration.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate media/stepLibrary.js:2265— `!message.succeeded && !message.cancelled` appears character-identically in 2 files — media/stepLibrary.js, media/stepLibrarySidebar.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/projectEntityDisplayOrder.ts:16— `!path.isAbsolute(root) || !['main', 'process', 'standalone'].includes(section)` appears character-identically in 2 files — src/projectEntityDisplayOrder.ts, src/projectGroupDisplayOrder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/userStepLibraryBuilder.ts:65— `!platform || token.isCancellationRequested` appears character-identically in 2 files — src/userStepLibraryBuilder.ts, src/userStepLibraryDump.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/infobaseManager.ts:694— `!raw || typeof raw !== 'object' || Array.isArray(raw)` appears character-identically in 3 files — src/infobaseManager.ts, src/phaseSwitcher.ts, src/vanessaInfobaseClientCommands.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/vanessaControlCommands.ts:137— `!requested || active?.uri !== requested.uri || active.text !== requested.text || active.line !== requested.line` appears character-identically in 2 files — src/vanessaControlCommands.ts, src/vanessaControlYamlTrialCommands.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/infobaseManager.ts:2398— `!selectedFile || selectedFile.length === 0` appears character-identically in 2 files — src/infobaseManager.ts, src/scenarioCreator.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/projectLibraryStore.ts:284— `!stat?.isDirectory() || stat.isSymbolicLink()` appears character-identically in 2 files — src/projectLibraryStore.ts, src/scenarioPropertiesPanel.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/projectLibraryStore.ts:307— `!stat?.isFile() || stat.isSymbolicLink()` appears character-identically in 2 files — src/projectLibraryStore.ts, src/scenarioFilesService.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate media/formExplorer.js:1999— `!tableElement || !Array.isArray(tableElement.children)` appears character-identically in 2 files — media/formExplorer.js, src/formExplorerStepSuggestions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/nativeProjectCatalogSettings.ts:29— `!value || typeof value !== 'object' || Array.isArray(value)` appears character-identically in 8 files — src/nativeProjectCatalogSettings.ts, src/projectLibraryStore.ts, src/scenarioPropertiesSession.ts, src/standaloneFeatureLaunch.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/completionProvider.ts:2038— `!value.includes('\n') && !value.includes('\r')` appears character-identically in 2 files — src/completionProvider.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/featureEditorActions.ts:165— `!value.trim() || /[\r\n\0]/u.test(value)` appears character-identically in 2 files — src/featureEditorActions.ts, src/scenarioPropertiesLibrarySupport.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/kotWorkspaceConfiguration.ts:12— `!vscode.workspace.workspaceFile && vscode.workspace.workspaceFolders?.length === 1` appears character-identically in 2 files — src/kotWorkspaceConfiguration.ts, src/nativeProjectCatalogSettings.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.
Silent fallback default in catch media/phaseSwitcher.js:724— `escapeHtmlAttr` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch media/phaseSwitcher.js:737— `escapeHtmlText` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/projectFormat.ts:10— `readOptional` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/compilerYamlBlocks.ts:57— `buildCompilerYamlBlockActions` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/workspaceScanner.ts:87— `collectFilesFromScanDirectory` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/vanessaControlStepResults.ts:12— `mapVanessaStepResults` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/standaloneFeatureService.ts:607— `orderedPlacementIds` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/compilerBuildReport.ts:127— `errorFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/infobaseManager.ts:355— `getDirectoryEntryCount` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/infobaseManager.ts:1509— `promptNewInfobaseTarget` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/scenarioPropertiesCatalogs.ts:158— `loadScenarioPropertiesCatalogs` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/scenarioPropertiesCatalogs.ts:178— `loadScenarioPropertiesCatalogs.bases` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/phaseSwitcher.ts:1352— `collectScenarioTestYamlFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/phaseSwitcher.ts:4415— `removeFavoriteEntriesUnderDirectory` swallows every exception into `return true` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/phaseSwitcher.ts:11193— `promptNewVanessaInfobasePath` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:510— `countFilesInScenarioFilesFolder` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/vanessaControlConnection.ts:67— `registerVanessaControl.saved` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/projectFeatureTags.ts:22— `getTags` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:714— `collectGitModifiedYamlUris` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Hand-rolled JSON/XML parsing via regex REDACTED:949— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:211— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:459— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:315— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:960— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:964— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:1046— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex REDACTED:1051— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Fat interface: InfobaseSidebarOperations (19 required operations) src/infobaseSidebarProvider.ts:39— `InfobaseSidebarOperations` declares 19 required operations: `createInfobase`, `openEnterprise`, `openDesigner`, `openFormExplorer`, `copy`, `recreate`, `updateConfiguration`, `updateFromSources`, `updateFromTemplate`, `edit`, `addToLauncher`, `removeFromLauncher`, `reveal`, `logs`, `exportDt`, `importDt`, `restoreFromTemplate`, `exportCf`, `importCf`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Outdated (npm): uuid REDACTED:3174— uuid is pinned at 11.1.1; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 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:3155— `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`.
R7 · Dead Code· Unused export 'getFormExplorerResolvedPaths' · ×1
Unused export 'getFormExplorerResolvedPaths' src/formExplorerPaths.ts:52— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'hashFileContents' · ×1
Unused module-local declaration 'hashFileContents' src/formExplorerBuilder.ts:102— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'resolveCandidatePath' · ×1
Unused module-local declaration 'resolveCandidatePath' REDACTED:530— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'getBuilderCacheState' · ×1
Unused module-local declaration 'getBuilderCacheState' REDACTED:1085— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'isSameBuilderCacheState' · ×1
Unused module-local declaration 'isSameBuilderCacheState' REDACTED:1094— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'buildCommandModuleText' · ×1
Unused module-local declaration 'buildCommandModuleText' REDACTED:4968— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'generateManagedFormArtifacts' · ×1
Unused module-local declaration 'generateManagedFormArtifacts' REDACTED:5235— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused private method 'createRussianStepDefinition' · ×1
Unused private method 'createRussianStepDefinition' REDACTED:228— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused private method 'extractStepArgumentLiterals' · ×1
Unused private method 'extractStepArgumentLiterals' REDACTED:312— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused private method 'applyLineLiteralsToTemplate' · ×1
Unused private method 'applyLineLiteralsToTemplate' REDACTED:322— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused private method 'matchLineToPattern' · ×1
Unused private method 'matchLineToPattern' REDACTED:332— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused private method 'provideScenarioCallHover' · ×1
Unused private method 'provideScenarioCallHover' REDACTED:577— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused private method 'isRussianText' · ×1
Unused private method 'isRussianText' REDACTED:1354— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused module-local declaration 'resolveConfiguredOneCClientExePath' · ×1
Unused module-local declaration 'resolveConfiguredOneCClientExePath' src/infobaseManager.ts:1682— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'VanessaInfobaseSource' · ×1
Unused module-local declaration 'VanessaInfobaseSource' src/phaseSwitcher.ts:456— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Write-only private field '_isScanning' · ×1
Write-only private field '_isScanning' src/phaseSwitcher.ts:478— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code· Unused module-local declaration 'collectScenarioSemanticFocusKinds' · ×1
Unused module-local declaration 'collectScenarioSemanticFocusKinds' REDACTED:1715— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'groupScenarioChunkSummariesByStage' · ×1
Unused module-local declaration 'groupScenarioChunkSummariesByStage' REDACTED:1733— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'mergeScenarioFactSnapshots' · ×1
Unused module-local declaration 'mergeScenarioFactSnapshots' REDACTED:3594— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'buildScenarioChunkAnalysisPrompt' · ×1
Unused module-local declaration 'buildScenarioChunkAnalysisPrompt' REDACTED:3842— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'requestScenarioFactSnapshotFromAi' · ×1
Unused module-local declaration 'requestScenarioFactSnapshotFromAi' REDACTED:3895— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'buildScenarioSynthesisPrompt' · ×1
Unused module-local declaration 'buildScenarioSynthesisPrompt' REDACTED:3929— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'buildScenarioValidationPrompt' · ×1
Unused module-local declaration 'buildScenarioValidationPrompt' REDACTED:3984— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'sortedUnique' · ×1
Unused module-local declaration 'sortedUnique' src/stepCatalogTemplateXml.ts:69— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Null assertions (`!`) override strict null checking — ~2.8 `!` null assertions per 1k TypeScript source lines — 288 assertion(s) across the 103692 source line(s) of the 269 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/phaseSwitcher.ts (32), REDACTED (11), src/gherkinAnnotations.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @cucumber/gherkin — @cucumber/gherkin is pinned at 42.0.1; registry.npmjs.org publishes 43.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @cucumber/messages — @cucumber/messages is pinned at 34.0.0; registry.npmjs.org publishes 35.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @modelcontextprotocol/client — @modelcontextprotocol/client is pinned at 2.3.1; registry.npmjs.org publishes 2.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jszip — jszip is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): node-html-parser — node-html-parser is pinned at 7.1.0; registry.npmjs.org publishes 9.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): (unnamed test) test/legacyPanelLayout.test.ts:88— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/legacyPanelLayout.test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): scenario files service rejects missing directories and symbolic-link leaves before confirmation test/scenarioFilesService.test.ts:513— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `src/compilerArtifacts.ts`, `src/compilerYamlBlockEditor.ts`, `REDACTED`, `REDACTED`, `src/phaseSwitcher.ts`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1e7d0-3ce2-741b-9cdb-00057c5d23d5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 14 · Warnings: 1521 · Recommendations: 108 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 04:42 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.