Public report — nussknacker, published 28 Sep 2026. Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches, dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase survey Measured under the Code Assurance Index · rubric rubric-2026.09.16 (frozen) · verify this survey Filed cd_0970132915e94856992f0ac0392d7e86 Filed 28 September 2026, 19:19 UTC Public

TouK/nussknacker

Measured 28 September 2026, 19:04 UTC

50% At Risk
Performance 100% Exemplary Code Health 73% Adequate Maturity 69% Adequate Security 67% Adequate Architecture 48% Weak Readiness 48% Weak Accessibility 45% Weak

Large · 183,133 LoC · 1 projects · rebuild ~2.4 person-years · weakest lens: Accessibility (45%)

Findings by grade

211 critical 1243 serious 32 minor 48 could not be resolved — could be critical — see Limitations

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
28 September 2026, 19:04 UTC

A measurement, not a certificate. The Code Assurance Index does not certify, approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said here so the number is checked rather than believed.

Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸

57/60dimensions tool-verifieddeterministic · confidence 1.0 · 3 LLM-assisted, advisory
1460findings with an exact file:lineof 1486 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
60/132dimensions across the health lenses183133 LoC · 1 projects — wide & deep
Chapters

Executive summary

⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.

This large-scale digital asset carries a moderate overall risk profile, scoring fifty percent against our health standards. While the system is stable and performant, its significant size and specific structural weaknesses create tangible business exposure that requires immediate attention to protect user trust and operational continuity.

The most critical vulnerability lies in accessibility, which scores poorly at forty-five percent. For a system of this magnitude, this is not merely a compliance checkbox but a direct barrier to user inclusion and potential legal liability. Remediation here offers the highest return on investment, as adding text alternatives to images, videos, and interactive elements is relatively low-effort compared to the risk of excluding users or facing regulatory scrutiny. This area represents the single biggest opportunity to reduce business risk quickly.

Beyond accessibility, the architecture and production readiness lenses also score low, indicating that changes may ripple unpredictably through the codebase. With nearly two hundred thousand lines of production code, the system is substantial, and its current state suggests that maintaining or modifying it could be costly and slow. The estimated effort to rebuild core logic is approximately two and a half person-years, highlighting the value tied up in this asset. However, the code itself is healthy, and performance is excellent, meaning the foundation is solid even if the surrounding structure needs reinforcement.

To maximize leverage, focus first on implementing basic accessibility standards: adding alt text, proper landmarks, and keyboard navigation. These actions address the highest-risk area with minimal disruption. While architectural improvements are necessary for long-term stability, they should follow the quick wins in accessibility. This approach balances immediate risk reduction with sustainable growth, ensuring the asset remains a reliable business driver rather than a liability.

Code Health 73% Adequate · gated by R7 Architecture 48% Weak · gated by D26, R9 Maturity 69% Adequate Readiness 48% Weak · gated by R8, P7 Security 67% Adequate · gated by D29, D30, D36 Accessibility 45% Weak · gated by AC1, AC4 Performance 100% ★ Exemplary
How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Accessibility 45% · 46% weightReadiness 48% · 25% weightArchitecture 48% · 14% weightSecurity 67% · 8% weightMaturity 69% · 4% weightCode Health 73% · 2% weightPerformance 100% · 1% weight

No single dominant problem — the weakest areas are close, so progress on any of them moves the score.

Code composition — where the lines go
Tests 100%
New since the last scan (100+)

150 finding(s) are new versus the previous scan (2026-09-11) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.

  • D4 · Duplicated block (5 lines × 2) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java
  • D10 · No assertions: should allow pan view designer/client/cypress/e2e/processSelection.cy.ts
  • D10 · No assertions: should select only fully covered (to right) designer/client/cypress/e2e/processSelection.cy.ts
  • D10 · No assertions: should select partially covered (to left) designer/client/cypress/e2e/processSelection.cy.ts
  • D10 · No assertions: should switch modes, append and inverse select with shift designer/client/cypress/e2e/processSelection.cy.ts
  • D10 · No assertions: should allow drag node designer/client/cypress/e2e/process.cy.ts
  • D10 · No assertions: should make a deploy of the new version designer/client/cypress/e2e/process.cy.ts
  • D10 · No assertions: should display and expand advanced deploy section designer/client/cypress/e2e/deployAdvancedSection.cy.ts
  • D10 · No assertions: should allow filtering by processing mode designer/client/cypress/e2e/components.cy.ts
  • D10 · No assertions: basic components - variable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - recordVariable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - filter designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - choice designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - split designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - foreach designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: basic components - union designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: aggregates - Single Side Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: aggregates - Full Outer Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: fragments - Properties designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: fragments - Inputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: fragments - Outputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts
  • D10 · No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts
  • D10 · No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts
  • D10 · No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts
  • D10 · No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts
  • D10 · No assertions: should omit brackets designer/client/src/components/graph/node-modal/typeHelpers.test.ts
  • D15 · Hotspot: designer/client/src/components/modals/CompareVersionsDialog.tsx designer/client/src/components/modals/CompareVersionsDialog.tsx
  • D17 · TodoComment repeated across 14 files engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinformation/SimpleTypeInformation.scala
  • D29 · REDACTED
  • D29 · REDACTED
  • D29 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • D30 · REDACTED
  • R10 · Duplication concentrated across 7 sibling directories (19 clone groups) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx
  • R10 · Duplication concentrated across 3 sibling directories (10 clone groups) designer/submodules/packages/components/src/components/usages/usagesTable.tsx
  • R10 · Duplicated block with local edits (111 matched lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts
  • R10 · Duplicated block (109 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx
  • R10 · Duplicated block with local edits (105 matched lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx
  • R10 · Duplicated block with local edits (75 matched lines × 2 locations) designer/submodules/packages/components/src/components/usages/usagesTable.tsx
  • R10 · Duplicated block with local edits (50 matched lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx
  • R10 · Duplicated block (50 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx
  • R10 · Duplicated block (49 lines × 2 locations) designer/client/configs/simpleScriptPlugin.ts
  • R10 · Duplicated block (48 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
  • R10 · Duplicated block (47 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts
  • R10 · Duplicated block (46 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx
  • R10 · Duplicated block (41 lines × 2 locations) designer/client/src/components/notifications/copyTooltip.tsx
  • R10 · 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
  • R10 · Duplicated block (37 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts
  • R10 · Duplicated block (34 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
  • R10 · Duplicated block (30 lines × 2 locations) designer/client/src/components/graph/node-modal/DescriptionField.tsx
  • R10 · Duplicated block (30 lines × 2 locations) designer/client/src/components/modals/DeployProcessDialog.tsx
  • R10 · Duplicated block (28 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx
  • R10 · Duplicated block (25 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx
  • R10 · Duplicated block (25 lines × 2 locations) designer/client/src/components/modals/AddCommentDialog.tsx
  • R10 · Duplicated block (24 lines × 3 locations) designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx
  • R10 · Duplicated block (23 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionRow.tsx
  • R10 · Duplicated block (23 lines × 2 locations) designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx
  • R10 · Duplicated block (23 lines × 2 locations) designer/client/src/components/modals/GenerateDataAndTestDialog.tsx
  • R10 · Duplicated block (22 lines × 2 locations) designer/client/src/components/dataMapper/dataMapperUtils.ts
  • R10 · Duplicated block (22 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx
  • R10 · Duplicated block with local edits (22 matched lines × 2 locations) designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €120,000–€590,000
Cost to rebuild€120,000–€590,000 (1.2–3.7 person-years (1,962–6,223 h), ~1–5 engineers)
Domain complexityStandard — harder problems cost more per line
Quality factor0.7× (at 50% quality) — the last 20% of quality is most of the work
Size & shapeLarge · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~2.4 person-years of build effort (about ~€350,000 to rebuild). Its weakest lens is Accessibility at 45% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — CQRS × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

1
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
+3.1 pts · Low effort · Project Cohesion
2
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
+3.0 pts · Low effort · REDACTED Scanning
3
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.
+4.8 pts · Medium effort · Text alternatives

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk
This is a Large asset (~2.4 person-years to rebuild), and its weakest lens is Accessibility at 45%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: Large, ~2.4 person-years rebuild (183,133 LoC) · weakest lens: Accessibility 45%
→ Direct remediation budget at Accessibility first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

1458 modules, 3415 dependencies. 11 dependency cycles across 198 modules, marked above the diagonal.

Showing the 40 most-connected modules; 1418 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →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
Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself
…aultFullScreenMessage…gine.api.typed.typing…n.Expression.Language…sion.TabularTypedData…gine.graph.expression….engine.api.parameter…ker.engine.graph.node…ode.VariableOperation…er.engine.api.process…ocessCompilationError…er.engine.api.context…ontext.transformation…engine.api.definition….engine.api.component…ussknacker.engine.api…cker.engine.api.graph…gine.expression.parse…ine.flink.api.process…ssknacker.engine.util…acker.ui.security.api…engine.canonicalgraph…ker.engine.deployment…sknacker.engine.kafka…ssknacker.engine.spel…odesApiEndpoints.Dtos…nacker.engine.compile…sknacker.ui.db.entity…mpile.nodecompilation…ui.process.repository….definition.component…ussknacker.ui.process…ui.process.deployment…uk.nussknacker.ui.api…nussknacker.ui.config…rocess.processingtype…engine.api.deployment…uk.nussknacker.engine…process.newdeployment…knacker.ui.statistics…ussknacker.ui.factory…aultFullScreenMessage1…gine.api.typed.typing2…n.Expression.Language3…sion.TabularTypedData4…gine.graph.expression5….engine.api.parameter6…ker.engine.graph.node7…ode.VariableOperation8…er.engine.api.process9…ocessCompilationError10…er.engine.api.context11…ontext.transformation12…engine.api.definition13….engine.api.component14…ussknacker.engine.api15…cker.engine.api.graph16…gine.expression.parse17…ine.flink.api.process18…ssknacker.engine.util19…acker.ui.security.api20…engine.canonicalgraph21…ker.engine.deployment22…sknacker.engine.kafka23…ssknacker.engine.spel24…odesApiEndpoints.Dtos25…nacker.engine.compile26…sknacker.ui.db.entity27…mpile.nodecompilation28…ui.process.repository29….definition.component30…ussknacker.ui.process31…ui.process.deployment32…uk.nussknacker.ui.api33…nussknacker.ui.config34…rocess.processingtype35…engine.api.deployment36…uk.nussknacker.engine37…process.newdeployment38…knacker.ui.statistics39…ussknacker.ui.factory4021116137231341410211402617538911118121342122612134231473143116522521212512252561223152131112211044133171437326112924110321326692221311581721116161173311532611146312231113245111213101811215264175631012016318118110413291117241122114141011444224117121131128236111622122121151221211+1418 more modules (most-connected shown)

At a glance — Code Health · 73% · Adequate · gated by R7 ·

The Good
D3 · Scala God Classes 8.9 D4 · Scala Code Duplication 9.9 D17 · Scala Explicit Debt 9.2 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 9.2 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 9.6
The Bad
D1 · Scala Cyclomatic Complexity 5.6 D2 · Scala Cognitive Complexity 5.6
The Ugly
R7 · React / TS Dead Code 3.5

At a glance — Architecture · 48% · Weak · gated by D26, R9 ·

The Good
D6 · Scala Cohesion (LCOM4) 9.5 D35 · Scala Change Coupling 10.0 AX10 · Repo Code composition 8.3 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0
The Bad
R11 · React / TS Import Boundaries 5.9
The Ugly
D26 · Scala Project Cohesion 0.0 R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 69% · Adequate ·

The Good
D15 · Scala Churn × Complexity Hotspots 9.9 D16 · Scala Bus Factor 9.5 D19 · Scala Documentation Quality 9.3 D21 · Scala Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 9.0
The Bad
D34 · Scala Knowledge Freshness 6.4 M1 · Repo Documentation (README) 5.8 M2 · Repo Architecture documentation 5.0
The Ugly
D20 · Scala ADR Quality 0.0

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

The Good
D9 · Scala Test Distribution 7.3 D10 · Scala Test Quality 9.4 D12 · Scala Dependency Hygiene 8.6 D14 · Scala License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 8.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 P8 · Repo Schema migrations 10.0 R5 · React / TS Dependency Freshness 10.0 R6 · React / TS Tooling 10.0
The Bad
D13 · Scala REDACTED Scanning 5.0 R4 · React / TS Test Coverage 5.2
The Ugly
P7 · Repo Outbound HTTP resilience 3.0 R8 · React / TS Dependency Hygiene 0.5

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

The Good
D28 · Scala Secrets (history) 9.0 D31 · Scala IaC & Container Security 9.3 D32 · Scala Data Compliance (PII/GDPR) 9.0 D43 · Scala Malicious Dependencies 10.0 S1 · Repo Web-Security Posture 8.0
The Ugly
D29 · Scala Static Analysis (SAST) 0.2 D30 · Scala Dependency Vulnerabilities 0.0 D36 · Scala Supply-chain Provenance & Signing 2.5

At a glance — Accessibility · 45% · Weak · gated by AC1, AC4 ·

The Good
AC2 · Repo Forms & labels 8.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0
The Ugly
AC1 · Repo Text alternatives 3.5 AC3 · Repo Page structure 4.5 AC4 · Repo Keyboard semantics 2.2 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

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
A06:2021 — Vulnerable & Outdated Components129High / Critical
A03:2021 — Injection95High / Critical
A05:2021 — Security Misconfiguration5High / Critical
A02:2021 — Cryptographic Failures3High / Critical
A04:2021 — Insecure Design1Medium

Roadmap

First, ensure all media elements have appropriate text alternatives and captions to support diverse user needs. Next, establish a solid page structure by defining language, titles, and landmarks, while fixing keyboard accessibility for custom controls and ensuring all form controls have programmatic labels. Finally, enforce these standards by integrating accessibility checks into the development toolchain and CI pipeline to prevent regressions.

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

Do thisHelpsEffortDimension
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.+3.1 ptsLowProject Cohesion
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+3.0 ptsLowREDACTED Scanning
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.+4.8 ptsMediumText alternatives
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+4.8 ptsMediumPage structure
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+4.8 ptsMediumKeyboard semantics
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.+4.8 ptsMediumA11y enforcement
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+3.7 ptsMediumForms & labels
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.+3.6 ptsMediumOutbound HTTP resilience

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala3.1SlopChange Coupling: Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala5.6MixedCyclomatic Complexity: DbScenarioActivityRepository.fromEntity (cyclomatic 43)
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
utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/decode/FromJsonSchemaBasedDecoder.scala6.0MixedExplicit Debt: TodoComment
scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/ExpressionCompiler.scala6.0MixedExplicit Debt: TodoComment
designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.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 — 211

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

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

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

Could not be resolved — 48

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. 57 of 60 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. 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 — 60 dimensions across the health lenses
D1D2D3D4D6D9D10D12D13D14D15D16D17D19D20D21D26D28D29D30D31D32D34D35D36D43AC1AC2AC3AC4AC5AC6AC7AX10AX3AX5M1M2M3M4P1P2P3P4P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1

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, 1460 of 1486 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 measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e967-c9f1-7732-ae78-6d2cbc3aac0e.

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.

  • D5 Coupling — 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.
  • 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 .scala, .tsx, and our analyzer cannot run the .scala, .tsx 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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 808 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 built-in reliability runner cannot re-run the .scala test suite(s) — 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.
  • D14 License Compliance — 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 repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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 a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • 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. `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/submodules/packages/components/src/scenarios/filters/useArrayStateWithUpdate.tsx` 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.
  • D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a REDACTED) is simply not read here yet.
  • AC3 Page structure — 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. 733 further occurrence(s) are not listed individually; the score already reflects all 773.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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 — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
  • 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.
  • C3 Audit Trail — 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 audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — 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 retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — 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 data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • ED5 Idempotency — not measured this run — 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 finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
  • GD1 Unfinished & placeholder code — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • IC1 Incompleteness & stubs — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • P10 Library API & versioning — 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 NuGet packaging and C# public API only, and no .NET project was loaded for this repository, 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.
  • PF1 Benchmark discipline — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • PF2 Allocation hygiene — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • PF3 Async & latency hygiene — 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 colour their functions async, so blocking inside them is the same defect this card counts elsewhere, but their blocking vocabulary is not modelled yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
  • 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. 195 further occurrence(s) are not listed individually; the score already reflects all 235.
  • X1 Async correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X10 Duplicated predicate — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X12 Unreachable branch — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X16 Unfloored truncation loop — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X17 Uncapped recursion over a caller-supplied document — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X18 Disposal-pattern correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X2 Cancellation propagation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X20 Mistyped argument guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X21 Side-effecting pattern guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X22 Contradicted release guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X23 Unguarded diagnostic materialisation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X24 Document value interpolated into markup unescaped — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X27 Collection changed while being enumerated — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X28 Index access outside its own emptiness guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X29 Per-element action decided by a fixed element — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X4 Structured logging — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X6 Hand-rolled structured-format parsing — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
  • X7 Silent fallback defaults — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 63 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.
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • 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.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • 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.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

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

57 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
useDataMapper.useDataMapper (cyclomatic 117)designer/client/src/components/dataMapper/useDataMapper.ts:139
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
drawText.buildFragmentsForTokens (cyclomatic 44)designer/client/src/components/modals/TestingDataRecords/drawText.ts:120

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

What to do

  1. Resolve the 1 SpelTyper.typeNode (cyclomatic 143) finding(s) in Cyclomatic Complexity — start with SpelTyper.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 useDataMapper.useDataMapper (cyclomatic 117) finding(s) in Cyclomatic Complexity — start with useDataMapper.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 CompareVersionsDialog.VersionsForm (cyclomatic 62) finding(s) in Cyclomatic Complexity — start with CompareVersionsDialog.tsx. — One of this dimension's main actionable groups (1 warning-level).
  4. 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

88 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
useDataMapper.useDataMapper (cognitive 125)designer/client/src/components/dataMapper/useDataMapper.ts:139
drawText.buildFragmentsForTokens (cognitive 116)designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107)scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114
DbScenarioActivityRepository.fromEntity (cognitive 62)designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720

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

What to do

  1. Resolve the 1 SpelTyper.typeNode (cognitive 146) finding(s) in Cognitive Complexity — start with SpelTyper.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 useDataMapper.useDataMapper (cognitive 125) finding(s) in Cognitive Complexity — start with useDataMapper.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 drawText.buildFragmentsForTokens (cognitive 116) finding(s) in Cognitive Complexity — start with drawText.ts. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.9 / 10Strong✓ Tool-verified

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

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

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

49 god class(es) detected.

FunctionTooLong: useDataMapper.useDataMapper · ×30designer/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 30 FunctionTooLong finding(s) in God Classes — start with useDataMapper.ts, FieldRow.tsx, DataMapper.tsx. — One of this dimension's main actionable groups (30 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. 2 of the 32 are in trees this repository does not ship — vendored, example/demo, 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.

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 Distribution7.3 / 10Strong✓ 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 7.3 / 10 · rule-coverage 100% · ceiling Documented

635 test methods: 501 unit, 0 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.

What to do

  1. Improve Test Distribution — currently 7.3/10. — 635 test methods: 501 unit, 0 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.

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 808 test source file(s) (.scala, .java) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: should allow pan view · ×25designer/client/cypress/e2e/processSelection.cy.ts:30

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 Hygiene9.7 8.6 / 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 8.6 / 10 · rule-coverage 89% · ceiling Verified

6 outdated direct sbt declarations. 8 of 9 direct declarations were graded against Maven Central (1 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 not read: sbt is a program rather than a manifest, and evaluating one 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: com.auth0:jwks-rsa · ×6

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 112 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 112 production dependency(ies) this repository's committed lockfile resolves, across 3 product package.json manifest(s). Its 180 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under ISC / UNLICENSED, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares an sbt build (build.sbt), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 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 1019 of the 2660 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 183133 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 · ×616common-api/src/main/scala/pl/touk/nussknacker/engine/api/TypeSpecificData.scala:60
FixmeComment · ×73components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/ParameterValidator.scala:280
HackCommentdesigner/server/src/main/scala/pl/touk/nussknacker/ui/server/NussknackerHttpServer.scala:108
TodoComment repeated across 14 filesengine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinformation/SimpleTypeInformation.scala:25

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 HackComment finding(s) in Explicit Debt — start with NussknackerHttpServer.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 QualityExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README and CONTRIBUTING/README are clear and complete for a project that is itself an open-source library (the README.md at the top shows the Maven Central badge, GitHub actions status, and links to demo, docs, quickstart, installation, and Nu Cloud). The architecture/design documentation set (45 markdown files) is well-organized with a full outline; each document in the summary is present and complete. The READMEs are focused on their own directories rather than the repository's overview, so missing-overview, missing-installation, or missing-usage findings would apply only to the root README. The documentation is comprehensive and well-structured for an open-source real-time decisioning platform: the repository's README plus four architecture/design docs (Changelog, FAQ, LicenseInfo, MigrationGuide) cover changelogs, FAQs, licensing terms, and migration steps; Glossary defines core concepts like component, engine, enricher, event, integration, and sink; Key Features lists features such as a spreadsheet-like authoring interface, schema-aware autocompletion, and AI-powered assistant; ProcessingModes explains the streaming vs request-response modes with contrast tables; and DesignRationale addresses real-time constraints and architectural choices. The Changelog is an excellent change log for any reader. The repository is well documented: the READMEs cover integrations (OpenAPI), scenarios (SpEL cheat sheet), and architecture/Docs markdown files. The OpenAPI integration guide explains what it does, its purpose, and a note about Cloud-only UI integrations; the SpEL cheat sheet gives an overview of expressions and types with a dedicated data-types section plus many subsections. All visible sections are present in the outline (front matter metadata for Docusaurus; sidebar_position:; OpenAPI; Overview; Integration parameters; Additional info; front matter metadata for LLM; processingModes; keywords; SpEL Cheat Sheet; Expressions and types; Data types and structures; Basic ...); the unshown content is clipped. The documentation is clear, complete, and well-structured.

Documentation: no project overview · ×2README.md

✓ On the Gold path — maintain.

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

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

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.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

1 of 1 build units (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)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

D29 · Static Analysis (SAST)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

95 finding(s): 0 critical, 90 high, 5 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/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, Go, Java and Kotlin via Maven/Gradle, 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

129 finding(s): 11 critical, 78 high, 32 medium, 8 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 75 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (75). — One of this dimension's main actionable groups (75 issue-level).
  2. Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
  3. Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 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 4 file(s) — `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/submodules/packages/components/src/scenarios/filters/useArrayStateWithUpdate.tsx` — 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 Freshness6.4 / 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 6.4 / 10 · rule-coverage 100% · ceiling Documented

371 of 1019 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/definition/clazz/ClassDefinitionExtractor.scala. Counted over 1019 of the 2660 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge

What to do

  1. Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

Strongest change-coupling: nodeDetails.ts↔nodeDetailsState.ts 90%; Interpreter.scala↔LoggingListener.scala 80%; TableSource.scala↔RowConversions.scala 60%

Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scalascenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala
Change coupling: nodeDetails.ts ↔ nodeDetailsState.ts · ×5designer/client/src/actions/nk/nodeDetails.ts

What to do

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

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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 & labels8.0 / 10Strong✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — 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 / name, and nothing it renders carries one either. 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 structure4.5 / 10Weak✓ Tool-verified

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×22) — designer/client/jest-coverage/lcov-report/index.html:3, designer/client/jest-coverage/lcov-report/src/WrapAllMethods.ts.html:3, designer/client/jest-coverage/lcov-report/src/actions/index.html:3, …
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×18) — designer/client/jest-coverage/lcov-report/src/WrapAllMethods.ts.html:65, designer/client/jest-coverage/lcov-report/src/actions/nk/abortControllersStack.ts.html:65, designer/client/jest-coverage/lcov-report/src/actions/nk/calculateProcessAfterChange.ts.html:65, …

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: interactive elements plus elements the markup gives a click/key handler or the repo's own CSS styles `cursor: pointer`, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). 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.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

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

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.

  • 325 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.
  • Add a 'Testing' section to the root README — 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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 accuracy9.0 / 10Exemplary◐ Sampled · advisory

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.

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.

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

What to do

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

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

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

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.

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

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

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 33 and cognitive complexity 8; 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/reducers/graph/reducer.ts:170
  • (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. — REDACTED: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
  • testingReducer has cyclomatic complexity 19 and cognitive complexity 8; 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/reducers/graph/testing.ts:59
  • 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. — designer/client/src/components/graph/node-modal/NodeSwitcherUtils.tsx: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
  • NodeDetails has cyclomatic complexity 16 and cognitive complexity 3; 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/NodeTypeDetailsContent.tsx:48

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.

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, designer/client/src/reducers/graph/reducer.ts, designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx, …

What to do

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

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

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

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code3.5 / 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.5 / 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 but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — designer/submodules/packages/components/src/settings/rootProviders.tsx:1, designer/submodules/packages/components/src/common/PlaceholderIconFallbackComponent.tsx:2, designer/submodules/packages/components/src/settings/rootProviders.tsx:7
  • Declared in designer/client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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

What to do

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

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

  • No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. This is reported because `defaultDesignerConfig.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.) — designer/server/src/main/resources/defaultDesignerConfig.conf:47

What to do

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

WCAG coverage — what static analysis assessed

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

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
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

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

LensScoreRatingImpact
Code Health73%Adequate — gated by R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture48%Weak — gated by D26, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity69%AdequateAcceptable, with room to improve.
Readiness48%Weak — gated by R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security67%Adequate — gated by D29, D30, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility45%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — not 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
  • AX2 Stateful singletons — 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)
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • 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) — redpanda Pulling designer Pulling designer Error Get "https://registry-1.docker.io/v2/": Forbidden redpanda Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redpanda Pulling designer Pulling redpanda Error Get "https://registry-1.docker.io/v2/": Forbidden 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.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — 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. 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 — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • 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); 1848 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 — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That 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
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — 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
  • P10 Library API & versioning — 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
  • 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.
  • PF1 Benchmark discipline — 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
  • PF2 Allocation hygiene — 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
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — 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
  • X10 Duplicated predicate — 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
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — 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
  • X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — 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
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — 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
  • X6 Hand-rolled structured-format parsing — 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
  • X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 211 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×75
  • 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
  • + 50 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • 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.
D30 · Dependency Vulnerabilities · High vulnerability · ×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
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.
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
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala — `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.
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 package.json — 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 package.json — 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 package.json — 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 — 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 — 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 — 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 — 1243 finding(s)
D17 · Explicit Debt · TodoComment · ×616
  • TodoComment common-api/src/main/scala/pl/touk/nussknacker/engine/api/TypeSpecificData.scala:60 — // TODO: rename to FlinkStreamMetaData — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/TypeSpecificData.scala:107 — // TODO: parallelism is fine? Maybe we should have other method to adjust number of workers? — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/ProcessVersion.scala:6 — // We should split this class - see TODO in ScenarioAction — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/MetaData.scala:12 — // TODO: This class should be moved into components-api, scenario-api shouldn't use this. It should hold only properties — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common-api/src/main/scala/pl/touk/nussknacker/engine/api/MetaData.scala:63 — // TODO: remove legacy constructors after the migration is completed — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/MetaData.scala:84 — // TODO: remove metaDataType val and typeSpecificProperties def after the migration is completed — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/MetaData.scala:110 — // TODO: is this currently needed? — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ProcessName.scala:7 — // TODO: Rename to ScenarioSlug / ScenarioId and add validations that it is a proper url path part — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ProcessName.scala:8 — // TODO: Avoid using it as a easy-to-change label. If we really need such a thing, we should introduce a separate ScenarioLabel 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ProcessId.scala:8 — // TODO: We should avoid exposing it anywhere, especially in the API as it is not safe to pass such information externally. — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ProcessId.scala:9 — // TODO: Also we'd rather not use a synthetic identifier, ProcessName (which meant to be a human friendly id) should be sufficient — 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 common-api/src/main/scala/pl/touk/nussknacker/engine/graph/expression/Expression.scala:16 — // TODO in the future 'expression' should be a dedicated type rather than String, it would for example make DictKeyWithLabelExpression handling prettier — 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 components-api/src/main/java/pl/touk/nussknacker/engine/api/MethodToInvoke.java:8 — // TODO: Rename to ComponentMainMethod — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/ModelConfig.scala:23 — // TODO: we should parse this underlying config as ModelConfig class fields instead of passing raw 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 components-api/src/main/scala/pl/touk/nussknacker/engine/ModelConfig.scala:63 — // todo: We should use Designer db configuration here, but it is not easily available from the places where we use live data. — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/ModelConfig.scala:130 — // TODO: left for a compatibility reasons, will be removed 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/Service.scala:32 — // TODO: EagerService shouldn't extend Lifecycle, instead ServiceInvoker should extend it - see notice in ProcessCompilerData.lifecycle — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/Params.scala:66 — // TODO: We should use fromParameterEvaluationResultMap instead of current variant. Thanks to that, — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/LazyParameter.scala:18 — // TODO: rename to TypedFunction — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/CustomStreamTransformer.scala:16 — //TODO this could be scala-trait, but we leave it as abstract class for now for java compatibility — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/Context.scala:114 — // TODO: all methods should has NotNothing type check to avoid situation when scala's compiler implicitly put Nothing — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/component/NodesDeploymentData.scala:15 — // TODO: consider replacing NodeDeploymentData with Json — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/component/NodeComponentInfo.scala:8 — // TODO: remove this method - in every place of usage, should be accessible ComponentId — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/component/NodeComponentInfo.scala:21 — // TODO: Remove Option from componentId - every Node used in runtime is related with some Component. After doing it, we should — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/component/DesignerWideComponentId.scala:6 — // TODO This class is used as a work around for the problem that the components are duplicated across processing types. — 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 components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/ParameterValidator.scala:280 — // FIXME: we should properly evaluate `possibleValues` — 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 components-api/src/test/scala/pl/touk/nussknacker/engine/api/typed/TypingResultDecoderSpec.scala:85 — // FIXME: tagged types doesn't work correctly — 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 components/openapi/src/main/scala/pl/touk/nussknacker/openapi/extractor/ServiceRequest.scala:59 — // FIXME: lepsza obsluga (rozpoznawanie multi headers, itp...) — 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 components/openapi/src/main/scala/pl/touk/nussknacker/openapi/parser/ParseToSwaggerService.scala:148 — // FIXME: nicer way of handling application/json;charset... — 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 designer/client/cypress/e2e/stickyNotes.cy.ts:51 — //FIXME flaky screenshot — 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 designer/client/cypress/e2e/fragment.cy.ts:248 — //FIXME flaky screenshot — 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 designer/client/cypress/e2e/fragment.cy.ts:256 — //FIXME flaky screenshot — 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 designer/client/cypress/e2e/processes.cy.ts:54 — //.matchImage() FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment designer/client/cypress/e2e/activities.cy.ts:24 — // FIXME: disabled snapshots because of styles blink problems (look for state & uuid) — 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 designer/client/src/actions/nk/calculateProcessAfterChange.ts:16 — // FIXME: this is not an action, — 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 designer/client/src/actions/nk/assignUser.ts:12 — //FIXME: remove class from store - plain data only — 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 designer/client/src/common/models/User.ts:18 — //FIXME: remove class from store - plain data only — 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 designer/client/src/reducers/settings.ts:63 — //FIXME: remove class from store - plain data only — 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 REDACTED:25 — //fixme maybe return hasErrors flag from backend? — 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 designer/client/src/components/graph/node-modal/NodeDetailsContent/selectors.tsx:87 — // FIXME: TypingResult is broken — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment REDACTED:65 — //FIXME: this should not work this way. We should either provide some helper, or (even better) create mini-expression-languages for those types and do not try — 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 designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:181 — // FIXME: other fields have outline instead of border, so we need to compensate for that — 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 designer/restmodel/src/main/scala/pl/touk/nussknacker/restmodel/validation/ValidationResults.scala:71 — // FIXME: BaseFlowTest fails otherwise?? — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/api/TapirCodecs.scala:114 — // FIXME: Type me properly — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ProcessesResources.scala:166 — // FIXME: The `skipValidateAndResolve` flag has a non-trivial side effect. — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/MigrationApiEndpoints.scala:58 — // FIXME uncomment examples when discriminator validation will work in the NuDesignerApiAvailableToExposeYamlSpec - — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/ActionInfoEndpoints.scala:54 — // FIXME uncomment examples when discriminator (ParameterEditor) validation will work in the NuDesignerApiAvailableToExposeYamlSpec - — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/config/ComponentLinkConfig.scala:17 — // FIXME: It should be probably supportedComponentIds - currently this filtering is unusable — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/migrations/MigrationService.scala:79 — // FIXME: Rename process to scenario everywhere it's possible — 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 designer/server/src/main/scala/pl/touk/nussknacker/ui/process/ProcessService.scala:397 — // FIXME: This doesn't work correctly because concurrent request can change a state and double archive actions will be done. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 · ×32
  • 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
  • + 7 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×30
  • 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: 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: 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.
  • FunctionTooLong: ConditionRow.ConditionRow designer/client/src/components/conditionBuilder/ConditionRow.tsx:33 — FunctionTooLong — ConditionRow runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nuTheme.nuTheme designer/client/src/containers/theme/nuTheme.tsx:129 — FunctionTooLong — nuTheme runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: FieldSwitch.FieldSwitch designer/client/src/components/graph/node-modal/editors/field/FieldSwitch.tsx:72 — FunctionTooLong — FieldSwitch runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 5 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×25
  • 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.
  • 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 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 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: 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: 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.
AC3 · Page structure · Page without a main landmark · ×22
  • Page without a main landmark designer/client/jest-coverage/lcov-report/index.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/WrapAllMethods.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/index.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/abortControllersStack.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/calculateProcessAfterChange.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/checkPendingChanges.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/displayProcessCounts.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/editProperties.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/index.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/liveData.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/node.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/preApplyValidation.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/process.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/processDefinitionData.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/scenarioActivities.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/testCasesActions.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/testingActions.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/ui/index.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/ui/layout.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/ui/panelSide.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/nk/userSettings.ts.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark designer/client/jest-coverage/lcov-report/src/actions/notificationActions.tsx.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Data table has no header cells · ×18
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/WrapAllMethods.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/abortControllersStack.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/calculateProcessAfterChange.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/checkPendingChanges.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/displayProcessCounts.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/editProperties.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/liveData.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/node.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/preApplyValidation.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/process.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/processDefinitionData.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/scenarioActivities.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/testCasesActions.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/testingActions.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/ui/layout.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/ui/panelSide.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/nk/userSettings.ts.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells designer/client/jest-coverage/lcov-report/src/actions/notificationActions.tsx.html:65 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
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 / name — and neither does anything it renders — 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 / name — and neither does anything it renders — 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 / name — and neither does anything it renders — 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.
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.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: nodeDetails.ts ↔ nodeDetailsState.ts designer/client/src/actions/nk/nodeDetails.ts — `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 — `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 — `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: TableSink.scala ↔ RowConversions.scala engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/sink/TableSink.scala — `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 — `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.
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 / name — and neither does anything it renders — 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 / name, and nothing it renders carries one either. 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 / name, and nothing it renders carries one either. 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 / name, and nothing it renders carries one either. 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.
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 / name — and neither does anything it renders — 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 / name — and neither does anything it renders — 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 / name — and neither does anything it renders — 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 · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×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
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 / name — and neither does anything it renders — 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 / name — and neither does anything it renders — 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.
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.
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 1005 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 · useDataMapper.useDataMapper (cyclomatic 117) · ×1
  • useDataMapper.useDataMapper (cyclomatic 117) designer/client/src/components/dataMapper/useDataMapper.ts:139 — useDataMapper.useDataMapper has cyclomatic complexity 117 (threshold 15). Most of this is not in the body itself: 1 of the 117 points is its own statement and the rest belongs to 32 function literals inside it that branch (lines 197, 477, 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.
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 literals inside it that branch (lines 319, 214, 397, …). 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 · 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 · drawText.buildFragmentsForTokens (cyclomatic 44) · ×1
  • drawText.buildFragmentsForTokens (cyclomatic 44) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120 — drawText.buildFragmentsForTokens has cyclomatic complexity 44 (threshold 15). Of this number, 18 points are the body's own statements and 26 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 · 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 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 · 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) designer/client/src/components/graph/node-modal/NodeSwitcherUtils.tsx: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 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 · 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 · 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 · useActivitiesSearch.useActivitiesSearch (cyclomatic 25) · ×1
  • useActivitiesSearch.useActivitiesSearch (cyclomatic 25) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:26 — useActivitiesSearch.useActivitiesSearch has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 107, 59, 73, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
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 · 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 · drawText.tokenizeDataRecords (cyclomatic 22) · ×1
  • drawText.tokenizeDataRecords (cyclomatic 22) designer/client/src/components/modals/TestingDataRecords/drawText.ts:51 — drawText.tokenizeDataRecords has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 70, 63, 68, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
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 · useDataRecordsActions.useDataRecordsActions (cyclomatic 21) · ×1
  • useDataRecordsActions.useDataRecordsActions (cyclomatic 21) designer/client/src/components/modals/TestingDataRecords/useDataRecordsActions.ts:14 — useDataRecordsActions.useDataRecordsActions has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 140, 22, 39, …). 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 · 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 literals inside it that branch (lines 105, 82, 100). 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 · 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, separate the cases: extract each independent 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 · 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 literals inside it that branch (lines 41, 100, 126, …). 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 · ProcessUtils._findVariablesDefinedInProcess (cyclomatic 19) · ×1
  • ProcessUtils._findVariablesDefinedInProcess (cyclomatic 19) REDACTED: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 · 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 · 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 · 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 · 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.
D17 · Explicit Debt · TodoComment repeated across 14 files · ×1
  • TodoComment repeated across 14 files engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinformation/SimpleTypeInformation.scala:25 — 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.)
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 · useDataMapper.useDataMapper (cognitive 125) · ×1
  • useDataMapper.useDataMapper (cognitive 125) designer/client/src/components/dataMapper/useDataMapper.ts:139 — useDataMapper.useDataMapper has cognitive complexity 125 (threshold 15). Drivers by points: if/else 49 (64 pts), ternaries 19 (32 pts), boolean chains 26, loops 2, error handling 1 (nesting depth added 28). Most of this is not in the body itself: 0 of the 125 points are its own statements and the rest belongs to 32 function literals inside it that branch (lines 197, 289, 477, …). 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.buildFragmentsForTokens (cognitive 116) · ×1
  • drawText.buildFragmentsForTokens (cognitive 116) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120 — drawText.buildFragmentsForTokens has cognitive complexity 116 (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). Of this number, 40 points are the body's own statements and 76 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · 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 · 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 literals inside it that branch (lines 486, 397, 176, …). 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 · 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 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 · 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 · NumberUtils.convertNumberToTargetClass (cognitive 45) · ×1
  • NumberUtils.convertNumberToTargetClass (cognitive 45) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:87 — NumberUtils.convertNumberToTargetClass has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (42 pts), boolean chains 3 (nesting depth added 24). 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 · 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 · NodeSwitcherUtils.adjustEdges (cognitive 39) · ×1
  • NodeSwitcherUtils.adjustEdges (cognitive 39) designer/client/src/components/graph/node-modal/NodeSwitcherUtils.tsx: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 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 · 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 · useActivitiesSearch.useActivitiesSearch (cognitive 38) · ×1
  • useActivitiesSearch.useActivitiesSearch (cognitive 38) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:26 — useActivitiesSearch.useActivitiesSearch has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 16). Most of this is not in the body itself: 0 of the 38 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 107, 59, 73, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
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 · NumberUtils.parseNumber (cognitive 30) · ×1
  • NumberUtils.parseNumber (cognitive 30) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:210 — NumberUtils.parseNumber has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 5 (20 pts), if/else 9, boolean chains 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
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 · drawText.tokenizeDataRecords (cognitive 27) · ×1
  • drawText.tokenizeDataRecords (cognitive 27) designer/client/src/components/modals/TestingDataRecords/drawText.ts:51 — drawText.tokenizeDataRecords has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, ternaries 3 (6 pts), error handling 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 70, 63, 68, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
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 · 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). Most of this is not in the body itself: 0 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 105, 82, 100). 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 · 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). Most of this is not in the body itself: 0 of the 21 points are its own statements 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.
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 · 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). Most of this is not in the body itself: 0 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 41, 100, 126, …). 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 · 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 · 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). Most of this is not in the body itself: 0 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 142, 171, 139). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
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 · ProcessUtils._findVariablesDefinedInProcess (cognitive 20) · ×1
  • ProcessUtils._findVariablesDefinedInProcess (cognitive 20) REDACTED: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 · 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 · useDataRecordsActions.useDataRecordsActions (cognitive 18) · ×1
  • useDataRecordsActions.useDataRecordsActions (cognitive 18) designer/client/src/components/modals/TestingDataRecords/useDataRecordsActions.ts:14 — useDataRecordsActions.useDataRecordsActions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 4, loops 1 (2 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 22, 39, 82, …). 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 · 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 literals inside it that branch (lines 71, 109, 64, …). 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 · 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 · 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. Most of this is not in the body itself: 0 of the 17 points are its own statements 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.
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 · SelectStyled.selectStyled (cognitive 16) · ×1
  • SelectStyled.selectStyled (cognitive 16) designer/client/src/stylesheets/SelectStyled.ts:9 — SelectStyled.selectStyled has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10 (14 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 35, 24, 10, …). 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 · 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. Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 11). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · 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 · 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 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.
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · 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 (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 (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 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.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 325 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 33, cognitive 8) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 8) designer/client/src/reducers/graph/reducer.ts:170 — (anonymous) has cyclomatic complexity 33 and cognitive complexity 8; 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) REDACTED: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 testingReducer (cyclomatic 19, cognitive 8) · ×1
  • Complex function testingReducer (cyclomatic 19, cognitive 8) designer/client/src/reducers/graph/testing.ts:59 — testingReducer has cyclomatic complexity 19 and cognitive complexity 8; 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) designer/client/src/components/graph/node-modal/NodeSwitcherUtils.tsx: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.
R2 · Cyclomatic Complexity · Complex function NodeDetails (cyclomatic 16, cognitive 3) · ×1
  • Complex function NodeDetails (cyclomatic 16, cognitive 3) designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:48 — NodeDetails has cyclomatic complexity 16 and cognitive complexity 3; 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.
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 · Unused dependency 'd3-transition' · ×1
  • Unused dependency 'd3-transition' — Declared in designer/client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'glob' · ×1
  • Unused dependency 'glob' — Declared in designer/client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'moment-duration-format' · ×1
  • Unused dependency 'moment-duration-format' — Declared in designer/client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 26 finding(s)
D30 · Dependency Vulnerabilities · Low CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
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/node/NodeContent/TestingContentElements/TestCaseSelect/TestCaseSelect.tsx, 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 (+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.
D19 · Documentation Quality · Documentation · ×2
  • Documentation: no project overview README.md — The first paragraph under 'What is Nussknacker' states what the project does but gives no overview of what it is and its scope (e.g. whether it is a tool, library, or service). Add an overview section that explains what Nussknacker is, its main value proposition, and which tiers it serves.
  • Documentation: no project overview docs/integrations/openAPI.md — The OpenAPI integration guide begins with metadata but does not state what the project does or what it integrates beyond describing OpenAPI specs. Add a one-line overview stating that Nussknacker reads OpenAPI interfaces and generates enricher components for each operation.
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 1019 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 1019 of the 2660 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.
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 — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (112761 LoC, 4838 public types across 395 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 · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 371 of 1019 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 1019 of the 2660 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: 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, 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, utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/SwaggerTyped.scala, scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/BuiltInNodeCompiler.scala (and 363 more). 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.
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`.
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 designer/server/src/main/resources/defaultDesignerConfig.conf:47 — No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. This is reported because `defaultDesignerConfig.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.)
Minor — 6 finding(s)
D12 · Dependency Hygiene · Outdated · ×6
  • Outdated: com.auth0:jwks-rsa — `com.auth0 %% jwks-rsa` is declared at 0.22.2 in build.sbt, 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 build.sbt, but 1.13.7 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: org.apache.xmlgraphics:fop — `org.apache.xmlgraphics %% fop` is declared at 2.9 in build.sbt, but 2.11 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.9 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.questdb:questdb — `org.questdb %% questdb` is declared at 7.4.2 in build.sbt, but 10.0.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 7.4.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.semver4j:semver4j — `org.semver4j %% semver4j` is declared at 5.4.0 in build.sbt, but 6.0.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 5.4.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: tech.allegro.schema.json2avro:converter — `tech.allegro.schema.json2avro %% converter` is declared at 0.2.15 in build.sbt, but 0.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.2.15 until the declaration is edited — there is no lockfile refresh that would move it.

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-c61438ffd0fb4ea693eba408eb100d73/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-c61438ffd0fb4ea693eba408eb100d73/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 .95artifacts/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-update129artifacts/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 .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 01a0e967-c9f1-7732-ae78-6d2cbc3aac0e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 211 · Warnings: 1243 · Recommendations: 26 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 28-09-2026 @ 19:04 UTC.

Downloadable artifacts

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

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