Public report of TouK/nussknacker, published 26 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 15:07 UTC · Survey ID cd_158441217000485980f01bbdd75ac88b

TouK/nussknacker

Measured 26 October 2026, 23:48 UTC, at code version 2e8d326

Regression: 1 dimension fell since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 37out of 100 At risk Down 11 since the last survey

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: 182,261 lines of product code in 79 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Accessibility, 27

Findings by how serious they are

236 critical 1299 serious 619 minor

13 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 23:48 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

92of 92 dimensions measured by tools.
2050of 2154 findings point to an exact file and line, so you can open each one in the code. The other 104 concern the repository as a whole, such as missing documentation.
92dimensions across 7 lenses, read from 182,261 lines of product code in 79 projects.
Chapters

Executive summary

TouK/nussknacker is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has buttons or links with no name. It scores 37 out of 100, which the At risk rating leaves unchanged.

Accessibility, at 27, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 4 points. Structuring the pages would lift Accessibility itself, worth about 5 points. Raising Accessibility to 70 would lift the score to about 45.

104 known security holes in the packages the code depends on can be used by attackers. Sixty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and fifteen secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the three automatic dependency updates that take new releases at once, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command. The 17 loops of files that import each other need breaking.

The product code is 182,261 lines, about €320,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 27 · counts for 46%Production Readiness 37 · counts for 25%Code Health 47 · counts for 14%Maturity 51 · counts for 8%Architecture 57 · counts for 4%Security and Compliance 59 · counts for 2%Performance 72 · counts for 1%

If Accessibility rose from 27 to 70, the lowest score rated Strong, the score would rise from 37 to about 45.

Code composition: what the lines of code are
Product code 58%Tests 42%
New since the last survey: 81 findings

These 81 critical or serious findings weren't in the previous survey, on 12 October 2026.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 1524 findings

These 1524 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.

  • Explicit Debt · TodoComment repeated across 14 files engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinformation/SimpleTypeInformation.scala
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (17 lines × 2 locations) designer/client/src/components/toolbars/activities/helpers/activityItemColors.ts
  • Code Duplication · Duplicated block (17 lines × 3 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) designer/client/src/components/toolbars/view/buttons/ZoomInButton.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx
  • Code Duplication · Duplicated block (16 lines × 4 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) designer/client/src/components/graph/node-modal/SourceSinkCommon.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) designer/submodules/packages/components/src/scenarios/useScenariosQuery.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) designer/client/src/components/common/error-boundary/fallbackComponent/PlaceholderIconFallbackComponent.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilderComponent.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) designer/submodules/packages/components/src/scenarios/filters/processingModeStack.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/ComponentPreview.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) designer/submodules/packages/components/src/components/usages/componentView.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) designer/client/src/containers/settings/SearchField.tsx
  • Code Duplication · Duplicated block (12 lines × 6 locations) designer/client/src/http/HttpService/HttpService.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) designer/submodules/packages/components/src/components/listWithFilters.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/actions/nk/selection.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/conditionBuilder/ConditionBuilderComponent.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/dataMapper/FieldRow.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/DataMapperComponent.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/customNode.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Formatter.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/graph/node-modal/editors/expression/Formatter.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/Assertions.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) designer/submodules/packages/components/src/components/usages/filtersPart.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/modals/AddAttachmentDialog.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/modals/GenericConfirmDialog.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemComment.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/search/utils.ts
Rebuild cost: about €320,000 · Estimate
Cost to rebuild€110,000 to €540,000, for 1,778 to 5,639 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 182,261 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: Watchdog prices 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 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 4 points · Low effort · REDACTED Scanning
2
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 5 points · Medium effort · Page structure
3
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 4 points · Medium effort · Forms & labels

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 €320,000 to build again, about 2.2 person-years of work. Its weakest lens is Accessibility, at 27 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch commonUtils commonUtils componentsApi componentsApi commonUtils->componentsApi componentsTestkit componentsTestkit componentsTestkit->commonUtils componentsTestkit->componentsApi scenarioCompiler scenarioCompiler componentsTestkit->scenarioCompiler componentsUtils componentsUtils componentsUtils->commonUtils componentsUtils->componentsApi deploymentManagerApi deploymentManagerApi extensionsApi extensionsApi deploymentManagerApi->extensionsApi designer designer designer->componentsApi designer->deploymentManagerApi designer->scenarioCompiler extensionsApi->componentsApi flinkComponentsUtils flinkComponentsUtils flinkComponentsUtils->componentsUtils flinkExtensionsApi flinkExtensionsApi flinkComponentsUtils->flinkExtensionsApi flinkDeploymentManager flinkDeploymentManager flinkDeploymentManager->commonUtils flinkDeploymentManager->deploymentManagerApi httpUtils httpUtils flinkDeploymentManager->httpUtils flinkDevModel flinkDevModel flinkDevModel->componentsUtils flinkDevModel->extensionsApi flinkDevModel->flinkComponentsUtils flinkSchemedKafkaComponentsUtils flinkSchemedKafkaComponentsUtils flinkDevModel->flinkSchemedKafkaComponentsUtils liteComponentsApi liteComponentsApi flinkDevModel->liteComponentsApi flinkDevModel->scenarioCompiler flinkExecutor flinkExecutor flinkExecutor->flinkComponentsUtils flinkExecutor->flinkExtensionsApi flinkExecutor->httpUtils flinkExecutor->scenarioCompiler flinkExtensionsApi->extensionsApi flinkKafkaComponentsUtils flinkKafkaComponentsUtils flinkKafkaComponentsUtils->componentsApi flinkKafkaComponentsUtils->componentsUtils flinkKafkaComponentsUtils->flinkComponentsUtils flinkKafkaComponentsUtils->flinkExtensionsApi flinkSchemedKafkaComponentsUtils->componentsUtils flinkSchemedKafkaComponentsUtils->flinkComponentsUtils flinkSchemedKafkaComponentsUtils->flinkExtensionsApi flinkSchemedKafkaComponentsUtils->flinkKafkaComponentsUtils flinkTableApiComponents flinkTableApiComponents flinkTableApiComponents->commonUtils flinkTableApiComponents->componentsApi flinkTableApiComponents->componentsUtils flinkTableApiComponents->extensionsApi flinkTableApiComponents->flinkComponentsUtils httpUtils->componentsApi httpUtils->componentsUtils liteComponentsApi->componentsApi liteComponentsTestkit liteComponentsTestkit liteComponentsTestkit->componentsTestkit requestResponseRuntime requestResponseRuntime liteComponentsTestkit->requestResponseRuntime requestResponseRuntime->httpUtils scenarioCompiler->componentsUtils __more__ +59 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

1410 modules, with 3312 dependencies between them. 11 loops run through 198 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 1370 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 designer.client.src.components.common.error-boundary.DefaultFullScreenMessage2 pl.touk.nussknacker.engine.api.typed.typing3 pl.touk.nussknacker.engine.graph.expression.Expression.Language4 pl.touk.nussknacker.engine.graph.expression.TabularTypedData5 pl.touk.nussknacker.engine.graph.expression6 pl.touk.nussknacker.engine.api.parameter7 pl.touk.nussknacker.engine.graph.node8 pl.touk.nussknacker.engine.graph.node.VariableOperation9 pl.touk.nussknacker.engine.api.process10 pl.touk.nussknacker.engine.api.context.ProcessCompilationError11 pl.touk.nussknacker.engine.api.context12 pl.touk.nussknacker.engine.api.context.transformation13 pl.touk.nussknacker.engine.api.definition14 pl.touk.nussknacker.engine.api.component15 pl.touk.nussknacker.engine.api16 pl.touk.nussknacker.engine.api.graph17 pl.touk.nussknacker.engine.expression.parse18 pl.touk.nussknacker.engine.flink.api.process19 pl.touk.nussknacker.engine.util20 pl.touk.nussknacker.ui.security.api21 pl.touk.nussknacker.engine.canonicalgraph22 pl.touk.nussknacker.engine.deployment23 pl.touk.nussknacker.engine.kafka24 pl.touk.nussknacker.engine.spel25 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos26 pl.touk.nussknacker.engine.compile27 pl.touk.nussknacker.ui.db.entity28 pl.touk.nussknacker.engine.compile.nodecompilation29 pl.touk.nussknacker.ui.process.repository30 pl.touk.nussknacker.engine.definition.component31 pl.touk.nussknacker.ui.process32 pl.touk.nussknacker.ui.process.deployment33 pl.touk.nussknacker.ui.api34 pl.touk.nussknacker.ui.config35 pl.touk.nussknacker.ui.process.processingtype36 pl.touk.nussknacker.engine.api.deployment37 pl.touk.nussknacker.engine38 pl.touk.nussknacker.ui.process.newdeployment39 pl.touk.nussknacker.ui.statistics40 pl.touk.nussknacker.ui.factory
1 designer.client.src.components.common.error-boundary.DefaultFullScreenMessage
2 pl.touk.nussknacker.engine.api.typed.typing
3 pl.touk.nussknacker.engine.graph.expression.Expression.Language
4 pl.touk.nussknacker.engine.graph.expression.TabularTypedData
5 pl.touk.nussknacker.engine.graph.expression21
6 pl.touk.nussknacker.engine.api.parameter11
7 pl.touk.nussknacker.engine.graph.node6137
8 pl.touk.nussknacker.engine.graph.node.VariableOperation2
9 pl.touk.nussknacker.engine.api.process313414102
10 pl.touk.nussknacker.engine.api.context.ProcessCompilationError114026175389
11 pl.touk.nussknacker.engine.api.context1111
12 pl.touk.nussknacker.engine.api.context.transformation81213
13 pl.touk.nussknacker.engine.api.definition4212261213423
14 pl.touk.nussknacker.engine.api.component14731
15 pl.touk.nussknacker.engine.api431165
16 pl.touk.nussknacker.engine.api.graph225
17 pl.touk.nussknacker.engine.expression.parse2121
18 pl.touk.nussknacker.engine.flink.api.process251225
19 pl.touk.nussknacker.engine.util25
20 pl.touk.nussknacker.ui.security.api61
21 pl.touk.nussknacker.engine.canonicalgraph223152
22 pl.touk.nussknacker.engine.deployment1311
23 pl.touk.nussknacker.engine.kafka1221
24 pl.touk.nussknacker.engine.spel10441331
25 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos714373261
26 pl.touk.nussknacker.engine.compile1292411032132669
27 pl.touk.nussknacker.ui.db.entity22213115
28 pl.touk.nussknacker.engine.compile.nodecompilation81721116161173311
29 pl.touk.nussknacker.ui.process.repository5326111463122
30 pl.touk.nussknacker.engine.definition.component3111324511
31 pl.touk.nussknacker.ui.process1213101811
32 pl.touk.nussknacker.ui.process.deployment2152641756310
33 pl.touk.nussknacker.ui.api1201631811811041
34 pl.touk.nussknacker.ui.config3291
35 pl.touk.nussknacker.ui.process.processingtype117241122114
36 pl.touk.nussknacker.engine.api.deployment1410114442
37 pl.touk.nussknacker.engine24117121131
38 pl.touk.nussknacker.ui.process.newdeployment1282361116
39 pl.touk.nussknacker.ui.statistics22122121
40 pl.touk.nussknacker.ui.factory151221211
Uses a module listed above itPart of a loopThe module itself
1 designer.client.src.components.common.error-boundary.DefaultFullScreenMessage2 pl.touk.nussknacker.engine.api.typed.typing3 pl.touk.nussknacker.engine.graph.expression.Expression.Language4 pl.touk.nussknacker.engine.graph.expression.TabularTypedData5 pl.touk.nussknacker.engine.graph.expression6 pl.touk.nussknacker.engine.api.parameter7 pl.touk.nussknacker.engine.graph.node8 pl.touk.nussknacker.engine.graph.node.VariableOperation9 pl.touk.nussknacker.engine.api.process10 pl.touk.nussknacker.engine.api.context.ProcessCompilationError11 pl.touk.nussknacker.engine.api.context12 pl.touk.nussknacker.engine.api.context.transformation13 pl.touk.nussknacker.engine.api.definition14 pl.touk.nussknacker.engine.api.component15 pl.touk.nussknacker.engine.api16 pl.touk.nussknacker.engine.api.graph17 pl.touk.nussknacker.engine.expression.parse18 pl.touk.nussknacker.engine.flink.api.process19 pl.touk.nussknacker.engine.util20 pl.touk.nussknacker.ui.security.api21 pl.touk.nussknacker.engine.canonicalgraph22 pl.touk.nussknacker.engine.deployment23 pl.touk.nussknacker.engine.kafka24 pl.touk.nussknacker.engine.spel25 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos26 pl.touk.nussknacker.engine.compile27 pl.touk.nussknacker.ui.db.entity28 pl.touk.nussknacker.engine.compile.nodecompilation29 pl.touk.nussknacker.ui.process.repository30 pl.touk.nussknacker.engine.definition.component31 pl.touk.nussknacker.ui.process32 pl.touk.nussknacker.ui.process.deployment33 pl.touk.nussknacker.ui.api34 pl.touk.nussknacker.ui.config35 pl.touk.nussknacker.ui.process.processingtype36 pl.touk.nussknacker.engine.api.deployment37 pl.touk.nussknacker.engine38 pl.touk.nussknacker.ui.process.newdeployment39 pl.touk.nussknacker.ui.statistics40 pl.touk.nussknacker.ui.factorydesigner.client.src.components.common.error-boundary.DefaultFullScreenMessage1pl.touk.nussknacker.engine.api.typed.typing2pl.touk.nussknacker.engine.graph.expression.Expression.Language3pl.touk.nussknacker.engine.graph.expression.TabularTypedData4pl.touk.nussknacker.engine.graph.expression5pl.touk.nussknacker.engine.api.parameter6pl.touk.nussknacker.engine.graph.node7pl.touk.nussknacker.engine.graph.node.VariableOperation8pl.touk.nussknacker.engine.api.process9pl.touk.nussknacker.engine.api.context.ProcessCompilationError10pl.touk.nussknacker.engine.api.context11pl.touk.nussknacker.engine.api.context.transformation12pl.touk.nussknacker.engine.api.definition13pl.touk.nussknacker.engine.api.component14pl.touk.nussknacker.engine.api15pl.touk.nussknacker.engine.api.graph16pl.touk.nussknacker.engine.expression.parse17pl.touk.nussknacker.engine.flink.api.process18pl.touk.nussknacker.engine.util19pl.touk.nussknacker.ui.security.api20pl.touk.nussknacker.engine.canonicalgraph21pl.touk.nussknacker.engine.deployment22pl.touk.nussknacker.engine.kafka23pl.touk.nussknacker.engine.spel24pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos25pl.touk.nussknacker.engine.compile26pl.touk.nussknacker.ui.db.entity27pl.touk.nussknacker.engine.compile.nodecompilation28pl.touk.nussknacker.ui.process.repository29pl.touk.nussknacker.engine.definition.component30pl.touk.nussknacker.ui.process31pl.touk.nussknacker.ui.process.deployment32pl.touk.nussknacker.ui.api33pl.touk.nussknacker.ui.config34pl.touk.nussknacker.ui.process.processingtype35pl.touk.nussknacker.engine.api.deployment36pl.touk.nussknacker.engine37pl.touk.nussknacker.ui.process.newdeployment38pl.touk.nussknacker.ui.statistics39pl.touk.nussknacker.ui.factory4021116137231341410211402617538911118121342122612134231473143116522521212512252561223152131112211044133171437326112924110321326692221311581721116161173311532611146312231113245111213101811215264175631012016318118110413291117241122114141011444224117121131128236111622122121151221211+1370 more modules (most-connected shown)

At a glance — Code Health · 47% · Weak · gated by R7, X5 ·

At a glance — Architecture · 57% · Adequate · gated by D26, R9 ·

At a glance — Maturity · 51% · Adequate · gated by M4 ·

At a glance — Readiness · 37% · Weak · gated by R5, R8, P7 ·

At a glance — Security · 59% · Adequate · gated by D29, D30, D36 ·

At a glance — Accessibility · 27% · Weak · gated by AC1, AC2, AC3, AC4 ·

At a glance — Performance · 72% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures158High / Critical
A05:2025 — Injection93High / Critical
A07:2025 — Authentication Failures6High / Critical
A02:2025 — Security Misconfiguration5High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

First, establish a solid page structure by defining the language, title, and main landmark while ensuring proper heading order and disabling meta-refresh. Next, address the extensive form and button labeling gaps to ensure every control is programmatically accessible, and fix keyboard navigation for custom controls by adding proper roles and handlers. Finally, resolve the leaked secret in the configuration file and update all media elements with appropriate text alternatives to complete the accessibility and security remediation.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+3.7 ptsLowREDACTED Scanning
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+5.0 ptsMediumPage structure
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+4.0 ptsMediumForms & labels
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+3.9 ptsMediumKeyboard semantics
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.+2.9 ptsMediumText alternatives
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.9 ptsMediumDependency Hygiene
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.+2.6 ptsMediumA11y enforcement
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.2 ptsLowADR Quality

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: High vulnerability: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala3.1SlopChange Coupling: Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala5.6MixedCyclomatic Complexity: DbScenarioActivityRepository.fromEntity (cyclomatic 43)
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala6.0MixedExplicit Debt: TodoComment
designer/client/src/reducers/graph/reducer.ts6.0MixedExplicit Debt: TodoComment
scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala6.0MixedExplicit Debt: TodoComment
engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala6.0MixedExplicit Debt: TodoComment
designer/client/src/components/graph/SelectionContextProvider.tsx6.0MixedExplicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 236

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

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

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

Could not be resolved — 13

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

Watchdog 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. 92 of 92 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 92 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D16D17D19D20D26D28D29D30D31D32D34D35D36D43D44AC1AC2AC3AC4AC5AC7AX10AX2AX3AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6P7P8PF1PF2PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2050 of 2154 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17a9d-70a9-7b43-9fe1-48a54dd15043.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 41.9% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
  • D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 635 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 725 test source file(s) (.scala, .java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — Watchdog 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 SCORED: this repository's production source includes .scala, and the scala executor ran against the .scala half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in designer/client/ (695 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — Watchdog 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.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx`, `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx`, `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx`, `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+2 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.
  • AC6 Visual & motion safety — not measured this run — Watchdog 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
  • AX1 Captive dependencies — not measured this run — Watchdog 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Spring (Scala), whose lifetimes are not modelled yet, 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.
  • AX2 Stateful singletons — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Those languages run requests on shared-memory threads, so a shared instance mutated without a lock is the same defect this card counts in C#, Java, Kotlin, Python, Go, Swift, Scala, Ruby and F#, but their singleton shapes are not read yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/installation/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — kafka Error Get "https://registry-1.docker.io/v2/": Forbidden grafana Error context canceled telegraf Error context canceled postgres Error context canceled nginx Error context canceled influxdb Error context canceled akhq Error context canceled designer Error context canceled schema-registry Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: grafana Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled kafka Error context canceled akhq Error context canceled schema-registry Error context canceled telegraf Error context canceled influxdb Error context canceled designer Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 85 further occurrence(s) are not listed individually; the score already reflects all 125.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 437 further occurrence(s) are not listed individually; the score already reflects all 477.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 202 further occurrence(s) are not listed individually; the score already reflects all 242.

Repo exclusion declarations: 55 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

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

60 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SpelTyper.typeNode at 143. A further 35 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 PrettyValidationErrors.formatErrorMessage at 69 — they are counted neither in the figure above nor in this dimension's score. 29 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: utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala (ToAvroSchemaBasedEncoder.encode at 48), designer/client/src/containers/event-tracking/helpers.ts (helpers.mapToolbarButtonToStatisticsEvent at 42), components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/encoders/ToJsonEncoderWithFallback.scala (ToJsonEncoderWithFallback.encodeValue at 41), designer/client/src/windowManager/ContentGetter.tsx (ContentGetter.contentGetter at 29), utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/AvroDefaultExpressionDeterminer.scala (AvroDefaultExpressionDeterminer.determine at 25), and 24 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

SpelTyper.typeNode (cyclomatic 143)scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169
CompareVersionsDialog.VersionsForm (cyclomatic 62)designer/client/src/components/modals/CompareVersionsDialog.tsx:159
FromJsonTypingResultBasedDecoder.decodeValue (cyclomatic 55)components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonTypingResultBasedDecoder.scala:51
reducer.graphReducer (cyclomatic 44)designer/client/src/reducers/graph/reducer.ts:170
DbScenarioActivityRepository.fromEntity (cyclomatic 43)designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with SpelTyper.typeNode (cyclomatic 143), CompareVersionsDialog.VersionsForm (cyclomatic 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity5.6 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

91 method(s) exceeded the cognitive complexity threshold of 15; the worst was SpelTyper.typeNode at 146.

SpelTyper.typeNode (cognitive 146)scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169
SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107)scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114
drawText.buildFragmentsForTokens::wrapAndPushWords (cognitive 75)designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
DbScenarioActivityRepository.fromEntity (cognitive 62)designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720
K8sDeploymentManager.runDeployment (cognitive 56)engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/K8sDeploymentManager.scala:157

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with SpelTyper.typeNode (cognitive 146), SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107), drawText.buildFragmentsForTokens::wrapAndPushWords (cognitive 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes8.7 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

54 god class(es) detected.

FunctionTooLong: useDataMapper.useDataMapper · ×35designer/client/src/components/dataMapper/useDataMapper.ts:139
FileTooLong: description/NodesApiEndpoints.scala · ×9designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/NodesApiEndpoints.scala
TooManyMethods: HttpService · ×6designer/client/src/http/HttpService/HttpService.ts:74
MethodTooLong: FlinkProcessRegistrar.createInterpreter · ×2engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:94
ClassTooLong: HttpService · ×2designer/client/src/http/HttpService/HttpService.ts:74

What to do

  1. Resolve the 35 FunctionTooLong finding(s) in God Classes — start with useDataMapper.ts, FieldRow.tsx, DataMapper.tsx. — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 9 FileTooLong finding(s) in God Classes — start with NodesApiEndpoints.scala, HttpService.ts, DbScenarioActivityRepository.scala. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 6 TooManyMethods finding(s) in God Classes — start with HttpService.ts, Graph.tsx, DbScenarioActivityRepository.scala. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.9 / 10Stronggated by 32 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

31 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 1 of the 32 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .tsx (25% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (5 lines × 2) · ×5designer/server/src/main/scala/db/migration/InvalidateComponentsUsagesCache.scala:20
Duplicated block (10 lines × 2) · ×3designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:561
Duplicated block (14 lines × 2) · ×2components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:86
Duplicated block (9 lines × 2) · ×2components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86
Duplicated block (7 lines × 2) · ×2defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/UnionParametersMigration.scala:22

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

What to do

  1. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with InvalidateComponentsUsagesCache.scala, ExpressionsMigration.scala, collection.scala. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with PeriodicProcessService.scala, CaseClassTypeInfo.scala, UniversalKafkaSourceFactory.scala. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with NodeDependency.scala, UnionTransformer.scala. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

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

79 production modules (npm+sbt), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 2 module(s) off the main sequence, with abstractness counted on 19 of the 79 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Unstable project flinkDeploymentManager
Unstable project flinkExecutor
Unstable project flinkKafkaComponentsUtils
Unstable project liteRequestResponseComponents
Off the main sequence: liveDataCollector

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

What to do

  1. Resolve the 1 Unstable project flinkDeploymentManager finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Unstable project flinkExecutor finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project flinkKafkaComponentsUtils finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

8 of 209 classes have LCOM4 above 3.

Low cohesion: CaseClassComparator (LCOM4 7) · ×8engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeComparator.scala:30

What to do

  1. Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with CaseClassTypeComparator.scala, DbScenarioActivityRepository.scala, TableSource.scala. — One of this dimension's main actionable groups (8 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

4257 test methods: 4015 unit, 108 integration, 0 BDD, 134 e2e. The JavaScript/TypeScript suite contributes 635 `it`/`test` case(s) across 94 test file(s) declaring at least one; its tier split is read from package names and paths only. The Scala suite contributes 3622 test case(s) across 519 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.4 / 10Stronggated by 25 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 25 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 635 tests. Measured on the JavaScript/TypeScript suite only — at least 725 test source file(s) (.scala, .java) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: resolves deep values · ×25designer/client/src/components/graph/node-modal/typeHelpers.test.ts:17

What to do

  1. Resolve the 25 No assertions finding(s) in Test Quality — start with autoScreenshotChangeDocs.cy.ts (12), typeHelpers.test.ts (5), processSelection.cy.ts (4). — One of this dimension's main actionable groups (25 warning-level).
  2. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene8.0 7.7 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.7 / 10 · rule-coverage 96% · ceiling Verified

75 outdated direct sbt declarations. 81 of 84 direct declarations were graded against Maven Central (3 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.

Outdated: ch.qos.logback:logback-classic · ×75

What to do

  1. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 81 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 7 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 68 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 3 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: designer/client/src/components/modals/CompareVersionsDialog.tsx (2×62=124)

Hotspot: designer/client/src/components/modals/CompareVersionsDialog.tsxdesigner/client/src/components/modals/CompareVersionsDialog.tsx:159

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with CompareVersionsDialog.tsx. — 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.

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

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

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

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

47 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is designer/client/src/components/conditionBuilder/ConditionBuilder.tsx. Counted over 1017 of the 2649 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

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

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.2 / 10Stronggated by 691 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

705 deducted task-comment markers across 182261 LoC (0.4/KLoC) → score 9.2. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×616utils/test-utils/src/main/scala/pl/touk/nussknacker/test/UniquePortProvider.scala:16
FixmeComment · ×73utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:47
TodoComment repeated across 14 filesutils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/TestResultSinkFactory.scala:56
HackCommentdesigner/server/src/main/scala/pl/touk/nussknacker/ui/server/NussknackerHttpServer.scala:108

What to do

  1. Resolve the 616 TodoComment finding(s) in Explicit Debt — start with node.scala (13), typing.scala (10), SpelTyper.scala (8). — One of this dimension's main actionable groups (616 warning-level).
  2. Resolve the 73 FixmeComment finding(s) in Explicit Debt — start with LiteKafkaUniversalAvroSchemaFunctionalTest.scala (7), RequestResponseTestScenarioRunnerSpec.scala (5), ProcessService.scala (3). — One of this dimension's main actionable groups (73 warning-level).
  3. Resolve the 1 TodoComment repeated across 14 files finding(s) in Explicit Debt — start with TestResultSinkFactory.scala. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 128 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

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

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

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

2 of 4 build units (npm, sbt) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

93 finding(s): 0 critical, 90 high, 3 medium, 0 low. 68 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 10 file(s) — `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx` (lines 3–18), `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx` (line 27), `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx` (line 56, line 58, line 59, …), `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 68 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 (68 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

150 finding(s): 13 critical, 91 high, 36 medium, 10 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 87 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (71), REDACTED (8), REDACTED (8). — One of this dimension's main actionable groups (87 issue-level).
  2. Resolve the 12 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
  3. Resolve the 4 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).

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

D31 · IaC & Container Security9.3 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

5 finding(s): 0 critical, 1 high, 3 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 7 file(s) — `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx`, `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx`, `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx`, `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness5.5 / 10Adequate✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

463 of 1017 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala. Counted over 1017 of the 2649 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledgescenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:1
Orphaned file · ×462designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/ActionService.scala:1
Further orphaned files (smaller)

What to do

  1. Resolve the 462 Orphaned file finding(s) in Knowledge Freshness — start with DeploymentService.scala (2), types.ts (2), MethodDefinition.scala (2). — One of this dimension's main actionable groups (462 recommendation-level).
  2. Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with SpelExpressionSuggester.scala. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: GenericSourceWithCustomTestingSupport.scala↔SampleNodes.scala 100%; nodeDetails.ts↔nodeDetailsState.ts 90%; Interpreter.scala↔LoggingListener.scala 80%

Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala · ×2scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:1
Change coupling: GenericSourceWithCustomTestingSupport.scala ↔ SampleNodes.scala · ×7engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with Interpreter.scala, GenericSourceWithCustomTestingSupport.scala. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 7 Change coupling finding(s) in Change Coupling — start with GenericSourceWithCustomTestingSupport.scala, nodeDetails.ts, TableSource.scala. — One of this dimension's main actionable groups (7 warning-level).

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored 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. SCORED, not informational.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives3.5 / 10Weak✓ Tool-verified

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.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — designer/client/src/components/graph/markups/bounding.html:2

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels2.2 / 10Critical✓ 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 UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×9) — designer/client/src/components/common/DropdownButton.tsx:58, designer/client/src/components/dataMapper/FieldRow.tsx:299, designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:107, …
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — designer/client/src/components/common/DropdownButton.tsx:128, designer/client/src/components/themed/InputWithIcon.tsx:92
  • This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×9) — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:175, designer/client/src/components/conditionBuilder/ConditionRow.tsx:128, designer/client/src/components/dataMapper/DataMapper.tsx:165, …
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:237, designer/client/src/components/conditionBuilder/ConditionRow.tsx:111, designer/client/src/components/dataMapper/FieldRow.tsx:328
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — designer/client/src/components/graph/node-modal/editors/expression/Duration/TimeRangeComponent.tsx:71, designer/client/src/components/sidePanels/SearchLabeledInput.tsx:14

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — designer/client/src/containers/DynamicTab.tsx:82

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.
AC4 · Keyboard semantics2.2 / 10Critical✓ Tool-verified

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 isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — designer/client/src/components/common/DropdownButton.tsx:128, designer/client/src/components/themed/InputWithIcon.tsx:92, designer/client/src/components/toolbars/creator/Tool.tsx:74

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 579 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition8.3 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `ListenerScenarioWithDetails` declares 21 abstract members: `name`, `processId`, `processVersionId`, `isLatestVersion`, `description`, `isArchived`, `isFragment`, `processingType`, `processCategory`, `modificationDate`, `modifiedAt`, `modifiedBy`, `createdAt`, `createdBy`, `scenarioLabels`, `lastDeployedAction`, `lastStateAction`, `lastAction`, `scenarioGraph`, `history`, `modelVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` 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. — designer/listener-api/src/main/scala/pl/touk/nussknacker/ui/listener/ListenerScenarioWithDetails.scala:9
  • `ProcessService` declares 18 abstract members: `getProcessIdUnsafe`, `getProcessId`, `getLatestProcessWithDetails`, `getProcessWithDetails`, `getLatestProcessesWithDetails`, `getLatestVersionForProcesses`, `getLatestRawProcessesWithDetails`, `getScenarioGraphsForVersionIds`, `archiveProcess`, `deleteProcess`, `unArchiveProcess`, `renameProcess`, `createProcess`, `updateProcess`, `updateProcessDBIO`, `migrateProcess`, `importProcess`, `getProcessActions`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` 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. — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/ProcessService.scala:129
  • `PeriodicProcessesRepository` declares 20 abstract members: `run`, `markInactive`, `getSchedulesState`, `create`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `findToBeDeployed`, `findToBeRetried`, `findActiveSchedulesForProcessesHavingDeploymentWithMatchingStatus`, `findProcessData`, `markDeployed`, `markFinished`, `markFailedOnDeployWithStatus`, `markFailed`, `schedule`, `fetchInputConfigDuringExecutionJson`, `fetchCanonicalProcess`, `fetchProcessVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 20 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:82

What to do

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • `setLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
  • `getLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
  • `setLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
  • `getParentLogger` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
  • `getLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
  • `exampleOfType` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
  • `getFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
  • `addFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
  • `zip` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
  • `invoke` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
  • `implementation` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
  • A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:22, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:46, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:62

What to do

  • Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs7.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `AlwaysUsingSameConnectionDataSource` has 5 unfinished members out of 9 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:9
  • `setLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
  • `getLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
  • `setLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
  • `getParentLogger` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
  • `getLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
  • `ExampleFunctions` has 4 unfinished members out of 5 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:25
  • `exampleOfType` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
  • `getFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
  • `addFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
  • `zip` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
  • `invoke` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
  • `implementation` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:261, designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:399, designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:79, …

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.
  • Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)5.8 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • 162 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 1 of 3 project(s) that lack one — worth up to 0.7 pts.
  • Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • README.md links to `./docs/NuHighLevelView.png`, but `docs/NuHighLevelView.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:61
  • CONTRIBUTING/README.md links to `docs/installation_configuration_guide/README.md`, but `CONTRIBUTING/docs/installation_configuration_guide/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING/README.md:58
  • CONTRIBUTING/README.md links to `designer/client/README.md`, but `CONTRIBUTING/designer/client/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING/README.md:205
  • designer/client/README.md links to `../../CONTRIBUTING.md#running`, but `CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — designer/client/README.md:37

What to do

  • Reconcile the README with reality: README.md links to `./docs/NuHighLevelView.png`, but `docs/NuHighLevelView.png` does not exist; CONTRIBUTING/README.md links to `docs/installation_configuration_guide/README.md`, but `CONTRIBUTING/docs/installation_configuration_guide/README.md` does not exist; CONTRIBUTING/README.md links to `designer/client/README.md`, but `CONTRIBUTING/designer/client/README.md` does not exist; designer/client/README.md links to `../../CONTRIBUTING.md#running`, but `CONTRIBUTING.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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

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

  • 55/62 types (89%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

What to do

  • Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability8.0 / 10Strong✓ Tool-verified

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

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

  • Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `designer/client`.
  • `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js:2
  • `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js:2
  • `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js:1

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
  • Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `axios.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — designer/client/src/api.ts:7

What to do

  • Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

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

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

  • A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/test/scala/pl/touk/nussknacker/engine/benchmarks/suggester/ExpressionSuggesterBenchmark.scala

What to do

  • Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene6.3 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 91 use(s) across 134,496 production line(s) (~0.7/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
  • Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene7.0 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language 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.

  • `invoke` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MeetingService.scala:17
  • `waitForSavepoint` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:126

What to do

  • Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
R1 · Type Safety9.9 / 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.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.

  • 19 duplicated blocks under designer/client/src/components/ have copies in at least two of the sibling directories conditionBuilder, dataMapper, graph, modals, spelExpressionBuilder, tips (+1 more sibling(s) not listed) — 16 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 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. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
  • 13 duplicated blocks under designer/client/src/components/toolbars/ have copies in at least two of the sibling directories creator, edit, process, scenarioActions, search, view — 3 of them are reported below, and 10 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — designer/client/src/components/toolbars/process/buttons/SaveButton.tsx:58
  • 10 duplicated blocks under designer/submodules/packages/components/src/ have copies in at least two of the sibling directories common, components, scenarios — 8 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 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. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
  • 7 duplicated blocks under designer/ have copies in at least two of the sibling directories client, submodules — 6 of them are reported below, and 1 is 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — designer/client/configs/simpleScriptPlugin.ts:8
  • 6 duplicated blocks under designer/client/src/components/graph/node-modal/ have copies in at least two of the sibling directories aggregate, editors, fragment-input-definition, node, node-action-buttons — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113 · designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:142 — the two spans are one implementation copied and then locally edited — 543 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. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113
  • designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:81 — 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. — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83
  • designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164 · designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:151 — the two spans are one implementation copied and then locally edited — 632 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. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
  • designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:23 — the two spans are one implementation copied and then locally edited — 555 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. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
  • designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32 · designer/client/src/components/graph/node-modal/editors/expression/Duration/PeriodEditor.tsx:28 — the two spans are one implementation copied and then locally edited — 320 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. — designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32
  • designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/FixedListVariant.tsx:15 — 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. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16
  • designer/client/configs/simpleScriptPlugin.ts:8 · designer/submodules/configs/webpack/simpleScriptPlugin.ts:8 — 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. — designer/client/configs/simpleScriptPlugin.ts:8
  • designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:63 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63
  • designer/client/src/http/HttpService/HttpService.ts:263 · designer/client/src/http/HttpService/HttpService.ts:311 — 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. — designer/client/src/http/HttpService/HttpService.ts:263
  • designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:25 — 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. — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25
  • designer/client/src/components/notifications/copyTooltip.tsx:15 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:31 — 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. — designer/client/src/components/notifications/copyTooltip.tsx:15
  • designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 — the two spans are one implementation copied and then locally edited — 226 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. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14
  • designer/client/src/http/HttpService/HttpService.ts:927 · designer/client/src/http/HttpService/HttpService.ts:1075 — 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. — designer/client/src/http/HttpService/HttpService.ts:927
  • designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:149 — 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. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159
  • designer/client/src/components/graph/node-modal/DescriptionField.tsx:10 · designer/client/src/components/graph/node-modal/DisableField.tsx:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/node-modal/DescriptionField.tsx:10
  • designer/client/src/components/modals/DeployProcessDialog.tsx:46 · designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx:48 — 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. — designer/client/src/components/modals/DeployProcessDialog.tsx:46
  • designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:27 — 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. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35
  • designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16 · designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/TimeEditor.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16
  • designer/client/src/components/modals/AddCommentDialog.tsx:28 · designer/client/src/components/modals/saveScenario/SaveScenarioDialog.tsx:22 — 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. — designer/client/src/components/modals/AddCommentDialog.tsx:28
  • designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:126 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:150 — all 3 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. — designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60
  • designer/client/src/components/conditionBuilder/ConditionRow.tsx:86 · designer/client/src/components/conditionBuilder/ConditionRow.tsx:136 — 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. — designer/client/src/components/conditionBuilder/ConditionRow.tsx:86
  • designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25 · designer/client/src/components/graph/node-modal/MapVariable.tsx:30 — 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. — designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25
  • designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38 · designer/client/src/components/modals/GenerateTestDataDialog.tsx:41 — 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. — designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38
  • designer/client/src/components/dataMapper/dataMapperUtils.ts:339 · designer/client/src/components/graph/node-modal/ParametersUtils.ts:30 — 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. — designer/client/src/components/dataMapper/dataMapperUtils.ts:339
  • designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62 · designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx:107 — 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. — designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
  • designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:123 — the two spans are one implementation copied and then locally edited — 216 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. — designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6
  • designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45 · designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45
  • designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:7 — 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. — designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5
  • designer/client/configs/withModuleFederationPlugins.ts:64 · designer/submodules/configs/webpack/withModuleFederationPlugins.ts:119 — 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. — designer/client/configs/withModuleFederationPlugins.ts:64
  • designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78 · designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:146 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:144 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78
  • designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65 · designer/client/src/components/dataMapper/useDataMapper.ts:292 — 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. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65
  • designer/client/src/components/dataMapper/dataMapperUtils.ts:215 · designer/client/src/components/dataMapper/dataMapperUtils.ts:239 — 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. — designer/client/src/components/dataMapper/dataMapperUtils.ts:215
  • designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:159 — 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. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206
  • designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:99 — 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. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99
  • designer/client/src/components/graph/node-modal/DescriptionField.tsx:23 · designer/client/src/components/graph/node-modal/DisableField.tsx:22 · designer/client/src/components/graph/node-modal/sink.tsx:21 · designer/client/src/components/graph/node-modal/source.tsx:20 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/graph/node-modal/DescriptionField.tsx:23

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.
R11 · Import Boundaries5.9 / 10Adequate✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • designer/client/configs/withModuleFederationPlugins.ts:9 imports webpack/lib/util/extractUrlAndGlobal, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/configs/withModuleFederationPlugins.ts:9
  • designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10
  • designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11 imports designer/client/src/components/toolbars/test/buttons/useProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11
  • designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10 imports designer/client/src/components/graph/node-modal/tests/ExpressionTestResults.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17
  • designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20
  • designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18
  • designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23 imports designer/client/src/components/toolbars/test/buttons/AdhocTestingButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:24 imports designer/client/src/components/toolbars/test/buttons/CountsButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:24
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:25 imports designer/client/src/components/toolbars/test/buttons/FromFileButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:25
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:26 imports designer/client/src/components/toolbars/test/buttons/GenerateAndTestButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:26
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:27 imports designer/client/src/components/toolbars/test/buttons/GenerateButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:27
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:28 imports designer/client/src/components/toolbars/test/buttons/HideButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:28
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:29 imports designer/client/src/components/toolbars/test/buttons/LiveDataButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:29
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:30 imports designer/client/src/components/toolbars/test/buttons/ScenarioTestButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:30
  • designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:31 imports designer/client/src/components/toolbars/test/buttons/SnowSnowButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:31
  • designer/client/src/components/toolbarSettings/getToolbarComponent.ts:35 imports designer/client/src/components/toolbars/testCases/testCasesPanel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/getToolbarComponent.ts:35
  • designer/client/src/reducers/notifications.ts:3 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/notifications.ts:3
  • designer/client/src/reducers/toolbars.ts:3 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/toolbars.ts:3
  • designer/client/src/reducers/userSettings.ts:2 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/userSettings.ts:2
  • designer/submodules/configs/webpack/common.ts:8 reaches into another package with a relative path (../../../client/version) — import the package by name instead. — designer/submodules/configs/webpack/common.ts:8
  • designer/submodules/configs/webpack/withModuleFederationPlugins.ts:7 imports webpack/lib/util/extractUrlAndGlobal, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/submodules/configs/webpack/withModuleFederationPlugins.ts:7
  • designer/submodules/configs/webpack/withModuleFederationPlugins.ts:9 reaches into another package with a relative path (../../../client/version) — import the package by name instead. — designer/submodules/configs/webpack/withModuleFederationPlugins.ts:9

What to do

  • Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (26 rows); move the shared test helper into a source directory production code may depend on (14 rows).
R2 · Cyclomatic Complexity9.3 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • FieldRow has cyclomatic complexity 40 and cognitive complexity 35; 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. — designer/client/src/components/dataMapper/FieldRow.tsx:90
  • ContextTreeNode has cyclomatic complexity 36 and cognitive complexity 35; 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. — designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
  • (anonymous) has cyclomatic complexity 26 and cognitive complexity 75; 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. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/dataMapper/useDataMapper.ts:197
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/common/ProcessUtils.ts:148
  • DataMapper has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — designer/client/src/components/dataMapper/DataMapper.tsx:68
  • ToolbarWrapper has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33
  • buildFragmentsForTokens has cyclomatic complexity 18 and cognitive complexity 43; 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. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
  • parseConditionAst has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/conditionBuilder/spelUtils.ts:64
  • typingResultToSample has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — designer/client/src/components/builderComponents/typeUtils.ts:12
  • VariantWrapper has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12
  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107
  • adjustEdges has cyclomatic complexity 16 and cognitive complexity 25; 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:50
  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:70
  • refClazzToValue has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/graph/node-modal/Variable.tsx:42

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • designer/client/src/http/HttpService/HttpService.ts has 1226 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/http/HttpService/HttpService.ts:1
  • designer/client/src/components/graph/Graph.tsx has 743 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/graph/Graph.tsx:1
  • designer/client/src/components/dataMapper/useDataMapper.ts has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/useDataMapper.ts:1
  • designer/client/src/components/modals/CompareVersionsDialog.tsx has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/modals/CompareVersionsDialog.tsx:1
  • designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx has 530 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:1
  • designer/client/src/reducers/graph/reducer.ts has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/reducers/graph/reducer.ts:1
  • designer/client/src/components/dataMapper/FieldRow.tsx has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/FieldRow.tsx:1
  • designer/client/src/components/dataMapper/dataMapperUtils.ts has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/dataMapperUtils.ts:1
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
  • designer/client/src/components/dataMapper/DataMapper.tsx has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/DataMapper.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage5.2 / 10Adequate✓ 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. (×40) — designer/client/src/components/graph/Graph.tsx:1, designer/client/src/reducers/graph/reducer.ts:1, designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:1, …

What to do

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

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

  • 158 outdated package(s); JS/npm CVEs scored in D30

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
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.

R7 · Dead Code3.2 / 10Weak✓ 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 40 application, 10 tooling and 126 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/scenarioDetails/ScenarioDetails.tsx, designer/client/src/components/toolbars/scenarioDetails/ScenarioStatusContent.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchResults.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/utils.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/Visualization.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/Toolbars.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbarSettings/getToolbarComponent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/creator/CreatorPanel.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/WindowManager.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/windowManager/ContentGetter.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CountsStyled.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/common/DropdownButton.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — designer/client/src/components/AddProcessDialog.tsx, designer/client/src/components/graph/node-modal/node/DescriptionDialog.tsx, designer/client/src/components/modals/MoreScenarioDetailsDialog.tsx, …
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/MenuBar/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/MenuBar/menu.tsx, designer/client/src/components/MenuBar/breadcrumbs.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — designer/client/src/containers/liveData/LiveDataThroughputs.tsx, designer/client/src/containers/ScenarioDescription.tsx, designer/client/src/components/aiAssistant/tools/ScenarioDataAIToolkit.tsx, …
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/search/SearchPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/aiAssistant/ModelAdapter.ts, designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/aiAssistant/InitializeChatStream.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Auth/strategies/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/Auth/strategies/OAuth2Strategy.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/components/AiAssistantModal.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/aiAssistant/components/Composer.tsx, designer/client/src/components/aiAssistant/components/AssistantMessage.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/CalculateCounts/RefreshSelectButton.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/DeployWithParameters/AdvancedParameters.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (designer/client/src/components/SidePanelToggleButton.tsx, designer/client/src/components/sidePanels/SidePanel.tsx, designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/sidePanels/SidePanelsContext.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/creator/CreatorPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/NodeCreationHandler.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/AiAssistantProvider.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/aiAssistant/ModelAdapter.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/liveData/LiveDataThroughputs.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/liveData/animationHelpers.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchPanel.tsx, designer/client/src/components/toolbars/search/utils.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/SearchResults.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/NussknackerApp.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/versionInfo.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/CommandBar/settings/useRegisterSettingsCommands.tsx, designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/settings/SettingsView.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx, designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/CalculateCounts/CalculateCountsDialog.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 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 — designer/client/configs/withModuleFederationPlugins.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/InitializeChatStream.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/aiAssistant/messageHelpers.ts, designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/sidePanels/CollapsibleScrollPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/sidePanels/CollapsiblePanel.tsx
  • no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/tips/Tips.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/tips/Warnings.tsx

What to do

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

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×4) — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:1, designer/client/src/components/graph/node-modal/io/PanelButton.tsx:2, designer/client/src/components/aiAssistant/useCheckPermission.tsx:1, …
  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×7) — designer/client/jest-setup.js:2, designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/useMockEnabled.ts:1, designer/client/src/components/graph/PanZoomPlugin.ts:2, …
  • Declared in 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. (×3)
  • Every import is type-only — move it to devDependencies. — designer/client/src/actions/notificationActions.tsx:5

What to do

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

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • designer/client/src/actions/nk/editNode.ts → designer/client/src/components/graph/node-modal/node/useNodeState.tsx → designer/client/src/actions/nk/editNode.ts — designer/client/src/actions/nk/editNode.ts:4
  • designer/client/src/actions/nk/liveData.ts → designer/client/src/actions/nk/process.ts → designer/client/src/actions/nk/liveData.ts — designer/client/src/actions/nk/liveData.ts:10
  • designer/client/src/actions/nk/nodeDetails.ts → designer/client/src/actions/nk/validationsActions.ts → designer/client/src/actions/nk/nodeDetails.ts — designer/client/src/actions/nk/nodeDetails.ts:12
  • designer/client/src/actions/nk/testCasesActions.ts → designer/client/src/actions/nk/testingActions.ts → designer/client/src/reducers/selectors/testCases.ts → designer/client/src/components/graph/node-modal/editors/expression/MockExpressionField.tsx → designer/client/src/actions/nk/testCasesActions.ts — designer/client/src/actions/nk/testCasesActions.ts:14
  • designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ButtonMenu.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx (one verified cycle inside a mutually-dependent group of 53 files) — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:7
  • designer/client/src/common/CodeBlock.tsx → designer/client/src/common/copyToClipboard/CopyIconButton.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/InfoTooltip.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/StyledInfoMarkdown.tsx → designer/client/src/components/graph/node-modal/MarkdownStyled.tsx → designer/client/src/components/graph/node-modal/MarkdownWithPlugins.tsx → designer/client/src/common/CodeBlock.tsx (one verified cycle inside a mutually-dependent group of 8 files) — designer/client/src/common/CodeBlock.tsx:7
  • designer/client/src/components/ValueDragPreview.tsx → designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx → designer/client/src/components/ValueDragPreview.tsx — designer/client/src/components/ValueDragPreview.tsx:11
  • designer/client/src/components/graph/EspNode/element.ts → designer/client/src/components/graph/EspNode/esp.ts → designer/client/src/components/graph/EspNode/element.ts (one verified cycle inside a mutually-dependent group of 11 files) — designer/client/src/components/graph/EspNode/element.ts:15
  • designer/client/src/components/graph/Graph.tsx → designer/client/src/components/graph/utils/dragHelpers.ts → designer/client/src/components/graph/Graph.tsx — designer/client/src/components/graph/Graph.tsx:49
  • designer/client/src/components/graph/NodeUtils.ts → designer/client/src/reducers/graph/utils.ts → designer/client/src/components/graph/NodeUtils.ts (one verified cycle inside a mutually-dependent group of 3 files) — designer/client/src/components/graph/NodeUtils.ts:7
  • designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx → designer/client/src/components/graph/node-modal/tests/TestErrors.tsx → designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx (one verified cycle inside a mutually-dependent group of 3 files) — designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx:12
  • designer/client/src/components/graph/node-modal/editors/expression/Editor.ts → designer/client/src/components/graph/node-modal/editors/expression/BoolEditor.tsx → designer/client/src/components/graph/node-modal/editors/expression/Editor.ts (one verified cycle inside a mutually-dependent group of 26 files) — designer/client/src/components/graph/node-modal/editors/expression/Editor.ts:6
  • designer/client/src/components/graph/node-modal/editors/map/Map.tsx → designer/client/src/components/graph/node-modal/editors/map/MapRow.tsx → designer/client/src/components/graph/node-modal/editors/map/Map.tsx — designer/client/src/components/graph/node-modal/editors/map/Map.tsx:11
  • designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/buttons/AddButton.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx — designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx:4
  • designer/client/src/components/toolbars/creator/ToolBox.tsx → designer/client/src/components/toolbars/creator/ToolboxCommands.tsx → designer/client/src/reducers/selectors/getFilteredComponentGroups.ts → designer/client/src/components/toolbars/creator/ToolBox.tsx — designer/client/src/components/toolbars/creator/ToolBox.tsx:16
  • designer/client/src/reducers/graph/historySquash.ts → designer/client/src/reducers/graph/reducer.ts → designer/client/src/reducers/graph/historySquash.ts — designer/client/src/reducers/graph/historySquash.ts:6
  • designer/submodules/packages/components/src/components/usages/nodesCell.tsx → designer/submodules/packages/components/src/components/usages/usagesTable.tsx → designer/submodules/packages/components/src/components/usages/nodesCell.tsx — designer/submodules/packages/components/src/components/usages/nodesCell.tsx:14

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's Scala source and the Java beside it: 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. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. This repository serves HTTP itself (engine/lite/embeddedDeploymentManager/src/main/scala/pl/touk/nussknacker/engine/embedded/requestresponse/RequestResponseDeploymentStrategy.scala:90 — `newServerAt`), so its Scala source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Scala spelling appears in production source, not proven on every route. A Play application is credited the security headers Play's default `SecurityHeadersFilter` sends unless its build or configuration switches that filter off, and its cookies the HttpOnly flag Play sets by default.

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+ (`MessageDigest.getInstance("SHA-256")`) 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. (×3) — engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40
  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — examples/installation/nginx/nginx.conf:2

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. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169` (MessageDigest.getInstance("SHA-1")), `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214` (MessageDigest.getInstance("SHA-1")), `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40` (MessageDigest.getInstance("SHA-1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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

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

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

  • `JsonSchemaUtils.circeToJson` is public and takes `value: Json` from its caller, and it calls itself at line 19 with a piece of `value` (and at line 20), not as a tail call the compiler turns into a loop — and nowhere in `JsonSchemaUtils.circeToJson` 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. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonSchemaUtils.circeToJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/util/json/JsonSchemaUtils.scala:19
  • `jsonToSpelString` is exported and takes `value: any` from its caller, and it calls itself at line 22 (`jsonToSpelString`) with a piece of `value` (and at line 26) — and nowhere in `jsonToSpelString` 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 `jsonToSpelString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx:22
  • `fieldsFromSample` is exported and takes `obj: unknown` from its caller, and it calls itself at line 331 (`fieldsFromSample`) with a piece of `obj` — and nowhere in `fieldsFromSample` 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 `fieldsFromSample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/dataMapper/dataMapperUtils.ts:331
  • `inferDisplayType` is exported and takes `val: unknown` from its caller, and it calls itself at line 6 (`inferDisplayType`) with a piece of `val` — and nowhere in `inferDisplayType` 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 `inferDisplayType` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:6
  • `typingResultToSample` is exported and takes `t: any` from its caller, and it calls itself at line 16 (`typingResultToSample`) with a piece of `t` (and at line 21) — and nowhere in `typingResultToSample` 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 `typingResultToSample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:16
  • `treeNodeMatchesFilter` is exported and takes `value: unknown` from its caller, and it calls itself at line 40 (`treeNodeMatchesFilter`) with a piece of `value` — and nowhere in `treeNodeMatchesFilter` 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 `treeNodeMatchesFilter` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:40
  • `FromJsonSimpleDecoder.jsonToAny` is public and takes `json: Json` from its caller, and it calls itself at line 15 with a piece of `json` (and at line 19), not as a tail call the compiler turns into a loop — and nowhere in `FromJsonSimpleDecoder.jsonToAny` 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. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `FromJsonSimpleDecoder.jsonToAny` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonSimpleDecoder.scala:15

What to do

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

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

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.

  • Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `read` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — designer/submodules/packages/components/src/settings/i18n.ts:16

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

X24 · Document value interpolated into markup unescaped4.6 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `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. — REDACTED:53
  • `` * { cursor: ${cursor} !important; } html, body, * { …` 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. — designer/client/src/components/graph/GlobalCursor.ts:10
  • `truncatedElement.innerHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — designer/client/src/components/graph/node-modal/editors/expression/LineClamp.tsx:106
  • `svgString` is text this program did not author, and it is written into the text of an element through `document.write` 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. — designer/client/src/components/graph/svg-export/prepareSvg.ts:17

What to do

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `case t: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassSerializer.scala:69
  • 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) — designer/client/src/windowManager/LoadingButton.tsx:19, designer/client/src/store/draftListener.ts:179, REDACTED:38, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×3) — designer/client/src/store/draftListener.ts:101, designer/client/src/store/draftListener.ts:129, designer/client/src/components/graph/SelectionContextProvider.tsx:96
  • `.catch((e) => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:340
  • `.catch(() => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:454
  • `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — designer/client/src/components/modals/saveScenario/useSaveScenario.ts:79

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging6.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `error` at line 46 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — live-data-collector/src/main/scala/pl/touk/nussknacker/engine/livedata/LiveDataUploader.scala:46

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

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

  • No build over this repository's 1575 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

What to do

  • On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health47%Weak — gated by R7, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture57%Adequate — gated by D26, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity51%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness37%Weak — gated by R5, R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security59%Adequate — gated by D29, D30, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility27%Weak — gated by AC1, AC2, AC3, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance72%StrongStrongest area.
Unscored — 2 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 — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 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.

  • AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • AX1 Captive dependencies — 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
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — kafka Error Get "https://registry-1.docker.io/v2/": Forbidden grafana Error context canceled telegraf Error context canceled postgres Error context canceled nginx Error context canceled influxdb Error context canceled akhq Error context canceled designer Error context canceled schema-registry Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: grafana Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled kafka Error context canceled akhq Error context canceled schema-registry Error context canceled telegraf Error context canceled influxdb Error context canceled designer Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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 Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • 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 Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Scala, TypeScript, html not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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"]`.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .scala, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Domain Modelling — applicable but not scored (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 7 strongly-typed id(s); 328 value object(s); 31 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
  • ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows 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'.
  • P9 Domain vs controller coverage — coverage data present for 344 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 236 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×87
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 62 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 43 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×14
  • Import cycle (2 files) designer/client/src/actions/nk/editNode.ts:4 — designer/client/src/actions/nk/editNode.ts → designer/client/src/components/graph/node-modal/node/useNodeState.tsx → designer/client/src/actions/nk/editNode.ts
  • Import cycle (2 files) designer/client/src/actions/nk/liveData.ts:10 — designer/client/src/actions/nk/liveData.ts → designer/client/src/actions/nk/process.ts → designer/client/src/actions/nk/liveData.ts
  • Import cycle (2 files) designer/client/src/actions/nk/nodeDetails.ts:12 — designer/client/src/actions/nk/nodeDetails.ts → designer/client/src/actions/nk/validationsActions.ts → designer/client/src/actions/nk/nodeDetails.ts
  • Import cycle (2 files) designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:7 — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ButtonMenu.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx (one verified cycle inside a mutually-dependent group of 53 files)
  • Import cycle (2 files) designer/client/src/components/ValueDragPreview.tsx:11 — designer/client/src/components/ValueDragPreview.tsx → designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx → designer/client/src/components/ValueDragPreview.tsx
  • Import cycle (2 files) designer/client/src/components/graph/EspNode/element.ts:15 — designer/client/src/components/graph/EspNode/element.ts → designer/client/src/components/graph/EspNode/esp.ts → designer/client/src/components/graph/EspNode/element.ts (one verified cycle inside a mutually-dependent group of 11 files)
  • Import cycle (2 files) designer/client/src/components/graph/Graph.tsx:49 — designer/client/src/components/graph/Graph.tsx → designer/client/src/components/graph/utils/dragHelpers.ts → designer/client/src/components/graph/Graph.tsx
  • Import cycle (2 files) designer/client/src/components/graph/NodeUtils.ts:7 — designer/client/src/components/graph/NodeUtils.ts → designer/client/src/reducers/graph/utils.ts → designer/client/src/components/graph/NodeUtils.ts (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx:12 — designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx → designer/client/src/components/graph/node-modal/tests/TestErrors.tsx → designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) designer/client/src/components/graph/node-modal/editors/expression/Editor.ts:6 — designer/client/src/components/graph/node-modal/editors/expression/Editor.ts → designer/client/src/components/graph/node-modal/editors/expression/BoolEditor.tsx → designer/client/src/components/graph/node-modal/editors/expression/Editor.ts (one verified cycle inside a mutually-dependent group of 26 files)
  • Import cycle (2 files) designer/client/src/components/graph/node-modal/editors/map/Map.tsx:11 — designer/client/src/components/graph/node-modal/editors/map/Map.tsx → designer/client/src/components/graph/node-modal/editors/map/MapRow.tsx → designer/client/src/components/graph/node-modal/editors/map/Map.tsx
  • Import cycle (2 files) designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx:4 — designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/buttons/AddButton.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx
  • Import cycle (2 files) designer/client/src/reducers/graph/historySquash.ts:6 — designer/client/src/reducers/graph/historySquash.ts → designer/client/src/reducers/graph/reducer.ts → designer/client/src/reducers/graph/historySquash.ts
  • Import cycle (2 files) designer/submodules/packages/components/src/components/usages/nodesCell.tsx:14 — designer/submodules/packages/components/src/components/usages/nodesCell.tsx → designer/submodules/packages/components/src/components/usages/usagesTable.tsx → designer/submodules/packages/components/src/components/usages/nodesCell.tsx
D30 · Dependency Vulnerabilities · Critical CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×3
  • Click handler on a non-interactive <div> designer/client/src/components/common/DropdownButton.tsx:128 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> designer/client/src/components/themed/InputWithIcon.tsx:92 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> designer/client/src/components/toolbars/creator/Tool.tsx:74 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D28 · Secrets (history) · High secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×2
  • Custom control with no accessible name on <div> designer/client/src/components/common/DropdownButton.tsx:128 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> designer/client/src/components/themed/InputWithIcon.tsx:92 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · <input> without a programmatic label · ×2
  • <input> without a programmatic label designer/client/src/components/graph/node-modal/editors/expression/Duration/TimeRangeComponent.tsx:71 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label designer/client/src/components/sidePanels/SearchLabeledInput.tsx:14 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:1 — `scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala` (context scenario-compiler) and `utils/utils-internal/src/main/scala/pl/touk/nussknacker/engine/util/LoggingListener.scala` (context utils) sit in DIFFERENT parts of the tree yet change together 80% of the time (12 of the 15 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e1802a98` Fix live data counts in node directly after fragment (#8782); `0cd2a509` Cleanup: remove deprecations (#3610) (at that commit the file was still `interpreter/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala`); `41ed5f89` Fix missing metrics for end nodes (#3040) (at that commit the file was still `interpreter/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala`) — run `git show` on any of them.
  • Boundary-crossing change coupling: GenericSourceWithCustomTestingSupport.scala ↔ KafkaContextInitializer.scala engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala:1 — `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala` (context engine) and `utils/kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/source/KafkaContextInitializer.scala` (context utils) sit in DIFFERENT parts of the tree yet change together 71% of the time (10 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `180c9334` method instead of function (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `05c70618` removed ContextIdGenerator passing (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `643b57f5` [NU-2189] Make ContextInitializer be responsible only for variables f… (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`) — run `git show` on any of them.
AC1 · Text alternatives · <img> without a text alternative · ×1
  • <img> without a text alternative designer/client/src/components/graph/markups/bounding.html:2 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title designer/client/src/containers/DynamicTab.tsx:82 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
D13 · REDACTED Scanning · Leaked secret · ×1
  • REDACTED
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×1
  • Orphaned knowledge scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
R8 · Dependency Hygiene · Unlisted import '@jest/globals' · ×1
  • Unlisted import '@jest/globals' designer/client/jest-setup.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@mui/utils' · ×1
  • Unlisted import '@mui/utils' designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/useMockEnabled.ts:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'd3-selection' · ×1
  • Unlisted import 'd3-selection' designer/client/src/components/graph/PanZoomPlugin.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'use-memo-one' · ×1
  • Unlisted import 'use-memo-one' designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:20 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@emotion/cache' · ×1
  • Unlisted import '@emotion/cache' designer/submodules/packages/components/src/settings/rootProviders.tsx:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@mui/system' · ×1
  • Unlisted import '@mui/system' designer/submodules/packages/components/src/common/PlaceholderIconFallbackComponent.tsx:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'stylis' · ×1
  • Unlisted import 'stylis' designer/submodules/packages/components/src/settings/rootProviders.tsx:7 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (4 files) · ×1
  • Import cycle (4 files) designer/client/src/actions/nk/testCasesActions.ts:14 — designer/client/src/actions/nk/testCasesActions.ts → designer/client/src/actions/nk/testingActions.ts → designer/client/src/reducers/selectors/testCases.ts → designer/client/src/components/graph/node-modal/editors/expression/MockExpressionField.tsx → designer/client/src/actions/nk/testCasesActions.ts
R9 · Circular Imports · Import cycle (6 files) · ×1
  • Import cycle (6 files) designer/client/src/common/CodeBlock.tsx:7 — designer/client/src/common/CodeBlock.tsx → designer/client/src/common/copyToClipboard/CopyIconButton.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/InfoTooltip.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/StyledInfoMarkdown.tsx → designer/client/src/components/graph/node-modal/MarkdownStyled.tsx → designer/client/src/components/graph/node-modal/MarkdownWithPlugins.tsx → designer/client/src/common/CodeBlock.tsx (one verified cycle inside a mutually-dependent group of 8 files)
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) designer/client/src/components/toolbars/creator/ToolBox.tsx:16 — designer/client/src/components/toolbars/creator/ToolBox.tsx → designer/client/src/components/toolbars/creator/ToolboxCommands.tsx → designer/client/src/reducers/selectors/getFilteredComponentGroups.ts → designer/client/src/components/toolbars/creator/ToolBox.tsx
Serious — 1299 finding(s)
D17 · Explicit Debt · TodoComment · ×616
  • TodoComment utils/test-utils/src/main/scala/pl/touk/nussknacker/test/UniquePortProvider.scala:16 — // TODO: reuse AvailablePortFinder — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/test/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/azure/AzureSchemaBasedSerdeProviderIntegrationTest.scala:58 — // TODO: we should check if schema name matches our topic-schema name matching convention in the serializer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/KafkaUniversalComponentTransformer.scala:102 — // TODO: add addNullOption feature flag to FixedValuesParameterEditor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/typed/AvroSchemaTypeDefinitionExtractor.scala:49 — // TODO: Is it ok? Or we should skip this element? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:459 — // TODO: ADT allowing to pass either information about schema or about ContentType — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/universal/RecordFormatterSupport.scala:45 — // Here should probably be default encoder and the loose one is for historical reasons TODO: verify and switch to default= — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/universal/UniversalKafkaDeserializer.scala:63 — // TODO: test this case when supporting json schema — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/confluent/serialization/jsonpayload/ConfluentJsonPayloadKafkaSerializer.scala:15 — //TODO: handle situation, where we have both json and avro payloads for one schema registry — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/azure/SchemaNameTopicMatchStrategy.scala:9 — // TODO: It probable should be configurable: e.g would be nice to have possibility to define static topic -> schemaName map in config — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schema/AvroSchemaBasedParameter.scala:144 — // TODO: for now, we don't use SchemaOutputValidator for Avro in editor mode, but we can add it in the future — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala:206 — // TODO: Check optional? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/LiteNodeCompiler.scala:27 — // TODO: configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/FlinkNodeCompiler.scala:30 — // TODO: configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/LiteTestScenarioRunner.scala:69 — // TODO: expose like kafkaLite and flink version + add docs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/SynchronousLiteInterpreter.scala:43 — // TODO: add generate test data support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/components-testkit/src/main/scala/pl/touk/nussknacker/engine/util/test/TestScenarioRunner.scala:93 — // TODO: add generate test data support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/KafkaComponentsConfig.scala:20 — // TODO: Replace this map with normal fields — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/KafkaComponentsConfig.scala:71 — // TODO: Rename to processName and processName-nodeName — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/exception/KafkaJsonExceptionSerializationSchema.scala:180 — // TODO: better hostname (e.g. from some Flink config) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/source/InputMeta.scala:59 — // TODO: exclude non-key parameters to trait BaseKafkaInputMetaVariables and use it in TypesInformationExtractor.mandatoryClasses — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/source/InputMeta.scala:60 — // TODO: add displayStrategy similar to this in Unknown type instead of extending case class — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/json-utils/src/test/scala/pl/touk/nussknacker/engine/json/SwaggerBasedJsonSchemaTypeDefinitionExtractorTest.scala:393 — // TODO: handle case when we have fields common for both versions on "main" level — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonDefaultExpressionDeterminer.scala:50 — // TODO: Add support for others type: enum, const, combined, etc.. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonSchemaBuilder.scala:13 — // TODO: parsing schema should be consistent with [io.confluent.kafka.schemaregistry.json.JsonSchema.rawSchema] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonSchemaBuilder.scala:14 — // TODO: Remove strict setting DRAFT7 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 591 more in this group — see findings.md.
D17 · Explicit Debt · FixmeComment · ×73
  • FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:47 — // FIXME: verify false positives — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:71 — // FIXME: verify false positives — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:96 — // FIXME: verify false positives — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:122 — // FIXME: verify false positives — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:148 — // FIXME: verify false positives — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment utils/http-utils/src/main/scala/pl/touk/nussknacker/http/backend/HttpClientConfig.scala:57 — // FIXME: does not work by default? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment scenario-compiler/src/test/scala/pl/touk/nussknacker/engine/compile/FragmentResolverSpec.scala:562 — // FIXME: not sure if it's good way. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:501 — // FIXME: what if more results are present? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment scenario-api/src/main/scala/pl/touk/nussknacker/engine/graph/evaluatedparam.scala:12 — // FIXME: after adding @JsonCodec — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/ScenarioInterpreterFactory.scala:382 — // FIXME: do we need it at all — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/TestRunner.scala:59 — // FIXME: validation?? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/TestRunner.scala:151 — // FIXME: it doesn't work properly with KafkaLite Engine, we should add proper converting method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/kafka/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/kafka/KafkaProducerRecordsHandler.scala:125 — // FIXME generate correct id - how to connect to topic/partition?? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components-api/src/main/scala/pl/touk/nussknacker/engine/lite/api/utils/sinks.scala:54 — // FIXME: figure out how to pass componentName here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/request-response/src/main/scala/pl/touk/nussknacker/engine/lite/components/requestresponse/CollectTransformer.scala:55 — // FIXME: This is an ugly workaround for the fact that we can't pass traceId from org Context to collect. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:85 — // FIXME: java.nio.ByteBuffer is not available from SpEL (sConfig(sampleString, stringSchema, bytesSchema, """T(java.nio.ByteBuffer).wrap(#input.getBytes("UTF-8"))"""), valid(ByteBuffer.wrap(sampleBytes))),
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:461 — // FIXME: List[Unknown] (rConfig(sampleInteger, recordIntegerSchema, recordWithArrayOfNumbers, s"""{$sampleBoolean, "$sampleString"}"""), invalidTypes(s"path 'field[]' actual: '${typeBool.display} | ${typeStr.display}' expected: 'Integer | Double'")), — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:482 — // FIXME: List[Unknown] (rConfig(sampleInteger, recordIntegerSchema, recordWithMaybeArrayOfNumbers, s"""{$sampleBoolean, "$sampleString"}"""), invalidTypes("path 'field[]' actual: '${typeBool.display} | ${typeStr.display}' expected: 'Integer | Double'")), — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:499 — // FIXME: List[Unknown] (rConfig(sampleInteger, recordIntegerSchema, recordWithMaybeArrayOfNumbers, s"""{$sampleBoolean, "$sampleString"}"""), invalidTypes("path 'field[]' actual: '${typeBool.display} | ${typeStr.display}' expected: 'Integer | Double'")), — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:533 — // FIXME: List[Unknown] (rConfig(sampleInteger, recordIntegerSchema, recordOptionalArrayOfArraysNumbers, s"""{{$sampleBoolean, "$sampleString"}}"""), invalidTypes("path 'field[][]' actual: 'Boolean | String' expected: 'Integer | Double'")), — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:1112 — // FIXME: Comparing EnumV2 -> Enum returns true, but in runner ToAvroSchemaBasedEncoder tries to encode String (that doesn't meet the requirements) to Enum — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:1118 — // FIXME: Comparing FixedV2 -> Fixed returns true, but in runner ToAvroSchemaBasedEncoder tries to encode value FixedV2 to Fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/lite/components/kafka/src/main/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalSinkImplFactory.scala:36 — // FIXME: we have to make sure ContextClassLoader is set to model classloader in lite — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:125 — // FIXME: get rid of sleep, refactor? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/ConstantStateTransformer.scala:11 — //FIXME: remove? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 48 more in this group — see findings.md.
R11 · Import Boundaries · Boundary violation [package · ×40
  • Boundary violation [package:third-party-deep-import] designer/client/configs/withModuleFederationPlugins.ts:9 — designer/client/configs/withModuleFederationPlugins.ts:9 imports webpack/lib/util/extractUrlAndGlobal, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:test-suite-dependency] designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10 — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11 — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11 imports designer/client/src/components/toolbars/test/buttons/useProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10 — designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10 imports designer/client/src/components/graph/node-modal/tests/ExpressionTestResults.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18 — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:test-suite-dependency] designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6 — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23 — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23 imports designer/client/src/components/toolbars/test/buttons/AdhocTestingButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file designer/client/src/components/graph/Graph.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/reducers/graph/reducer.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/modals/TestingDataRecords/Table.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/RangeSelectPlugin.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/search/utils.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/containers/Visualization.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/submodules/packages/components/src/components/usages/usagesTable.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/AddProcessForm.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/node-modal/ParametersUtils.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/NodeDescriptionPopover.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/submodules/packages/components/src/components/listWithFilters.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/containers/settings/collapsibleSwitchList.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/node-modal/node/NodeDetails.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/activities/ActivitiesPanel.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItem.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/creator/ToolBox.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/toolbars/creator/CreatorPanel.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/PanZoomPlugin.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/Assertions.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×36
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 11 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×35
  • FunctionTooLong: useDataMapper.useDataMapper designer/client/src/components/dataMapper/useDataMapper.ts:139 — FunctionTooLong — useDataMapper runs 371 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 271 over it, 3.71× 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: FieldRow.FieldRow designer/client/src/components/dataMapper/FieldRow.tsx:90 — FunctionTooLong — FieldRow runs 349 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 249 over it, 3.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.
  • FunctionTooLong: DataMapper.DataMapper designer/client/src/components/dataMapper/DataMapper.tsx:68 — FunctionTooLong — DataMapper runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: CompareVersionsDialog.VersionsForm designer/client/src/components/modals/CompareVersionsDialog.tsx:159 — FunctionTooLong — VersionsForm runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: TableEditor.Table designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119 — FunctionTooLong — Table runs 322 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 222 over it, 3.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ConditionBuilder.ConditionBuilder designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47 — FunctionTooLong — ConditionBuilder runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: reducer.graphReducer designer/client/src/reducers/graph/reducer.ts:170 — FunctionTooLong — graphReducer runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× 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: ScenarioLabels.ScenarioLabels designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132 — FunctionTooLong — ScenarioLabels runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SpelExpressionBuilder.SpelExpressionBuilder designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83 — FunctionTooLong — SpelExpressionBuilder runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× 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: Table.Table designer/client/src/components/modals/TestingDataRecords/Table.tsx:56 — FunctionTooLong — Table runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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: InputDataRecords.InputDataRecords designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx:33 — FunctionTooLong — InputDataRecords runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× 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: Variable.Variable designer/client/src/components/graph/node-modal/Variable.tsx:82 — FunctionTooLong — Variable runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: AddProcessForm.AddProcessForm designer/client/src/components/AddProcessForm.tsx:39 — FunctionTooLong — AddProcessForm runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× 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: NodeTypeDetailsContent.NodeDetails designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:48 — FunctionTooLong — NodeDetails runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.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: usagesTable.UsagesTable designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 — FunctionTooLong — UsagesTable 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.
  • FunctionTooLong: ContextTreeNode.ContextTreeNode designer/client/src/components/builderComponents/ContextTreeNode.tsx:50 — FunctionTooLong — ContextTreeNode runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.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: tablePart.TablePart designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:23 — FunctionTooLong — TablePart runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: DeployButton.DeployButton designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33 — FunctionTooLong — DeployButton runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: EdgeFields.EdgeFields designer/client/src/components/graph/node-modal/EdgeFields.tsx:39 — FunctionTooLong — EdgeFields runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: InputOutputLayout.InputOutputLayout designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38 — FunctionTooLong — InputOutputLayout runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: AssertionItem.AssertionItemComponent designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/AssertionItem.tsx:72 — FunctionTooLong — AssertionItemComponent runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: RedeployButton.RedeployButton designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33 — FunctionTooLong — RedeployButton runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: styles.aceEditorStyles designer/client/src/containers/theme/styles.ts:6 — FunctionTooLong — aceEditorStyles runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: filtersPart.FiltersPart designer/submodules/packages/components/src/scenarios/filters/filtersPart.tsx:20 — FunctionTooLong — FiltersPart runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: use-touch-sensor.useTouchSensor designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:278 — FunctionTooLong — useTouchSensor runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 10 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×25
  • No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts:43 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts:51 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should omit brackets designer/client/src/components/graph/node-modal/typeHelpers.test.ts:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - variable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - recordVariable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:31 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - filter designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:44 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - choice designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:57 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - split designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - foreach designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:75 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: basic components - union designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:82 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: aggregates - Single Side Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:93 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: aggregates - Full Outer Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:103 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fragments - Properties designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:111 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fragments - Inputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:120 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fragments - Outputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:135 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should allow filtering by processing mode designer/client/cypress/e2e/components.cy.ts:257 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should display and expand advanced deploy section designer/client/cypress/e2e/deployAdvancedSection.cy.ts:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should allow drag node designer/client/cypress/e2e/process.cy.ts:157 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should make a deploy of the new version designer/client/cypress/e2e/process.cy.ts:200 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should allow pan view designer/client/cypress/e2e/processSelection.cy.ts:30 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should select only fully covered (to right) designer/client/cypress/e2e/processSelection.cy.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should select partially covered (to left) designer/client/cypress/e2e/processSelection.cy.ts:50 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should switch modes, append and inverse select with shift designer/client/cypress/e2e/processSelection.cy.ts:59 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
GD1 · Unfinished & placeholder code · Unfinished stub · ×13
  • Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39 — `setLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41 — `getLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43 — `setLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45 — `getParentLogger` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47 — `getLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47 — `exampleOfType` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82 — `getFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102 — `addFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123 — `zip` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10 — `invoke` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14 — `invoke` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14 — `invoke` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32 — `implementation` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×13
  • Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39 — `setLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41 — `getLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43 — `setLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45 — `getParentLogger` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47 — `getLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47 — `exampleOfType` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82 — `getFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102 — `addFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123 — `zip` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10 — `invoke` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14 — `invoke` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14 — `invoke` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32 — `implementation` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
X3 · Exception handling · Swallowed exception (empty catch) · ×11
  • Swallowed exception (empty catch) designer/client/src/windowManager/LoadingButton.tsx:19 — 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) designer/client/src/store/draftListener.ts:101 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) designer/client/src/store/draftListener.ts:129 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) designer/client/src/store/draftListener.ts:179 — 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:38 — 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) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts:34 — 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) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts:55 — 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) designer/client/src/components/graph/SelectionContextProvider.tsx:72 — 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) designer/client/src/components/graph/SelectionContextProvider.tsx:96 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) designer/client/src/components/graph/node-modal/Variable.tsx:145 — 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) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx:83 — 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.
AC2 · Forms & labels · <TextField> field component without a label · ×10
  • <TextField> field component without a label designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:175 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/conditionBuilder/ConditionRow.tsx:128 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/dataMapper/DataMapper.tsx:165 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:299 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:381 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/dataMapper/SampleJsonPanel.tsx:53 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/modals/TestingDataRecords/AppendFromLiveDataButton.tsx:52 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/modals/TestingDataRecords/PasteRecordsDialog.tsx:96 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:162 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label designer/client/src/containers/settings/SearchField.tsx:31 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D3 · God Classes · FileTooLong · ×9
  • FileTooLong: description/NodesApiEndpoints.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/NodesApiEndpoints.scala — FileTooLong — 1675 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1175 over it, 3.35× 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: HttpService/HttpService.ts designer/client/src/http/HttpService/HttpService.ts — FileTooLong — 902 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: HttpService (74-1340). The bar is 500 significant lines; this is 402 over it, 1.80× 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: activities/DbScenarioActivityRepository.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala — FileTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: DbScenarioActivityRepository (37-991). The bar is 500 significant lines; this is 318 over it, 1.64× 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: spel/SpelTyper.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala — FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 249 over it, 1.50× 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: nodecompilation/NodeCompiler.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/NodeCompiler.scala — FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: NodeCompiler (202-962). The bar is 500 significant lines; this is 223 over it, 1.45× 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: periodic/PeriodicProcessService.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala — FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: PeriodicProcessService (34-740). The bar is 500 significant lines; this is 167 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: scenarioActivity/Dtos.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/scenarioActivity/Dtos.scala — FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 166 over it, 1.33× 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: graph/Graph.tsx designer/client/src/components/graph/Graph.tsx — FileTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 54 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: api/ScenarioActivityApiHttpService.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala — FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ScenarioActivityApiHttpService (41-666). The bar is 500 significant lines; this is 27 over it, 1.05× 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×8
  • Low cohesion: CaseClassComparator (LCOM4 7) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeComparator.scala:30 — CaseClassComparator's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DbScenarioActivityRepository (LCOM4 5) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:37 — DbScenarioActivityRepository's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TableSource (LCOM4 5) engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/source/TableSource.scala:47 — TableSource's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ScenarioActivityApiHttpService (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala:41 — ScenarioActivityApiHttpService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DBFetchingProcessRepository (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:49 — DBFetchingProcessRepository's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SlickPeriodicProcessesRepository (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:172 — SlickPeriodicProcessesRepository's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: JsonSchemaRequestResponseSource (LCOM4 4) engine/lite/components/request-response/src/main/scala/pl/touk/nussknacker/engine/lite/components/requestresponse/jsonschema/sources/JsonSchemaRequestResponseSource.scala:29 — JsonSchemaRequestResponseSource's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NodeCompiler (LCOM4 4) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/NodeCompiler.scala:202 — NodeCompiler's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: GenericSourceWithCustomTestingSupport.scala ↔ SampleNodes.scala engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala:1 — `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala` and `engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala` change together 100% of the time (14 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 14 shared commits counted here, the most recent 3 are `180c9334` method instead of function (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `05c70618` removed ContextIdGenerator passing (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `643b57f5` [NU-2189] Make ContextInitializer be responsible only for variables f… (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`) — run `git show` on any of them.
  • Change coupling: nodeDetails.ts ↔ nodeDetailsState.ts designer/client/src/actions/nk/nodeDetails.ts:1 — `designer/client/src/actions/nk/nodeDetails.ts` and `designer/client/src/reducers/nodeDetailsState.ts` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `7f6b0513` [NU-2440] switch mocks mechanism to test cases (#8891); `dc19e87d` NU-2160-show-loader-during-dynamic-parameters-loading (#8059); `3909867e` cleanup unnecessary errors in console (#5511) — run `git show` on any of them.
  • Change coupling: TableSource.scala ↔ RowConversions.scala engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/source/TableSource.scala:1 — `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/source/TableSource.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/RowConversions.scala` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `aebee4e5` Table types alignment (#6546) (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/source/TableSource.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`); `3c5861ac` [NU-1766] TypedObjectTypingResult.fields are backed by ListMap for co… (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/source/TableSource.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`); `0582b2c6` TableAggregation: using stream of rows with specified typeinformation… (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/source/TableSource.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`) — run `git show` on any of them.
  • Change coupling: process.ts ↔ reducer.ts designer/client/src/actions/nk/process.ts:1 — `designer/client/src/actions/nk/process.ts` and `designer/client/src/reducers/graph/reducer.ts` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `5fad387f` [NU-2483] fix scenario validation error for imported scenario (#9132); `525063fa` Bulk fe (live data) bugfixes (#8312); `4960c6a6` Live data bugfixes (#8291) — run `git show` on any of them.
  • Change coupling: EventGeneratorSourceFactory.scala ↔ GenericSourceWithCustomTestingSupport.scala engine/flink/components/base-unbounded/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/EventGeneratorSourceFactory.scala:1 — `engine/flink/components/base-unbounded/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/EventGeneratorSourceFactory.scala` and `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `180c9334` method instead of function (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `05c70618` removed ContextIdGenerator passing (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`); `643b57f5` [NU-2189] Make ContextInitializer be responsible only for variables f… (at that commit the file was still `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomVariablesSample.scala`) — run `git show` on any of them.
  • Change coupling: TableSink.scala ↔ RowConversions.scala engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/sink/TableSink.scala:1 — `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/sink/TableSink.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/RowConversions.scala` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `aebee4e5` Table types alignment (#6546) (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/sink/TableSink.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`); `0582b2c6` TableAggregation: using stream of rows with specified typeinformation… (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/sink/TableSink.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`); `1882a946` [NU-1728] Move table components to public distribution (#6294) (at that commit the files were still `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/sink/TableSink.scala` and `engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/utils/RowConversions.scala`) — run `git show` on any of them.
  • Change coupling: actionTypes.ts ↔ node.ts designer/client/src/actions/actionTypes.ts:1 — `designer/client/src/actions/actionTypes.ts` and `designer/client/src/actions/nk/node.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `00cdd3d3` fixed search focus and keyboard/clipboard events (#7207); `9c655ca8` [NU-1145] fragment outputs (#4933); `c57979f9` fixed fragment node id prefix (#3232) (at that commit the files were still `ui/client/actions/actionTypes.ts` and `ui/client/actions/nk/node.ts`) — run `git show` on any of them.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×7
  • Recursive walk over a caller-supplied document has no depth cap utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/util/json/JsonSchemaUtils.scala:19 — `JsonSchemaUtils.circeToJson` is public and takes `value: Json` from its caller, and it calls itself at line 19 with a piece of `value` (and at line 20), not as a tail call the compiler turns into a loop — and nowhere in `JsonSchemaUtils.circeToJson` 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. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonSchemaUtils.circeToJson` 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 designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx:22 — `jsonToSpelString` is exported and takes `value: any` from its caller, and it calls itself at line 22 (`jsonToSpelString`) with a piece of `value` (and at line 26) — and nowhere in `jsonToSpelString` 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 `jsonToSpelString` 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 designer/client/src/components/dataMapper/dataMapperUtils.ts:331 — `fieldsFromSample` is exported and takes `obj: unknown` from its caller, and it calls itself at line 331 (`fieldsFromSample`) with a piece of `obj` — and nowhere in `fieldsFromSample` 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 `fieldsFromSample` 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 designer/client/src/components/builderComponents/typeUtils.ts:6 — `inferDisplayType` is exported and takes `val: unknown` from its caller, and it calls itself at line 6 (`inferDisplayType`) with a piece of `val` — and nowhere in `inferDisplayType` 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 `inferDisplayType` 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 designer/client/src/components/builderComponents/typeUtils.ts:16 — `typingResultToSample` is exported and takes `t: any` from its caller, and it calls itself at line 16 (`typingResultToSample`) with a piece of `t` (and at line 21) — and nowhere in `typingResultToSample` 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 `typingResultToSample` 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 designer/client/src/components/builderComponents/typeUtils.ts:40 — `treeNodeMatchesFilter` is exported and takes `value: unknown` from its caller, and it calls itself at line 40 (`treeNodeMatchesFilter`) with a piece of `value` — and nowhere in `treeNodeMatchesFilter` 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 `treeNodeMatchesFilter` 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonSimpleDecoder.scala:15 — `FromJsonSimpleDecoder.jsonToAny` is public and takes `json: Json` from its caller, and it calls itself at line 15 with a piece of `json` (and at line 19), not as a tail call the compiler turns into a loop — and nowhere in `FromJsonSimpleDecoder.jsonToAny` 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. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `FromJsonSimpleDecoder.jsonToAny` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: HttpService designer/client/src/http/HttpService/HttpService.ts:74 — TooManyMethods — 87 methods. The bar is 30 methods; this is 57 over it, 2.90× 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: Graph designer/client/src/components/graph/Graph.tsx:126 — 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: DbScenarioActivityRepository designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:37 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GraphBuilder scenario-api/src/main/scala/pl/touk/nussknacker/engine/build/GraphBuilder.scala:16 — 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: NodeUtils designer/client/src/components/graph/NodeUtils.ts:14 — 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: PeriodicProcessService designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:34 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) designer/server/src/main/scala/db/migration/InvalidateComponentsUsagesCache.scala:20 — designer/server/src/main/scala/db/migration/InvalidateComponentsUsagesCache.scala:20-24 | designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/SlickMigration.scala:69-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/db/migration/InvalidateComponentsUsagesCache.scala:20` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) extensions-api/src/main/scala/pl/touk/nussknacker/engine/migration/ExpressionsMigration.scala:23 — extensions-api/src/main/scala/pl/touk/nussknacker/engine/migration/ExpressionsMigration.scala:23-27 | extensions-api/src/main/scala/pl/touk/nussknacker/engine/migration/ParametersMigration.scala:18-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) utils/default-helpers/src/main/scala/pl/touk/nussknacker/engine/util/functions/collection.scala:527 — utils/default-helpers/src/main/scala/pl/touk/nussknacker/engine/util/functions/collection.scala:527-531 | utils/default-helpers/src/main/scala/pl/touk/nussknacker/engine/util/functions/collection.scala:553-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/default-helpers/src/main/scala/pl/touk/nussknacker/engine/util/functions/collection.scala:527` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:69 — engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:69-73 | engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala:84-88 — before extracting anything, compare `engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala` and `engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:58 — scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:58-62 | scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:67-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
AC2 · Forms & labels · <Select> field component without a label · ×4
  • <Select> field component without a label designer/client/src/components/common/DropdownButton.tsx:58 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:237 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label designer/client/src/components/conditionBuilder/ConditionRow.tsx:111 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:328 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×4
  • Untrusted text written into markup unescaped REDACTED:53 — `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 designer/client/src/components/graph/GlobalCursor.ts:10 — `` * { cursor: ${cursor} !important; } html, body, * { …` 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 designer/client/src/components/graph/node-modal/editors/expression/LineClamp.tsx:106 — `truncatedElement.innerHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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 designer/client/src/components/graph/svg-export/prepareSvg.ts:17 — `svgString` is text this program did not author, and it is written into the text of an element through `document.write` 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassSerializer.scala:69 — `case t: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:340 — `.catch((e) => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:454 — `.catch(() => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (caught, then discarded) designer/client/src/components/modals/saveScenario/useSaveScenario.ts:79 — `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC2 · Forms & labels · <Autocomplete> field component without a label · ×3
  • <Autocomplete> field component without a label designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:107 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Autocomplete> field component without a label designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:86 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Autocomplete> field component without a label designer/client/src/components/sidePanels/SearchLabeledAutocomplete.tsx:15 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D31 · IaC & Container Security · Medium IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:561 — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:561-570 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:593-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:561` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:118 — engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:118-127 | engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:140-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:138 — utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:138-148 | utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:154-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×3
  • Duplicated block (23 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionRow.tsx:86 — designer/client/src/components/conditionBuilder/ConditionRow.tsx:86 · designer/client/src/components/conditionBuilder/ConditionRow.tsx:136 — 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.
  • Duplicated block (23 lines × 2 locations) designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25 — designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25 · designer/client/src/components/graph/node-modal/MapVariable.tsx:30 — 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 (23 lines × 2 locations) designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38 — designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38 · designer/client/src/components/modals/GenerateTestDataDialog.tsx:41 — 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 (18 lines × 2 locations) · ×3
  • Duplicated block (18 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65 — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65 · designer/client/src/components/dataMapper/useDataMapper.ts:292 — 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 (18 lines × 2 locations) designer/client/src/components/dataMapper/dataMapperUtils.ts:215 — designer/client/src/components/dataMapper/dataMapperUtils.ts:215 · designer/client/src/components/dataMapper/dataMapperUtils.ts:239 — 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 (18 lines × 2 locations) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206 — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:159 — 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.
R7 · Dead Code · Dead file (~89 LoC) · ×3
  • Dead file (~89 LoC) designer/client/src/components/MenuBar/breadcrumbs.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/MenuBar/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~89 LoC) designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/InitializeChatStream.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~89 LoC) designer/client/src/components/modals/PropertiesDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
S1 · Web-Security Posture · Weak hash algorithm · ×3
  • Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169 — 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+ (`MessageDigest.getInstance("SHA-256")`) 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.
  • Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214 — 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+ (`MessageDigest.getInstance("SHA-256")`) 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.
  • Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40 — 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+ (`MessageDigest.getInstance("SHA-256")`) 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.
AC2 · Forms & labels · <RadioGroup> field component without a label · ×2
  • <RadioGroup> field component without a label designer/client/src/components/graph/node-modal/editors/expression/FixedValuesRadioEditor.tsx:22 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/fields/FixedValuesGroup.tsx:24 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: FlinkProcessRegistrar.createInterpreter engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:94 — MethodTooLong — createInterpreter runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FlinkProcessRegistrar.register engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103 — MethodTooLong — register runs 314 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 214 over it, 3.14× 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.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: HttpService designer/client/src/http/HttpService/HttpService.ts:74 — ClassTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded), 87 methods. The bar is 400 significant lines; this is 432 over it, 2.08× 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: ScenarioActivityApiHttpService designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala:41 — ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:86 — components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:86-99 | components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:112-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:86` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:50 — engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:50-63 | engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala:65-78 — before extracting anything, compare `engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala` and `engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86 — components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86-94 | components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:111-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/RowConversions.scala:81 — engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/RowConversions.scala:81-89 | live-data-collector/src/main/scala/pl/touk/nussknacker/engine/livedata/CollectedLiveData.scala:29-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/UnionParametersMigration.scala:22 — defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/UnionParametersMigration.scala:22-28 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/migrate/UnionParametersMigration.scala:18-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/UnionParametersMigration.scala:22` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:117 — designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:117-123 | designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:130-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
IC1 · Incompleteness & stubs · Skeleton type · ×2
  • Skeleton type — most members are unfinished designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:9 — `AlwaysUsingSameConnectionDataSource` has 5 unfinished members out of 9 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented.
  • Skeleton type — most members are unfinished engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:25 — `ExampleFunctions` has 4 unfinished members out of 5 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×2
  • Sync-over-async blocking engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MeetingService.scala:17 — `invoke` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs.
  • Sync-over-async blocking engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:126 — `waitForSavepoint` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×2
  • Duplicated block (30 lines × 2 locations) designer/client/src/components/graph/node-modal/DescriptionField.tsx:10 — designer/client/src/components/graph/node-modal/DescriptionField.tsx:10 · designer/client/src/components/graph/node-modal/DisableField.tsx:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (30 lines × 2 locations) designer/client/src/components/modals/DeployProcessDialog.tsx:46 — designer/client/src/components/modals/DeployProcessDialog.tsx:46 · designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx:48 — 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 (25 lines × 2 locations) · ×2
  • Duplicated block (25 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16 — designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16 · designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/TimeEditor.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (25 lines × 2 locations) designer/client/src/components/modals/AddCommentDialog.tsx:28 — designer/client/src/components/modals/AddCommentDialog.tsx:28 · designer/client/src/components/modals/saveScenario/SaveScenarioDialog.tsx:22 — 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 (22 lines × 2 locations) · ×2
  • Duplicated block (22 lines × 2 locations) designer/client/src/components/dataMapper/dataMapperUtils.ts:339 — designer/client/src/components/dataMapper/dataMapperUtils.ts:339 · designer/client/src/components/graph/node-modal/ParametersUtils.ts:30 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (22 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62 — designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62 · designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx:107 — 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.
R7 · Dead Code · Dead file (~151 LoC) · ×2
  • Dead file (~151 LoC) designer/client/src/components/MenuBar/menu.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/MenuBar/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~151 LoC) designer/client/src/containers/liveData/LiveDataThroughputs.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~139 LoC) · ×2
  • Dead file (~139 LoC) designer/client/src/components/aiAssistant/InitializeChatStream.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/aiAssistant/ModelAdapter.ts, designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~139 LoC) designer/client/src/containers/ScenarioDescription.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~113 LoC) · ×2
  • Dead file (~113 LoC) designer/client/src/components/sidePanels/SidePanelsContext.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (designer/client/src/components/SidePanelToggleButton.tsx, designer/client/src/components/sidePanels/SidePanel.tsx, designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~113 LoC) designer/client/src/containers/NodeCreationHandler.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/creator/CreatorPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~104 LoC) · ×2
  • Dead file (~104 LoC) designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~104 LoC) designer/client/src/components/versionInfo.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/NussknackerApp.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~80 LoC) · ×2
  • Dead file (~80 LoC) designer/client/src/components/tips/Warnings.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/tips/Tips.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~80 LoC) designer/client/src/containers/assertions/addAssertionResultToNodes.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC2 · Forms & labels · <Textarea> field component without a label · ×1
  • <Textarea> field component without a label designer/client/src/components/graph/node-modal/editors/expression/TextareaEditor.tsx:36 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <TextArea> field component without a label · ×1
  • <TextArea> field component without a label designer/client/src/components/graph/node-modal/editors/field/Textarea.tsx:32 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 579 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · SpelTyper.typeNode (cyclomatic 143) · ×1
  • SpelTyper.typeNode (cyclomatic 143) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169 — SpelTyper.typeNode has cyclomatic complexity 143 (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.
D1 · Cyclomatic Complexity · CompareVersionsDialog.VersionsForm (cyclomatic 62) · ×1
  • CompareVersionsDialog.VersionsForm (cyclomatic 62) designer/client/src/components/modals/CompareVersionsDialog.tsx:159 — CompareVersionsDialog.VersionsForm has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 14 of the 62 points are its own statements and the rest belongs to 22 function items inside it that branch (printDiff, a function literal at line 214, a function literal at line 397, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FromJsonTypingResultBasedDecoder.decodeValue (cyclomatic 55) · ×1
  • FromJsonTypingResultBasedDecoder.decodeValue (cyclomatic 55) components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonTypingResultBasedDecoder.scala:51 — FromJsonTypingResultBasedDecoder.decodeValue has cyclomatic complexity 55 (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.
D1 · Cyclomatic Complexity · reducer.graphReducer (cyclomatic 44) · ×1
  • reducer.graphReducer (cyclomatic 44) designer/client/src/reducers/graph/reducer.ts:170 — reducer.graphReducer has cyclomatic complexity 44 (threshold 15). Of this number, 33 points are the body's own statements and 11 belong to 7 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.
D1 · Cyclomatic Complexity · DbScenarioActivityRepository.fromEntity (cyclomatic 43) · ×1
  • DbScenarioActivityRepository.fromEntity (cyclomatic 43) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720 — DbScenarioActivityRepository.fromEntity has cyclomatic complexity 43 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · FieldRow.FieldRow (cyclomatic 43) · ×1
  • FieldRow.FieldRow (cyclomatic 43) designer/client/src/components/dataMapper/FieldRow.tsx:90 — FieldRow.FieldRow has cyclomatic complexity 43 (threshold 15). Of this number, 39 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · InterpreterInternal.interpretNode (cyclomatic 42) · ×1
  • InterpreterInternal.interpretNode (cyclomatic 42) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:81 — InterpreterInternal.interpretNode has cyclomatic complexity 42 (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.
D1 · Cyclomatic Complexity · ContextTreeNode.ContextTreeNode (cyclomatic 41) · ×1
  • ContextTreeNode.ContextTreeNode (cyclomatic 41) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50 — ContextTreeNode.ContextTreeNode has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · SpelExpressionSuggester.expressionSuggestionsAux (cyclomatic 39) · ×1
  • SpelExpressionSuggester.expressionSuggestionsAux (cyclomatic 39) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114 — SpelExpressionSuggester.expressionSuggestionsAux has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · Table.Table (cyclomatic 39) · ×1
  • Table.Table (cyclomatic 39) designer/client/src/components/modals/TestingDataRecords/Table.tsx:56 — Table.Table has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 184, 213, 244, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ScenarioLabels.ScenarioLabels (cyclomatic 37) · ×1
  • ScenarioLabels.ScenarioLabels (cyclomatic 37) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132 — ScenarioLabels.ScenarioLabels has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 289, 385, 171, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DataMapper.DataMapper (cyclomatic 32) · ×1
  • DataMapper.DataMapper (cyclomatic 32) designer/client/src/components/dataMapper/DataMapper.tsx:68 — DataMapper.DataMapper has cyclomatic complexity 32 (threshold 15). Of this number, 19 points are the body's own statements and 13 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FieldSwitch.FieldSwitch (cyclomatic 31) · ×1
  • FieldSwitch.FieldSwitch (cyclomatic 31) designer/client/src/components/graph/node-modal/editors/field/FieldSwitch.tsx:72 — FieldSwitch.FieldSwitch has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 214, 94, 141, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cyclomatic 27) · ×1
  • DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cyclomatic 27) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/dict/DictKeyParameterAdapter.scala:64 — DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · ButtonRoot.ButtonRoot (cyclomatic 27) · ×1
  • ButtonRoot.ButtonRoot (cyclomatic 27) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12 — ButtonRoot.ButtonRoot has cyclomatic complexity 27 (threshold 15). Of this number, 17 points are the body's own statements and 10 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.
D1 · Cyclomatic Complexity · NodeSwitcherUtils.adjustEdges (cyclomatic 27) · ×1
  • NodeSwitcherUtils.adjustEdges (cyclomatic 27) REDACTED:50 — NodeSwitcherUtils.adjustEdges has cyclomatic complexity 27 (threshold 15). Of this number, 16 points are the body's own statements and 11 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.
D1 · Cyclomatic Complexity · useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cyclomatic 26) · ×1
  • useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cyclomatic 26) designer/client/src/components/dataMapper/useDataMapper.ts:438 — useDataMapper.useDataMapper.defaultFetchTopicDefinitions has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 477, 452, 472, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ConditionBuilder.ConditionBuilder (cyclomatic 26) · ×1
  • ConditionBuilder.ConditionBuilder (cyclomatic 26) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47 — ConditionBuilder.ConditionBuilder has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 63, 90, 98, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · drawText.buildFragmentsForTokens · ×1
  • drawText.buildFragmentsForTokens::wrapAndPushWords (cyclomatic 26) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141 — drawText.buildFragmentsForTokens::wrapAndPushWords 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. This shape REPEATS in the file: one other method here (drawText.buildFragmentsForTokens) 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.
D1 · Cyclomatic Complexity · FlinkProcessRegistrar.register (cyclomatic 25) · ×1
  • FlinkProcessRegistrar.register (cyclomatic 25) engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103 — FlinkProcessRegistrar.register has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · Variable.Variable (cyclomatic 25) · ×1
  • Variable.Variable (cyclomatic 25) designer/client/src/components/graph/node-modal/Variable.tsx:82 — Variable.Variable has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 124, 269, 108, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SelectionContextProvider.SelectionContextProvider (cyclomatic 24) · ×1
  • SelectionContextProvider.SelectionContextProvider (cyclomatic 24) designer/client/src/components/graph/SelectionContextProvider.tsx:137 — SelectionContextProvider.SelectionContextProvider has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 231, 153, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PrettyValidationErrors.mapIdErrorToNodeError (cyclomatic 23) · ×1
  • PrettyValidationErrors.mapIdErrorToNodeError (cyclomatic 23) designer/restmodel/src/main/scala/pl/touk/nussknacker/restmodel/validation/PrettyValidationErrors.scala:425 — PrettyValidationErrors.mapIdErrorToNodeError has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: PrettyValidationErrors.formatErrorMessage (cyclomatic 69) 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.
D1 · Cyclomatic Complexity · FromJsonSchemaBasedDecoder.decode (cyclomatic 23) · ×1
  • FromJsonSchemaBasedDecoder.decode (cyclomatic 23) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/decode/FromJsonSchemaBasedDecoder.scala:23 — FromJsonSchemaBasedDecoder.decode has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ToolbarWrapper.ToolbarWrapper (cyclomatic 23) · ×1
  • ToolbarWrapper.ToolbarWrapper (cyclomatic 23) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33 — ToolbarWrapper.ToolbarWrapper has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · ExpressionCompiler.compileNodeParameters (cyclomatic 22) · ×1
  • ExpressionCompiler.compileNodeParameters (cyclomatic 22) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/ExpressionCompiler.scala:175 — ExpressionCompiler.compileNodeParameters has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · useDataMapper.useDataMapper.enrichedContext (cyclomatic 22) · ×1
  • useDataMapper.useDataMapper.enrichedContext (cyclomatic 22) designer/client/src/components/dataMapper/useDataMapper.ts:197 — useDataMapper.useDataMapper.enrichedContext 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.
D1 · Cyclomatic Complexity · TableEditor.Table (cyclomatic 22) · ×1
  • TableEditor.Table (cyclomatic 22) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119 — TableEditor.Table has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 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.
D1 · Cyclomatic Complexity · DeployButton.DeployButton (cyclomatic 22) · ×1
  • DeployButton.DeployButton (cyclomatic 22) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33 — DeployButton.DeployButton has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RedeployButton.RedeployButton (cyclomatic 22) · ×1
  • RedeployButton.RedeployButton (cyclomatic 22) designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33 — RedeployButton.RedeployButton has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cyclomatic 21) · ×1
  • AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cyclomatic 21) components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala:151 — AssignabilityDeterminer.isSingleTypeMatchesTargetObjType has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · reducer.reducer (cyclomatic 21) · ×1
  • reducer.reducer (cyclomatic 21) designer/client/src/components/graph/node-modal/editors/expression/Table/state/reducer.ts:6 — reducer.reducer has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · LiveDataThroughputs.LiveDataThroughputs (cyclomatic 21) · ×1
  • LiveDataThroughputs.LiveDataThroughputs (cyclomatic 21) designer/client/src/containers/liveData/LiveDataThroughputs.tsx:16 — LiveDataThroughputs.LiveDataThroughputs 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 9 function literals inside it that branch (lines 80, 114, 37, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cyclomatic 20) · ×1
  • JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cyclomatic 20) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonTemplateFromJsonSchemaDeterminer.scala:39 — JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · Selection.getValueRef (cyclomatic 20) · ×1
  • Selection.getValueRef (cyclomatic 20) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Selection.java:86 — Selection.getValueRef has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · collapsibleSwitchList.CollapsibleSwitchList (cyclomatic 20) · ×1
  • collapsibleSwitchList.CollapsibleSwitchList (cyclomatic 20) designer/client/src/containers/settings/collapsibleSwitchList.tsx:66 — collapsibleSwitchList.CollapsibleSwitchList 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 3 function items inside it that branch (a function literal at line 105, flattenPath, a function literal at line 100). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · use-mouse-sensor.useMouseSensor (cyclomatic 20) · ×1
  • use-mouse-sensor.useMouseSensor (cyclomatic 20) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:211 — use-mouse-sensor.useMouseSensor 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 5 function literals inside it that branch (lines 220, 292, 335, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · NumberUtils.convertNumberToTargetClass (cyclomatic 19) · ×1
  • NumberUtils.convertNumberToTargetClass (cyclomatic 19) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:87 — NumberUtils.convertNumberToTargetClass has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SpelExpressionBuilder.SpelExpressionBuilder (cyclomatic 19) · ×1
  • SpelExpressionBuilder.SpelExpressionBuilder (cyclomatic 19) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83 — SpelExpressionBuilder.SpelExpressionBuilder has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · extendActivitiesWithUIData.extendActivitiesWithUIData (cyclomatic 19) · ×1
  • extendActivitiesWithUIData.extendActivitiesWithUIData (cyclomatic 19) designer/client/src/components/toolbars/activities/helpers/extendActivitiesWithUIData.ts:37 — extendActivitiesWithUIData.extendActivitiesWithUIData 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 4 function items inside it that branch (recursiveDateLabelDesignation, recursiveToggleItemsButtonDesignation, initiallyHideItems, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ProcessUtils._findVariablesDefinedInProcess (cyclomatic 19) · ×1
  • ProcessUtils._findVariablesDefinedInProcess (cyclomatic 19) designer/client/src/common/ProcessUtils.ts:143 — ProcessUtils._findVariablesDefinedInProcess has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NuSpelExpressionParser.skipToCorrectEndSuffix (cyclomatic 18) · ×1
  • NuSpelExpressionParser.skipToCorrectEndSuffix (cyclomatic 18) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:190 — NuSpelExpressionParser.skipToCorrectEndSuffix has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CustomCompleterAceEditor.CustomCompleterAceEditor (cyclomatic 18) · ×1
  • CustomCompleterAceEditor.CustomCompleterAceEditor (cyclomatic 18) designer/client/src/components/graph/node-modal/editors/expression/CustomCompleterAceEditor.tsx:49 — CustomCompleterAceEditor.CustomCompleterAceEditor has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useDataMapper.useDataMapper (cyclomatic 18) · ×1
  • useDataMapper.useDataMapper (cyclomatic 18) designer/client/src/components/dataMapper/useDataMapper.ts:139 — useDataMapper.useDataMapper has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 153, 552, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · useDataMapper.useDataMapper.handleAutoMap (cyclomatic 18) · ×1
  • useDataMapper.useDataMapper.handleAutoMap (cyclomatic 18) designer/client/src/components/dataMapper/useDataMapper.ts:328 — useDataMapper.useDataMapper.handleAutoMap has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function items inside it that branch (isTrivialExpression, traverse, a function literal at line 353, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ToolbarsContainer.ToolbarsContainer (cyclomatic 18) · ×1
  • ToolbarsContainer.ToolbarsContainer (cyclomatic 18) designer/client/src/components/toolbarComponents/ToolbarsContainer.tsx:133 — ToolbarsContainer.ToolbarsContainer has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 145, 200, 193, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · drawText.buildFragmentsForTokens (cyclomatic 18) · ×1
  • drawText.buildFragmentsForTokens (cyclomatic 18) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120 — drawText.buildFragmentsForTokens 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. This shape REPEATS in the file: one other method here (drawText.buildFragmentsForTokens::wrapAndPushWords) 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.
D1 · Cyclomatic Complexity · InputOutputLayout.InputOutputLayout (cyclomatic 18) · ×1
  • InputOutputLayout.InputOutputLayout (cyclomatic 18) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38 — InputOutputLayout.InputOutputLayout has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NameValueListEditor.NameValueListEditor (cyclomatic 18) · ×1
  • NameValueListEditor.NameValueListEditor (cyclomatic 18) designer/client/src/components/graph/node-modal/editors/expression/NameValueList/NameValueListEditor.tsx:43 — NameValueListEditor.NameValueListEditor has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 62, 131, 56, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DeploymentService.runDeploymentOrRedeploy (cyclomatic 17) · ×1
  • DeploymentService.runDeploymentOrRedeploy (cyclomatic 17) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:97 — DeploymentService.runDeploymentOrRedeploy has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · spelUtils.parseConditionAst (cyclomatic 17) · ×1
  • spelUtils.parseConditionAst (cyclomatic 17) designer/client/src/components/conditionBuilder/spelUtils.ts:64 — spelUtils.parseConditionAst has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EdgeFields.EdgeFields (cyclomatic 17) · ×1
  • EdgeFields.EdgeFields (cyclomatic 17) designer/client/src/components/graph/node-modal/EdgeFields.tsx:39 — EdgeFields.EdgeFields has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · EdgesDndComponent.EdgesDndComponent (cyclomatic 17) · ×1
  • EdgesDndComponent.EdgesDndComponent (cyclomatic 17) designer/client/src/components/graph/node-modal/EdgesDndComponent.tsx:59 — EdgesDndComponent.EdgesDndComponent 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 6 function literals inside it that branch (lines 105, 139, 137, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · typeUtils.typingResultToSample (cyclomatic 16) · ×1
  • typeUtils.typingResultToSample (cyclomatic 16) designer/client/src/components/builderComponents/typeUtils.ts:12 — typeUtils.typingResultToSample has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Variable.refClazzToValue (cyclomatic 16) · ×1
  • Variable.refClazzToValue (cyclomatic 16) designer/client/src/components/graph/node-modal/Variable.tsx:42 — Variable.refClazzToValue has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ActivityItemHeader.HeaderActivity (cyclomatic 16) · ×1
  • ActivityItemHeader.HeaderActivity (cyclomatic 16) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx:58 — ActivityItemHeader.HeaderActivity has cyclomatic complexity 16 (threshold 15). Of this number, 14 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.
D1 · Cyclomatic Complexity · useActivitiesSearch.useActivitiesSearch.handleGetResults (cyclomatic 16) · ×1
  • useActivitiesSearch.useActivitiesSearch.handleGetResults (cyclomatic 16) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107 — useActivitiesSearch.useActivitiesSearch.handleGetResults has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · drawText.tokenizeDataRecords · ×1
  • drawText.tokenizeDataRecords::walk (cyclomatic 16) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70 — drawText.tokenizeDataRecords::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.
D1 · Cyclomatic Complexity · NodeCreationHandler.useNodeCreationHandler (cyclomatic 16) · ×1
  • NodeCreationHandler.useNodeCreationHandler (cyclomatic 16) designer/client/src/containers/NodeCreationHandler.tsx:14 — NodeCreationHandler.useNodeCreationHandler has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 42, 18, 104, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · usagesTable.UsagesTable (cyclomatic 16) · ×1
  • usagesTable.UsagesTable (cyclomatic 16) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 — usagesTable.UsagesTable 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 11 function literals inside it that branch (lines 66, 195, 74, …). 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: designer/client/src/components/modals/CompareVersionsDialog.tsx designer/client/src/components/modals/CompareVersionsDialog.tsx:159 — designer/client/src/components/modals/CompareVersionsDialog.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in CompareVersionsDialog.VersionsForm at line 159. 1 of those changes was a fix/bug commit, and the other 1 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 11:31:12 +02:00' --until='2026-09-24 11:31:12 +02:00' --full-history --no-merges -- designer/client/src/components/modals/CompareVersionsDialog.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 · Explicit Debt · TodoComment repeated across 14 files · ×1
  • TodoComment repeated across 14 files utils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/TestResultSinkFactory.scala:56 — The identical TodoComment appears in 14 files (15 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 15 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO: Remove after upgrade to Flink 2.x". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · HackComment · ×1
  • HackComment designer/server/src/main/scala/pl/touk/nussknacker/ui/server/NussknackerHttpServer.scala:108 — // HACK!!! This is awful solution, but it's done for a purpose ProcessesResourcesSpec. The spec will be rewritten with — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · SpelTyper.typeNode (cognitive 146) · ×1
  • SpelTyper.typeNode (cognitive 146) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169 — SpelTyper.typeNode has cognitive complexity 146 (threshold 15). Drivers by points: if/else 45 (59 pts), match/switch 32 (51 pts), loops 10 (27 pts), boolean chains 9 (nesting depth added 50). To reduce it, split the body into named stages: move each independent 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 · SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107) · ×1
  • SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114 — SpelExpressionSuggester.expressionSuggestionsAux has cognitive complexity 107 (threshold 15). Drivers by points: match/switch 8 (40 pts), loops 9 (36 pts), if/else 20 (28 pts), boolean chains 3 (nesting depth added 67). To reduce it, split the body into named stages: move each independent 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 · drawText.buildFragmentsForTokens · ×1
  • drawText.buildFragmentsForTokens::wrapAndPushWords (cognitive 75) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141 — drawText.buildFragmentsForTokens::wrapAndPushWords has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (63 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 48). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (drawText.buildFragmentsForTokens) 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.
D2 · Cognitive Complexity · DbScenarioActivityRepository.fromEntity (cognitive 62) · ×1
  • DbScenarioActivityRepository.fromEntity (cognitive 62) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720 — DbScenarioActivityRepository.fromEntity has cognitive complexity 62 (threshold 15). Drivers by points: loops 24 (61 pts), match/switch 1 (nesting depth added 37). 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.
D2 · Cognitive Complexity · K8sDeploymentManager.runDeployment (cognitive 56) · ×1
  • K8sDeploymentManager.runDeployment (cognitive 56) engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/K8sDeploymentManager.scala:157 — K8sDeploymentManager.runDeployment has cognitive complexity 56 (threshold 15). Drivers by points: loops 10 (55 pts), match/switch 1 (nesting depth added 45). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · DomainServices.create (cognitive 55) · ×1
  • DomainServices.create (cognitive 55) designer/server/src/main/scala/pl/touk/nussknacker/ui/factory/DomainServices.scala:101 — DomainServices.create has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · NussknackerAppFactory.createApp (cognitive 55) · ×1
  • NussknackerAppFactory.createApp (cognitive 55) designer/server/src/main/scala/pl/touk/nussknacker/ui/factory/NussknackerAppFactory.scala:20 — NussknackerAppFactory.createApp has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · CompareVersionsDialog.VersionsForm (cognitive 51) · ×1
  • CompareVersionsDialog.VersionsForm (cognitive 51) designer/client/src/components/modals/CompareVersionsDialog.tsx:159 — CompareVersionsDialog.VersionsForm has cognitive complexity 51 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 16, ternaries 15 (16 pts), match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 14 of the 51 points are its own statements and the rest belongs to 22 function items inside it that branch (a function literal at line 486, a function literal at line 397, a function literal at line 176, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · FromJsonTypingResultBasedDecoder.decodeValue (cognitive 47) · ×1
  • FromJsonTypingResultBasedDecoder.decodeValue (cognitive 47) components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonTypingResultBasedDecoder.scala:51 — FromJsonTypingResultBasedDecoder.decodeValue has cognitive complexity 47 (threshold 15). Drivers by points: loops 9 (26 pts), if/else 7 (12 pts), match/switch 5 (9 pts) (nesting depth added 26). 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.
D2 · Cognitive Complexity · ContextTreeNode.ContextTreeNode (cognitive 46) · ×1
  • ContextTreeNode.ContextTreeNode (cognitive 46) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50 — ContextTreeNode.ContextTreeNode has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 24 (37 pts), boolean chains 7, if/else 2 (nesting depth added 13). Of this number, 44 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.
D2 · Cognitive Complexity · ScenarioLabels.ScenarioLabels (cognitive 46) · ×1
  • ScenarioLabels.ScenarioLabels (cognitive 46) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132 — ScenarioLabels.ScenarioLabels has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (26 pts), ternaries 7 (12 pts), boolean chains 8 (nesting depth added 13). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 184, 171, 289, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FieldRow.FieldRow (cognitive 40) · ×1
  • FieldRow.FieldRow (cognitive 40) designer/client/src/components/dataMapper/FieldRow.tsx:90 — FieldRow.FieldRow has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 14 (23 pts), boolean chains 15, if/else 2 (nesting depth added 9). Of this number, 37 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.
D2 · Cognitive Complexity · drawText.buildFragmentsForTokens (cognitive 40) · ×1
  • drawText.buildFragmentsForTokens (cognitive 40) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120 — drawText.buildFragmentsForTokens has cognitive complexity 40 (threshold 15). Drivers by points: if/else 33 (95 pts), loops 4 (9 pts), boolean chains 7, ternaries 2 (5 pts) (nesting depth added 70). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (drawText.buildFragmentsForTokens::wrapAndPushWords) 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.
D2 · Cognitive Complexity · NodeSwitcherUtils.adjustEdges (cognitive 39) · ×1
  • NodeSwitcherUtils.adjustEdges (cognitive 39) REDACTED:50 — NodeSwitcherUtils.adjustEdges has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 4 (7 pts), boolean chains 6, ternaries 3 (5 pts), match/switch 1 (nesting depth added 15). Of this number, 25 points are the body's own statements and 14 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.
D2 · Cognitive Complexity · Table.Table (cognitive 39) · ×1
  • Table.Table (cognitive 39) designer/client/src/components/modals/TestingDataRecords/Table.tsx:56 — Table.Table has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 9, ternaries 5 (6 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 39 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 229, 86, 213, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · Selection.getValueRef (cognitive 38) · ×1
  • Selection.getValueRef (cognitive 38) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Selection.java:86 — Selection.getValueRef has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Migration.migrate (cognitive 36) · ×1
  • Migration.migrate (cognitive 36) designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:36 — Migration.migrate has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · MigrationService.migrateCurrentScenarioDescription (cognitive 36) · ×1
  • MigrationService.migrateCurrentScenarioDescription (cognitive 36) designer/server/src/main/scala/pl/touk/nussknacker/ui/migrations/MigrationService.scala:80 — MigrationService.migrateCurrentScenarioDescription has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · NuRuntimeApp.createProgram (cognitive 36) · ×1
  • NuRuntimeApp.createProgram (cognitive 36) engine/lite/runtime-app/src/main/scala/pl/touk/nussknacker/engine/lite/app/NuRuntimeApp.scala:46 — NuRuntimeApp.createProgram has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · CaseClassTypeInfo.getFlatFields (cognitive 35) · ×1
  • CaseClassTypeInfo.getFlatFields (cognitive 35) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:76 — CaseClassTypeInfo.getFlatFields has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (21 pts), match/switch 3 (11 pts), loops 1 (2 pts), boolean chains 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.
D2 · Cognitive Complexity · ButtonRoot.ButtonRoot (cognitive 33) · ×1
  • ButtonRoot.ButtonRoot (cognitive 33) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12 — ButtonRoot.ButtonRoot has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 21 (29 pts), boolean chains 4 (nesting depth added 8). Of this number, 18 points are the body's own statements and 15 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 · InterpreterInternal.interpretNode (cognitive 29) · ×1
  • InterpreterInternal.interpretNode (cognitive 29) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:81 — InterpreterInternal.interpretNode has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 9 (16 pts), if/else 8 (12 pts), boolean chains 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · Variable.Variable (cognitive 29) · ×1
  • Variable.Variable (cognitive 29) designer/client/src/components/graph/node-modal/Variable.tsx:82 — Variable.Variable has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (10 pts), ternaries 4 (5 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 124, 269, 108, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FieldSwitch.FieldSwitch (cognitive 28) · ×1
  • FieldSwitch.FieldSwitch (cognitive 28) designer/client/src/components/graph/node-modal/editors/field/FieldSwitch.tsx:72 — FieldSwitch.FieldSwitch has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, if/else 9, ternaries 6. Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 214, 94, 141, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ReloadableProcessingTypeDataProvider.reloadAll (cognitive 27) · ×1
  • ReloadableProcessingTypeDataProvider.reloadAll (cognitive 27) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/processingtype/provider/ReloadableProcessingTypeDataProvider.scala:27 — ReloadableProcessingTypeDataProvider.reloadAll has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 1 (6 pts) (nesting depth added 20). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · ConditionBuilder.ConditionBuilder (cognitive 27) · ×1
  • ConditionBuilder.ConditionBuilder (cognitive 27) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47 — ConditionBuilder.ConditionBuilder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 7, ternaries 6 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 63, 90, 98, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · useActivitiesSearch.useActivitiesSearch.handleGetResults (cognitive 27) · ×1
  • useActivitiesSearch.useActivitiesSearch.handleGetResults (cognitive 27) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107 — useActivitiesSearch.useActivitiesSearch.handleGetResults has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · reducer.graphReducer (cognitive 27) · ×1
  • reducer.graphReducer (cognitive 27) designer/client/src/reducers/graph/reducer.ts:170 — reducer.graphReducer has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 9 (20 pts), boolean chains 4, if/else 1 (2 pts), match/switch 1 (nesting depth added 12). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 376, 280, 361, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · NumberUtils.convertNumberToTargetClass (cognitive 26) · ×1
  • NumberUtils.convertNumberToTargetClass (cognitive 26) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:87 — NumberUtils.convertNumberToTargetClass has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DataMapper.DataMapper (cognitive 26) · ×1
  • DataMapper.DataMapper (cognitive 26) designer/client/src/components/dataMapper/DataMapper.tsx:68 — DataMapper.DataMapper has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, ternaries 8, if/else 4. Of this number, 13 points are the body's own statements and 13 belong to 7 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.
D2 · Cognitive Complexity · TableEditor.Table (cognitive 26) · ×1
  • TableEditor.Table (cognitive 26) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119 — TableEditor.Table has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (19 pts), boolean chains 4, if/else 2, match/switch 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · DeploymentService.runDeployment (cognitive 25) · ×1
  • DeploymentService.runDeployment (cognitive 25) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/DeploymentService.scala:80 — DeploymentService.runDeployment has cognitive complexity 25 (threshold 15). Drivers by points: loops 7 (25 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SpelExpressionBuilder.resolveSpelPath (cognitive 25) · ×1
  • SpelExpressionBuilder.resolveSpelPath (cognitive 25) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:47 — SpelExpressionBuilder.resolveSpelPath has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 1 (3 pts), boolean chains 2, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeploymentService.runDeploymentOrRedeploy (cognitive 24) · ×1
  • DeploymentService.runDeploymentOrRedeploy (cognitive 24) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:97 — DeploymentService.runDeploymentOrRedeploy has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (14 pts), match/switch 5 (10 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · DistributedLeadership.stop (cognitive 23) · ×1
  • DistributedLeadership.stop (cognitive 23) designer/server/src/main/scala/pl/touk/nussknacker/ui/ha/Leadership.scala:208 — DistributedLeadership.stop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FlinkProcessRegistrar.register (cognitive 23) · ×1
  • FlinkProcessRegistrar.register (cognitive 23) engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103 — FlinkProcessRegistrar.register has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 10 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · K8sDeploymentManager.cancelScenario (cognitive 23) · ×1
  • K8sDeploymentManager.cancelScenario (cognitive 23) engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/K8sDeploymentManager.scala:293 — K8sDeploymentManager.cancelScenario has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 2 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · collapsibleSwitchList.CollapsibleSwitchList (cognitive 22) · ×1
  • collapsibleSwitchList.CollapsibleSwitchList (cognitive 22) designer/client/src/containers/settings/collapsibleSwitchList.tsx:66 — collapsibleSwitchList.CollapsibleSwitchList has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (16 pts), boolean chains 5, loops 1 (nesting depth added 5). None of this is in the body itself: all 22 points belong to 3 function items inside it that branch (a function literal at line 105, flattenPath, a function literal at line 100). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · alignCells.alignCells (cognitive 22) · ×1
  • alignCells.alignCells (cognitive 22) designer/client/src/components/graph/alignCells.tsx:16 — alignCells.alignCells has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 3 (5 pts), boolean chains 1 (nesting depth added 10). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 41, 34). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cognitive 21) · ×1
  • AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cognitive 21) components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala:151 — AssignabilityDeterminer.isSingleTypeMatchesTargetObjType has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 7 (10 pts), boolean chains 7, if/else 4 (nesting depth added 3). 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.
D2 · Cognitive Complexity · QuestDbFEStatisticsRepository.createRepositoryResource (cognitive 21) · ×1
  • QuestDbFEStatisticsRepository.createRepositoryResource (cognitive 21) designer/server/src/main/scala/pl/touk/nussknacker/ui/db/timeseries/questdb/QuestDbFEStatisticsRepository.scala:179 — QuestDbFEStatisticsRepository.createRepositoryResource has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · PeriodicProcessService.deploy (cognitive 21) · ×1
  • PeriodicProcessService.deploy (cognitive 21) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:438 — PeriodicProcessService.deploy has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · NkGlobalParametersToMapEncoder.decode (cognitive 21) · ×1
  • NkGlobalParametersToMapEncoder.decode (cognitive 21) engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/NkGlobalParameters.scala:97 — NkGlobalParametersToMapEncoder.decode has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (21 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Projection.getValueRef (cognitive 21) · ×1
  • Projection.getValueRef (cognitive 21) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Projection.java:62 — Projection.getValueRef has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 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.
D2 · Cognitive Complexity · SelectionContextProvider.SelectionContextProvider (cognitive 21) · ×1
  • SelectionContextProvider.SelectionContextProvider (cognitive 21) designer/client/src/components/graph/SelectionContextProvider.tsx:137 — SelectionContextProvider.SelectionContextProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 2 (4 pts), error handling 1 (nesting depth added 3). None of this is in the body itself: all 21 points belong to 6 function literals inside it that branch (lines 231, 153, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ParametersUtils.migrateKafkaParams (cognitive 21) · ×1
  • ParametersUtils.migrateKafkaParams (cognitive 21) designer/client/src/components/graph/node-modal/ParametersUtils.ts:137 — ParametersUtils.migrateKafkaParams has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 5 (nesting depth added 9). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 155, 140, 174). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · AceEditorJsonBasedSnippets.getEditorContext (cognitive 21) · ×1
  • AceEditorJsonBasedSnippets.getEditorContext (cognitive 21) designer/client/src/components/graph/node-modal/editors/expression/AceEditorJsonBasedSnippets.ts:77 — AceEditorJsonBasedSnippets.getEditorContext has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useDataMapper.useDataMapper (cognitive 21) · ×1
  • useDataMapper.useDataMapper (cognitive 21) designer/client/src/components/dataMapper/useDataMapper.ts:139 — useDataMapper.useDataMapper has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 5). None of this is in the body itself: all 21 points belong to 6 function literals inside it that branch (lines 153, 552, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · extendActivitiesWithUIData.extendActivitiesWithUIData (cognitive 21) · ×1
  • extendActivitiesWithUIData.extendActivitiesWithUIData (cognitive 21) designer/client/src/components/toolbars/activities/helpers/extendActivitiesWithUIData.ts:37 — extendActivitiesWithUIData.extendActivitiesWithUIData has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, loops 1 (nesting depth added 4). None of this is in the body itself: all 21 points belong to 4 function items inside it that branch (recursiveDateLabelDesignation, recursiveToggleItemsButtonDesignation, initiallyHideItems, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · UIProcessValidator.resolveNodeNamesForResult (cognitive 20) · ×1
  • UIProcessValidator.resolveNodeNamesForResult (cognitive 20) designer/server/src/main/scala/pl/touk/nussknacker/ui/validation/UIProcessValidator.scala:240 — UIProcessValidator.resolveNodeNamesForResult has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (14 pts), match/switch 2 (4 pts), if/else 2 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Ops.waitForJobState (cognitive 20) · ×1
  • Ops.waitForJobState (cognitive 20) engine/flink/minicluster/src/main/scala/pl/touk/nussknacker/engine/flink/minicluster/MiniClusterJobStatusCheckingOps.scala:104 — Ops.waitForJobState has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · NumberUtils.parseNumber (cognitive 20) · ×1
  • NumberUtils.parseNumber (cognitive 20) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:210 — NumberUtils.parseNumber has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 9, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · use-register-tracking-events.useRegisterTrackingEvents (cognitive 20) · ×1
  • use-register-tracking-events.useRegisterTrackingEvents (cognitive 20) designer/client/src/containers/event-tracking/use-register-tracking-events.ts:136 — use-register-tracking-events.useRegisterTrackingEvents has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2, ternaries 1 (nesting depth added 10). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (a function literal at line 142, a function literal at line 171, isEnabledForStatisticsEvent). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ParametersUtils.flattenSpelRecord (cognitive 20) · ×1
  • ParametersUtils.flattenSpelRecord (cognitive 20) designer/client/src/components/graph/node-modal/ParametersUtils.ts:60 — ParametersUtils.flattenSpelRecord has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useDataMapper.useDataMapper.validateExpression (cognitive 20) · ×1
  • useDataMapper.useDataMapper.validateExpression (cognitive 20) designer/client/src/components/dataMapper/useDataMapper.ts:289 — useDataMapper.useDataMapper.validateExpression has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 8). Of this number, 16 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 · useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cognitive 20) · ×1
  • useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cognitive 20) designer/client/src/components/dataMapper/useDataMapper.ts:438 — useDataMapper.useDataMapper.defaultFetchTopicDefinitions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, ternaries 2, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 477, 452, 444, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ProcessUtils._findVariablesDefinedInProcess (cognitive 20) · ×1
  • ProcessUtils._findVariablesDefinedInProcess (cognitive 20) designer/client/src/common/ProcessUtils.ts:143 — ProcessUtils._findVariablesDefinedInProcess has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 3 (6 pts), boolean chains 3, loops 1 (3 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExpressionCompiler.compileNodeParameters (cognitive 19) · ×1
  • ExpressionCompiler.compileNodeParameters (cognitive 19) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/ExpressionCompiler.scala:175 — ExpressionCompiler.compileNodeParameters has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (9 pts), match/switch 6, boolean chains 4 (nesting depth added 4). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cognitive 19) · ×1
  • DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cognitive 19) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/dict/DictKeyParameterAdapter.scala:64 — DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 7 (11 pts), if/else 5 (8 pts) (nesting depth added 7). 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.
D2 · Cognitive Complexity · reducer.reducer (cognitive 19) · ×1
  • reducer.reducer (cognitive 19) designer/client/src/components/graph/node-modal/editors/expression/Table/state/reducer.ts:6 — reducer.reducer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (7 pts), boolean chains 1, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 15, 35, 35, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · drawText.tokenizeDataRecords · ×1
  • drawText.tokenizeDataRecords::walk (cognitive 19) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70 — drawText.tokenizeDataRecords::walk has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeploymentsStatusesSynchronizer.synchronizeAll (cognitive 18) · ×1
  • DeploymentsStatusesSynchronizer.synchronizeAll (cognitive 18) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/synchronize/DeploymentsStatusesSynchronizer.scala:22 — DeploymentsStatusesSynchronizer.synchronizeAll has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (9 pts), match/switch 3 (9 pts) (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.
D2 · Cognitive Complexity · CaseClassTypeInfo.getTypeAt (cognitive 18) · ×1
  • CaseClassTypeInfo.getTypeAt (cognitive 18) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:167 — CaseClassTypeInfo.getTypeAt has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NuSpelExpressionParser.skipToCorrectEndSuffix (cognitive 18) · ×1
  • NuSpelExpressionParser.skipToCorrectEndSuffix (cognitive 18) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:190 — NuSpelExpressionParser.skipToCorrectEndSuffix has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 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.
D2 · Cognitive Complexity · ToolbarWrapper.ToolbarWrapper (cognitive 18) · ×1
  • ToolbarWrapper.ToolbarWrapper (cognitive 18) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33 — ToolbarWrapper.ToolbarWrapper has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 13, ternaries 3 (5 pts) (nesting depth added 2). Of this number, 15 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · spelUtils.parseConditionAst (cognitive 18) · ×1
  • spelUtils.parseConditionAst (cognitive 18) designer/client/src/components/conditionBuilder/spelUtils.ts:64 — spelUtils.parseConditionAst has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, ternaries 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · DeployButton.DeployButton (cognitive 18) · ×1
  • DeployButton.DeployButton (cognitive 18) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33 — DeployButton.DeployButton has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (6 pts), ternaries 4 (6 pts), boolean chains 4, match/switch 2 (nesting depth added 3). Of this number, 9 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · RedeployButton.RedeployButton (cognitive 18) · ×1
  • RedeployButton.RedeployButton (cognitive 18) designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33 — RedeployButton.RedeployButton has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (6 pts), ternaries 4 (6 pts), boolean chains 4, match/switch 2 (nesting depth added 3). Of this number, 9 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · AddProcessDialog.AddProcessDialog (cognitive 18) · ×1
  • AddProcessDialog.AddProcessDialog (cognitive 18) designer/client/src/components/AddProcessDialog.tsx:25 — AddProcessDialog.AddProcessDialog has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 4, error handling 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 71, a function literal at line 109, a function literal at line 64, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · LiveDataThroughputs.LiveDataThroughputs (cognitive 18) · ×1
  • LiveDataThroughputs.LiveDataThroughputs (cognitive 18) designer/client/src/containers/liveData/LiveDataThroughputs.tsx:16 — LiveDataThroughputs.LiveDataThroughputs has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 2, match/switch 1. Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 37, 80, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · DbScenarioActivityRepository.doModifyActivity (cognitive 17) · ×1
  • DbScenarioActivityRepository.doModifyActivity (cognitive 17) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:388 — DbScenarioActivityRepository.doModifyActivity has cognitive complexity 17 (threshold 15). Drivers by points: loops 6 (15 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cognitive 17) · ×1
  • JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cognitive 17) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonTemplateFromJsonSchemaDeterminer.scala:39 — JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 6 (15 pts), if/else 2 (nesting depth added 9). 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.
D2 · Cognitive Complexity · CustomCompleterAceEditor.CustomCompleterAceEditor (cognitive 17) · ×1
  • CustomCompleterAceEditor.CustomCompleterAceEditor (cognitive 17) designer/client/src/components/graph/node-modal/editors/expression/CustomCompleterAceEditor.tsx:49 — CustomCompleterAceEditor.CustomCompleterAceEditor has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 72, 85, 63, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · useDataMapper.useDataMapper.enrichedContext (cognitive 17) · ×1
  • useDataMapper.useDataMapper.enrichedContext (cognitive 17) designer/client/src/components/dataMapper/useDataMapper.ts:197 — useDataMapper.useDataMapper.enrichedContext has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), ternaries 1 (2 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.
D2 · Cognitive Complexity · SpelExpressionBuilder.SpelExpressionBuilder (cognitive 17) · ×1
  • SpelExpressionBuilder.SpelExpressionBuilder (cognitive 17) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83 — SpelExpressionBuilder.SpelExpressionBuilder has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, ternaries 5 (6 pts), if/else 2 (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · EdgesDndComponent.EdgesDndComponent (cognitive 17) · ×1
  • EdgesDndComponent.EdgesDndComponent (cognitive 17) designer/client/src/components/graph/node-modal/EdgesDndComponent.tsx:59 — EdgesDndComponent.EdgesDndComponent has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 3, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 105, 139, 137, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · use-mouse-sensor.useMouseSensor (cognitive 17) · ×1
  • use-mouse-sensor.useMouseSensor (cognitive 17) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:211 — use-mouse-sensor.useMouseSensor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, boolean chains 1. None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 220, 292, 335, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · NameValueListEditor.NameValueListEditor (cognitive 17) · ×1
  • NameValueListEditor.NameValueListEditor (cognitive 17) designer/client/src/components/graph/node-modal/editors/expression/NameValueList/NameValueListEditor.tsx:43 — NameValueListEditor.NameValueListEditor has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 5, ternaries 3. Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 62, 131, 56, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ScenarioStatusProvider.getScenarioStatus (cognitive 16) · ×1
  • ScenarioStatusProvider.getScenarioStatus (cognitive 16) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/scenariostatus/ScenarioStatusProvider.scala:199 — ScenarioStatusProvider.getScenarioStatus has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 7 (nesting depth added 6). 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.
D2 · Cognitive Complexity · OptionTypeComparator.compareSerialized (cognitive 16) · ×1
  • OptionTypeComparator.compareSerialized (cognitive 16) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/option/OptionTypeComparator.scala:59 — OptionTypeComparator.compareSerialized has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NuSpelExpressionParser.parseExpressions (cognitive 16) · ×1
  • NuSpelExpressionParser.parseExpressions (cognitive 16) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:111 — NuSpelExpressionParser.parseExpressions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 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.
D2 · Cognitive Complexity · SpelReflectionHelper.convertArguments (cognitive 16) · ×1
  • SpelReflectionHelper.convertArguments (cognitive 16) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:52 — SpelReflectionHelper.convertArguments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ButtonMenu.ButtonMenu (cognitive 16) · ×1
  • ButtonMenu.ButtonMenu (cognitive 16) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonMenu.tsx:34 — ButtonMenu.ButtonMenu has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 2, boolean chains 1 (nesting depth added 3). 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: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · RawDisplay.useBoundedSelection (cognitive 16) · ×1
  • RawDisplay.useBoundedSelection (cognitive 16) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx:7 — RawDisplay.useBoundedSelection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, error handling 1. None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 43, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · dataMapperUtils.expandDottedKeys (cognitive 16) · ×1
  • dataMapperUtils.expandDottedKeys (cognitive 16) designer/client/src/components/dataMapper/dataMapperUtils.ts:302 — dataMapperUtils.expandDottedKeys has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · dataMapperUtils.parseSpelToFields (cognitive 16) · ×1
  • dataMapperUtils.parseSpelToFields (cognitive 16) designer/client/src/components/dataMapper/dataMapperUtils.ts:378 — dataMapperUtils.parseSpelToFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useDataMapper.useDataMapper.handleAutoMap (cognitive 16) · ×1
  • useDataMapper.useDataMapper.handleAutoMap (cognitive 16) designer/client/src/components/dataMapper/useDataMapper.ts:328 — useDataMapper.useDataMapper.handleAutoMap has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 5 (6 pts), boolean chains 3 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 4 function items inside it that branch (traverse, a function literal at line 353, a function literal at line 332, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · EdgeFields.EdgeFields (cognitive 16) · ×1
  • EdgeFields.EdgeFields (cognitive 16) designer/client/src/components/graph/node-modal/EdgeFields.tsx:39 — EdgeFields.EdgeFields has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6 (7 pts), if/else 2 (nesting depth added 1). Of this number, 9 points are the body's own statements and 7 belong to 4 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.
D2 · Cognitive Complexity · ToolbarsContainer.ToolbarsContainer (cognitive 16) · ×1
  • ToolbarsContainer.ToolbarsContainer (cognitive 16) designer/client/src/components/toolbarComponents/ToolbarsContainer.tsx:133 — ToolbarsContainer.ToolbarsContainer has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 3. 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 literals inside it that branch (lines 145, 193, 200, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · InputOutputLayout.InputOutputLayout (cognitive 16) · ×1
  • InputOutputLayout.InputOutputLayout (cognitive 16) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38 — InputOutputLayout.InputOutputLayout has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11, if/else 5. Of this number, 8 points are the body's own statements and 8 belong to 6 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.
D2 · Cognitive Complexity · InitializeChatStream.initializeChatStream (cognitive 16) · ×1
  • InitializeChatStream.initializeChatStream (cognitive 16) designer/client/src/components/aiAssistant/InitializeChatStream.ts:74 — InitializeChatStream.initializeChatStream has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (3 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 4). Of this number, 15 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86 — components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86-99 | components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:111-124 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:211 — components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:211-230 | components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:251-270 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:252 — utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:252-270 | utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:299-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:252` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:251` calls `DefinedEagerParameter` and `utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:298` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/ScenarioActionRepository.scala:269 — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/ScenarioActionRepository.scala:269-285 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/ScenarioActionRepository.scala:553-570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/ScenarioActionRepository.scala:269` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:111 — designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:111-126 | designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:158-173 | designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:204-219 — 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.
D4 · Code Duplication · Duplicated block (11–16 lines × 2) · ×1
  • Duplicated block (11–16 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:119 — utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:119-134 | utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:140-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:119` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:34 — engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:34-44 | engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala:30-42 — before extracting anything, compare `engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala` and `engine/lite/components/base/src/main/scala/pl/touk/nussknacker/engine/lite/components/Union.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:175 — designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:175-186 | designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:195-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:160 — designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:160-169 | designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:352-363 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/CustomTimestampExtractingTransformationCopy.scala:17 — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/CustomTimestampExtractingTransformationCopy.scala:17-27 | engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:470-481 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/CustomTimestampExtractingTransformationCopy.scala:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • Duplicated block (8–11 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:289 — designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:289-296 | designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:347-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/DefaultConfigCreator.scala:14 — defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/DefaultConfigCreator.scala:14-23 | engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/DevProcessConfigCreator.scala:234-241 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/DefaultConfigCreator.scala:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:89 — components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:89-94 | components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:114-119 | components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:143-148 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:89` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:79 — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:79-83 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:100-104 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:124-128 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) designer/server/src/main/scala/db/migration/V1_061__PeriodicDeploymentManagerTablesDefinition.scala:64 — designer/server/src/main/scala/db/migration/V1_061__PeriodicDeploymentManagerTablesDefinition.scala:64-76 | designer/server/src/main/scala/pl/touk/nussknacker/ui/db/entity/PeriodicProcessDeploymentsTable.scala:48-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) engine/lite/embeddedDeploymentManager/src/main/scala/pl/touk/nussknacker/engine/embedded/EmbeddedRequestResponseScenarioValidator.scala:16 — engine/lite/embeddedDeploymentManager/src/main/scala/pl/touk/nussknacker/engine/embedded/EmbeddedRequestResponseScenarioValidator.scala:16-26 | engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/RequestResponseScenarioValidator.scala:17-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/GroupByMigration.scala:15 — defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/GroupByMigration.scala:15-20 | designer/server/src/main/scala/pl/touk/nussknacker/ui/process/migrate/GroupByMigration.scala:15-20 — before extracting anything, compare `defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/GroupByMigration.scala` and `designer/server/src/main/scala/pl/touk/nussknacker/ui/process/migrate/GroupByMigration.scala` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/GroupByMigration.scala:15` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:430 — engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:430-437 | engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:452-460 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:430` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D5 · Coupling · Unstable project flinkDeploymentManager · ×1
  • Unstable project flinkDeploymentManager — flinkDeploymentManager has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project flinkExecutor · ×1
  • Unstable project flinkExecutor — flinkExecutor has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project flinkKafkaComponentsUtils · ×1
  • Unstable project flinkKafkaComponentsUtils — flinkKafkaComponentsUtils has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project liteRequestResponseComponents · ×1
  • Unstable project liteRequestResponseComponents — liteRequestResponseComponents has instability 0.83 with 1 dependents.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: liveDataCollector — liveDataCollector: abstractness 0.04, instability 0.25, distance 0.71 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 162 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience designer/client/src/api.ts:7 — `axios.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (19 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (19 clone groups) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164 — 19 duplicated blocks under designer/client/src/components/ have copies in at least two of the sibling directories conditionBuilder, dataMapper, graph, modals, spelExpressionBuilder, tips (+1 more sibling(s) not listed) — 16 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (13 clone groups) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx:58 — 13 duplicated blocks under designer/client/src/components/toolbars/ have copies in at least two of the sibling directories creator, edit, process, scenarioActions, search, view — 3 of them are reported below, and 10 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (10 clone groups) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 — 10 duplicated blocks under designer/submodules/packages/components/src/ have copies in at least two of the sibling directories common, components, scenarios — 8 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (7 clone groups) designer/client/configs/simpleScriptPlugin.ts:8 — 7 duplicated blocks under designer/ have copies in at least two of the sibling directories client, submodules — 6 of them are reported below, and 1 is 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (6 clone groups) designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62 — 6 duplicated blocks under designer/client/src/components/graph/node-modal/ have copies in at least two of the sibling directories aggregate, editors, fragment-input-definition, node, node-action-buttons — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (111 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (111 matched lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113 — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113 · designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:142 — the two spans are one implementation copied and then locally edited — 543 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 (109 lines × 2 locations) · ×1
  • Duplicated block (109 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83 — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:81 — 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 (105 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (105 matched lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164 — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164 · designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:151 — the two spans are one implementation copied and then locally edited — 632 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 (75 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (75 matched lines × 2 locations) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:23 — the two spans are one implementation copied and then locally edited — 555 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 (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32 — designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32 · designer/client/src/components/graph/node-modal/editors/expression/Duration/PeriodEditor.tsx:28 — the two spans are one implementation copied and then locally edited — 320 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 (50 lines × 2 locations) · ×1
  • Duplicated block (50 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/FixedListVariant.tsx:15 — 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 (49 lines × 2 locations) · ×1
  • Duplicated block (49 lines × 2 locations) designer/client/configs/simpleScriptPlugin.ts:8 — designer/client/configs/simpleScriptPlugin.ts:8 · designer/submodules/configs/webpack/simpleScriptPlugin.ts:8 — 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 (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63 — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:63 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts:263 — designer/client/src/http/HttpService/HttpService.ts:263 · designer/client/src/http/HttpService/HttpService.ts:311 — 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 (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25 — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:25 — 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 (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) designer/client/src/components/notifications/copyTooltip.tsx:15 — designer/client/src/components/notifications/copyTooltip.tsx:15 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14 — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 — the two spans are one implementation copied and then locally edited — 226 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 (37 lines × 2 locations) · ×1
  • Duplicated block (37 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts:927 — designer/client/src/http/HttpService/HttpService.ts:927 · designer/client/src/http/HttpService/HttpService.ts:1075 — 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 (34 lines × 2 locations) · ×1
  • Duplicated block (34 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159 — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:149 — 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 (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35 — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:27 — 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 (24 lines × 3 locations) · ×1
  • Duplicated block (24 lines × 3 locations) designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60 — designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:126 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:150 — all 3 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 (22 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (22 matched lines × 2 locations) designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6 — designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:123 — the two spans are one implementation copied and then locally edited — 216 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 (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45 — designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45 · designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5 — designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:7 — 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 (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) designer/client/configs/withModuleFederationPlugins.ts:64 — designer/client/configs/withModuleFederationPlugins.ts:64 · designer/submodules/configs/webpack/withModuleFederationPlugins.ts:119 — 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 (19 lines × 3 locations) · ×1
  • Duplicated block (19 lines × 3 locations) designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78 — designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78 · designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:146 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:144 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99 — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:99 — 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 (17 lines × 4 locations) · ×1
  • Duplicated block (17 lines × 4 locations) designer/client/src/components/graph/node-modal/DescriptionField.tsx:23 — designer/client/src/components/graph/node-modal/DescriptionField.tsx:23 · designer/client/src/components/graph/node-modal/DisableField.tsx:22 · designer/client/src/components/graph/node-modal/sink.tsx:21 · designer/client/src/components/graph/node-modal/source.tsx:20 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function FieldRow (cyclomatic 40, cognitive 35) · ×1
  • Complex function FieldRow (cyclomatic 40, cognitive 35) designer/client/src/components/dataMapper/FieldRow.tsx:90 — FieldRow has cyclomatic complexity 40 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ContextTreeNode (cyclomatic 36, cognitive 35) · ×1
  • Complex function ContextTreeNode (cyclomatic 36, cognitive 35) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50 — ContextTreeNode has cyclomatic complexity 36 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 26, cognitive 75) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 75) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141 — (anonymous) has cyclomatic complexity 26 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 24) designer/client/src/components/dataMapper/useDataMapper.ts:197 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 20) designer/client/src/common/ProcessUtils.ts:148 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function DataMapper (cyclomatic 19, cognitive 17) · ×1
  • Complex function DataMapper (cyclomatic 19, cognitive 17) designer/client/src/components/dataMapper/DataMapper.tsx:68 — DataMapper has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ToolbarWrapper (cyclomatic 19, cognitive 16) · ×1
  • Complex function ToolbarWrapper (cyclomatic 19, cognitive 16) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33 — ToolbarWrapper has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildFragmentsForTokens (cyclomatic 18, cognitive 43) · ×1
  • Complex function buildFragmentsForTokens (cyclomatic 18, cognitive 43) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120 — buildFragmentsForTokens has cyclomatic complexity 18 and cognitive complexity 43; 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 parseConditionAst (cyclomatic 17, cognitive 18) · ×1
  • Complex function parseConditionAst (cyclomatic 17, cognitive 18) designer/client/src/components/conditionBuilder/spelUtils.ts:64 — parseConditionAst has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function typingResultToSample (cyclomatic 17, cognitive 16) · ×1
  • Complex function typingResultToSample (cyclomatic 17, cognitive 16) designer/client/src/components/builderComponents/typeUtils.ts:12 — typingResultToSample has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function VariantWrapper (cyclomatic 17, cognitive 16) · ×1
  • Complex function VariantWrapper (cyclomatic 17, cognitive 16) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12 — VariantWrapper has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 28) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 28) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function adjustEdges (cyclomatic 16, cognitive 25) · ×1
  • Complex function adjustEdges (cyclomatic 16, cognitive 25) REDACTED:50 — adjustEdges has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 19) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 19) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function refClazzToValue (cyclomatic 16, cognitive 14) · ×1
  • Complex function refClazzToValue (cyclomatic 16, cognitive 14) designer/client/src/components/graph/node-modal/Variable.tsx:42 — refClazzToValue has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · designer/client/src/http/HttpService/HttpService.ts · ×1
  • designer/client/src/http/HttpService/HttpService.ts: 1226 lines of code designer/client/src/http/HttpService/HttpService.ts:1 — designer/client/src/http/HttpService/HttpService.ts has 1226 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 · designer/client/src/components/graph/Graph.tsx · ×1
  • designer/client/src/components/graph/Graph.tsx: 743 lines of code designer/client/src/components/graph/Graph.tsx:1 — designer/client/src/components/graph/Graph.tsx has 743 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 · designer/client/src/components/dataMapper/useDataMapper.ts · ×1
  • designer/client/src/components/dataMapper/useDataMapper.ts: 589 lines of code designer/client/src/components/dataMapper/useDataMapper.ts:1 — designer/client/src/components/dataMapper/useDataMapper.ts has 589 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 · designer/client/src/components/modals/CompareVersionsDialog.tsx · ×1
  • designer/client/src/components/modals/CompareVersionsDialog.tsx: 569 lines of code designer/client/src/components/modals/CompareVersionsDialog.tsx:1 — designer/client/src/components/modals/CompareVersionsDialog.tsx has 569 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 · designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx · ×1
  • designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx: 530 lines of code designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:1 — designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx has 530 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 · designer/client/src/reducers/graph/reducer.ts · ×1
  • designer/client/src/reducers/graph/reducer.ts: 501 lines of code designer/client/src/reducers/graph/reducer.ts:1 — designer/client/src/reducers/graph/reducer.ts has 501 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 · designer/client/src/components/dataMapper/FieldRow.tsx · ×1
  • designer/client/src/components/dataMapper/FieldRow.tsx: 467 lines of code designer/client/src/components/dataMapper/FieldRow.tsx:1 — designer/client/src/components/dataMapper/FieldRow.tsx has 467 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 · designer/client/src/components/dataMapper/dataMapperUtils.ts · ×1
  • designer/client/src/components/dataMapper/dataMapperUtils.ts: 452 lines of code designer/client/src/components/dataMapper/dataMapperUtils.ts:1 — designer/client/src/components/dataMapper/dataMapperUtils.ts has 452 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 · designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts · ×1
  • designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts: 434 lines of code designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1 — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts has 434 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 · designer/client/src/components/dataMapper/DataMapper.tsx · ×1
  • designer/client/src/components/dataMapper/DataMapper.tsx: 417 lines of code designer/client/src/components/dataMapper/DataMapper.tsx:1 — designer/client/src/components/dataMapper/DataMapper.tsx has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 158 outdated package(s); JS/npm CVEs scored in D30
R7 · Dead Code · Dead file (~436 LoC) · ×1
  • Dead file (~436 LoC) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/scenarioDetails/ScenarioDetails.tsx, designer/client/src/components/toolbars/scenarioDetails/ScenarioStatusContent.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~260 LoC) · ×1
  • Dead file (~260 LoC) designer/client/src/components/toolbars/search/utils.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchResults.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~252 LoC) · ×1
  • Dead file (~252 LoC) designer/client/src/containers/Visualization.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~197 LoC) · ×1
  • Dead file (~197 LoC) designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/Toolbars.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~172 LoC) · ×1
  • Dead file (~172 LoC) designer/client/src/components/toolbars/creator/CreatorPanel.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbarSettings/getToolbarComponent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~161 LoC) · ×1
  • Dead file (~161 LoC) designer/client/src/windowManager/ContentGetter.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/WindowManager.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~160 LoC) · ×1
  • Dead file (~160 LoC) designer/client/src/components/common/DropdownButton.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CountsStyled.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~156 LoC) · ×1
  • Dead file (~156 LoC) designer/client/src/components/AddProcessDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~140 LoC) · ×1
  • Dead file (~140 LoC) designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/search/SearchPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~137 LoC) · ×1
  • Dead file (~137 LoC) designer/client/src/containers/Auth/strategies/OAuth2Strategy.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Auth/strategies/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~127 LoC) · ×1
  • Dead file (~127 LoC) designer/client/src/components/graph/node-modal/node/DescriptionDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~126 LoC) · ×1
  • Dead file (~126 LoC) designer/client/src/components/aiAssistant/components/Composer.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/components/AiAssistantModal.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~122 LoC) · ×1
  • Dead file (~122 LoC) designer/client/src/components/modals/CalculateCounts/RefreshSelectButton.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~121 LoC) · ×1
  • Dead file (~121 LoC) designer/client/src/components/modals/MoreScenarioDetailsDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~117 LoC) · ×1
  • Dead file (~117 LoC) designer/client/src/components/modals/DeployWithParameters/AdvancedParameters.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~110 LoC) · ×1
  • Dead file (~110 LoC) designer/client/src/components/aiAssistant/ModelAdapter.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/AiAssistantProvider.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~109 LoC) · ×1
  • Dead file (~109 LoC) designer/client/src/components/aiAssistant/tools/ScenarioDataAIToolkit.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~108 LoC) · ×1
  • Dead file (~108 LoC) designer/client/src/containers/liveData/animationHelpers.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/liveData/LiveDataThroughputs.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~105 LoC) · ×1
  • Dead file (~105 LoC) designer/client/src/components/toolbars/search/SearchResults.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchPanel.tsx, designer/client/src/components/toolbars/search/utils.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~102 LoC) · ×1
  • Dead file (~102 LoC) designer/client/src/containers/settings/SettingsView.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/CommandBar/settings/useRegisterSettingsCommands.tsx, designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~93 LoC) · ×1
  • Dead file (~93 LoC) designer/client/src/components/modals/CalculateCounts/CalculateCountsDialog.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx, designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~91 LoC) · ×1
  • Dead file (~91 LoC) designer/client/configs/withModuleFederationPlugins.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~90 LoC) · ×1
  • Dead file (~90 LoC) designer/client/src/components/aiAssistant/messageHelpers.ts — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/InitializeChatStream.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~87 LoC) · ×1
  • Dead file (~87 LoC) designer/client/src/containers/AddComponentsButtons.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~84 LoC) · ×1
  • Dead file (~84 LoC) designer/client/src/components/aiAssistant/components/AssistantMessage.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/components/AiAssistantModal.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~81 LoC) · ×1
  • Dead file (~81 LoC) designer/client/src/components/sidePanels/CollapsiblePanel.tsx — no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/sidePanels/CollapsibleScrollPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unlisted import '@emotion/serialize' · ×1
  • Unlisted import '@emotion/serialize' designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:1 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unlisted import '@mui/styled-engine' · ×1
  • Unlisted import '@mui/styled-engine' designer/client/src/components/graph/node-modal/io/PanelButton.tsx:2 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unlisted import 'assistant-stream' · ×1
  • Unlisted import 'assistant-stream' designer/client/src/components/aiAssistant/useCheckPermission.tsx:1 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unlisted import 'css-box-model' · ×1
  • Unlisted import 'css-box-model' designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:22 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unused dependency 'd3-transition' · ×1
  • Unused dependency 'd3-transition' — Declared in 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.
R8 · Dependency Hygiene · Unused dependency 'glob' · ×1
  • Unused dependency 'glob' — Declared in 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.
R8 · Dependency Hygiene · Unused dependency 'moment-duration-format' · ×1
  • Unused dependency 'moment-duration-format' — Declared in 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: read designer/submodules/packages/components/src/settings/i18n.ts:16 — `read` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Minor — 543 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×462
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/ActionService.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/definition/clazz/ClassDefinitionExtractor.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/internal/propertyAccessors.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file utils/math-utils/src/main/scala/pl/touk/nussknacker/engine/util/MathUtils.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ClassExtractionSettings.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/encode/JsonSchemaOutputValidator.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/DeploymentService.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/migrations/MigrationService.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/MigrationApiEndpoints.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/SwaggerTyped.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/StatisticsApiEndpoints.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/AppApiEndpoints.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/statistics/ScenarioStatistics.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/reconciliation/ScenarioDeploymentReconciler.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/BuiltInNodeCompiler.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/ParameterDeclaration.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/scenariostatus/ScenarioStatusProvider.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/batch/TableJoinComponent.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/FragmentResolver.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file utils/utils/src/main/java/org/springframework/util/NumberUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 437 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate designer/client/src/components/dataMapper/dataMapperUtils.ts:380 — `!trimmed.startsWith("{") || !trimmed.endsWith("}")` appears character-identically in 2 files — designer/client/src/components/dataMapper/dataMapperUtils.ts, designer/client/src/components/graph/node-modal/ParametersUtils.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 designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:25 — `(f === ScenariosFiltersModelType.SCENARIOS && !row.isFragment) || (f === ScenariosFiltersModelType.FRAGMENTS && row.isFragment)` appears character-identically in 2 files — designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx, designer/submodules/packages/components/src/scenarios/list/tablePart.tsx. 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 designer/client/src/components/dataMapper/dataMapperUtils.ts:353 — `ch === "," && braces === 0 && parens === 0 && brackets === 0` appears character-identically in 2 files — designer/client/src/components/dataMapper/dataMapperUtils.ts, designer/client/src/components/graph/node-modal/ParametersUtils.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 designer/submodules/packages/components/src/components/useComponentsQuery.tsx:31 — `createdAt && DateTime.fromISO(createdAt).toFormat("yyyy-MM-dd HH:mm:ss")` appears character-identically in 2 files — designer/submodules/packages/components/src/components/useComponentsQuery.tsx, designer/submodules/packages/components/src/scenarios/useScenariosQuery.tsx. 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 designer/client/src/containers/settings/SearchField.tsx:9 — `event.key.length === 1 && /^[a-zA-Z0-9]$/.test(event.key)` appears character-identically in 2 files — designer/client/src/containers/settings/SearchField.tsx, designer/submodules/packages/components/src/scenarios/filters/quickFilter.tsx. 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 designer/client/src/containers/settings/SearchField.tsx:8 — `event.shiftKey || event.altKey || event.ctrlKey || event.metaKey` appears character-identically in 2 files — designer/client/src/containers/settings/SearchField.tsx, designer/submodules/packages/components/src/scenarios/filters/quickFilter.tsx. 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 designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx:50 — `isParseable(expressionObj) || isEmpty(expressionObj.expression)` appears character-identically in 3 files — designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/TimeEditor.tsx. 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 designer/submodules/packages/components/src/components/useComponentsQuery.tsx:32 — `modificationDate && DateTime.fromISO(modificationDate).toFormat("yyyy-MM-dd HH:mm:ss")` appears character-identically in 2 files — designer/submodules/packages/components/src/components/useComponentsQuery.tsx, designer/submodules/packages/components/src/scenarios/useScenariosQuery.tsx. 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 designer/client/src/components/ValueDragPreview.tsx:83 — `monitor.isDragging() && monitor.getItemType() === DndTypes.VALUE` appears character-identically in 2 files — designer/client/src/components/ValueDragPreview.tsx, designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx. 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 designer/client/src/components/ComponentDragPreview.tsx:46 — `monitor.isOverTarget(id) && monitor.canDropOnTarget(id)` appears character-identically in 2 files — designer/client/src/components/ComponentDragPreview.tsx, designer/client/src/components/ValueDragPreview.tsx. 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 designer/client/src/components/builderComponents/typeUtils.ts:19 — `name.includes("List") || name.includes("Collection")` appears character-identically in 2 files — designer/client/src/components/builderComponents/typeUtils.ts, designer/client/src/components/graph/node-modal/Variable.tsx. 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 designer/client/configs/simpleScriptPlugin.ts:22 — `platform === "win32" && !!process.env.MSYSTEM` appears character-identically in 2 files — designer/client/configs/simpleScriptPlugin.ts, designer/submodules/configs/webpack/simpleScriptPlugin.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 designer/client/src/components/graph/node-modal/editors/expression/Cron/CronEditor.tsx:42 — `result == null || typeof result !== "string"` appears character-identically in 2 files — designer/client/src/components/graph/node-modal/editors/expression/Cron/CronEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/Duration/PeriodEditor.tsx. 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 designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DatepickerEditor.tsx:80 — `showValidation && !isEmpty(fieldErrors) && nodeInputWithError` appears character-identically in 2 files — designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DatepickerEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/JsonEditor.tsx. 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 designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:116 — `showValidation && !isValid && nodeInputWithError` appears character-identically in 3 files — designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/Duration/TimeRangeComponent.tsx, designer/client/src/components/graph/node-modal/editors/expression/NumericInput.tsx. 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 designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:98 — `showValidation && fieldErrors.length > 0` appears character-identically in 3 files — designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx, designer/client/src/components/graph/node-modal/endpointFieldWrapper.tsx, designer/client/src/components/graph/node-modal/webSocketUrlFieldWrapper.tsx. 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 designer/client/src/reducers/graph/testing.ts:34 — `testCaseResult.status !== "loaded" || testCaseResult.results.type !== "Completed"` appears character-identically in 2 files — designer/client/src/reducers/graph/testing.ts, designer/client/src/reducers/selectors/testing.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 designer/client/src/reducers/graph/testing.ts:28 — `testCaseResult?.status === "loaded" && testCaseResult.results.type === "Completed"` appears character-identically in 2 files — designer/client/src/reducers/graph/testing.ts, designer/client/src/reducers/selectors/testing.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 designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:29 — `tryParseOrNull(expressionObj.expression) && typeof tryParseOrNull(expressionObj.expression) === "object"` appears character-identically in 2 files — designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx, designer/client/src/components/graph/node-modal/editors/expression/SpelEditor.tsx. 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 designer/client/src/components/dataMapper/dataMapperUtils.ts:394 — `val.startsWith("{") && val.endsWith("}")` appears character-identically in 2 files — designer/client/src/components/dataMapper/dataMapperUtils.ts, designer/client/src/components/graph/node-modal/ParametersUtils.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 designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:56 — `validationResultPresent && !disabled && isPossible && capabilities.deploy` appears character-identically in 3 files — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx, designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx, designer/client/src/components/toolbars/scenarioActions/buttons/RunOffScheduleButton.tsx. 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 designer/client/src/components/builderComponents/ContextTreeNode.tsx:73 — `value !== null && typeof value === "object" && !Array.isArray(value)` appears character-identically in 2 files — designer/client/src/components/builderComponents/ContextTreeNode.tsx, designer/client/src/components/builderComponents/typeUtils.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 designer/client/src/components/CommandBar/ResultFlagItem.tsx:28 — `value === false || value === true || value === "default"` appears character-identically in 2 files — designer/client/src/components/CommandBar/ResultFlagItem.tsx, designer/client/src/containers/settings/SettingsView.tsx. 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 engine/flink/components-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/state/EvictableState.scala:114 — `latestEvictionTimeValue == null || time > latestEvictionTimeValue` appears character-identically in 2 files — engine/flink/components-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/state/EvictableState.scala, engine/flink/components/base-unbounded/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/aggregate/AggregatorFunction.scala. 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 engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/ToTableTypeEncoder.scala:44 — `m.getName == "get" || m.getName == "getField"` appears character-identically in 2 files — engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/ToTableTypeEncoder.scala, scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/internal/propertyAccessors.scala. 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.
D30 · Dependency Vulnerabilities · Low CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×9
  • Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:261 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:399 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:79 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:119 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/process/processingtype/ScenarioParametersServiceTest.scala:271 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test engine/flink/management/src/it/scala/pl/touk/nussknacker/engine/management/streaming/BaseFlinkDeploymentManagerSpec.scala:242 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test engine/flink/tests/src/test/scala/pl/touk/nussknacker/defaultmodel/StateCompatibilityTest.scala:126 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test scenario-compiler/src/test/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSpec.scala:2792 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test security/src/test/scala/pl/touk/nussknacker/ui/security/api/SecurityApiSpec.scala:51 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx, designer/client/src/components/graph/SelectionContextProvider.tsx, designer/client/src/containers/settings/collapsibleSwitchList.tsx, designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx, designer/client/src/components/toolbars/creator/CreatorPanel.tsx, designer/client/src/containers/liveData/LiveDataThroughputs.tsx, designer/client/src/components/graph/node-modal/aggregate/aggregateContext.tsx, designer/client/src/components/aiAssistant/InitializeChatStream.ts (+8 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 15 significant file(s) lose their only recent owner: designer/client/src/components/modals/TestingDataRecords/drawText.ts, designer/client/src/containers/theme/styles.ts, designer/client/src/components/toolbars/testCases/definitions.tsx, designer/client/src/reducers/graph/testing.ts, designer/client/src/components/graph/node-modal/editors/expression/AceEditorJsonBasedSnippets.ts, designer/client/src/components/toolbars/testCases/results.tsx, designer/client/src/components/toolbars/testCases/testCase.tsx, designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/MockResponse.tsx (+7 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala, engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/sql/FlinkSqlQueryComponentFactory.scala, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/MergeRuleResolver.scala, engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/sql/QueryContextSchema.scala. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/scenariotesting/DataRecordsSource.scala, engine/flink/components-utils/src/main/scala/pl/touk/nussknacker/engine/flink/watermarkstrategy/FlinkWatermarkStrategyRuntimeHandler.scala, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala. Pair on, review, or document these before any departure.
M4 · Documentation accuracy · README/code drift · ×4
  • README/code drift README.md:61 — README.md links to `./docs/NuHighLevelView.png`, but `docs/NuHighLevelView.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING/README.md:58 — CONTRIBUTING/README.md links to `docs/installation_configuration_guide/README.md`, but `CONTRIBUTING/docs/installation_configuration_guide/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING/README.md:205 — CONTRIBUTING/README.md links to `designer/client/README.md`, but `CONTRIBUTING/designer/client/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift designer/client/README.md:37 — designer/client/README.md links to `../../CONTRIBUTING.md#running`, but `CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
AX6 · Interface segregation · Fat interface · ×3
  • Fat interface: ListenerScenarioWithDetails (21 abstract members) designer/listener-api/src/main/scala/pl/touk/nussknacker/ui/listener/ListenerScenarioWithDetails.scala:9 — `ListenerScenarioWithDetails` declares 21 abstract members: `name`, `processId`, `processVersionId`, `isLatestVersion`, `description`, `isArchived`, `isFragment`, `processingType`, `processCategory`, `modificationDate`, `modifiedAt`, `modifiedBy`, `createdAt`, `createdBy`, `scenarioLabels`, `lastDeployedAction`, `lastStateAction`, `lastAction`, `scenarioGraph`, `history`, `modelVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ProcessService (18 abstract members) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/ProcessService.scala:129 — `ProcessService` declares 18 abstract members: `getProcessIdUnsafe`, `getProcessId`, `getLatestProcessWithDetails`, `getProcessWithDetails`, `getLatestProcessesWithDetails`, `getLatestVersionForProcesses`, `getLatestRawProcessesWithDetails`, `getScenarioGraphsForVersionIds`, `archiveProcess`, `deleteProcess`, `unArchiveProcess`, `renameProcess`, `createProcess`, `updateProcess`, `updateProcessDBIO`, `migrateProcess`, `importProcess`, `getProcessActions`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PeriodicProcessesRepository (20 abstract members) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:82 — `PeriodicProcessesRepository` declares 20 abstract members: `run`, `markInactive`, `getSchedulesState`, `create`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `findToBeDeployed`, `findToBeRetried`, `findActiveSchedulesForProcessesHavingDeploymentWithMatchingStatus`, `findProcessData`, `markDeployed`, `markFinished`, `markFailedOnDeployWithStatus`, `markFailed`, `schedule`, `fetchInputConfigDuringExecutionJson`, `fetchCanonicalProcess`, `fetchProcessVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 20 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×3
  • Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:22 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:46 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:62 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
P2 · Observability · Console output used as the logging channel · ×3
  • Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js:2 — `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js:2 — `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js:1 — `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch designer/client/src/components/modals/TestingDataRecords/drawText.ts:56 — `tokenizeDataRecords` 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 designer/client/src/components/modals/TestingDataRecords/utils.ts:44 — `buildDefaultVariables` 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 designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:50 — `MultiSelectFixedValuesEditor` 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.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (47 single-owned of 1017 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1017 of the 2649 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (2 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: designer/client/src/components/conditionBuilder/ConditionBuilder.tsx, designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx, utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/confluent/client/ConfluentSchemaRegistryClient.scala, utils/schemed-kafka-components-utils/src/main/java/org/apache/flink/formats/avro/typeutils/NkSerializableParsedSchema.java, utils/components-utils/src/main/scala/pl/touk/nussknacker/engine/util/service/EagerServiceWithErrorSupport.scala, components/openapi/src/main/scala/pl/touk/nussknacker/openapi/http/SwaggerSttpService.scala, engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/DeduplicationTransformer.scala, designer/client/src/components/graph/node-modal/dataMapperFieldWrapper.tsx.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 2 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (115584 LoC, 4900 module-visible types across 419 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 462 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/ActionService.scala, scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/definition/clazz/ClassDefinitionExtractor.scala, scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/internal/propertyAccessors.scala, utils/math-utils/src/main/scala/pl/touk/nussknacker/engine/util/MathUtils.scala, utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/encode/JsonSchemaOutputValidator.scala, designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala, scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java, designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/DeploymentService.scala (and 454 more) (463 orphaned of 1017 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1017 of the 2649 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 55/62 types (89%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `designer/client`.
PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1
  • Benchmarks don't track allocations benchmarks/src/test/scala/pl/touk/nussknacker/engine/benchmarks/suggester/ExpressionSuggesterBenchmark.scala — A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
R8 · Dependency Hygiene · Type-only dependency 'react-notification-system' in production deps · ×1
  • Type-only dependency 'react-notification-system' in production deps designer/client/src/actions/notificationActions.tsx:5 — Every import is type-only — move it to devDependencies.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected examples/installation/nginx/nginx.conf:2 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X4 · Structured logging · Interpolated log message defeats structured logging · ×1
  • Interpolated log message defeats structured logging live-data-collector/src/main/scala/pl/touk/nussknacker/engine/livedata/LiveDataUploader.scala:46 — `error` at line 46 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 1575 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Minor — 76 finding(s)
D12 · Dependency Hygiene · Outdated · ×75
  • Outdated: ch.qos.logback:logback-classic — `ch.qos.logback %% logback-classic` is declared at 1.2.13 in REDACTED, but 1.6.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.2.13 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: ch.qos.logback:logback-core — `ch.qos.logback %% logback-core` is declared at 1.2.13 in REDACTED, but 1.6.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.2.13 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.auth0:jwks-rsa — `com.auth0 %% jwks-rsa` is declared at 0.22.2 in REDACTED, but 0.24.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.22.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.azure:azure-core-http-okhttp — `com.azure %% azure-core-http-okhttp` is declared at 1.11.9 in REDACTED, but 1.13.8 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.11.9 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.azure:azure-data-schemaregistry — `com.azure %% azure-data-schemaregistry` is declared at 1.4.9 in REDACTED, but 1.5.14 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.4.9 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.azure:azure-identity — `com.azure %% azure-identity` is declared at 1.16.3 in REDACTED, but 1.18.7 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.16.3 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.cronutils:cron-utils — `com.cronutils %% cron-utils` is declared at 9.1.6 in REDACTED, but 9.2.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 9.1.6 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.core:jackson-annotations — `com.fasterxml.jackson.core %% jackson-annotations` is declared at 2.18.2 in REDACTED, but 2.22 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.core:jackson-core — `com.fasterxml.jackson.core %% jackson-core` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.core:jackson-databind — `com.fasterxml.jackson.core %% jackson-databind` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-cbor — `com.fasterxml.jackson.dataformat %% jackson-dataformat-cbor` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-toml — `com.fasterxml.jackson.dataformat %% jackson-dataformat-toml` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml — `com.fasterxml.jackson.dataformat %% jackson-dataformat-yaml` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.datatype:jackson-datatype-guava — `com.fasterxml.jackson.datatype %% jackson-datatype-guava` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.datatype:jackson-datatype-jdk8 — `com.fasterxml.jackson.datatype %% jackson-datatype-jdk8` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.datatype:jackson-datatype-joda — `com.fasterxml.jackson.datatype %% jackson-datatype-joda` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 — `com.fasterxml.jackson.datatype %% jackson-datatype-jsr310` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.fasterxml.jackson.module:jackson-module-parameter-names — `com.fasterxml.jackson.module %% jackson-module-parameter-names` is declared at 2.18.2 in REDACTED, but 2.22.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.18.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.github.ben-manes.caffeine:caffeine — `com.github.ben-manes.caffeine %% caffeine` is declared at 3.2.2 in REDACTED, but 3.3.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.2.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.github.erosb:everit-json-schema — `com.github.erosb %% everit-json-schema` is declared at 1.14.5 in REDACTED, but 1.14.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.14.5 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.microsoft.azure:azure-schemaregistry-kafka-avro — `com.microsoft.azure %% azure-schemaregistry-kafka-avro` is declared at 1.1.2 in REDACTED, but 1.1.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.1.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.networknt:json-schema-validator — `com.networknt %% json-schema-validator` is declared at 1.5.8 in REDACTED, but 3.0.8 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.5.8 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.typesafe:config — `com.typesafe %% config` is declared at 1.4.4 in REDACTED, but 1.4.9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.4.4 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.typesafe.netty:netty-reactive-streams — `com.typesafe.netty %% netty-reactive-streams` is declared at 2.0.12 in REDACTED, but 2.0.20 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.0.12 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.zaxxer:HikariCP — `com.zaxxer %% HikariCP` is declared at 7.0.0 in REDACTED, but 7.1.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 7.0.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • + 50 more in this group — see findings.md.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: commonApi — commonApi: abstractness 0.09, instability 0.00, distance 0.91 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8364e7cfd771456fbf983bd2fd1a59f9/history.json --exit-code 0 --source .2artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8364e7cfd771456fbf983bd2fd1a59f9/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude designer/client/src/brace --exclude designer/client/test/Editors --exclude designer/client/test/Process/FrgamentInputDefinition .93artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update150artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .5artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude designer/client/src/brace --exclude designer/client/test/Editors --exclude designer/client/test/Process/FrgamentInputDefinition .1artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a17a9d-70a9-7b43-9fe1-48a54dd15043 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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