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

Ahoo-Wang/Wow

Measured 10 November 2026, 01:36 UTC, at code version dd95d43

CAI score 64out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 8 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 405,735 lines of product code in 73 projects, tests not counted · Estimated rebuild effort: about 6.7 person-years · Weakest lens: Security and Compliance, 55

Findings by how serious they are

168 critical 962 serious 264 minor

11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
10 November 2026, 01:36 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

94of 94 dimensions measured by tools.
1241of 1394 findings point to an exact file and line, so you can open each one in the code. The other 153 concern the repository as a whole, such as missing documentation.
94dimensions across 7 lenses, read from 405,735 lines of product code in 73 projects.
Chapters

Executive summary

Ahoo-Wang/Wow falls short of our standard for production because it has passwords or keys in the code's history and pipeline tools referenced by a changeable name. It scores 64 out of 100 and is rated Adequate, and 167 of its 168 critical findings are security problems.

Security and Compliance, at 55, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the security flaws the scanner found, worth about 2 points. Replacing the 59 passwords or keys found in the code's history comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 70.

Seventy-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixty-four passwords or keys are open to anyone who can read the repository, and eleven weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, replacing each exposed password or key and fixing the weaknesses the scanner points to would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and the 11 unsafe settings in infrastructure or container files need changing to safe values. The inner part of the code that depends on an outer part needs turning around so it points inward.

The product code is 405,735 lines, about €980,000 to rebuild.

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

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

If Security and Compliance rose from 55 to 70, the lowest score rated Strong, the score would rise from 64 to about 70.

Code composition: what the lines of code are
Product code 48%Tests 52%
New since the last survey: 256 findings

These 256 critical or serious findings weren't in the previous survey, on 22 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · ClickHouseFilterCompiler.compile (cyclomatic 35) backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseFilterCompiler.kt
  • Cyclomatic Complexity · InMemoryFilters.compare (cyclomatic 29) query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt
  • Cyclomatic Complexity · DashboardPanelCard.DashboardPanelCard (cyclomatic 28) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx
  • Cyclomatic Complexity · kotlinDuration.parseDefault (cyclomatic 27) platform/ops/console/src/views/kotlinDuration.ts
  • Cyclomatic Complexity · datasetRecord.notJsonAt (cyclomatic 26) platform/analytics/catalog/console/src/detail/datasetRecord.ts
  • Cyclomatic Complexity · issueNames.analysisIssueNamer.<returned closure> (cyclomatic 23) typescript/wow-view-engine/src/ui/analysis/issueNames.ts
  • Cyclomatic Complexity · kotlinDuration.parseIso (cyclomatic 22) platform/ops/console/src/views/kotlinDuration.ts
  • Cyclomatic Complexity · manifestClients.emitCommandClient (cyclomatic 21) typescript/wow-generator/src/emitters/manifestClients.ts
  • Cyclomatic Complexity · ReferenceLabels.want (cyclomatic 20) typescript/wow-view-engine/src/runtime/referenceLabels.ts
  • Cyclomatic Complexity · manifestClients.commandMethods (cyclomatic 19) typescript/wow-generator/src/emitters/manifestClients.ts
  • Cyclomatic Complexity · wire-literals.wireLiterals (cyclomatic 19) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cyclomatic Complexity · DashboardPanelCard.PanelHeader (cyclomatic 19) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx
  • Cyclomatic Complexity · analyze.aggregateModel.commands (cyclomatic 18) typescript/wow-generator/src/manifest/analyze.ts
  • Cyclomatic Complexity · wire-literals.wireVocabularies (cyclomatic 18) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cyclomatic Complexity · document.validateManifest (cyclomatic 16) typescript/wow-generator/src/manifest/document.ts
  • Cyclomatic Complexity · ActionButtons.RowActionButtons (cyclomatic 16) typescript/wow-view-engine/src/ui/actions/ActionButtons.tsx
  • Cyclomatic Complexity · SortSettings.SortSettings (cyclomatic 16) typescript/wow-view-engine/src/ui/sort/SortSettings.tsx
  • Cyclomatic Complexity · Failure.code (cyclomatic 16) typescript/wow-view-store/src/errors.ts
  • Cognitive Complexity · kotlinDuration.parseDefault (cognitive 42) platform/ops/console/src/views/kotlinDuration.ts
  • Cognitive Complexity · kotlinDuration.parseIso (cognitive 40) platform/ops/console/src/views/kotlinDuration.ts
  • Cognitive Complexity · issueNames.analysisIssueNamer.<returned closure> (cognitive 32) typescript/wow-view-engine/src/ui/analysis/issueNames.ts
  • Cognitive Complexity · datasetRecord.notJsonAt (cognitive 29) platform/analytics/catalog/console/src/detail/datasetRecord.ts
  • Cognitive Complexity · ReferenceLabels.want (cognitive 26) typescript/wow-view-engine/src/runtime/referenceLabels.ts
  • Cognitive Complexity · wire-literals.slotValues (cognitive 20) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cognitive Complexity · DashboardPanelCard.DashboardPanelCard (cognitive 20) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx
  • Cognitive Complexity · EntityTags.parse (cognitive 19) edge/http/src/main/kotlin/me/ahoo/wow/http/EntityTags.kt
  • Cognitive Complexity · manifestClients.commandMethods (cognitive 19) typescript/wow-generator/src/emitters/manifestClients.ts
  • Cognitive Complexity · typeText.compound (cognitive 18) typescript/wow-generator/src/manifest/typeText.ts
  • Cognitive Complexity · summaries.storedSummaries (cognitive 18) typescript/wow-view-engine/src/runtime/summaries.ts
  • Cognitive Complexity · wire-literals.wireVocabularies::visit (cognitive 18) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cognitive Complexity · wire-literals.enumsNamed::visit (cognitive 18) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cognitive Complexity · NineXEventSource.tagged (cognitive 17) migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/NineXEventSource.kt
  • Cognitive Complexity · SubscriptionWorker.runRetry (cognitive 17) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt
  • Cognitive Complexity · aggregate.summarise (cognitive 17) typescript/wow-view-engine/src/testing/aggregate.ts
  • Cognitive Complexity · SortSettings.SortSettings (cognitive 17) typescript/wow-view-engine/src/ui/sort/SortSettings.tsx
  • Cognitive Complexity · EmbeddedView.EmbeddedData (cognitive 17) typescript/wow-view-engine/src/ui/EmbeddedView.tsx
  • Cognitive Complexity · Comparison.compareBound (cognitive 16) compiler/manifest-tools/src/main/kotlin/me/ahoo/wow/manifest/tools/SchemaCompatibility.kt
  • Cognitive Complexity · analyze.aggregateModel.commands (cognitive 16) typescript/wow-generator/src/manifest/analyze.ts
  • Cognitive Complexity · actions.nextChange (cognitive 16) typescript/wow-view-engine/src/runtime/actions.ts
  • Cognitive Complexity · wire-literals.admitted (cognitive 16) typescript/wow-view-engine/scripts/wire-literals.mjs
  • Cognitive Complexity · wire-literals.wireLiterals (cognitive 16) typescript/wow-view-engine/scripts/wire-literals.mjs
  • God Classes · FileTooLong: query/AggregationQuery.kt api/query-api/src/main/kotlin/me/ahoo/wow/api/query/AggregationQuery.kt
  • God Classes · ClassTooLong: QueryViolation query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryViolation.kt
  • God Classes · FileTooLong: query/RelativeTimeFilters.kt api/query-api/src/main/kotlin/me/ahoo/wow/api/query/RelativeTimeFilters.kt
  • God Classes · TooManyMethods: QueryResolver query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt
  • God Classes · FunctionTooLong: analyze.aggregateModel typescript/wow-generator/src/manifest/analyze.ts
  • God Classes · TooManyMethods: AggregateModelBuilder core/kernel/src/main/kotlin/me/ahoo/wow/kernel/AggregateModelDsl.kt
  • God Classes · FileTooLong: schema/QueryViolation.kt query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryViolation.kt
  • God Classes · FileTooLong: admission/CommandGateway.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt
  • God Classes · TooManyMethods: SubscriptionRuntime core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionRuntime.kt
  • God Classes · FileTooLong: emitters/manifestClients.ts typescript/wow-generator/src/emitters/manifestClients.ts
  • God Classes · ClassTooLong: PartitionOwnership core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt
  • God Classes · FileTooLong: migrate/MigrateData.kt migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrateData.kt
  • God Classes · TooManyMethods: PartitionOwnership core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt
  • God Classes · FunctionTooLong: analysis.narrowAggregation typescript/wow-view-engine/src/capabilities/analysis.ts
  • God Classes · FunctionTooLong: ActionButtons.RowActionButtons typescript/wow-view-engine/src/ui/actions/ActionButtons.tsx
  • God Classes · TooManyMethods: QueryHandler edge/http/src/main/kotlin/me/ahoo/wow/http/query/QueryHandler.kt
  • God Classes · FunctionTooLong: DatasetWorkbench.DatasetWorkbench typescript/wow-view-engine/src/ui/DatasetWorkbench.tsx
  • God Classes · TooManyMethods: Builder query/query/src/main/kotlin/me/ahoo/wow/query/engine/QueryEngine.kt
  • God Classes · FunctionTooLong: validateFields.validateFields typescript/wow-view-engine/src/runtime/validateFields.ts
  • God Classes · FileTooLong: cluster/PartitionOwnership.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt
  • God Classes · FileTooLong: wait/WaitCoordinator.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt
  • God Classes · ClassTooLong: MongoNineXEventSource migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MongoNineXEventSource.kt
  • Code Duplication · Duplicated block (11 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt
  • Code Duplication · Duplicated block (8 lines × 2) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt
  • Code Duplication · Duplicated block (8 lines × 2) platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferences.kt
  • Code Duplication · Duplicated block (7 lines × 3) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/aggregate/AccessResolver.kt
  • Code Duplication · Duplicated block (7 lines × 2) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt
  • Code Duplication · Duplicated block (5–6 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt
  • Code Duplication · Duplicated block (6 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt
  • Code Duplication · Duplicated block (5 lines × 2) backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseDatasetAccess.kt
  • Code Duplication · Duplicated block (7 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/Admission.kt
  • Code Duplication · Duplicated block (6 lines × 2) edge/client/src/main/kotlin/me/ahoo/wow/client/HttpQueryApi.kt
  • Code Duplication · Duplicated block (5 lines × 2) platform/view-store/view-store-server/src/main/kotlin/me/ahoo/wow/viewstore/server/QueriedViewReads.kt
  • Code Duplication · Duplicated block (8 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLogTables.kt
  • Code Duplication · Duplicated block (7 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt
  • Code Duplication · Duplicated block (5 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt
  • Code Duplication · Duplicated block (5 lines × 2) edge/http/src/main/kotlin/me/ahoo/wow/http/PeerReadRoutes.kt
  • Code Duplication · Duplicated block (5 lines × 2) query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt
  • Code Duplication · Duplicated block (8 lines × 3) examples/eshop/catalog/catalog-server/src/main/kotlin/me/ahoo/wow/example/eshop/catalog/server/CatalogAuthorization.kt
  • Test Quality · No assertions: list every member of the union, and nothing else typescript/wow-view-engine/test/choiceLists.test.ts
  • Test Quality · No assertions: keep a field metric type one a metric has typescript/wow-view-engine/test/choiceLists.test.ts
  • Test Quality · No assertions: refuses an operation that is not its kind's typescript/wow-view-engine/test/hostErrors.test.tsx
  • Test Quality · No assertions: names every store method but the synchronous `permissions` typescript/wow-view-engine/test/hostErrors.test.tsx
  • Test Quality · No assertions: are typed by their values, so a config stays plain JSON typescript/wow-view-engine/test/wire.test.ts
  • Test Quality · No assertions: defaults every hook to its filter request type typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: accepts filter request subtypes typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: takes a query client cursor and aggregate method as execute typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: refuses a cursor in the cursor hook's query: the hook owns it typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: streams records into items, position and done in place of result typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: reads a cursor page by page into items, hasMore and fetchNext typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: reports an Error, and a Wow service's answer as problem typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: returns the records of a stream as items, never the stream itself typescript/wow-react/test/streamTypes.test.ts
  • Test Quality · No assertions: takes the stream options, resume included typescript/wow-react/test/streamTypes.test.ts
  • Test Quality · No assertions: takes a query client streamRows method as execute typescript/wow-react/test/streamTypes.test.ts
  • Test Quality · No assertions: types a record access by the aggregate, and an event stream with its owner and space typescript/wow-client/test/access.test.ts
  • Test Quality · No assertions: names the access attributes a query may filter on, where the aggregate's contract allows typescript/wow-client/test/access.test.ts
  • Test Quality · No assertions: types what send and wait answer as a result that succeeded, and a rejection as one that may name no id typescript/wow-client/test/client.test.ts
  • Test Quality · No assertions: say whether a value may be null and what it means alike typescript/wow-client/test/dsl/descriptor.test.ts
  • Churn × Complexity Hotspots · Hotspot: typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx

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

Fixed since the last survey: 565 findings

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

  • Cyclomatic Complexity · validate_wow_skills._validate_suite (cyclomatic 64) scripts/validate_wow_skills.py
  • Cyclomatic Complexity · validate_wow_skills._validate_resources (cyclomatic 34) scripts/validate_wow_skills.py
  • Cyclomatic Complexity · InMemoryFilters.field (cyclomatic 29) query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt
  • Cyclomatic Complexity · validate_wow_skills.validate_repository (cyclomatic 29) scripts/validate_wow_skills.py
  • Cyclomatic Complexity · issueNames.analysisIssueNamer (cyclomatic 27) typescript/wow-view-engine/src/ui/analysis/issueNames.ts
  • Cyclomatic Complexity · DashboardPanel.DashboardPanel (cyclomatic 24) typescript/wow-view-engine/src/ui/dashboard/DashboardPanel.tsx
  • Cyclomatic Complexity · migrate.intoDefaults (cyclomatic 20) typescript/wow-view-engine/src/dashboard/migrate.ts
  • Cyclomatic Complexity · DashboardPanel.PanelHeader (cyclomatic 19) typescript/wow-view-engine/src/ui/dashboard/DashboardPanel.tsx
  • Cyclomatic Complexity · validate_wow_skills._validate_openai_yaml (cyclomatic 17) scripts/validate_wow_skills.py
  • Cyclomatic Complexity · issueNames.recordIssueNamer (cyclomatic 16) typescript/wow-view-engine/src/ui/record/issueNames.ts
  • Cognitive Complexity · validate_wow_skills._validate_suite (cognitive 128) scripts/validate_wow_skills.py
  • Cognitive Complexity · validate_wow_skills._validate_resources (cognitive 62) scripts/validate_wow_skills.py
  • Cognitive Complexity · validate_wow_skills.validate_repository (cognitive 39) scripts/validate_wow_skills.py
  • Cognitive Complexity · issueNames.analysisIssueNamer (cognitive 35) typescript/wow-view-engine/src/ui/analysis/issueNames.ts
  • Cognitive Complexity · migrate.intoDefaults (cognitive 27) typescript/wow-view-engine/src/dashboard/migrate.ts
  • Cognitive Complexity · ParkedOps.list (cognitive 21) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/node/ParkedOps.kt
  • Cognitive Complexity · validate_wow_skills._validate_filesystem_paths (cognitive 19) scripts/validate_wow_skills.py
  • Cognitive Complexity · validate_wow_skills._validate_openai_yaml (cognitive 19) scripts/validate_wow_skills.py
  • Cognitive Complexity · eval-skills.behaviorMetrics (cognitive 18) scripts/eval-skills.mjs
  • Cognitive Complexity · DashboardPanel.DashboardPanel (cognitive 18) typescript/wow-view-engine/src/ui/dashboard/DashboardPanel.tsx
  • Cognitive Complexity · SubscriptionWorker.runResume (cognitive 16) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt
  • God Classes · ClassTooLong: ServiceNode core/runtime/src/main/kotlin/me/ahoo/wow/runtime/node/ServiceNode.kt
  • God Classes · FileTooLong: node/ServiceNode.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/node/ServiceNode.kt
  • God Classes · FunctionTooLong: useAnalysisResult.useAnalysisResult typescript/wow-view-engine/src/react/useAnalysisResult.ts
  • God Classes · TooManyMethods: MongoEventLog backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt
  • God Classes · TooManyMethods: QueryResolver query/query/src/main/kotlin/me/ahoo/wow/query/QueryResolver.kt
  • God Classes · FunctionTooLong: useViewManager.useViewManager typescript/wow-view-engine/src/react/useViewManager.ts
  • God Classes · ClassTooLong: ModelSymbolProcessor compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/ModelSymbolProcessor.kt
  • God Classes · TooManyMethods: ModelSymbolProcessor compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/ModelSymbolProcessor.kt
  • God Classes · FileTooLong: model/ModelSymbolProcessor.kt compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/ModelSymbolProcessor.kt
  • God Classes · FunctionTooLong: useRecordExport.useRecordExport typescript/wow-view-engine/src/react/useRecordExport.ts
  • God Classes · FileTooLong: scripts/validate_wow_skills.py scripts/validate_wow_skills.py
  • Code Duplication · Duplicated block (11 lines × 2) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt
  • Code Duplication · Duplicated block (8 lines × 2) platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/AnalyticsCatalogCallers.kt
  • Code Duplication · Duplicated block (8 lines × 2) platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferences.kt
  • Code Duplication · Duplicated block (7 lines × 3) platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/PublicCallersFirst.kt
  • Code Duplication · Duplicated block (7 lines × 2) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/SubscriptionResolver.kt
  • Code Duplication · Duplicated block (5 lines × 2) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/SubscriptionResolver.kt
  • Code Duplication · Duplicated block (5 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt
  • Code Duplication · Duplicated block (5 lines × 2) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/ModelProviderSource.kt
  • Code Duplication · Duplicated block (6 lines × 2) edge/client/src/main/kotlin/me/ahoo/wow/client/HttpQueryApi.kt
  • Code Duplication · Duplicated block (7 lines × 8) example/eshop/basket/basket-server/src/main/kotlin/me/ahoo/wow/example/eshop/basket/server/PostgresDataSource.kt
  • Code Duplication · Duplicated block (5 lines × 2) query/query/src/main/kotlin/me/ahoo/wow/query/RecordAdmission.kt
  • Code Duplication · Duplicated block (7 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt
  • Code Duplication · Duplicated block (5 lines × 2) query/query/src/main/kotlin/me/ahoo/wow/query/QueryResolver.kt
  • Code Duplication · Duplicated block (8 lines × 3) example/eshop/basket/basket-server/src/main/kotlin/me/ahoo/wow/example/eshop/basket/server/BasketCallers.kt
  • Test Quality · No assertions: returns the rows of a stream as items, never the stream itself typescript/wow-react/test/listStreamTypes.test.ts
  • Test Quality · No assertions: sets its own result extractor and Accept header on the endpoint hook typescript/wow-react/test/listStreamTypes.test.ts
  • Test Quality · No assertions: takes a query client stream method as execute typescript/wow-react/test/listStreamTypes.test.ts
  • Test Quality · No assertions: takes the endpoint and the Fetcher in place of execute typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: streams rows into items and done in place of result typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: reports an Error unless told otherwise typescript/wow-react/test/hookContract.types.test.ts
  • Test Quality · No assertions: defaults custom-executor hooks to filter request subtypes typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: defaults Fetcher hooks to filter request subtypes typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: accepts filter request subtypes in custom-executor hooks typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: accepts filter request subtypes in Fetcher hooks typescript/wow-react/test/filterQueryTypes.test.ts
  • Test Quality · No assertions: runs a cursor query through useSingleQuery until a cursor hook exists typescript/wow-react/test/filterQueryTypes.test.ts
  • Churn × Complexity Hotspots · Hotspot: typescript/wow-view-engine/src/ui/dashboard/DashboardPanel.tsx typescript/wow-view-engine/src/ui/dashboard/DashboardPanel.tsx
  • Churn × Complexity Hotspots · Hotspot: typescript/wow-view-engine/src/dashboard/migrate.ts typescript/wow-view-engine/src/dashboard/migrate.ts
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/ui/analysis/HavingRows.tsx typescript/wow-view-engine/src/ui/analysis/HavingRows.tsx
  • Churn × Complexity Hotspots · Repeated repair: core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/ClusterOptions.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/ClusterOptions.kt
  • Churn × Complexity Hotspots · Repeated repair: core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/CommandRouter.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/CommandRouter.kt
  • Churn × Complexity Hotspots · Repeated repair: edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpSignalSender.kt edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpSignalSender.kt
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/filter/kinds/metadata.ts typescript/wow-view-engine/src/filter/kinds/metadata.ts
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/filter/kinds/enum.ts typescript/wow-view-engine/src/filter/kinds/enum.ts
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/filter/kinds/reference.ts typescript/wow-view-engine/src/filter/kinds/reference.ts
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/filter/kinds/number.ts typescript/wow-view-engine/src/filter/kinds/number.ts
  • Churn × Complexity Hotspots · Repeated repair: backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresFormat.kt backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresFormat.kt
  • Churn × Complexity Hotspots · Repeated repair: edge/http/src/main/kotlin/me/ahoo/wow/http/problem/Problem.kt edge/http/src/main/kotlin/me/ahoo/wow/http/problem/Problem.kt
  • Churn × Complexity Hotspots · Repeated repair: typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx
  • Churn × Complexity Hotspots · Repeated repair: host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/InternalServer.kt host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/InternalServer.kt
  • Churn × Complexity Hotspots · Repeated repair: backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/MongoFailures.kt backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/MongoFailures.kt
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/package-lock.json
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/package-lock.json
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/package-lock.json
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/package-lock.json
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED compensation/wow-compensation-dashboard/REDACTED
  • Secrets (history) · High secret: REDACTED deploy/example/perf/config/kafka_redis.yaml
  • Secrets (history) · High secret: REDACTED deploy/example/perf/config/mongo_kafka_redis.yaml
  • Secrets (history) · High secret: REDACTED deploy/example/perf/config/redis.yaml
  • Secrets (history) · REDACTED: REDACTED deploy/example/perf/mongo.yaml
  • Secrets (history) · High secret: REDACTED deploy/example/perf/redis.yaml
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/basket/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
  • Secrets (history) · REDACTED: REDACTED example/eshop/web/src/generated/catalog/.wow-generator.json
Rebuild cost: about €980,000 · Estimate
Cost to rebuild€320,000 to €1,600,000, for 5,407 to 17,154 hours of work, about 6.7 person-years for 4 to 13 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 405,735 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9).
Raises the score by about 2 points · Low effort · Static Analysis (SAST)
2
Resolve the 59 REDACTED finding(s) in Secrets (history) — start with REDACTED (55), REDACTED (4).
Raises the score by about 4 points · Medium effort · Secrets (history)
3
Resolve the 4 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 2 points · Low effort · Kernel & Syscall Confinement

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €980,000 to build again, about 6.7 person-years of work. Its weakest lens is Security and Compliance, at 55 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST). Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 9 Static Analysis (SAST) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch @ahoo-wang/wow-client wow-client @ahoo-wang/wow-generator wow-generator @ahoo-wang/wow-generator->@ahoo-wang/wow-client @ahoo-wang/wow-react wow-react @ahoo-wang/wow-react->@ahoo-wang/wow-client @ahoo-wang/wow-view-engine wow-view-engine @ahoo-wang/wow-view-engine->@ahoo-wang/wow-client @ahoo-wang/wow-view-store wow-view-store @ahoo-wang/wow-view-store->@ahoo-wang/wow-client @ahoo-wang/wow-view-store->@ahoo-wang/wow-view-engine Wow Wow Wow:api:annotations Wow:api:annotations Wow:api:api Wow:api:api Wow:api:manifest Wow:api:manifest Wow:api:query-api Wow:api:query-api Wow:backends:clickhouse Wow:backends:clickhouse Wow:backends:elasticsearch Wow:backends:elasticsearch Wow:backends:kafka Wow:backends:kafka Wow:backends:mongo Wow:backends:mongo Wow:backends:postgres Wow:backends:postgres catalog:catalog-api catalog:catalog-api catalog:catalog-domain catalog:catalog-domain catalog:catalog-domain->catalog:catalog-api catalog:catalog-server catalog:catalog-server catalog:catalog-server->catalog:catalog-domain wow-analytics-catalog-console wow-analytics-catalog-console wow-analytics-catalog-console->@ahoo-wang/wow-client wow-analytics-catalog-console->@ahoo-wang/wow-view-engine wow-analytics-catalog-console->@ahoo-wang/wow-view-store wow-ops-console wow-ops-console wow-ops-console->@ahoo-wang/wow-client wow-ops-console->@ahoo-wang/wow-view-engine __more__ +53 more projects

Architecture: which parts of the code depend on which

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

2003 modules, with 4343 dependencies between them. 31 loops run through 137 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 me.ahoo.wow.api.aggregate2 me.ahoo.wow.api.query3 typescript.wow-client.src.http4 typescript.wow-view-engine.src.model.chart5 typescript.wow-view-engine.src.model.instance6 typescript.wow-view-engine.src.record.project7 typescript.wow-view-engine.src.ui.analysis.DrillMenu8 me.ahoo.wow.api.caller9 me.ahoo.wow.api.result10 me.ahoo.wow.api.schedule11 me.ahoo.wow.query.schema.QueryViolation12 me.ahoo.wow.spi.ledger13 typescript.wow-view-engine.src.filter.fieldKind14 typescript.wow-view-engine.src.model.dashboard15 typescript.wow-view-engine.src.ui.analysis16 typescript.wow-view-engine.src.ui.charts17 typescript.wow-view-engine.src.ui.record18 me.ahoo.wow.api.decide19 me.ahoo.wow.api.read20 me.ahoo.wow.manifest21 me.ahoo.wow.spi.snapshot22 typescript.wow-view-engine.src.analysis23 typescript.wow-view-engine.src.runtime24 typescript.wow-view-engine.src.runtime.viewEngine25 me.ahoo.wow.query.schema26 me.ahoo.wow.spi.log27 typescript.wow-view-engine.src.react28 typescript.wow-view-engine.src.ui.dashboard29 me.ahoo.wow.kernel30 me.ahoo.wow.spi.store31 me.ahoo.wow.migrate32 me.ahoo.wow.query.dataset33 me.ahoo.wow.runtime.admission34 me.ahoo.wow.runtime.subscription35 me.ahoo.wow.query.policy36 me.ahoo.wow.runtime.cluster37 me.ahoo.wow.query.admission38 me.ahoo.wow.runtime.node39 me.ahoo.wow.query40 me.ahoo.wow.spring.boot
1 me.ahoo.wow.api.aggregate
2 me.ahoo.wow.api.query
3 typescript.wow-client.src.http
4 typescript.wow-view-engine.src.model.chart
5 typescript.wow-view-engine.src.model.instance
6 typescript.wow-view-engine.src.record.project
7 typescript.wow-view-engine.src.ui.analysis.DrillMenu
8 me.ahoo.wow.api.caller2
9 me.ahoo.wow.api.result1
10 me.ahoo.wow.api.schedule2
11 me.ahoo.wow.query.schema.QueryViolation2444
12 me.ahoo.wow.spi.ledger3
13 typescript.wow-view-engine.src.filter.fieldKind1
14 typescript.wow-view-engine.src.model.dashboard1
15 typescript.wow-view-engine.src.ui.analysis314
16 typescript.wow-view-engine.src.ui.charts218
17 typescript.wow-view-engine.src.ui.record54
18 me.ahoo.wow.api.decide3212
19 me.ahoo.wow.api.read91031
20 me.ahoo.wow.manifest1
21 me.ahoo.wow.spi.snapshot611
22 typescript.wow-view-engine.src.analysis541910
23 typescript.wow-view-engine.src.runtime43451
24 typescript.wow-view-engine.src.runtime.viewEngine31
25 me.ahoo.wow.query.schema6431513
26 me.ahoo.wow.spi.log7122
27 typescript.wow-view-engine.src.react242617
28 typescript.wow-view-engine.src.ui.dashboard1492
29 me.ahoo.wow.kernel507762914818
30 me.ahoo.wow.spi.store113
31 me.ahoo.wow.migrate14171133176
32 me.ahoo.wow.query.dataset81916145
33 me.ahoo.wow.runtime.admission187541113
34 me.ahoo.wow.runtime.subscription115121199
35 me.ahoo.wow.query.policy88114228
36 me.ahoo.wow.runtime.cluster6225151
37 me.ahoo.wow.query.admission21926235
38 me.ahoo.wow.runtime.node119416272142619
39 me.ahoo.wow.query3242243
40 me.ahoo.wow.spring.boot13521485418185722120
Uses a module listed above itPart of a loopThe module itself
1 me.ahoo.wow.api.aggregate2 me.ahoo.wow.api.query3 typescript.wow-client.src.http4 typescript.wow-view-engine.src.model.chart5 typescript.wow-view-engine.src.model.instance6 typescript.wow-view-engine.src.record.project7 typescript.wow-view-engine.src.ui.analysis.DrillMenu8 me.ahoo.wow.api.caller9 me.ahoo.wow.api.result10 me.ahoo.wow.api.schedule11 me.ahoo.wow.query.schema.QueryViolation12 me.ahoo.wow.spi.ledger13 typescript.wow-view-engine.src.filter.fieldKind14 typescript.wow-view-engine.src.model.dashboard15 typescript.wow-view-engine.src.ui.analysis16 typescript.wow-view-engine.src.ui.charts17 typescript.wow-view-engine.src.ui.record18 me.ahoo.wow.api.decide19 me.ahoo.wow.api.read20 me.ahoo.wow.manifest21 me.ahoo.wow.spi.snapshot22 typescript.wow-view-engine.src.analysis23 typescript.wow-view-engine.src.runtime24 typescript.wow-view-engine.src.runtime.viewEngine25 me.ahoo.wow.query.schema26 me.ahoo.wow.spi.log27 typescript.wow-view-engine.src.react28 typescript.wow-view-engine.src.ui.dashboard29 me.ahoo.wow.kernel30 me.ahoo.wow.spi.store31 me.ahoo.wow.migrate32 me.ahoo.wow.query.dataset33 me.ahoo.wow.runtime.admission34 me.ahoo.wow.runtime.subscription35 me.ahoo.wow.query.policy36 me.ahoo.wow.runtime.cluster37 me.ahoo.wow.query.admission38 me.ahoo.wow.runtime.node39 me.ahoo.wow.query40 me.ahoo.wow.spring.bootme.ahoo.wow.api.aggregate1me.ahoo.wow.api.query2typescript.wow-client.src.http3typescript.wow-view-engine.src.model.chart4typescript.wow-view-engine.src.model.instance5typescript.wow-view-engine.src.record.project6typescript.wow-view-engine.src.ui.analysis.DrillMenu7me.ahoo.wow.api.caller8me.ahoo.wow.api.result9me.ahoo.wow.api.schedule10me.ahoo.wow.query.schema.QueryViolation11me.ahoo.wow.spi.ledger12typescript.wow-view-engine.src.filter.fieldKind13typescript.wow-view-engine.src.model.dashboard14typescript.wow-view-engine.src.ui.analysis15typescript.wow-view-engine.src.ui.charts16typescript.wow-view-engine.src.ui.record17me.ahoo.wow.api.decide18me.ahoo.wow.api.read19me.ahoo.wow.manifest20me.ahoo.wow.spi.snapshot21typescript.wow-view-engine.src.analysis22typescript.wow-view-engine.src.runtime23typescript.wow-view-engine.src.runtime.viewEngine24me.ahoo.wow.query.schema25me.ahoo.wow.spi.log26typescript.wow-view-engine.src.react27typescript.wow-view-engine.src.ui.dashboard28me.ahoo.wow.kernel29me.ahoo.wow.spi.store30me.ahoo.wow.migrate31me.ahoo.wow.query.dataset32me.ahoo.wow.runtime.admission33me.ahoo.wow.runtime.subscription34me.ahoo.wow.query.policy35me.ahoo.wow.runtime.cluster36me.ahoo.wow.query.admission37me.ahoo.wow.runtime.node38me.ahoo.wow.query39me.ahoo.wow.spring.boot4021224443113142185432129103116115419104345131643151371222426171492507762914818113141711331768191614518754111311512119988114228622515121926235119416272142619324224313521485418185722120+1963 more modules (most-connected shown)

At a glance — Code Health · 70% · Adequate · gated by R3 ·

At a glance — Architecture · 85% · Strong ·

At a glance — Maturity · 80% · Strong ·

At a glance — Readiness · 68% · Adequate · gated by P3 ·

At a glance — Security · 55% · Adequate · gated by D28, D29, D36 ·

At a glance — Accessibility · 85% · Strong ·

At a glance — Performance · 73% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection94High / Critical
A07:2025 — Authentication Failures65High / Critical
A02:2025 — Security Misconfiguration43High / Critical
A03:2025 — Software Supply Chain Failures8High / Critical

Roadmap

Top priorities: Resolve the 59 REDACTED finding(s) in Secrets (history) — start with REDACTED (55), REDACTED (4); Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9); Resolve the 4 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED.

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

Do thisHelpsEffortDimension
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9).+2.1 ptsLowStatic Analysis (SAST)
Resolve the 59 REDACTED finding(s) in Secrets (history) — start with REDACTED (55), REDACTED (4).+4.1 ptsMediumSecrets (history)
Resolve the 4 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED.+1.8 ptsLowKernel & Syscall Confinement
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.1 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.1 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.1 ptsLowSupply-chain Provenance & Signing
Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED.+0.9 ptsLowSecrets (history)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+0.9 ptsLowStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED1.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.8SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedSecrets (history): REDACTED: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx5.9MixedCyclomatic Complexity: DashboardGrid.DashboardGrid (cyclomatic 48)
typescript/wow-view-engine/src/ui/charts/Cartesian.tsx5.9MixedCyclomatic Complexity: Cartesian.Cartesian (cyclomatic 34)
typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx5.9MixedCyclomatic Complexity: ColumnRow.ColumnRow (cyclomatic 31)
typescript/wow-view-engine/src/ui/record/RecordPagination.tsx5.9MixedCyclomatic Complexity: RecordPagination.RecordPagination (cyclomatic 23)

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

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

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

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

Could not be resolved — 11

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 94 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 94 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D17D19D20D23D24D26D28D29D30D31D34D35D36D37D40D41D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P5P6P7PF1PF3R1R10R11R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X4X5

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, 1241 of 1394 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 or a scanner, 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
Canine Code Analyzer 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 · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1c319-0a81-7b25-abfc-a9c11d78890b.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .mts, .ts, .tsx, .kt, and our analyzer cannot run the .kt 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 22.8% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or JaCoCo XML — the Gradle `jacocoTestReport` task) 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 (JaCoCo XML — the Gradle `jacocoTestReport` task) 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 7,614 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 1,383 test source file(s) (.kt, .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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .kt, and the jvm executor ran against the .kt half and did not finish re-running within its tier budget — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in documentation/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/eshop/web/ (7 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in platform/analytics/catalog/console/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in platform/ops/console/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/integration-test/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/storybook/ (83 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/wow-client/ (566 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/wow-generator/ (673 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/wow-react/ (3 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/wow-view-engine/ (7 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in typescript/wow-view-store/ (126 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in documentation/ was NOT MEASURED: the node:test run in documentation/ produced no per-test report (throw new Error(). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (7 contributor(s) across 8065 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 6 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D31 IaC & Container Security — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.github/scripts/breaking-label.mjs`, `.github/scripts/release-admission.mjs`, `api/api/src/main/kotlin/me/ahoo/wow/api/wire/WaitHeader.kt`, `api/manifest/src/main/kotlin/me/ahoo/wow/manifest/AccessAttributeName.kt`, `api/query-api/src/main/kotlin/me/ahoo/wow/api/query/AggregationQuery.kt`, … (+237 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Deploy/helm/wow-service/templates/deployment.yaml:4 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (platform/view-store/view-store-server/Dockerfile). docker build failed (exit 1) — 27b1a: failed to resolve source metadata for dragonwell-registry.cn-hangzhou.cr.aliyuncs.com/dragonwell/dragonwell:25-ubuntu@sha256:6490a55d94a6ba1dcf88f8a1de8a5d67f5cf0fac717c1d84f18933516bd27b1a: failed to do request: Head "https://dragonwell-registry.cn-hangzhou.cr.aliyuncs.com/v2/dragonwell/dragonwell/manifests/sha256:6490a55d94a6ba1dcf88f8a1de8a5d67f5cf0fac717c1d84f18933516bd27b1a": Forbidden; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 195 further occurrence(s) are not listed individually; the score already reflects all 235.
  • R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.

Repo exclusion declarations: 26 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
  • D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity5.9 / 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.9 / 10 · rule-coverage 100% · ceiling Prevented

164 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was generate.generateRetail.project at 107. A further 16 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 FilterExpressionJsonKt.filterType at 54 — they are counted neither in the figure above nor in this dimension's score. 12 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: core/spi/src/main/kotlin/me/ahoo/wow/spi/json/query/FilterExpressionJson.kt (FilterExpressionJsonKt.filterType at 54), query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt (QueryResolver.filter at 40), query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryFieldAliases.kt (QueryFieldAliases.filter at 38), backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt (ElasticsearchIndexMappingResolverKt.nullValue at 21), query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryValueDomains.kt (QueryValueDomainsKt.copyTemporal at 20), and 7 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.

generate.generateRetail.project (cyclomatic 107)typescript/storybook/stories/view-engine/retail/generate.ts:1476
check.checkTheme (cyclomatic 84)typescript/wow-view-engine/theme-check/check.ts:132
AnalysisTable.AnalysisTable (cyclomatic 67)typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121
WorkbenchShell.WorkbenchShell (cyclomatic 64)typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344
EChart.EChart (cyclomatic 60)typescript/wow-view-engine/src/ui/charts/EChart.tsx:205

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with generate.generateRetail.project (cyclomatic 107), check.checkTheme (cyclomatic 84), AnalysisTable.AnalysisTable (cyclomatic 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

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

197 method(s) exceeded the cognitive complexity threshold of 15; the worst was generate.generateRetail.project at 146.

generate.generateRetail.project (cognitive 146)typescript/storybook/stories/view-engine/retail/generate.ts:1476
generate.generateRetail (cognitive 143)typescript/storybook/stories/view-engine/retail/generate.ts:766
check.checkTheme (cognitive 139)typescript/wow-view-engine/theme-check/check.ts:132
AnalysisTable.AnalysisTable (cognitive 62)typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121
DashboardGrid.DashboardGrid (cognitive 62)typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:167

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with generate.generateRetail.project (cognitive 146), generate.generateRetail (cognitive 143), check.checkTheme (cognitive 139). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes8.5 / 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.5 / 10 · rule-coverage 100% · ceiling Prevented

143 god class(es) detected.

FunctionTooLong: generate.generateRetail.project · ×94typescript/storybook/stories/view-engine/retail/generate.ts:1476
FileTooLong: retail/generate.ts · ×21typescript/storybook/stories/view-engine/retail/generate.ts
TooManyMethods: AggregationQueryDsl · ×16api/query-api/src/main/kotlin/me/ahoo/wow/api/query/dsl/AggregationQueryDsl.kt:47
ClassTooLong: Kernel · ×10core/kernel/src/main/kotlin/me/ahoo/wow/kernel/Kernel.kt:158
MethodTooLong: CommandGateway.admit · ×2core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:413

What to do

  1. Resolve the 94 FunctionTooLong finding(s) in God Classes — start with boards.ts (3), MetricCard.tsx (2), FilterBar.tsx (2). — One of this dimension's main actionable groups (94 warning-level).
  2. Resolve the 21 FileTooLong finding(s) in God Classes — start with generate.ts, views.ts, AggregationQuery.kt. — One of this dimension's main actionable groups (21 warning-level).
  3. Resolve the 16 TooManyMethods finding(s) in God Classes — start with AggregationQueryDsl.kt, FilterDsl.kt, commands.ts. — One of this dimension's main actionable groups (16 warning-level).

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

D4 · Code Duplication10.0 / 10Stronggated by 37 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

37 duplicated block group(s) detected. 2 of the 37 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts, .tsx (58% 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) · ×8backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseDatasetAccess.kt:118
Duplicated block (8 lines × 2) · ×7compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt:411
Duplicated block (6 lines × 2) · ×5backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt:345
Duplicated block (7 lines × 2) · ×4backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt:171
Duplicated block (11 lines × 2) · ×3backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:221

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

What to do

  1. Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ClickHouseDatasetAccess.kt, ViewStoreOpenApi.kt, MongoAggregationWindows.kt. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SubscriptionResolver.kt, ViewPreferences.kt, ElasticsearchEventDocuments.kt. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ElasticsearchIndexMappingResolver.kt, CommandGateway.kt, ViewStoreOpenApi.kt. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

73 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 57 of the 73 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: @ahoo-wang/wow-client

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 of 452 classes have LCOM4 above 3.

Low cohesion: DatasetWording (LCOM4 4)skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/wording/DatasetWording.kt:41

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DatasetWording.kt. — One of this dimension's main actionable groups (1 warning-level).

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

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

7631 test methods: 7590 unit, 11 integration, 0 BDD, 30 e2e. The JavaScript/TypeScript suite contributes 7614 `it`/`test` case(s) across 578 test file(s) declaring at least one beside 3 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 14 test function(s) across 1 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.9 / 10Stronggated by 38 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.9 / 10 · rule-coverage 100% · ceiling Prevented

15 skipped (15 with a documented reason), 38 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 7614 tests. Measured on the JavaScript/TypeScript suite only — at least 1,383 test source file(s) (.kt, .java) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: list every member of the union, and nothing else · ×38typescript/wow-view-engine/test/choiceLists.test.ts:40
Mock-dominated test: hands the drag handlers the library gives it to its button · ×10typescript/wow-view-engine/test/dashboardUi.test.tsx:1117
Skipped (documented): (unnamed test) · ×15typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:375

What to do

  1. Resolve the 38 No assertions finding(s) in Test Quality — start with hookContract.types.test.ts (7), filterQueryTypes.test.ts (4), viewStoreConformance.ts (3). — One of this dimension's main actionable groups (38 warning-level).
  2. Resolve the 10 Mock-dominated test finding(s) in Test Quality — start with logger.test.ts (5), renameInput.test.tsx (2), dashboardUi.test.tsx. — One of this dimension's main actionable groups (10 recommendation-level).

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

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

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 95% · ceiling Verified

This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 437 artifact(s) resolved, 415 of them gradable against Maven Central, and 140 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.

Outdated (compile): org.jetbrains:annotations · ×140

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 27 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 96 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 3 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, 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 149 serious findings✓ 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: typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx (69×64=4416); typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx (50×48=2400); typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx (34×67=2278) Repeated repair below the complexity floor: typescript/wow-view-engine/src/ui/record/columns.ts (13 of 25 changes were fixes); typescript/wow-view-engine/src/filter/validate.ts (9 of 15 changes were fixes); typescript/wow-view-engine/src/ui/filter/inputs/number.tsx (9 of 15 changes were fixes)

Hotspot: typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx · ×130typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344
Repeated repair: typescript/wow-view-engine/src/ui/record/columns.ts · ×19typescript/wow-view-engine/src/ui/record/columns.ts:374

What to do

  1. Resolve the 130 Hotspot finding(s) in Churn × Complexity Hotspots — start with MetricCard.tsx (2), fields.ts (2), WorkbenchShell.tsx. — One of this dimension's main actionable groups (130 warning-level).
  2. Resolve the 19 Repeated repair finding(s) in Churn × Complexity Hotspots — start with validate.ts (2), columns.ts, number.tsx. — One of this dimension's main actionable groups (19 warning-level).

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

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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

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

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

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

2 of 2 documentation facets pass in full. 334 document(s) read across 11 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types leak across context boundaries (6 contexts). Contexts: analytics, compensation, datasetregistry, example, ops, viewstore.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.8 9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

12 of 5527 judged comments only repeat the code they sit on (0.2 %). 381 comment(s) in another language or script were not judged.

redundant comment · ×12platform/analytics/catalog/console/src/setupTests.ts:50
doc comments repeat the names · ×5typescript/wow-client/src/developmentCaller.ts:55

✓ On the Gold path — maintain.

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

D26 · Project Cohesion6.6 / 10Adequate✓ 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.

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

11 of 60 build units (Gradle, npm) 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)0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

D29 · Static Analysis (SAST)0.6 / 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.6 / 10 · rule-coverage 100% · ceiling Documented

94 finding(s): 0 critical, 91 high, 3 medium, 0 low. 76 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 159 file(s) — `.github/ga-e2e/cluster.sh` (line 161, line 176), `.github/scripts/bench.mjs`, `.github/scripts/breaking-label.mjs` (lines 73–78), `.github/scripts/pr-safety.sh` (line 46), `.github/scripts/release-admission.mjs` (lines 163–164), … (+154 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 1 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

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

What to do

  1. Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9). — One of this dimension's main actionable groups (9 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 76 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 (76 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities8.8 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 8.8 / 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 CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D31 · IaC & Container Security4.7 / 10Weak✓ 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 4.7 / 10 · rule-coverage 100% · ceiling Documented

43 finding(s): 0 critical, 11 high, 10 medium, 22 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 1664 of the 2188 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.8 / 10Stronggated by 16 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: zh-CN.ts↔RecordParts.tsx 90%; chart.ts↔analysis.ts 80%; chart.ts↔zh-CN.ts 80%

Change coupling: DashboardWorkbench.tsx ↔ DataWorkbench.tsx · ×13typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:1
Change-coupling hub: zh-CN.ts → chart.ts, chart.ts, useAnalysisEditor.ts, useAnalysisResult.ts, useDashboard.ts, useRecordTable.ts, useWorkbench.ts, project.ts, execute.ts, validateDefinition.ts, DataWorkbench.tsx, EmbeddedView.tsx, AnalysisChart.tsx, ChartPicker.tsx, DataTab.tsx, DisplayTab.tsx, Cartesian.tsx, PieSlices.tsx, family.ts, ColumnRow.tsx, ColumnSettings.tsx, ConditionPill.tsx, FilterValueEditor.tsx, display.ts, ViewManagerRow.tsx, RecordPagination.tsx, SortableHeader.tsx, SummaryRows.tsx, cells.tsx, SortSettings.tsx, AnalysisParts.tsx, RecordParts.tsx, ResultToolbar.tsx · ×3typescript/wow-view-engine/src/ui/messages/zh-CN.ts

What to do

  1. Resolve the 13 Change coupling finding(s) in Change Coupling — start with DashboardWorkbench.tsx, validateDefinition.ts, DataTab.tsx. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with zh-CN.ts, analysis.ts, SortSettings.tsx. — One of this dimension's main actionable groups (3 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

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D40 · Network Egress Confinement10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

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

Kubernetes workloads are covered by a network policy that restricts egress.

✓ On the Gold path — maintain.

Detailed fixes: d40_recommendation.md.

D41 · Kernel & Syscall Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

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

0/4 workload(s) run every container under a seccomp profile; 0/4 declare an AppArmor/SELinux profile.

No seccomp profile · ×4REDACTED:6

What to do

  1. Resolve the 4 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 recommendation-level).

Detailed fixes: d41_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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

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.

AC3 · Page structure6.8 / 10Adequate✓ 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.

  • 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). — platform/analytics/catalog/console/src/detail/DatasetReading.tsx:203

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 semantics10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

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 safety7.1 / 10Strong✓ Tool-verified

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.

  • `.story-app-page:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — typescript/storybook/.storybook/preview.css:510

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement10.0 / 10Exemplary✓ 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.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.2 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

  • `StoredSystemViews` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (warnedClashes; e.g. `warnedClashes` in `warnClash` at line 69). — skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/system/StoredSystemViews.kt:37
  • `CatalogWatcher` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (seen; e.g. `seen` in `look` at line 60). — platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/CatalogWatcher.kt:50
  • `DatasetPublicationWatcher` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (lastFull, watermark, applied; e.g. `lastFull` in `sync` at line 90). — platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/DatasetPublicationWatcher.kt:62
  • `CommandGateway` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (rejectedWithEvents; e.g. `rejectedWithEvents` in `transformerRejected` at line 889). — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:151

What to do

  • Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
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.

AX4 · Dependency direction7.5 / 10Strong✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

  • `catalog:catalog-domain` is a Domain project but references `catalog:catalog-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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

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

  • `DashboardEditing` declares 19 required operations: `addPanel`, `removePanel`, `duplicatePanel`, `renamePanel`, `replacePanelView`, `editPanelContent`, `movePanelToTab`, `setPresentation`, `referToSaved`, `setPanelClick`, `addTab`, `renameTab`, `moveTab`, `removeTab`, `place`, `reorderPanel`, `setWidth`, `undo`, `redo`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/runtime/dashboard/editing.ts:94
  • `DashboardRuntime` declares 21 required operations: `getSnapshot`, `ready`, `panelRuntime`, `refreshPanel`, `setBuilding`, `setRefreshInterval`, `preload`, `showTab`, `setFilterValue`, `setGroupingUnit`, `clearFilters`, `holdFilters`, `setFilters`, `wiredOptions`, `crossFilter`, `pressed`, `spanFilters`, `pressSpan`, `destination`, `destinationBoard`, `handOver`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/runtime/dashboard/contract.ts:115
  • `QuestionEditing` declares 22 required operations: `addGroup`, `updateGroup`, `removeGroup`, `renameGroup`, `setMissingBucket`, `setDense`, `addMetric`, `updateMetric`, `replaceMetric`, `renameMetric`, `setMetricFilter`, `duplicateMetric`, `addFiveNumbers`, `addOhlc`, `moveMetric`, `removeMetric`, `addFormula`, `addDuration`, `groupByDuration`, `addDerived`, `setHaving`, `setTop`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/react/analysisEditing.ts:74
  • `AnalysisEditorController` declares 19 required operations: `undoDrop`, `dismissDrop`, `metricRemoval`, `elementLabel`, `elementFields`, `expand`, `collapse`, `setElementFilter`, `dateUnitFor`, `setSort`, `sortNow`, `setLimit`, `setLayout`, `setChartType`, `updateChart`, `setTotals`, `submit`, `focus`, `blur`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/react/useAnalysisEditor.ts:82
  • `DashboardController` declares 20 required operations: `showTab`, `place`, `refresh`, `refreshPanel`, `setBuilding`, `setFilterValue`, `setGroupingUnit`, `clearFilters`, `setAwaiting`, `filterCandidates`, `filterChoices`, `filterOptions`, `preload`, `crossFilter`, `pressed`, `spanFilters`, `pressSpan`, `destination`, `destinationBoard`, `handOver`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/react/useDashboard.ts:84
  • `RecordTableController` declares 23 required operations: `setCard`, `sortOf`, `toggleSort`, `setSort`, `setLayout`, `hiddenOf`, `setColumns`, `setColumnOrder`, `pinnedOf`, `setPinned`, `setColumnWidth`, `summaryOf`, `setSummary`, `setPageSize`, `isSelected`, `toggle`, `toggleAll`, `clearSelection`, `select`, `goTo`, `next`, `previous`, `refresh`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/react/useRecordTable.ts:83
  • `CartesianPlan` declares 18 required operations: `tickOf`, `stackOf`, `stacked`, `asShares`, `shareAt`, `drawnAt`, `drawnText`, `labelled`, `peaksOnly`, `filledAt`, `insideText`, `span`, `reach`, `wholeOn`, `sharesOn`, `logOn`, `valuesOn`, `extremesOf`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts:244

What to do

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

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

  • The guard above `return relative;` also returns `relative`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — typescript/wow-generator/src/naming/paths.ts:25
  • `noMeasure` has an empty body — confirm it's an intentional no-op and not an unfinished method. — typescript/wow-view-engine/src/ui/analysis/virtualRows.ts:258
  • `setMode` has an empty body — confirm it's an intentional no-op and not an unfinished method. — typescript/wow-view-engine/src/ui/colorMode.tsx:51
  • `removing` has an empty body — confirm it's an intentional no-op and not an unfinished method. — typescript/wow-view-engine/src/ui/filter/conditionFocus.ts:87

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)8.4 / 10Strong✓ 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.

What to do

  • Describe the projects a newcomer cannot place from the root README: 70 of 87 have no README of their own, in their folder or in their family's project (`documentation`, `api/annotations`, `api/api`, `api/manifest`, `api/query-api` and 65 more).
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

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

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability9.6 / 10Exemplary✓ 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 23/27 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `migration/migrate-data`, `platform/ops/ops-server`, `skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-server`, `typescript/wow-view-engine`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling3.0 / 10Weak✓ 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.

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 19 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:27

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • 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.

P5 · DR & Backup10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `existsSync` in `attachServerDiagnostics` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — examples/eshop/web/e2e/diagnostics.ts:56, examples/eshop/web/e2e/diagnostics.ts:63
  • `fs.readFileSync` in `callback to files.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/src/output/outputStore.ts:218
  • `fs.mkdirSync` in `attempt("write")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/src/output/outputStore.ts:226
  • `writeFileSync` in `generateCold` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — typescript/wow-generator/test/support/generation.ts:119, typescript/wow-generator/test/support/generation.ts:123
  • `writeFileSync` in `generateProject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/test/support/generation.ts:171
  • `realpathSync` in `generateProject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/test/support/generation.ts:199
  • `writeFileSync` in `generateCompiling` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/test/support/probes.ts:49
  • `readFileSync` in `read` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — typescript/wow-generator/test/support/probes.ts:54

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety9.8 / 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.5 / 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.

  • examples/eshop/web/src/generated/ and typescript/wow-generator/expected/eshop-manifest/ are near-verbatim copies of each other: 56 files are byte-identical under the same relative paths (~2585 lines; the trees hold 63 and 63 files). That is one structural fact, not 56 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — typescript/wow-generator/expected/eshop-manifest/catalog/eshop-catalog/types.ts:1
  • 45 duplicated blocks under platform/ have copies in at least two of the sibling directories analytics, ops — 34 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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. — platform/analytics/catalog/console/src/app/CallerForm.tsx:14
  • 32 duplicated blocks under typescript/wow-view-engine/src/ui/ have copies in at least two of the sibling directories analysis, charts, columns, dashboard, embed, filter (+5 more sibling(s) not listed) — 17 of them are reported below, and 15 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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. — typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:412
  • 22 duplicated blocks under typescript/wow-view-engine/src/ have copies in at least two of the sibling directories analysis, capabilities, dashboard, filter, model, react (+4 more sibling(s) not listed) — 13 of them are reported below, and 9 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — typescript/wow-view-engine/src/analysis/validate.ts:40
  • 20 duplicated blocks under typescript/ have copies in at least two of the sibling directories storybook, wow-client, wow-generator, wow-react, wow-view-engine, wow-view-store — 12 of them are reported below, and 8 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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. — typescript/wow-client/scripts/api-report.mjs:40
  • platform/analytics/catalog/console/src/app/CallerForm.tsx:14 · platform/ops/console/src/app/CallerForm.tsx:14 — these 2 files are line-for-line copies of one another — 145 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — platform/analytics/catalog/console/src/app/CallerForm.tsx:14
  • platform/analytics/catalog/console/src/services/caller.ts:74 · platform/ops/console/src/services/caller.ts:62 — 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. — platform/analytics/catalog/console/src/services/caller.ts:74
  • platform/analytics/catalog/console/src/components/ui/dropdown-menu.tsx:14 · platform/ops/console/src/components/ui/dropdown-menu.tsx:14 — these 2 files are line-for-line copies of one another — 132 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — platform/analytics/catalog/console/src/components/ui/dropdown-menu.tsx:14
  • typescript/wow-client/scripts/api-report.mjs:40 · typescript/wow-react/scripts/api-report.mjs:40 · typescript/wow-view-store/scripts/api-report.mjs:40 — these 3 files are line-for-line copies of one another — 110 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — typescript/wow-client/scripts/api-report.mjs:40
  • typescript/wow-view-engine/src/ui/charts/funnelFit.ts:212 · typescript/wow-view-engine/src/ui/charts/funnelFit.ts:378 — the two spans are one implementation copied and then locally edited — 584 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — typescript/wow-view-engine/src/ui/charts/funnelFit.ts:212
  • typescript/wow-view-engine/src/analysis/boxplot.ts:84 · typescript/wow-view-engine/src/analysis/candlestick.ts:72 — the two spans are one implementation copied and then locally edited — 561 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. — typescript/wow-view-engine/src/analysis/boxplot.ts:84
  • typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:70 · typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:264 — the two spans are one implementation copied and then locally edited — 474 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:70
  • platform/analytics/catalog/console/src/components/ui/field.tsx:8 · platform/ops/console/src/components/ui/field.tsx:8 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — platform/analytics/catalog/console/src/components/ui/field.tsx:8
  • platform/analytics/catalog/console/src/i18n.tsx:276 · platform/ops/console/src/i18n.tsx:166 — 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. — platform/analytics/catalog/console/src/i18n.tsx:276
  • typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:114 · typescript/wow-view-engine/src/ui/DataWorkbench.tsx:107 — the two spans are one implementation copied and then locally edited — 365 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. — typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:114
  • typescript/wow-view-engine/src/ui/charts/PieSlices.tsx:66 · typescript/wow-view-engine/src/ui/charts/ScatterPoints.tsx:40 — the two spans are one implementation copied and then locally edited — 295 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. — typescript/wow-view-engine/src/ui/charts/PieSlices.tsx:66
  • platform/analytics/catalog/console/playwright.config.ts:23 · platform/ops/console/playwright.config.ts:23 — 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. — platform/analytics/catalog/console/playwright.config.ts:23
  • typescript/storybook/stories/view-engine/compensationEvents.ts:82 · typescript/storybook/stories/view-engine/tradeOrderEvents.ts:147 — 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. — typescript/storybook/stories/view-engine/compensationEvents.ts:82
  • typescript/wow-client/scripts/api-report.mjs:102 · typescript/wow-react/scripts/api-report.mjs:90 · typescript/wow-view-engine/scripts/api-report.mjs:103 · typescript/wow-view-store/scripts/api-report.mjs:90 — 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. — typescript/wow-client/scripts/api-report.mjs:102
  • platform/analytics/catalog/console/src/setupTests.ts:14 · platform/ops/console/src/setupTests.ts:14 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — platform/analytics/catalog/console/src/setupTests.ts:14
  • platform/analytics/catalog/console/src/components/ui/button.tsx:19 · platform/ops/console/src/components/ui/button.tsx:19 — 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. — platform/analytics/catalog/console/src/components/ui/button.tsx:19
  • typescript/storybook/stories/view-engine/compensationEvents.ts:382 · typescript/storybook/stories/view-engine/customerEvents.ts:466 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — typescript/storybook/stories/view-engine/compensationEvents.ts:382
  • platform/analytics/catalog/console/src/app/App.tsx:124 · platform/ops/console/src/app/App.tsx:105 — 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. — platform/analytics/catalog/console/src/app/App.tsx:124
  • typescript/wow-view-engine/src/filter/kinds/number.ts:73 · typescript/wow-view-engine/src/filter/kinds/string.ts:69 — the two spans are one implementation copied and then locally edited — 369 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. — typescript/wow-view-engine/src/filter/kinds/number.ts:73
  • typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:162 · typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:367 — the two spans are one implementation copied and then locally edited — 205 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:162
  • typescript/wow-view-engine/src/ui/charts/boxplotOption.ts:47 · typescript/wow-view-engine/src/ui/charts/candlestickOption.ts:39 — the two spans are one implementation copied and then locally edited — 278 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. — typescript/wow-view-engine/src/ui/charts/boxplotOption.ts:47
  • typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:126 · typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx:281 — the two spans are one implementation copied and then locally edited — 202 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. — typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:126
  • platform/analytics/catalog/console/src/views/datasets.ts:173 · platform/analytics/catalog/console/src/views/sources.ts:196 — 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. — platform/analytics/catalog/console/src/views/datasets.ts:173
  • platform/analytics/catalog/console/src/app/App.tsx:43 · platform/ops/console/src/app/App.tsx:33 — 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. — platform/analytics/catalog/console/src/app/App.tsx:43
  • typescript/storybook/stories/view-engine/compensationEvents.ts:340 · typescript/storybook/stories/view-engine/customerEvents.ts:423 · typescript/storybook/stories/view-engine/tradeOrderEvents.ts:355 — 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. — typescript/storybook/stories/view-engine/compensationEvents.ts:340
  • platform/analytics/catalog/console/src/app/CallerGate.tsx:29 · platform/ops/console/src/app/CallerGate.tsx:28 — 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. — platform/analytics/catalog/console/src/app/CallerGate.tsx:29
  • typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:42 · typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:83 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:42
  • typescript/storybook/stories/view-engine/compensation.ts:79 · typescript/storybook/stories/view-engine/productPricing.ts:139 — 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. — typescript/storybook/stories/view-engine/compensation.ts:79
  • typescript/storybook/stories/view-engine/compensation.ts:102 · typescript/storybook/stories/view-engine/customer.ts:111 — 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. — typescript/storybook/stories/view-engine/compensation.ts:102
  • platform/analytics/catalog/console/eslint.config.js:11 · platform/ops/console/eslint.config.js:11 — 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. — platform/analytics/catalog/console/eslint.config.js:11
  • platform/analytics/catalog/console/src/services/cosec.ts:36 · platform/ops/console/src/services/cosec.ts:36 — 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. — platform/analytics/catalog/console/src/services/cosec.ts:36
  • typescript/wow-view-engine/src/ui/charts/Boxplot.tsx:40 · typescript/wow-view-engine/src/ui/charts/Candlestick.tsx:39 — the two spans are one implementation copied and then locally edited — 166 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. — typescript/wow-view-engine/src/ui/charts/Boxplot.tsx:40
  • typescript/wow-client/scripts/verify-package.mjs:122 · typescript/wow-client/scripts/verify-package.mjs: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. — typescript/wow-client/scripts/verify-package.mjs:122
  • typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:58 · typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:92 — the two spans are one implementation copied and then locally edited — 141 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:58
  • typescript/wow-client/scripts/verify-package.mjs:85 · typescript/wow-generator/scripts/verify-package.mjs:72 — 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. — typescript/wow-client/scripts/verify-package.mjs:85

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 Boundaries9.8 / 10Exemplary✓ 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.

  • typescript/wow-client/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead. — typescript/wow-client/scripts/api-report.mjs:45
  • typescript/wow-react/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead. — typescript/wow-react/scripts/api-report.mjs:45
  • typescript/wow-view-store/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead. — typescript/wow-view-store/scripts/api-report.mjs:45

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.0 / 10Strong✓ 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.

  • project has cyclomatic complexity 100 and cognitive complexity 137; 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. — typescript/storybook/stories/view-engine/retail/generate.ts:1476
  • WorkbenchShell has cyclomatic complexity 62 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344
  • AnalysisParts has cyclomatic complexity 50 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 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. — typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx:126
  • generateRetail has cyclomatic complexity 48 and cognitive complexity 128; 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. — typescript/storybook/stories/view-engine/retail/generate.ts:766
  • MetricCard has cyclomatic complexity 48 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. — typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78
  • ConditionPill has cyclomatic complexity 46 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:80
  • (anonymous) has cyclomatic complexity 44 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 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. — typescript/wow-view-engine/src/runtime/viewRuntime.ts:283
  • checkTheme has cyclomatic complexity 43 and cognitive complexity 94; 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. — typescript/wow-view-engine/theme-check/check.ts:132
  • ActionDialog has cyclomatic complexity 41 and cognitive complexity 37; 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. — typescript/wow-view-engine/src/ui/actions/ActionDialog.tsx:81
  • narrowAggregation has cyclomatic complexity 40 and cognitive complexity 34; 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. — typescript/wow-view-engine/src/capabilities/analysis.ts:263
  • dataContext has cyclomatic complexity 40 and cognitive complexity 30; 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. — typescript/wow-view-engine/test/prefixedClasses.test.ts:111
  • criteria has cyclomatic complexity 39 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — typescript/wow-view-engine/src/testing/filter.ts:114
  • buildField has cyclomatic complexity 38 and cognitive complexity 44; 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. — typescript/wow-view-engine/src/runtime/define/fields.ts:89
  • useWorkbench has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — typescript/wow-view-engine/src/react/useWorkbench.ts:408
  • RecordTable has cyclomatic complexity 35 and cognitive complexity 32; 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. — typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209
  • metricOf has cyclomatic complexity 34 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — typescript/wow-view-engine/src/testing/aggregate.ts:290
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 38; 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. — typescript/wow-view-engine/theme-check/check.ts:222
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 36; 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. — typescript/wow-view-engine/src/runtime/dashboardRuntime.ts:416
  • serve has cyclomatic complexity 33 and cognitive complexity 36; 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. — typescript/wow-view-store/test/support/fakeViewStore.ts:1234
  • ColumnRow has cyclomatic complexity 33 and cognitive complexity 31; 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. — typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files3.8 / 10Weak✓ 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.

  • typescript/storybook/stories/view-engine/retail/generate.ts has 2103 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/generate.ts:1
  • typescript/storybook/stories/view-engine/retail/views.ts has 1831 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/views.ts:1
  • typescript/wow-client/src/dsl/filter/builders.ts has 1438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-client/src/dsl/filter/builders.ts:1
  • typescript/storybook/stories/view-engine/fixtures.ts has 1312 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/fixtures.ts:1
  • typescript/storybook/stories/view-engine/retail/boards.ts has 1236 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/boards.ts:1
  • typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx has 1214 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx:1
  • typescript/storybook/stories/view-engine/retail/definitions.ts has 1059 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/definitions.ts:1
  • typescript/storybook/stories/view-engine/retail/catalog.ts has 1021 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/catalog.ts:1
  • typescript/wow-view-engine/src/ui/kit/variants.tsx has 1001 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/kit/variants.tsx:1
  • typescript/wow-generator/src/manifest/analyze.ts has 994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-generator/src/manifest/analyze.ts:1
  • typescript/storybook/stories/view-engine/Dashboard.stories.tsx has 987 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/Dashboard.stories.tsx:1
  • typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx has 876 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx:1
  • typescript/wow-view-engine/src/analysis/project.ts has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/analysis/project.ts:1
  • typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:1
  • typescript/wow-view-engine/src/react/useWorkbench.ts has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/react/useWorkbench.ts:1
  • typescript/wow-view-engine/src/ui/kit/display.ts has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/kit/display.ts:1
  • typescript/wow-generator/src/types/typeResolver.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-generator/src/types/typeResolver.ts:1
  • typescript/wow-view-engine/src/record/project.ts has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/record/project.ts:1
  • typescript/wow-generator/src/emitters/manifestClients.ts has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-generator/src/emitters/manifestClients.ts:1
  • typescript/wow-view-engine/src/react/useFilterEditor.ts has 782 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/react/useFilterEditor.ts:1
  • typescript/storybook/stories/view-engine/customer.ts has 779 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/customer.ts:1
  • typescript/wow-view-engine/src/runtime/viewEngine.ts has 779 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/runtime/viewEngine.ts:1
  • typescript/wow-view-engine/src/ui/kit/popups.tsx has 766 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/kit/popups.tsx:1
  • typescript/wow-client/src/dsl/aggregation/types.ts has 762 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-client/src/dsl/aggregation/types.ts:1
  • typescript/storybook/stories/view-engine/retail/showcase.ts has 760 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/retail/showcase.ts:1
  • typescript/storybook/stories/view-engine/tradeOrder.ts has 748 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/tradeOrder.ts:1
  • typescript/wow-view-engine/src/dashboard/layout.ts has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/dashboard/layout.ts:1
  • typescript/wow-view-store/src/wowViewStore.ts has 731 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-store/src/wowViewStore.ts:1
  • typescript/wow-view-engine/src/react/useRecordTable.ts has 727 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/react/useRecordTable.ts:1
  • typescript/wow-view-engine/theme-check/resolve.ts has 715 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/theme-check/resolve.ts:1
  • typescript/wow-view-engine/src/runtime/dashboardRuntime.ts has 709 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/runtime/dashboardRuntime.ts:1
  • typescript/wow-view-engine/src/ui/charts/EChart.tsx has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/charts/EChart.tsx:1
  • typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts:1
  • typescript/wow-view-engine/src/model/field.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/model/field.ts:1
  • typescript/wow-client/src/dsl/aggregation/builders.ts has 698 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-client/src/dsl/aggregation/builders.ts:1
  • typescript/wow-view-engine/src/react/useAnalysisResult.ts has 694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/react/useAnalysisResult.ts:1
  • typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx:1
  • typescript/wow-view-engine/src/runtime/viewRuntime.ts has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/runtime/viewRuntime.ts:1
  • typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:1
  • platform/ops/console/src/views/parked.ts has 662 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — platform/ops/console/src/views/parked.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage9.8 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • typescript/storybook/scripts/verify-storybook.mjs:20 imports '../stories/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — typescript/storybook/scripts/verify-storybook.mjs:20
  • typescript/storybook/stories/view-engine/retail/descriptions.test.ts:35 imports '../', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — typescript/storybook/stories/view-engine/retail/descriptions.test.ts:35
  • typescript/wow-client/test/packageTypes.test.ts:20 imports './__package_consumer__.mts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — typescript/wow-client/test/packageTypes.test.ts:20
  • 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. (×16) — typescript/wow-view-engine/scripts/api-report.mjs:1, typescript/wow-client/scripts/api-report.mjs:1, typescript/wow-react/scripts/api-report.mjs:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
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.

  • This repository declares test tooling, and the ✓ above records that declaration — but typescript/storybook/scripts/verify-storybook.mjs and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — typescript/storybook/scripts/verify-storybook.mjs:20
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 8 file(s) (~961 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — typescript/integration-test
  • Unreachable from the 117 application, 47 tooling and 755 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (117 application, 47 tooling, 755 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 (×4) — typescript/storybook/scripts/verify-storybook-browser.mjs, typescript/storybook/stories/view-engine/IntroBlocks.tsx, typescript/storybook/stories/view-engine/integration/wowCommands.ts, …
  • Nothing imports this binding — it is safe to review for removal. (×3) — typescript/wow-generator/src/manifest/document.ts:42, typescript/wow-generator/src/manifest/document.ts:45, typescript/wow-generator/src/manifest/document.ts:51
  • Nothing ultimately consumes this binding: its only referrer is the re-export in typescript/wow-view-engine/src/model/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in typescript/wow-view-engine/src/model/index.ts in the same commit, or the barrel will import a name that no longer exists. — typescript/wow-view-engine/src/model/wire.ts:93

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 Hygiene9.0 / 10Exemplary✓ 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.

  • Every import is type-only — move it to devDependencies. — typescript/wow-view-engine/src/ui/filter/inputs/daterange.tsx:17

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

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

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

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

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

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

  • `cellText` is exported and takes `value: unknown` from its caller, and it calls itself at line 613 (`cellText`) with a piece of `value` — and nowhere in `cellText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cellText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/ui/kit/display.ts:613
  • `numberOf` is exported and takes `value: unknown` from its caller, and it calls itself at line 45 (`numberOf`) with a piece of `value` — and nowhere in `numberOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `numberOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/testing/values.ts:45
  • `expressionFieldsOf` is exported and takes `expression: AnalysisExpression` from its caller, and it calls itself at line 140 (`expressionFieldsOf`) with a piece of `expression` (and at line 141) — and nowhere in `expressionFieldsOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionFieldsOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/model/analysis.ts:140
  • `sameJson` is exported, takes a document from its caller (line 63) and hands it to `keysInOrder`, which calls itself at line 69 (`keysInOrder`) with a piece of `value` (and at line 74) — and nowhere in `keysInOrder` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `keysInOrder` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/model/json.ts:69
  • `withoutBlankLeaves` is exported, takes a document from its caller (line 33) and hands it to `prune`, which calls itself at line 43 (`prune`) with a piece of `group` — and nowhere in `prune` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `prune` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/filter/compile.ts:43
  • `budgetedExpressionIssues` is exported, takes a document from its caller (line 126) and hands it to `expressionIssues`, which calls itself at line 105 (`expressionIssues`) with a piece of `expression` (and at line 113) — and nowhere in `expressionIssues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionIssues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/expressions.ts:105
  • `budgetedDerivedIssues` is exported, takes a document from its caller (line 187) and hands it to `derivedIssues`, which calls itself at line 258 (`derivedIssues`) with a piece of `expression` (and at line 259) — and nowhere in `derivedIssues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `derivedIssues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/expressions.ts:258
  • `expressionText` is exported and takes `expression: AnalysisExpression` from its caller, and it calls itself at line 186 (`expressionText`) with a piece of `expression` (and at line 188) — and nowhere in `expressionText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/formula.ts:186
  • `derivedText` is exported and takes `expression: AnalysisDerivedExpression` from its caller, and it calls itself at line 217 (`derivedText`) with a piece of `expression` (and at line 219) — and nowhere in `derivedText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `derivedText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/formula.ts:217
  • `derivedOperandFormat` is exported, takes a document from its caller (line 145) and hands it to `walk`, which calls itself at line 156 (`walk`) with a piece of `node` (and at line 157) — and nowhere in `walk` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/metricFormat.ts:156
  • `formulaFormat` is exported, takes a document from its caller (line 223) and hands it to `reading`, which calls itself at line 276 (`reading`) with a piece of `expression` (and at line 277) — and nowhere in `reading` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `reading` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-view-engine/src/analysis/metricFormat.ts:276
  • `resolveLiteral` is exported and takes `value: unknown` from its caller, and it calls itself at line 359 (`resolveLiteral`) with a piece of `value` (and at line 363) — and nowhere in `resolveLiteral` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveLiteral` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-generator/src/types/typeResolver.ts:359
  • `findDanglingReferences` is exported, takes a document from its caller (line 59) and hands it to `visit`, which calls itself at line 68 (`visit`) with a piece of `value` (and at line 80) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-generator/src/openapi/references.ts:68
  • `marksNothing` is exported and takes `marks: TextNumbers | undefined` from its caller, and it calls itself at line 62 (`marksNothing`) with a piece of `marks` (and at line 64) — and nowhere in `marksNothing` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `marksNothing` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-client/src/exactJson.ts:62
  • `stringifyJson` is exported, takes a document from its caller (line 387) and hands it to `replace`, which calls itself at line 428 (`replace`) with a piece of `value` (and at line 445) — and nowhere in `replace` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `replace` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-client/src/exactJson.ts:428
  • `requireElementScopedFilter` is exported and takes `expression: FilterExpression` from its caller, and it calls itself at line 73 (`requireElementScopedFilter`) with a piece of `expression` (and at line 77) — and nowhere in `requireElementScopedFilter` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `requireElementScopedFilter` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-client/src/dsl/filter/scope.ts:73
  • `expressionFields` is exported and takes `expression: AggregationExpression` from its caller, and it calls itself at line 86 (`expressionFields`) with a piece of `expression` (and at line 87) — and nowhere in `expressionFields` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — typescript/wow-client/src/dsl/aggregation/expressionTrees.ts:86
  • `declaration` is public, takes a document from its caller (line 79) and hands it to `read`, which calls itself at line 86 with a piece of `schema` (and at line 89) — the function is not `tailrec`, so every call is a real frame — and nowhere in `read` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — query/query/src/main/kotlin/me/ahoo/wow/query/schema/ManifestSchemaReader.kt:86
  • `sameValue` is public and takes `other: JsonNode` from its caller, and it calls itself at line 65 with a piece of `other` — the function is not `tailrec`, so every call is a real frame — and nowhere in `sameValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `sameValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryValues.kt:65
  • `problemText` is exported and takes `error: unknown` from its caller, and it calls itself at line 83 (`problemText`) with a piece of `error` — and nowhere in `problemText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `problemText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — platform/ops/console/src/views/parkedCommands.ts:83
  • `refusedInput` is exported, takes a document from its caller (line 137) and hands it to `refusalOf`, which calls itself at line 116 (`refusalOf`) with a piece of `error` — and nowhere in `refusalOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `refusalOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — platform/ops/console/src/views/parkedCommands.ts:116
  • `problemText` is exported and takes `error: unknown` from its caller, and it calls itself at line 112 (`problemText`) with a piece of `error` — and nowhere in `problemText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `problemText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — platform/analytics/catalog/console/src/views/catalogCommands.ts:112
  • `MongoNineXEventTarget.bsonOf` is public and takes `node: JsonNode` from its caller, and it calls itself at line 168 with a piece of `node` (and at line 171) — the function is not `tailrec`, so every call is a real frame — and nowhere in `MongoNineXEventTarget.bsonOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `MongoNineXEventTarget.bsonOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MongoNineXEventTarget.kt:168
  • `StateDiff.diff` is public, takes a document from its caller (line 52) and hands it to `StateDiff.remove`, which calls itself at line 74 with a piece of `node` — the function is not `tailrec`, so every call is a real frame — and nowhere in `StateDiff.remove` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `StateDiff.remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/StateDiff.kt:74
  • `StateDiff.diff` is public, takes a document from its caller (line 52) and hands it to `StateDiff.compare`, which calls itself at line 87 with a piece of `left` (and at line 93) — the function is not `tailrec`, so every call is a real frame — and nowhere in `StateDiff.compare` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `StateDiff.compare` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/StateDiff.kt:87
  • `AdmissionLimits.holdsNul` is public and takes `node: JsonNode` from its caller, and it calls itself at line 68 with a piece of `node` (and at line 69) — the function is not `tailrec`, so every call is a real frame — and nowhere in `AdmissionLimits.holdsNul` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `AdmissionLimits.holdsNul` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/AdmissionLimits.kt:68
  • `sameJson` is public and takes `left: JsonNode` from its caller, and it calls itself at line 294 with a piece of `left` (and at line 297) — the function is not `tailrec`, so every call is a real frame — and nowhere in `sameJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `sameJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — core/kernel/src/main/kotlin/me/ahoo/wow/kernel/EventCodec.kt:294

What to do

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

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

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

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

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

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

X2 · Cancellation propagation8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether functions that make a cancellable request accept or pass on an AbortSignal or the coroutine's cancellation (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 6/9 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `load` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — typescript/storybook/stories/view-engine/chinaProvinces.ts:64, typescript/storybook/stories/view-engine/worldExports.ts:51
  • `ready` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript/storybook/scripts/linux-browser.mjs:140

What to do

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

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

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

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

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

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

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

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

X23 · Unguarded diagnostic materialisation6.9 / 10Adequate✓ Tool-verified

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

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

  • `debug` at line 172 is called with an argument built by `command.toJson()` (line 172), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/MongoSharding.kt:172

What to do

  • In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

Other · Code Health — Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

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

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

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

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

X29 · Per-element action decided by a fixed element7.5 / 10Strong✓ Tool-verified

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

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

  • This loop runs once per element of `stages`, and the statement it guards acts on the element it is on — `stage`. The test deciding whether that statement runs does not: `first === 0` reads `stages[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 147, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — typescript/wow-view-engine/src/analysis/funnel.ts:149

What to do

  • Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
X3 · Exception handling7.0 / 10Strong✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — typescript/wow-view-store/src/wowViewStore.ts:138, typescript/wow-view-store/src/wowViewStore.ts:581, typescript/wow-view-engine/src/ui/colorMode.tsx:81, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — typescript/wow-react/src/internal/readStreamRows.ts:67
  • `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — core/spi/src/main/kotlin/me/ahoo/wow/spi/transport/EnvelopeCodec.kt:87, core/runtime/src/main/kotlin/me/ahoo/wow/runtime/source/TopicEntries.kt:137

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

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

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

X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

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

  • ~0.5 `!` null assertions per 1k TypeScript source lines — 114 assertion(s) across the 230885 source line(s) of the 999 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: typescript/wow-view-engine/src/dashboard/layout.ts (10), typescript/wow-generator/src/analysis/apiClients.ts (9), typescript/storybook/stories/view-engine/themeContrast.tsx (7). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

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 Health70%Adequate — gated by R3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture85%StrongSolid.
Maturity80%StrongSolid.
Readiness68%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security55%Adequate — gated by D28, D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility85%StrongStrongest area.
Performance73%StrongSolid.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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: this repository stores data through 'com.mongodb' (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through 'com.mongodb' (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.mongodb' (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 33 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.

  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • 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 — docker build failed (exit 1) — 27b1a: failed to resolve source metadata for dragonwell-registry.cn-hangzhou.cr.aliyuncs.com/dragonwell/dragonwell:25-ubuntu@sha256:6490a55d94a6ba1dcf88f8a1de8a5d67f5cf0fac717c1d84f18933516bd27b1a: failed to do request: Head "https://dragonwell-registry.cn-hangzhou.cr.aliyuncs.com/v2/dragonwell/dragonwell/manifests/sha256:6490a55d94a6ba1dcf88f8a1de8a5d67f5cf0fac717c1d84f18933516bd27b1a": Forbidden; 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: this repository stores data through 'com.mongodb' (migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrationConfig.kt:16) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • 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's runner produced no measurement
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Kotlin, Python not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .java, .mts, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 242 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
  • 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 (6 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (entities that raise its domain events); 24 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 521 value object(s); 43 domain event(s); a Domain/Aggregates/ValueObjects layer; 2 per-aggregate domain namespaces (…/BasketAggregate, …/OrderAggregate); a DDD annotation stack (jMolecules/Axon @AggregateRoot/@Aggregate/@ValueObject — persistence @Entity does not count); 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 none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 799 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.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 168 finding(s)
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
  • + 51 more in this group — see findings.md.
D28 · Secrets (history) · REDACTED · ×59
  • 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
  • + 34 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AX4 · Dependency direction · Dependency-rule violation · ×1
  • Dependency-rule violation: catalog:catalog-domain (Domain) → catalog:catalog-api (Web) — `catalog:catalog-domain` is a Domain project but references `catalog:catalog-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
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 · High CVE · ×1
  • REDACTED
Serious — 962 finding(s)
D15 · Churn × Complexity Hotspots · Hotspot · ×130
  • Hotspot: typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344 — typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx changed 69 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in WorkbenchShell.WorkbenchShell at line 344. 4 of those changes were fix/bug commits, and the other 65 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.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.
  • Hotspot: typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:167 — typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx changed 50 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in DashboardGrid.DashboardGrid at line 167. 2 of those changes were fix/bug commits, and the other 48 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.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.
  • Hotspot: typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121 — typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in AnalysisTable.AnalysisTable at line 121. 2 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/analysis/AnalysisTable.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.
  • Hotspot: typescript/wow-view-engine/src/ui/record/RecordTable.tsx typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209 — typescript/wow-view-engine/src/ui/record/RecordTable.tsx changed 48 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in RecordTable.RecordTable at line 209. 2 of those changes were fix/bug commits, and the other 46 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/record/RecordTable.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.
  • Hotspot: typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx:126 — typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in AnalysisParts.AnalysisParts at line 126. 20 of those changes were fix/bug commits, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/AnalysisParts.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.
  • Hotspot: typescript/wow-view-engine/src/analysis/project.ts typescript/wow-view-engine/src/analysis/project.ts:415 — typescript/wow-view-engine/src/analysis/project.ts changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in project.projectAnalysis at line 415. 21 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/analysis/project.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/workbench/SaveActions.tsx typescript/wow-view-engine/src/ui/workbench/SaveActions.tsx:87 — typescript/wow-view-engine/src/ui/workbench/SaveActions.tsx changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in SaveActions.SaveActions at line 87. 3 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/SaveActions.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.
  • Hotspot: typescript/wow-view-engine/src/ui/charts/EChart.tsx typescript/wow-view-engine/src/ui/charts/EChart.tsx:205 — typescript/wow-view-engine/src/ui/charts/EChart.tsx changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in EChart.EChart at line 205. 7 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/EChart.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.
  • Hotspot: core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:413 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in CommandGateway.admit at line 413. 9 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:80 — typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in ConditionPill.ConditionPill at line 80. 11 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/filter/ConditionPill.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.
  • Hotspot: typescript/wow-view-engine/src/react/useWorkbench.ts typescript/wow-view-engine/src/react/useWorkbench.ts:408 — typescript/wow-view-engine/src/react/useWorkbench.ts changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in useWorkbench.useWorkbench at line 408. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/react/useWorkbench.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78 — typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in MetricCard.MetricCard at line 78. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/analysis/MetricCard.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.
  • Hotspot: typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:213 — typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx changed 52 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in DashboardWorkbench.DashboardWorkbenchBody at line 213. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/DashboardWorkbench.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.
  • Hotspot: typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx:157 — typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in ResultToolbar.ResultToolbar at line 157. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/ResultToolbar.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.
  • Hotspot: typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx:257 — typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in DashboardPanelCard.DashboardPanelCard at line 257. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.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.
  • Hotspot: typescript/wow-view-engine/src/react/useAnalysisResult.ts typescript/wow-view-engine/src/react/useAnalysisResult.ts:251 — typescript/wow-view-engine/src/react/useAnalysisResult.ts changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in useAnalysisResult.useAnalysisResult at line 251. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/react/useAnalysisResult.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/charts/Cartesian.tsx typescript/wow-view-engine/src/ui/charts/Cartesian.tsx:42 — typescript/wow-view-engine/src/ui/charts/Cartesian.tsx changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in Cartesian.Cartesian at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/Cartesian.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.
  • Hotspot: typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx:202 — typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in RecordParts.RecordParts at line 202. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/RecordParts.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.
  • Hotspot: typescript/wow-view-engine/src/ui/record/SortableHeader.tsx typescript/wow-view-engine/src/ui/record/SortableHeader.tsx:97 — typescript/wow-view-engine/src/ui/record/SortableHeader.tsx changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in SortableHeader.SortableHeader at line 97. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/record/SortableHeader.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.
  • Hotspot: typescript/wow-view-engine/src/ui/charts/cartesianOption.ts typescript/wow-view-engine/src/ui/charts/cartesianOption.ts:74 — typescript/wow-view-engine/src/ui/charts/cartesianOption.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in cartesianOption.optionOf at line 74. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/cartesianOption.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/EmbeddedView.tsx typescript/wow-view-engine/src/ui/EmbeddedView.tsx:168 — typescript/wow-view-engine/src/ui/EmbeddedView.tsx changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in EmbeddedView.EmbeddedData at line 168. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/EmbeddedView.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.
  • Hotspot: typescript/wow-view-engine/src/ui/kit/display.ts typescript/wow-view-engine/src/ui/kit/display.ts:157 — typescript/wow-view-engine/src/ui/kit/display.ts changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in display.displayValue at line 157. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/kit/display.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx:293 — typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in PanelBodies.AnalysisPanel at line 293. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/dashboard/PanelBodies.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.
  • Hotspot: typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx:142 — typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in DisplayTab.ValueLabelsField at line 142. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/analysis/DisplayTab.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.
  • Hotspot: typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151 — typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ColumnRow.ColumnRow at line 151. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/columns/ColumnRow.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.
  • + 105 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×94
  • FunctionTooLong: generate.generateRetail.project typescript/storybook/stories/view-engine/retail/generate.ts:1476 — FunctionTooLong — generateRetail.project runs 388 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 288 over it, 3.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: AnalysisTable.AnalysisTable typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121 — FunctionTooLong — AnalysisTable runs 335 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 235 over it, 3.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: RecordTable.RecordTable typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209 — FunctionTooLong — RecordTable runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useWorkbench.useWorkbench typescript/wow-view-engine/src/react/useWorkbench.ts:408 — FunctionTooLong — useWorkbench runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× 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: resolve.createResolver typescript/wow-view-engine/theme-check/resolve.ts:399 — FunctionTooLong — createResolver runs 257 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 157 over it, 2.57× 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: MetricCard.MetricCard typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78 — FunctionTooLong — MetricCard runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: DashboardGrid.DashboardGrid typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:167 — FunctionTooLong — DashboardGrid runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useAnalysisEditor.useAnalysisEditor typescript/wow-view-engine/src/react/useAnalysisEditor.ts:284 — FunctionTooLong — useAnalysisEditor runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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: useRecordTable.useRecordTable typescript/wow-view-engine/src/react/useRecordTable.ts:392 — FunctionTooLong — useRecordTable runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: NewAnalysisDialog.NewAnalysisForm typescript/wow-view-engine/src/ui/dashboard/NewAnalysisDialog.tsx:154 — FunctionTooLong — NewAnalysisForm runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ViewManagerRow.ViewManagerRow typescript/wow-view-engine/src/ui/manage/ViewManagerRow.tsx:131 — FunctionTooLong — ViewManagerRow runs 237 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× 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: ContentEditor.ContentForm typescript/wow-view-engine/src/ui/dashboard/ContentEditor.tsx:204 — FunctionTooLong — ContentForm runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× 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: Board.DashboardBoard typescript/wow-view-engine/src/ui/dashboard/Board.tsx:91 — FunctionTooLong — DashboardBoard 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: ViewHeader.ViewHeader typescript/wow-view-engine/src/ui/workbench/ViewHeader.tsx:143 — FunctionTooLong — ViewHeader runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.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: boards.opsDailyConfig typescript/storybook/stories/view-engine/retail/boards.ts:450 — FunctionTooLong — opsDailyConfig runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Cartesian.Cartesian typescript/wow-view-engine/src/ui/charts/Cartesian.tsx:42 — FunctionTooLong — Cartesian runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ColumnRow.ColumnRow typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151 — FunctionTooLong — ColumnRow runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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: PanelMenu.PanelMenu typescript/wow-view-engine/src/ui/dashboard/PanelMenu.tsx:112 — FunctionTooLong — PanelMenu runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: FieldChecklist.FieldChecklist typescript/wow-view-engine/src/ui/filter/FieldChecklist.tsx:86 — FunctionTooLong — FieldChecklist runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: cartesianPlan.cartesianPlan typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts:511 — FunctionTooLong — cartesianPlan runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: ResultToolbar.ResultToolbar typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx:157 — FunctionTooLong — ResultToolbar runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ViewManager.ViewManager typescript/wow-view-engine/src/ui/manage/ViewManager.tsx:90 — FunctionTooLong — ViewManager runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: ActionDialog.ActionDialog typescript/wow-view-engine/src/ui/actions/ActionDialog.tsx:81 — FunctionTooLong — ActionDialog runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: FilterBar.FilterBar typescript/wow-view-engine/src/ui/dashboard/FilterBar.tsx:170 — FunctionTooLong — FilterBar runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.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: useSaveCommands.useSaveCommands typescript/wow-view-engine/src/react/useSaveCommands.ts:211 — FunctionTooLong — useSaveCommands runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 69 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×38
  • No assertions: list every member of the union, and nothing else typescript/wow-view-engine/test/choiceLists.test.ts:40 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: keep a field metric type one a metric has typescript/wow-view-engine/test/choiceLists.test.ts:56 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: calls it by its subject once the group it was named by is taken off typescript/wow-view-engine/test/dashboardPressUi.test.tsx:517 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: refuses an operation that is not its kind's typescript/wow-view-engine/test/hostErrors.test.tsx:556 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: names every store method but the synchronous `permissions` typescript/wow-view-engine/test/hostErrors.test.tsx:608 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: says when only the most frequent values are listed typescript/wow-view-engine/test/suggestedValue.test.tsx:181 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: match the recipes they draw with typescript/wow-view-engine/test/variants.test.tsx:284 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: are typed by their values, so a config stays plain JSON typescript/wow-view-engine/test/wire.test.ts:52 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: answers a missing view as NOT_FOUND typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:370 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: answers a write to a view another client deleted as NOT_FOUND typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:618 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: answers a write to a missing view as NOT_FOUND typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:649 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: defaults every hook to its filter request type typescript/wow-react/test/filterQueryTypes.test.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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: accepts filter request subtypes typescript/wow-react/test/filterQueryTypes.test.ts:108 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: takes a query client cursor and aggregate method as execute typescript/wow-react/test/filterQueryTypes.test.ts:140 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: refuses a cursor in the cursor hook's query: the hook owns it typescript/wow-react/test/filterQueryTypes.test.ts:167 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: names the four query statuses as a plain string union typescript/wow-react/test/hookContract.types.test.ts:99 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: hands every executor the query and the request options with a signal typescript/wow-react/test/hookContract.types.test.ts:108 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: holds the members of the shared options and return typescript/wow-react/test/hookContract.types.test.ts:123 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: specializes the shared types for each request hook typescript/wow-react/test/hookContract.types.test.ts:159 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: streams records into items, position and done in place of result typescript/wow-react/test/hookContract.types.test.ts:192 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: reads a cursor page by page into items, hasMore and fetchNext typescript/wow-react/test/hookContract.types.test.ts:219 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: reports an Error, and a Wow service's answer as problem typescript/wow-react/test/hookContract.types.test.ts:240 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: returns the records of a stream as items, never the stream itself typescript/wow-react/test/streamTypes.test.ts:28 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: takes the stream options, resume included typescript/wow-react/test/streamTypes.test.ts:45 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: takes a query client streamRows method as execute typescript/wow-react/test/streamTypes.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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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.
  • + 13 more in this group — see findings.md.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×27
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/ui/kit/display.ts:613 — `cellText` is exported and takes `value: unknown` from its caller, and it calls itself at line 613 (`cellText`) with a piece of `value` — and nowhere in `cellText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cellText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/testing/values.ts:45 — `numberOf` is exported and takes `value: unknown` from its caller, and it calls itself at line 45 (`numberOf`) with a piece of `value` — and nowhere in `numberOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `numberOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/model/analysis.ts:140 — `expressionFieldsOf` is exported and takes `expression: AnalysisExpression` from its caller, and it calls itself at line 140 (`expressionFieldsOf`) with a piece of `expression` (and at line 141) — and nowhere in `expressionFieldsOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionFieldsOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/model/json.ts:69 — `sameJson` is exported, takes a document from its caller (line 63) and hands it to `keysInOrder`, which calls itself at line 69 (`keysInOrder`) with a piece of `value` (and at line 74) — and nowhere in `keysInOrder` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `keysInOrder` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/filter/compile.ts:43 — `withoutBlankLeaves` is exported, takes a document from its caller (line 33) and hands it to `prune`, which calls itself at line 43 (`prune`) with a piece of `group` — and nowhere in `prune` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `prune` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/expressions.ts:105 — `budgetedExpressionIssues` is exported, takes a document from its caller (line 126) and hands it to `expressionIssues`, which calls itself at line 105 (`expressionIssues`) with a piece of `expression` (and at line 113) — and nowhere in `expressionIssues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionIssues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/expressions.ts:258 — `budgetedDerivedIssues` is exported, takes a document from its caller (line 187) and hands it to `derivedIssues`, which calls itself at line 258 (`derivedIssues`) with a piece of `expression` (and at line 259) — and nowhere in `derivedIssues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `derivedIssues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/formula.ts:186 — `expressionText` is exported and takes `expression: AnalysisExpression` from its caller, and it calls itself at line 186 (`expressionText`) with a piece of `expression` (and at line 188) — and nowhere in `expressionText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/formula.ts:217 — `derivedText` is exported and takes `expression: AnalysisDerivedExpression` from its caller, and it calls itself at line 217 (`derivedText`) with a piece of `expression` (and at line 219) — and nowhere in `derivedText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `derivedText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/metricFormat.ts:156 — `derivedOperandFormat` is exported, takes a document from its caller (line 145) and hands it to `walk`, which calls itself at line 156 (`walk`) with a piece of `node` (and at line 157) — and nowhere in `walk` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-view-engine/src/analysis/metricFormat.ts:276 — `formulaFormat` is exported, takes a document from its caller (line 223) and hands it to `reading`, which calls itself at line 276 (`reading`) with a piece of `expression` (and at line 277) — and nowhere in `reading` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `reading` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-generator/src/types/typeResolver.ts:359 — `resolveLiteral` is exported and takes `value: unknown` from its caller, and it calls itself at line 359 (`resolveLiteral`) with a piece of `value` (and at line 363) — and nowhere in `resolveLiteral` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveLiteral` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-generator/src/openapi/references.ts:68 — `findDanglingReferences` is exported, takes a document from its caller (line 59) and hands it to `visit`, which calls itself at line 68 (`visit`) with a piece of `value` (and at line 80) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-client/src/exactJson.ts:62 — `marksNothing` is exported and takes `marks: TextNumbers | undefined` from its caller, and it calls itself at line 62 (`marksNothing`) with a piece of `marks` (and at line 64) — and nowhere in `marksNothing` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `marksNothing` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-client/src/exactJson.ts:428 — `stringifyJson` is exported, takes a document from its caller (line 387) and hands it to `replace`, which calls itself at line 428 (`replace`) with a piece of `value` (and at line 445) — and nowhere in `replace` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `replace` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-client/src/dsl/filter/scope.ts:73 — `requireElementScopedFilter` is exported and takes `expression: FilterExpression` from its caller, and it calls itself at line 73 (`requireElementScopedFilter`) with a piece of `expression` (and at line 77) — and nowhere in `requireElementScopedFilter` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `requireElementScopedFilter` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap typescript/wow-client/src/dsl/aggregation/expressionTrees.ts:86 — `expressionFields` is exported and takes `expression: AggregationExpression` from its caller, and it calls itself at line 86 (`expressionFields`) with a piece of `expression` (and at line 87) — and nowhere in `expressionFields` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `expressionFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap query/query/src/main/kotlin/me/ahoo/wow/query/schema/ManifestSchemaReader.kt:86 — `declaration` is public, takes a document from its caller (line 79) and hands it to `read`, which calls itself at line 86 with a piece of `schema` (and at line 89) — the function is not `tailrec`, so every call is a real frame — and nowhere in `read` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • Recursive walk over a caller-supplied document has no depth cap query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryValues.kt:65 — `sameValue` is public and takes `other: JsonNode` from its caller, and it calls itself at line 65 with a piece of `other` — the function is not `tailrec`, so every call is a real frame — and nowhere in `sameValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `sameValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • Recursive walk over a caller-supplied document has no depth cap platform/ops/console/src/views/parkedCommands.ts:83 — `problemText` is exported and takes `error: unknown` from its caller, and it calls itself at line 83 (`problemText`) with a piece of `error` — and nowhere in `problemText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `problemText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap platform/ops/console/src/views/parkedCommands.ts:116 — `refusedInput` is exported, takes a document from its caller (line 137) and hands it to `refusalOf`, which calls itself at line 116 (`refusalOf`) with a piece of `error` — and nowhere in `refusalOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `refusalOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap platform/analytics/catalog/console/src/views/catalogCommands.ts:112 — `problemText` is exported and takes `error: unknown` from its caller, and it calls itself at line 112 (`problemText`) with a piece of `error` — and nowhere in `problemText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `problemText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MongoNineXEventTarget.kt:168 — `MongoNineXEventTarget.bsonOf` is public and takes `node: JsonNode` from its caller, and it calls itself at line 168 with a piece of `node` (and at line 171) — the function is not `tailrec`, so every call is a real frame — and nowhere in `MongoNineXEventTarget.bsonOf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `MongoNineXEventTarget.bsonOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • Recursive walk over a caller-supplied document has no depth cap migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/StateDiff.kt:74 — `StateDiff.diff` is public, takes a document from its caller (line 52) and hands it to `StateDiff.remove`, which calls itself at line 74 with a piece of `node` — the function is not `tailrec`, so every call is a real frame — and nowhere in `StateDiff.remove` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `StateDiff.remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • Recursive walk over a caller-supplied document has no depth cap migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/StateDiff.kt:87 — `StateDiff.diff` is public, takes a document from its caller (line 52) and hands it to `StateDiff.compare`, which calls itself at line 87 with a piece of `left` (and at line 93) — the function is not `tailrec`, so every call is a real frame — and nowhere in `StateDiff.compare` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `StateDiff.compare` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • + 2 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×22
  • Swallowed exception (empty catch) typescript/wow-view-store/src/wowViewStore.ts:138 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-store/src/wowViewStore.ts:581 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/ui/colorMode.tsx:81 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/ui/record/ColumnResizer.tsx:119 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/ui/record/ColumnResizer.tsx:131 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/ui/kit/copyText.ts:31 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/runtime/actions.ts:372 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/runtime/actions.ts:400 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/runtime/referenceLabels.ts:194 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/runtime/failure/failures.ts:53 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/react/actionRunner.ts:324 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/react/useViewManager.ts:423 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-view-engine/src/react/manager/useCommandRunner.ts:196 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-react/src/internal/readStreamRows.ts:67 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-generator/src/openapi/references.ts:31 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/wow-client/src/problem.ts:329 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/storybook/stories/view-engine/chartDom.ts:381 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) typescript/storybook/scripts/linux-browser.mjs:147 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) platform/ops/console/src/i18n.tsx:251 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) platform/ops/console/src/services/caller.ts:199 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) platform/analytics/catalog/console/src/i18n.tsx:358 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) platform/analytics/catalog/console/src/services/caller.ts:211 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D3 · God Classes · FileTooLong · ×21
  • FileTooLong: retail/generate.ts typescript/storybook/stories/view-engine/retail/generate.ts — FileTooLong — 1700 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1200 over it, 3.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: retail/views.ts typescript/storybook/stories/view-engine/retail/views.ts — FileTooLong — 1278 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 778 over it, 2.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: query/AggregationQuery.kt api/query-api/src/main/kotlin/me/ahoo/wow/api/query/AggregationQuery.kt — FileTooLong — 959 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 459 over it, 1.92× 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: retail/boards.ts typescript/storybook/stories/view-engine/retail/boards.ts — FileTooLong — 899 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 399 over it, 1.80× 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: scripts/verify-package.mjs typescript/wow-view-engine/scripts/verify-package.mjs — FileTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 326 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: kernel/Kernel.kt core/kernel/src/main/kotlin/me/ahoo/wow/kernel/Kernel.kt — FileTooLong — 815 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Kernel (158-1366). The bar is 500 significant lines; this is 315 over it, 1.63× 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: retail/definitions.ts typescript/storybook/stories/view-engine/retail/definitions.ts — FileTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 273 over it, 1.55× 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: boot/WowAutoConfiguration.kt host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/WowAutoConfiguration.kt — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: WowAutoConfiguration (189-1082). The bar is 500 significant lines; this is 256 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: retail/catalog.ts typescript/storybook/stories/view-engine/retail/catalog.ts — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 256 over it, 1.51× 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: query/RelativeTimeFilters.kt api/query-api/src/main/kotlin/me/ahoo/wow/api/query/RelativeTimeFilters.kt — FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× 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: manifest/analyze.ts typescript/wow-generator/src/manifest/analyze.ts — FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 183 over it, 1.37× 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: postgres/PostgresEventLog.kt backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt — FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: PostgresEventLog (107-1047). The bar is 500 significant lines; this is 131 over it, 1.26× 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: schema/QueryViolation.kt query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryViolation.kt — FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: QueryViolation (31-1098). The bar is 500 significant lines; this is 115 over it, 1.23× 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: boot/WowProperties.kt host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/WowProperties.kt — FileTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WowProperties (83-1706). The bar is 500 significant lines; this is 112 over it, 1.22× 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: admission/CommandGateway.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt — FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: CommandGateway (151-1041). The bar is 500 significant lines; this is 108 over it, 1.22× 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: emitters/manifestClients.ts typescript/wow-generator/src/emitters/manifestClients.ts — FileTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 83 over it, 1.17× 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: retail/showcase.ts typescript/storybook/stories/view-engine/retail/showcase.ts — FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 79 over it, 1.16× 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: migrate/MigrateData.kt migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MigrateData.kt — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 62 over it, 1.12× 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: log/MongoEventLog.kt backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: MongoEventLog (139-920). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: cluster/PartitionOwnership.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt — FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: PartitionOwnership (132-896). The bar is 500 significant lines; this is 6 over it, 1.01× 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: wait/WaitCoordinator.kt core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt — FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: WaitCoordinator (214-903). The bar is 500 significant lines; this is 6 over it, 1.01× 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×19
  • Repeated repair: typescript/wow-view-engine/src/ui/record/columns.ts typescript/wow-view-engine/src/ui/record/columns.ts:374 — typescript/wow-view-engine/src/ui/record/columns.ts changed 25 times in last 90 days and 13 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is columns.tablePins at line 374), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): the nine known accessibility items of the pre-release review (#3792)”; “fix(view-engine): the analysis table reads like an analyst's table (Ahoo-Wang/fetcher#1807)”; “fix(view-engine): a dashboard panel's record table holds no end column on the right (Ahoo-Wang/fetcher#1797)”; “fix(view-engine): the held columns' edges are drawn only while the middle can scroll (P-23, D13 amended) (Ahoo-Wang/fetcher#1703)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/record/columns.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/filter/validate.ts typescript/wow-view-engine/src/filter/validate.ts:68 — typescript/wow-view-engine/src/filter/validate.ts changed 15 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is validate.validateFilter at line 68), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): a misspelled binding and a stale EQ on an enum no longer fail silently (#3902)”; “fix(view-engine): a host kind that throws judging a condition puts out only the panel standing on it (#3767)”; “fix(view-engine): read a number band's two bounds as one segment (#3311)”; “fix(view-engine): a condition whose kind has no editor is read-only and refused, never a text box; the picker offers no such field (F-06) (Ahoo-Wang/fetcher#1688)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/filter/validate.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/filter/inputs/number.tsx typescript/wow-view-engine/src/ui/filter/inputs/number.tsx:108 — typescript/wow-view-engine/src/ui/filter/inputs/number.tsx changed 15 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is number.NumberValue at line 108), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): declared actions — outcome unknown, focus kept, said in the host's words (review round 2, B1) (#3834)”; “fix(view-engine): second-round accessibility findings — focus after 展开 and the drop notice, menu focus mark and forced colours, zh names; the statement re-evaluated (#3826)”; “fix(view-engine): the analysis tray reads clearly — a labelled result step, a quiet Apply, a capped height (Ahoo-Wang/fetcher#1805)”; “fix(view-engine): chart options button, follow-up menu width, top-N field (Ahoo-Wang/fetcher#1799)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/filter/inputs/number.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.
  • Repeated repair: typescript/wow-view-engine/src/ui/filter/inputs/daterange.tsx typescript/wow-view-engine/src/ui/filter/inputs/daterange.tsx:42 — typescript/wow-view-engine/src/ui/filter/inputs/daterange.tsx changed 14 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is daterange.AbsoluteDate at line 42), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): controls' accessible names hold their visible text (WCAG 2.5.3) (#4904)”; “fix(view-engine): read a stored instant in the date editor on the surface's clock; one cached zone reader (#4150)”; “fix(view-engine): workbench and board interaction — hand-over focus, an added panel in view, no leave question for look-ups, the follow-up hint, a one-day date on the day in force (review round 2, B6) (#3849)”; “fix(view-engine): a valued calendar opens on its value's month, not today's (#3813)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/filter/inputs/daterange.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.
  • Repeated repair: typescript/wow-view-engine/src/analysis/validate.ts typescript/wow-view-engine/src/analysis/validate.ts:57 — typescript/wow-view-engine/src/analysis/validate.ts changed 15 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is validate.validateAnalysis at line 57), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): the table always runs; chart findings name columns, not aliases (Ahoo-Wang/fetcher#1838)”; “fix(view-engine): the earliest and the latest of a date read as dates, not as epoch milliseconds (production review) (Ahoo-Wang/fetcher#1761)”; “fix(view-engine): the analysis kernel walks elements as Wow's chain, compiles element-relative names, rejects root fields under elements, and defaults TERMS missing keys (batch K) (Ahoo-Wang/fetcher#1717)”; “fix(view-engine): low-severity findings from the package review (Ahoo-Wang/fetcher#1517)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/analysis/validate.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/storybook/stories/view-engine/chartDom.ts typescript/storybook/stories/view-engine/chartDom.ts:80 — typescript/storybook/stories/view-engine/chartDom.ts changed 13 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is chartDom.painted at line 80), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): what the nightly WebKit leg found — a focus mark shows at once, a long table lets go of its rows when printing ends, a bulk command's keyboard lands on its line; the leg runs on macOS (#3828)”; “fix(view-engine): keep chart annotations off each other; label only the peak and trough of a long row of bars (#3654)”; “fix(view-engine): keep the chart tooltip's swatch 10px — the plot's svg rule reaches the drawing only (#3434)”; “fix(view-engine): the Storybook interactions pass in Firefox and WebKit (#3389)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/storybook/stories/view-engine/chartDom.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/filter/time.ts typescript/wow-view-engine/src/filter/time.ts:376 — typescript/wow-view-engine/src/filter/time.ts changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is time.periodOf at line 376), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): period-to-date and hourly buckets keep the offset of the moment they name (#5579)”; “fix(view-engine): time windows and number formatting (review round 2, B3) (#3833)”; “fix(view-engine): the analysis review's P2 leftovers — group names, one wording for a drilled bucket, header sort names (Ahoo-Wang/fetcher#1870)”; “fix(view-engine): medium-severity findings from the package review (Ahoo-Wang/fetcher#1514)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/filter/time.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/filter/compile.ts typescript/wow-view-engine/src/filter/compile.ts:33 — typescript/wow-view-engine/src/filter/compile.ts changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is compile.withoutBlankLeaves at line 33), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): a condition added and not filled in is not an edit of the view (#4138)”; “fix(view-engine): a misspelled binding and a stale EQ on an enum no longer fail silently (#3902)”; “fix(view-engine): medium-severity findings from the package review (Ahoo-Wang/fetcher#1514)”; “fix(view-engine): run only admitted configs, hold unknown writes, and close a date range on its last day (Ahoo-Wang/fetcher#1513)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/filter/compile.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/storybook/stories/view-engine/contrast.ts typescript/storybook/stories/view-engine/contrast.ts:211 — typescript/storybook/stories/view-engine/contrast.ts changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is contrast.measureFocusMark at line 211), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): the Storybook interactions pass in Firefox and WebKit (#3389)”; “fix(view-engine): theme foundation for phase 5 (5A) (#3312)”; “fix(view-engine): R2 — menus hand focus to their dialogs, one voice per board, focus landings, tokens, one panel handle (Ahoo-Wang/fetcher#1888)”; “fix(view-engine): 标题栏的五条打磨——还原先问一句、动效让给 reduce、两级标题、看得见的分隔线与徽章边 (P-01/P-06/P-08/P-09/P-10) (Ahoo-Wang/fetcher#1677)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/storybook/stories/view-engine/contrast.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/charts/pieOption.ts typescript/wow-view-engine/src/ui/charts/pieOption.ts:231 — typescript/wow-view-engine/src/ui/charts/pieOption.ts changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is pieOption.pieOption at line 231), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): the known 界面与图表 items of the pre-release review (#3802)”; “fix(view-engine): a pie wears its categories' tones, and no groups is the empty state (#3579)”; “fix(view-engine)!: retail-scene defects — empty group, ANY in totals, yes/no series, dense zeros, embed landmarks, metric card changes (#3381)”; “fix(view-engine): analysis chart P2 polish — emphasis, labels, scales, titles, funnel, drawer (Ahoo-Wang/fetcher#1856)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/pieOption.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpClusterChannel.kt edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpClusterChannel.kt:173 — edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpClusterChannel.kt changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is HttpClusterChannel.post at line 173), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(runtime): a forward not sent by its deadline is withdrawn or busy, and the owner's answer just after it is its outcome (X-61) (#5355)”; “fix(http): internal HTTP/2 waits at the peer's stream limit and stops resetting forwards at their deadline (X-55) (#5340)”; “fix(v10): the internal port's trust boundary (F5, D226) (#4525)”; “fix(v10): review A.1 kernel and runtime findings (F1, D223) (#4516)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- edge/http/src/main/kotlin/me/ahoo/wow/http/internal/HttpClusterChannel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/filter/inputs/relative.tsx typescript/wow-view-engine/src/ui/filter/inputs/relative.tsx:37 — typescript/wow-view-engine/src/ui/filter/inputs/relative.tsx changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is relative.RelativeDate at line 37), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): a board's date filter shows what the board reads (#3619)”; “fix(view-engine): narrow boards keep their filters and badges inside, and a wide panel table says it scrolls (#3583)”; “fix(view-engine): a count picks its English form ("1 record", "last 30 days") (#3574)”; “fix(view-engine): the forms half of the shadcn audit — Field, FieldSet, FieldError, and an invalid state a reader can hear (Ahoo-Wang/fetcher#1634)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/filter/inputs/relative.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.
  • Repeated repair: typescript/wow-view-engine/src/ui/record/queryAnnouncement.ts typescript/wow-view-engine/src/ui/record/queryAnnouncement.ts:36 — typescript/wow-view-engine/src/ui/record/queryAnnouncement.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is queryAnnouncement.querySentence at line 36), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): say the page past the first, lead the field search into its list, walk the chart tiles by row (#4136)”; “fix(view-engine): declared actions — outcome unknown, focus kept, said in the host's words (review round 2, B1) (#3834)”; “fix(view-engine): removing unavailable conditions reaches inside an element match; the query announcement empties on failure (#3733)”; “fix(view-engine): a count picks its English form ("1 record", "last 30 days") (#3574)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/record/queryAnnouncement.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: backends/kafka/src/main/kotlin/me/ahoo/wow/kafka/SharedTopicConsumer.kt backends/kafka/src/main/kotlin/me/ahoo/wow/kafka/SharedTopicConsumer.kt:151 — backends/kafka/src/main/kotlin/me/ahoo/wow/kafka/SharedTopicConsumer.kt changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is SharedTopicConsumer.run at line 151), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(kafka): offset reads and reassignments no longer warn of unassigned partitions; consumers are named (F22) (#5007)”; “fix(v10): R2 review batch G4 — backends (#4556)”; “fix(v10): review A.2 backend findings (F3) (#4520)”; “fix(v10): a topic's shared consumer starts a new session after its last reader leaves (C.1 F1) (#4448)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- backends/kafka/src/main/kotlin/me/ahoo/wow/kafka/SharedTopicConsumer.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/workbench/Unopenable.tsx typescript/wow-view-engine/src/ui/workbench/Unopenable.tsx:43 — typescript/wow-view-engine/src/ui/workbench/Unopenable.tsx changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is Unopenable.Unopenable at line 43), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): visual polish — flat chart words, whole text one hover away, gauge, filter pill, mixed select-all (review round 2, B12) (#3848)”; “fix(view-engine): a view that failed to open offers a retry; a panel whose view could not be read is not called deleted; the first describe has a deadline (review round 2, B5) (#3842)”; “fix(view-engine): say dashboard in what the engine reports about a board (#3297)”; “fix(view-engine): R7b — the board says 仪表盘, 保存, filters in a sheet on a phone, no applied band on a board, wording (Ahoo-Wang/fetcher#1897)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/workbench/Unopenable.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.
  • Repeated repair: typescript/wow-view-engine/src/react/useRecordActions.ts typescript/wow-view-engine/src/react/useRecordActions.ts:467 — typescript/wow-view-engine/src/react/useRecordActions.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is useRecordActions.useRecordActions.execute at line 467), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ops-console, view-engine): the retry spec form keeps what was typed and checks as the service does; row controls named by the record (UI-13, UI-30) (#5372)”; “fix(ops-console, view-engine): the UI walk's fixes for the ops console and the engine (#5232)”; “fix(view-engine): declared actions — outcome unknown, focus kept, said in the host's words (review round 2, B1) (#3834)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/react/useRecordActions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/charts/timeOption.ts typescript/wow-view-engine/src/ui/charts/timeOption.ts:262 — typescript/wow-view-engine/src/ui/charts/timeOption.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is timeOption.themeRiverOption at line 262), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): give a river's axis room for its first and last names (#4195)”; “fix(view-engine): the known 界面与图表 items of the pre-release review (#3802)”; “fix(view-engine): the period still under way is drawn, marked and read for nothing (#3695)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/timeOption.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/ui/charts/palette.ts typescript/wow-view-engine/src/ui/charts/palette.ts:71 — typescript/wow-view-engine/src/ui/charts/palette.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is palette.pinnedColor at line 71), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(view-engine): the known 界面与图表 items of the pre-release review (#3802)”; “fix(view-engine): a pie wears its categories' tones, and no groups is the empty state (#3579)”; “fix(view-engine): a time axis runs forward, and the palette has eight colours before a pie folds (Ahoo-Wang/fetcher#1798)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/ui/charts/palette.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: typescript/wow-view-engine/src/runtime/failure/issueReport.ts typescript/wow-view-engine/src/runtime/failure/issueReport.ts:125 — typescript/wow-view-engine/src/runtime/failure/issueReport.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is issueReport.consoleIssueReporter at line 125), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(typescript): an empty id refused, AGGREGATE_REQUIRED, the generator's optional peers, one primary action (X-49) (#5293)”; “fix(view-engine): focus never falls to the page when its opener is gone; development warns when an action reads an unfetched field (#3904)”; “fix(view-engine): a misspelled binding and a stale EQ on an enum no longer fail silently (#3902)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-11..2026-11-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-11 17:03:50 -08:00' --until='2026-11-09 17:03:50 -08:00' --full-history --no-merges -- typescript/wow-view-engine/src/runtime/failure/issueReport.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D3 · God Classes · TooManyMethods · ×16
  • TooManyMethods: AggregationQueryDsl api/query-api/src/main/kotlin/me/ahoo/wow/api/query/dsl/AggregationQueryDsl.kt:47 — TooManyMethods — 86 methods. The bar is 30 methods; this is 56 over it, 2.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FilterDsl api/query-api/src/main/kotlin/me/ahoo/wow/api/query/dsl/FilterDsl.kt:98 — TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: BoardCommands typescript/wow-view-engine/src/runtime/dashboard/commands.ts:228 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: Kernel core/kernel/src/main/kotlin/me/ahoo/wow/kernel/Kernel.kt:158 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PostgresEventLog backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:107 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: QueryResolver query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt:119 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: ViewEngine typescript/wow-view-engine/src/runtime/viewEngine.ts:117 — 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: WowAutoConfiguration host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/WowAutoConfiguration.kt:189 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: DataViewRuntime typescript/wow-view-engine/src/runtime/viewRuntime.ts:96 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: AggregateModelBuilder core/kernel/src/main/kotlin/me/ahoo/wow/kernel/AggregateModelDsl.kt:52 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SubscriptionWorker core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt:110 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: DashboardViewRuntime typescript/wow-view-engine/src/runtime/dashboardRuntime.ts:116 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: SubscriptionRuntime core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionRuntime.kt:77 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: PartitionOwnership core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt:132 — 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: QueryHandler edge/http/src/main/kotlin/me/ahoo/wow/http/query/QueryHandler.kt:114 — 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.
  • TooManyMethods: Builder query/query/src/main/kotlin/me/ahoo/wow/query/engine/QueryEngine.kt:139 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
R4 · Test Coverage · No test reaches this file · ×16
  • No test reaches this file typescript/wow-view-engine/scripts/api-report.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-client/scripts/api-report.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-react/scripts/api-report.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-view-store/scripts/api-report.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/scripts/verify-storybook-browser.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/stories/view-engine/IntroBlocks.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/scripts/linux-browser.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-view-engine/scripts/scope-utilities.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/scripts/shard-sequencer.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/scripts/visual.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/stories/view-engine/integration/wowCommands.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/scripts/test-durations.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-view-engine/scripts/build-theme-check.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/storybook/stories/view-engine/integration/wowSource.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-view-engine/src/styles.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file typescript/wow-view-engine/theme-check/bin.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D35 · Change Coupling · Change coupling · ×13
  • Change coupling: DashboardWorkbench.tsx ↔ DataWorkbench.tsx typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:1 — `typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx` and `typescript/wow-view-engine/src/ui/DataWorkbench.tsx` change together 75% of the time (15 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `94f5c16e` feat(view-engine): a workbench can be a named region inside a host's …; `6b440fda` feat(view-engine): preset mechanism and theme="system" (phase 5, 5B) …; `ec25f13f` fix(view-engine): every number reads the same everywhere, a row actio… — run `git show` on any of them.
  • Change coupling: validateDefinition.ts ↔ definition.ts typescript/wow-view-engine/src/runtime/validateDefinition.ts:1 — `typescript/wow-view-engine/src/runtime/validateDefinition.ts` and `typescript/wow-view-engine/src/ui/messages/definition.ts` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8f45b4b8` fix(view-engine): a declared board's owned analysis is admitted whole…; `55930005` feat(view-engine): search inside an element where the source offers i…; `f468ac6a` feat(view-engine): an array of objects reads in a cell as its element… — run `git show` on any of them.
  • Change coupling: DataTab.tsx ↔ DisplayTab.tsx typescript/wow-view-engine/src/ui/analysis/DataTab.tsx:1 — `typescript/wow-view-engine/src/ui/analysis/DataTab.tsx` and `typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx` 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `2fe940e5` refactor(view-engine): one chart-family table instead of fourteen swi…; `72e9f818` feat(view-engine): combo right axis by units; missing values and 100%…; `848a0473` fix(view-engine): the analysis view keeps the keyboard's place — visu… — run `git show` on any of them.
  • Change coupling: Cartesian.tsx ↔ PieSlices.tsx typescript/wow-view-engine/src/ui/charts/Cartesian.tsx:1 — `typescript/wow-view-engine/src/ui/charts/Cartesian.tsx` and `typescript/wow-view-engine/src/ui/charts/PieSlices.tsx` 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dd2d0d1d` fix(view-engine): narrow pie shares whole, <0.1% shares, three-digit …; `31e8eccd` feat(view-engine): a cartesian chart writes its values unasked, where…; `2eaee957` fix(view-engine): charts stop animating for a reader who asked for le… — run `git show` on any of them.
  • Change coupling: ColumnRow.tsx ↔ record.ts typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:1 — `typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx` and `typescript/wow-view-engine/src/ui/messages/record.ts` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `76666a6f` feat(view-engine): a date column can carry its earliest and latest as…; `abda4f25` fix(view-engine): five screen-reader credentials — queries, pins, the…; `e878b791` fix(view-engine): the pin cap reads a fitting table as fitting, the e… — run `git show` on any of them.
  • Change coupling: FilterPanel.tsx ↔ messages.ts typescript/wow-view-engine/src/ui/filter/FilterPanel.tsx:1 — `typescript/wow-view-engine/src/ui/filter/FilterPanel.tsx` and `typescript/wow-view-engine/src/ui/kit/messages.ts` change together 53% of the time (8 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `33b708b6` feat(view-engine): field groups, one searchable entry for adding, and… (at that commit the files were still `typescript/wow-view-engine/src/ui/FilterPanel.tsx` and `typescript/wow-view-engine/src/ui/messages.ts`); `bdc29feb` feat(view-engine): lay a group's conditions out as inline pills (Ahoo… (at that commit the files were still `typescript/wow-view-engine/src/ui/FilterPanel.tsx` and `typescript/wow-view-engine/src/ui/messages.ts`); `c68525f1` feat(view-engine): one condition per field in a group (Ahoo-Wang/fetc… (at that commit the files were still `typescript/wow-view-engine/src/ui/FilterPanel.tsx` and `typescript/wow-view-engine/src/ui/messages.ts`) — run `git show` on any of them.
  • Change coupling: ColumnSettings.tsx ↔ record.ts typescript/wow-view-engine/src/ui/columns/ColumnSettings.tsx:1 — `typescript/wow-view-engine/src/ui/columns/ColumnSettings.tsx` and `typescript/wow-view-engine/src/ui/messages/record.ts` change together 53% of the time (9 of the 17 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 `abda4f25` fix(view-engine): five screen-reader credentials — queries, pins, the… (at that commit the file was still `typescript/wow-view-engine/src/ui/ColumnSettings.tsx`); `06a6c501` feat(view-engine): the column settings on a wide table — scroll, sear… (at that commit the file was still `typescript/wow-view-engine/src/ui/ColumnSettings.tsx`); `e878b791` fix(view-engine): the pin cap reads a fitting table as fitting, the e… (at that commit the file was still `typescript/wow-view-engine/src/ui/ColumnSettings.tsx`) — run `git show` on any of them.
  • Change coupling: ViewHeader.tsx ↔ WorkbenchShell.tsx typescript/wow-view-engine/src/ui/workbench/ViewHeader.tsx:1 — `typescript/wow-view-engine/src/ui/workbench/ViewHeader.tsx` and `typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `28d45a56` fix(view-engine): 标题栏的五条打磨——还原先问一句、动效让给 reduce、两级标题、看得见的分隔线与徽章边 (P-01… (at that commit the files were still `typescript/wow-view-engine/src/ui/ViewHeader.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`); `da396db5` fix(view-engine): one rule across both heads, one frame round the res… (at that commit the files were still `typescript/wow-view-engine/src/ui/ViewHeader.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`); `a339fb76` feat(view-engine): the title bar, status line, tray, applied band and… (at that commit the files were still `typescript/wow-view-engine/src/ui/ViewHeader.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`) — run `git show` on any of them.
  • Change coupling: ConditionPill.tsx ↔ filter.ts typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:1 — `typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx` and `typescript/wow-view-engine/src/ui/messages/filter.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `78cd727d` fix(view-engine): one word per condition: yes or no, the list's relat…; `e68aad12` feat(view-engine): a text condition's values are offered from the dat…; `1f9084e9` feat(view-engine): a reference field's candidates are searched from t… — run `git show` on any of them.
  • Change coupling: AnalysisChart.tsx ↔ PieSlices.tsx typescript/wow-view-engine/src/ui/analysis/AnalysisChart.tsx:1 — `typescript/wow-view-engine/src/ui/analysis/AnalysisChart.tsx` and `typescript/wow-view-engine/src/ui/charts/PieSlices.tsx` change together 50% of the time (6 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 6 shared commits counted here, the most recent 3 are `67d4e228` fix(view-engine): a pie wears its categories' tones, and no groups is… (at that commit the file was still `typescript/wow-view-engine/src/ui/AnalysisChart.tsx`); `1500bd8a` feat(view-engine): pie, donut and scatter draw with ECharts — shares … (at that commit the file was still `typescript/wow-view-engine/src/ui/AnalysisChart.tsx`); `6f8b1096` fix(view-engine): a chart type switch keeps its metric, and a pie say… (at that commit the file was still `typescript/wow-view-engine/src/ui/AnalysisChart.tsx`) — run `git show` on any of them.
  • Change coupling: DashboardGrid.tsx ↔ dashboard.ts typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:1 — `typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx` and `typescript/wow-view-engine/src/ui/messages/dashboard.ts` change together 50% of the time (6 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 6 shared commits counted here, the most recent 3 are `a9d31e90` fix(view-engine): board table panels grow to their rows and say what … (at that commit the file was still `typescript/wow-view-engine/src/ui/DashboardGrid.tsx`); `cfb68547` fix(view-engine): a board's date filter shows what the board reads (#… (at that commit the file was still `typescript/wow-view-engine/src/ui/DashboardGrid.tsx`); `89eadbb0` feat(view-engine): lay a dashboard out at a fixed width or full width… (at that commit the file was still `typescript/wow-view-engine/src/ui/DashboardGrid.tsx`) — run `git show` on any of them.
  • Change coupling: ChartPicker.tsx ↔ AnalysisParts.tsx typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx:1 — `typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx` and `typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx` 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 `b83269e4` refactor(view-engine): share the visualization panel and read looks t…; `08fb1855` fix(view-engine): chart options button, follow-up menu width, top-N f…; `848a0473` fix(view-engine): the analysis view keeps the keyboard's place — visu… — run `git show` on any of them.
  • Change coupling: RecordPagination.tsx ↔ WorkbenchShell.tsx typescript/wow-view-engine/src/ui/record/RecordPagination.tsx:1 — `typescript/wow-view-engine/src/ui/record/RecordPagination.tsx` and `typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx` 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 `e54c6635` fix(view-engine): keyboard and screen-reader walkthrough, WCAG 2.2 AA… (at that commit the files were still `typescript/wow-view-engine/src/ui/RecordPagination.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`); `9fa3fbe5` fix(view-engine): every icon-only button says its name on hover (Ahoo… (at that commit the files were still `typescript/wow-view-engine/src/ui/RecordPagination.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`); `0b4d1ab9` feat(view-engine): the result runs to the edge — pinned ends with the… (at that commit the files were still `typescript/wow-view-engine/src/ui/RecordPagination.tsx` and `typescript/wow-view-engine/src/ui/WorkbenchShell.tsx`) — run `git show` on any of them.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: Kernel core/kernel/src/main/kotlin/me/ahoo/wow/kernel/Kernel.kt:158 — ClassTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 323 over it, 1.81× 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: WowAutoConfiguration host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/WowAutoConfiguration.kt:189 — ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 227 over it, 1.57× 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: QueryViolation query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryViolation.kt:31 — ClassTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 207 over it, 1.52× 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: PostgresEventLog backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:107 — ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 169 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: WowProperties host/spring-boot/src/main/kotlin/me/ahoo/wow/spring/boot/WowProperties.kt:83 — ClassTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 155 over it, 1.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CommandGateway core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:151 — ClassTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 147 over it, 1.37× 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: PartitionOwnership core/runtime/src/main/kotlin/me/ahoo/wow/runtime/cluster/PartitionOwnership.kt:132 — ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 52 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.
  • ClassTooLong: MongoEventLog backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt:139 — ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 50 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.
  • ClassTooLong: SubscriptionWorker core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt:110 — ClassTooLong — 442 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 42 over it, 1.11× 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: MongoNineXEventSource migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/MongoNineXEventSource.kt:51 — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 2 over it, 1.01× 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.
D31 · IaC & Container Security · Medium IaC · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×10
  • Sync-over-async blocking examples/eshop/web/e2e/diagnostics.ts:56 — `existsSync` in `attachServerDiagnostics` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking examples/eshop/web/e2e/diagnostics.ts:63 — `existsSync` in `attachServerDiagnostics` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/src/output/outputStore.ts:218 — `fs.readFileSync` in `callback to files.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/src/output/outputStore.ts:226 — `fs.mkdirSync` in `attempt("write")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/generation.ts:119 — `writeFileSync` in `generateCold` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/generation.ts:123 — `writeFileSync` in `generateCold` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/generation.ts:171 — `writeFileSync` in `generateProject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/generation.ts:199 — `realpathSync` in `generateProject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/probes.ts:49 — `writeFileSync` in `generateCompiling` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking typescript/wow-generator/test/support/probes.ts:54 — `readFileSync` in `read` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×8
  • Duplicated block (5 lines × 2) backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseDatasetAccess.kt:118 — backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseDatasetAccess.kt:118-122 | backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseFilterCompiler.kt:89-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseDatasetAccess.kt: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 (5 lines × 2) skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:186 — skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:186-190 | skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:201-205 — 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 `skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:186` 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) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/pipeline/MongoAggregationWindows.kt:138 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/pipeline/MongoAggregationWindows.kt:138-142 | query/query/src/main/kotlin/me/ahoo/wow/query/aggregation/GroupWindows.kt:33-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.
  • Duplicated block (5 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresFilterCompiler.kt:378 — backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresFilterCompiler.kt:378-382 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryValues.kt:39-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) platform/view-store/view-store-server/src/main/kotlin/me/ahoo/wow/viewstore/server/QueriedViewReads.kt:63 — platform/view-store/view-store-server/src/main/kotlin/me/ahoo/wow/viewstore/server/QueriedViewReads.kt:63-67 | platform/view-store/view-store-server/src/main/kotlin/me/ahoo/wow/viewstore/server/system/StoredSystemViews.kt:81-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:496 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:496-500 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:670-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) edge/http/src/main/kotlin/me/ahoo/wow/http/PeerReadRoutes.kt:105 — edge/http/src/main/kotlin/me/ahoo/wow/http/PeerReadRoutes.kt:105-109 | edge/http/src/main/kotlin/me/ahoo/wow/http/WowRoutes.kt:144-148 — 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) query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt:313 — query/query/src/main/kotlin/me/ahoo/wow/query/resolve/QueryResolver.kt:313-317 | query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryFieldAliases.kt:84-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×7
  • Duplicated block (8 lines × 2) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt:411 — compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt:411-418 | compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt:511-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferences.kt:37 — platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferences.kt:37-44 | platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/wording/DatasetWording.kt:45-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventDocuments.kt:94 — backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventDocuments.kt:94-101 | backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/snapshot/ElasticsearchSnapshotDocuments.kt:150-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `operator` to `Operator?) = if (operator == null` in one and `Operator?): JsonNode = if (operator == null` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferencesState.kt:40 — platform/view-store/view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferencesState.kt:40-47 | skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/preferences/ViewPreferencesState.kt:38-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) query/query/src/main/kotlin/me/ahoo/wow/query/aggregation/ResidualOperators.kt:64 — query/query/src/main/kotlin/me/ahoo/wow/query/aggregation/ResidualOperators.kt:64-71 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt:269-276 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLogTables.kt:169 — backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLogTables.kt:169-176 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLogTables.kt:228-235 — 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 `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLogTables.kt:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchQuerySupport.kt:47 — backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchQuerySupport.kt:47-54 | query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryStorageAdapter.kt:182-189 — 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) · ×5
  • Duplicated block (6 lines × 2) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt:345 — backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt:345-350 | backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt:354-359 — 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 `backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchIndexMappingResolver.kt:345` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:450 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:450-455 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:641-646 — 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 `core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:450` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:198 — skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:198-203 | skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:213-218 — 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 `skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/ViewStoreOpenApi.kt:198` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 2) edge/client/src/main/kotlin/me/ahoo/wow/client/HttpQueryApi.kt:423 — edge/client/src/main/kotlin/me/ahoo/wow/client/HttpQueryApi.kt:423-428 | query/query/src/main/kotlin/me/ahoo/wow/query/read/InProcessQueryApi.kt:352-357 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `query/query/src/main/kotlin/me/ahoo/wow/query/read/InProcessQueryApi.kt:360` calls `covers` and `edge/client/src/main/kotlin/me/ahoo/wow/client/HttpQueryApi.kt:429` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresSnapshotSqlCompiler.kt:45 — backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresSnapshotSqlCompiler.kt:45-50 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresSnapshotSqlCompiler.kt:59-64 — 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.
AX2 · Stateful singletons · Stateful singleton · ×4
  • Stateful singleton: StoredSystemViews skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-starter/src/main/kotlin/me/ahoo/wow/viewstore/starter/system/StoredSystemViews.kt:37 — `StoredSystemViews` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (warnedClashes; e.g. `warnedClashes` in `warnClash` at line 69).
  • Stateful singleton: CatalogWatcher platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/CatalogWatcher.kt:50 — `CatalogWatcher` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (seen; e.g. `seen` in `look` at line 60).
  • Stateful singleton: DatasetPublicationWatcher platform/analytics/catalog/server/src/main/kotlin/me/ahoo/wow/analytics/catalog/server/DatasetPublicationWatcher.kt:62 — `DatasetPublicationWatcher` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (lastFull, watermark, applied; e.g. `lastFull` in `sync` at line 90).
  • Stateful singleton: CommandGateway core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:151 — `CommandGateway` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (rejectedWithEvents; e.g. `rejectedWithEvents` in `transformerRejected` at line 889).
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt:171 — backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt:171-177 | backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt:214-220 — 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 `backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/events/ElasticsearchEventSink.kt:171` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt:286 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/log/MongoEventLog.kt:286-292 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:379-385 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/Admission.kt:117 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/Admission.kt:117-123 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/ServiceRouteAuthorizer.kt:84-90 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `authorizers` to `List<CommandAuthorizer>): CommandAuthorizer = when (authorizers.size` in one and `List<ServiceRouteAuthorizer>): ServiceRouteAuthorizer = when (authorizers.size` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt:131 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt:131-137 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/source/TopicEntries.kt:143-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×3
  • Change-coupling hub: zh-CN.ts → chart.ts, chart.ts, useAnalysisEditor.ts, useAnalysisResult.ts, useDashboard.ts, useRecordTable.ts, useWorkbench.ts, project.ts, execute.ts, validateDefinition.ts, DataWorkbench.tsx, EmbeddedView.tsx, AnalysisChart.tsx, ChartPicker.tsx, DataTab.tsx, DisplayTab.tsx, Cartesian.tsx, PieSlices.tsx, family.ts, ColumnRow.tsx, ColumnSettings.tsx, ConditionPill.tsx, FilterValueEditor.tsx, display.ts, ViewManagerRow.tsx, RecordPagination.tsx, SortableHeader.tsx, SummaryRows.tsx, cells.tsx, SortSettings.tsx, AnalysisParts.tsx, RecordParts.tsx, ResultToolbar.tsx typescript/wow-view-engine/src/ui/messages/zh-CN.ts — `typescript/wow-view-engine/src/ui/messages/zh-CN.ts` changes together with 33 other files — `typescript/wow-view-engine/src/analysis/chart.ts`, `typescript/wow-view-engine/src/model/chart.ts`, `typescript/wow-view-engine/src/react/useAnalysisEditor.ts`, `typescript/wow-view-engine/src/react/useAnalysisResult.ts`, `typescript/wow-view-engine/src/react/useDashboard.ts`, `typescript/wow-view-engine/src/react/useRecordTable.ts`, `typescript/wow-view-engine/src/react/useWorkbench.ts`, `typescript/wow-view-engine/src/record/project.ts`, `typescript/wow-view-engine/src/runtime/execute.ts`, `typescript/wow-view-engine/src/runtime/validateDefinition.ts`, `typescript/wow-view-engine/src/ui/DataWorkbench.tsx`, `typescript/wow-view-engine/src/ui/EmbeddedView.tsx`, `typescript/wow-view-engine/src/ui/analysis/AnalysisChart.tsx`, `typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx`, `typescript/wow-view-engine/src/ui/analysis/DataTab.tsx`, `typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx`, `typescript/wow-view-engine/src/ui/charts/Cartesian.tsx`, `typescript/wow-view-engine/src/ui/charts/PieSlices.tsx`, `typescript/wow-view-engine/src/ui/charts/family.ts`, `typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx`, `typescript/wow-view-engine/src/ui/columns/ColumnSettings.tsx`, `typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx`, `typescript/wow-view-engine/src/ui/filter/FilterValueEditor.tsx`, `typescript/wow-view-engine/src/ui/kit/display.ts`, `typescript/wow-view-engine/src/ui/manage/ViewManagerRow.tsx`, `typescript/wow-view-engine/src/ui/record/RecordPagination.tsx`, `typescript/wow-view-engine/src/ui/record/SortableHeader.tsx`, `typescript/wow-view-engine/src/ui/record/SummaryRows.tsx`, `typescript/wow-view-engine/src/ui/record/cells.tsx`, `typescript/wow-view-engine/src/ui/sort/SortSettings.tsx`, `typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx`, `typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx`, `typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx` — none of which declares a dependency on it: one file is the hub of 33 separate couplings, not 33 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 33.
  • Change-coupling hub: analysis.ts → chart.ts, chart.ts, useAnalysisEditor.ts, ChartPicker.tsx, DataTab.tsx, DisplayTab.tsx, family.ts, AnalysisParts.tsx typescript/wow-view-engine/src/ui/messages/analysis.ts — `typescript/wow-view-engine/src/ui/messages/analysis.ts` changes together with 8 other files — `typescript/wow-view-engine/src/analysis/chart.ts`, `typescript/wow-view-engine/src/model/chart.ts`, `typescript/wow-view-engine/src/react/useAnalysisEditor.ts`, `typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx`, `typescript/wow-view-engine/src/ui/analysis/DataTab.tsx`, `typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx`, `typescript/wow-view-engine/src/ui/charts/family.ts`, `typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx` — none of which declares a dependency on it: one file is the hub of 8 separate couplings, not 8 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 8.
  • Change-coupling hub: SortSettings.tsx → ColumnRow.tsx, ColumnSettings.tsx, ViewManagerRow.tsx typescript/wow-view-engine/src/ui/sort/SortSettings.tsx — `typescript/wow-view-engine/src/ui/sort/SortSettings.tsx` changes together with 3 other files — `typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx`, `typescript/wow-view-engine/src/ui/columns/ColumnSettings.tsx`, `typescript/wow-view-engine/src/ui/manage/ViewManagerRow.tsx` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:221 — backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:221-231 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/timer/PostgresTimerStore.kt:102-112 — 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 `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:221` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryAggregation.kt:223 — query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryAggregation.kt:223-233 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt:244-254 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryAggregation.kt:223` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `expression` to `DerivedExpression` in one and `AggregationExpression` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 2) scripts/validate_wow_skills.py:193 — scripts/validate_wow_skills.py:193-203 | scripts/validate_wow_skills.py:258-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R11 · Import Boundaries · Boundary violation [package · ×3
  • Boundary violation [package:relative-cross-package] typescript/wow-client/scripts/api-report.mjs:45 — typescript/wow-client/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] typescript/wow-react/scripts/api-report.mjs:45 — typescript/wow-react/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] typescript/wow-view-store/scripts/api-report.mjs:45 — typescript/wow-view-store/scripts/api-report.mjs:45 reaches into another package with a relative path (../../../.github/scripts/symbol-index.mjs) — import the package by name instead.
R4 · Test Coverage · This test file cannot be loaded · ×3
  • This test file cannot be loaded typescript/storybook/scripts/verify-storybook.mjs:20 — typescript/storybook/scripts/verify-storybook.mjs:20 imports '../stories/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded typescript/storybook/stories/view-engine/retail/descriptions.test.ts:35 — typescript/storybook/stories/view-engine/retail/descriptions.test.ts:35 imports '../', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded typescript/wow-client/test/packageTypes.test.ts:20 — typescript/wow-client/test/packageTypes.test.ts:20 imports './__package_consumer__.mts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
X2 · Cancellation propagation · Async function without AbortSignal · ×3
  • Async function without AbortSignal: load typescript/storybook/stories/view-engine/chinaProvinces.ts:64 — `load` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: load typescript/storybook/stories/view-engine/worldExports.ts:51 — `load` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: ready typescript/storybook/scripts/linux-browser.mjs:140 — `ready` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: CommandGateway.admit core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:413 — MethodTooLong — admit runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: DatasetBinder.bind platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetBinder.kt:97 — MethodTooLong — bind 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:93 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:93-100 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt:317-324 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryQueryBackend.kt:250-257 — before extracting anything, compare `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt` and `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:93` 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 (8 lines × 3) examples/eshop/catalog/catalog-server/src/main/kotlin/me/ahoo/wow/example/eshop/catalog/server/CatalogAuthorization.kt:51 — examples/eshop/catalog/catalog-server/src/main/kotlin/me/ahoo/wow/example/eshop/catalog/server/CatalogAuthorization.kt:51-58 | examples/eshop/inventory/inventory-server/src/main/kotlin/me/ahoo/wow/example/eshop/inventory/server/InventoryAuthorization.kt:53-60 | examples/eshop/ordering/ordering-server/src/main/kotlin/me/ahoo/wow/example/eshop/ordering/server/OrderingAuthorization.kt:52-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (61 lines × 2 locations) · ×2
  • Duplicated block (61 lines × 2 locations) platform/analytics/catalog/console/playwright.config.ts:23 — platform/analytics/catalog/console/playwright.config.ts:23 · platform/ops/console/playwright.config.ts:23 — 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 (61 lines × 2 locations) typescript/storybook/stories/view-engine/compensationEvents.ts:82 — typescript/storybook/stories/view-engine/compensationEvents.ts:82 · typescript/storybook/stories/view-engine/tradeOrderEvents.ts:147 — 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 (41 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (41 matched lines × 2 locations) typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:162 — typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:162 · typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:367 — the two spans are one implementation copied and then locally edited — 205 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (41 matched lines × 2 locations) typescript/wow-view-engine/src/ui/charts/boxplotOption.ts:47 — typescript/wow-view-engine/src/ui/charts/boxplotOption.ts:47 · typescript/wow-view-engine/src/ui/charts/candlestickOption.ts:39 — the two spans are one implementation copied and then locally edited — 278 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 (31 lines × 2 locations) · ×2
  • Duplicated block (31 lines × 2 locations) platform/analytics/catalog/console/src/app/CallerGate.tsx:29 — platform/analytics/catalog/console/src/app/CallerGate.tsx:29 · platform/ops/console/src/app/CallerGate.tsx:28 — 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 (31 lines × 2 locations) typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:42 — typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:42 · typescript/wow-view-engine/src/ui/analysis/StatisticalOptions.tsx:83 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×2
  • Duplicated block (30 lines × 2 locations) typescript/storybook/stories/view-engine/compensation.ts:79 — typescript/storybook/stories/view-engine/compensation.ts:79 · typescript/storybook/stories/view-engine/productPricing.ts:139 — 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) typescript/storybook/stories/view-engine/compensation.ts:102 — typescript/storybook/stories/view-engine/compensation.ts:102 · typescript/storybook/stories/view-engine/customer.ts:111 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) core/spi/src/main/kotlin/me/ahoo/wow/spi/transport/EnvelopeCodec.kt:87 — `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/source/TopicEntries.kt:137 — `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC3 · Page structure · Data table has no header cells · ×1
  • Data table has no header cells platform/analytics/catalog/console/src/detail/DatasetReading.tsx:203 — 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).
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement typescript/storybook/.storybook/preview.css:510 — `.story-app-page:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D1 · Cyclomatic Complexity · generate.generateRetail.project (cyclomatic 107) · ×1
  • generate.generateRetail.project (cyclomatic 107) typescript/storybook/stories/view-engine/retail/generate.ts:1476 — generate.generateRetail.project has cyclomatic complexity 107 (threshold 15). Of this number, 99 points are the body's own statements and 8 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 · check.checkTheme (cyclomatic 84) · ×1
  • check.checkTheme (cyclomatic 84) typescript/wow-view-engine/theme-check/check.ts:132 — check.checkTheme has cyclomatic complexity 84 (threshold 15). Of this number, 41 points are the body's own statements and 43 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AnalysisTable.AnalysisTable (cyclomatic 67) · ×1
  • AnalysisTable.AnalysisTable (cyclomatic 67) typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121 — AnalysisTable.AnalysisTable has cyclomatic complexity 67 (threshold 15). Of this number, 24 points are the body's own statements and 43 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · WorkbenchShell.WorkbenchShell (cyclomatic 64) · ×1
  • WorkbenchShell.WorkbenchShell (cyclomatic 64) typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344 — WorkbenchShell.WorkbenchShell has cyclomatic complexity 64 (threshold 15). Of this number, 51 points are the body's own statements and 13 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EChart.EChart (cyclomatic 60) · ×1
  • EChart.EChart (cyclomatic 60) typescript/wow-view-engine/src/ui/charts/EChart.tsx:205 — EChart.EChart has cyclomatic complexity 60 (threshold 15). Of this number, 19 points are the body's own statements and 41 belong to 21 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 · generate.generateRetail (cyclomatic 53) · ×1
  • generate.generateRetail (cyclomatic 53) typescript/storybook/stories/view-engine/retail/generate.ts:766 — generate.generateRetail has cyclomatic complexity 53 (threshold 15). Of this number, 47 points are the body's own statements and 6 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 · MetricCard.MetricCard (cyclomatic 49) · ×1
  • MetricCard.MetricCard (cyclomatic 49) typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78 — MetricCard.MetricCard has cyclomatic complexity 49 (threshold 15). Of this number, 45 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ActionDialog.ActionDialog (cyclomatic 48) · ×1
  • ActionDialog.ActionDialog (cyclomatic 48) typescript/wow-view-engine/src/ui/actions/ActionDialog.tsx:81 — ActionDialog.ActionDialog has cyclomatic complexity 48 (threshold 15). Of this number, 39 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DashboardGrid.DashboardGrid (cyclomatic 48) · ×1
  • DashboardGrid.DashboardGrid (cyclomatic 48) typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:167 — DashboardGrid.DashboardGrid has cyclomatic complexity 48 (threshold 15). Of this number, 24 points are the body's own statements and 24 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AnalysisParts.AnalysisParts (cyclomatic 47) · ×1
  • AnalysisParts.AnalysisParts (cyclomatic 47) typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx:126 — AnalysisParts.AnalysisParts has cyclomatic complexity 47 (threshold 15). Of this number, 44 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · analysis.narrowAggregation (cyclomatic 46) · ×1
  • analysis.narrowAggregation (cyclomatic 46) typescript/wow-view-engine/src/capabilities/analysis.ts:263 — analysis.narrowAggregation has cyclomatic complexity 46 (threshold 15). Of this number, 39 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ConditionPill.ConditionPill (cyclomatic 46) · ×1
  • ConditionPill.ConditionPill (cyclomatic 46) typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:80 — ConditionPill.ConditionPill has cyclomatic complexity 46 (threshold 15). Of this number, 44 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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 · SaveActions.SaveActions (cyclomatic 46) · ×1
  • SaveActions.SaveActions (cyclomatic 46) typescript/wow-view-engine/src/ui/workbench/SaveActions.tsx:87 — SaveActions.SaveActions has cyclomatic complexity 46 (threshold 15). Of this number, 29 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ElasticsearchFilterCompiler.compileNormalized (cyclomatic 45) · ×1
  • ElasticsearchFilterCompiler.compileNormalized (cyclomatic 45) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/ElasticsearchFilterCompiler.kt:57 — ElasticsearchFilterCompiler.compileNormalized has cyclomatic complexity 45 (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 · RecordTable.RecordTable (cyclomatic 45) · ×1
  • RecordTable.RecordTable (cyclomatic 45) typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209 — RecordTable.RecordTable has cyclomatic complexity 45 (threshold 15). Of this number, 35 points are the body's own statements and 10 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 · cartesianFit.cartesianFit (cyclomatic 43) · ×1
  • cartesianFit.cartesianFit (cyclomatic 43) typescript/wow-view-engine/src/ui/charts/cartesianFit.ts:230 — cartesianFit.cartesianFit has cyclomatic complexity 43 (threshold 15). Of this number, 23 points are the body's own statements and 20 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ElasticsearchQuerySchemaAdapterKt.supports (cyclomatic 41) · ×1
  • ElasticsearchQuerySchemaAdapterKt.supports (cyclomatic 41) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/schema/ElasticsearchQuerySchemaAdapter.kt:469 — ElasticsearchQuerySchemaAdapterKt.supports has cyclomatic complexity 41 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · MongoMatchCompiler.compile (cyclomatic 40) · ×1
  • MongoMatchCompiler.compile (cyclomatic 40) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoMatchCompiler.kt:133 — MongoMatchCompiler.compile has cyclomatic complexity 40 (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 · filter.criteria (cyclomatic 40) · ×1
  • filter.criteria (cyclomatic 40) typescript/wow-view-engine/src/testing/filter.ts:114 — filter.criteria has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · DatasetBinder.bind (cyclomatic 39) · ×1
  • DatasetBinder.bind (cyclomatic 39) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetBinder.kt:97 — DatasetBinder.bind has cyclomatic complexity 39 (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 · cartesianOption.optionOf (cyclomatic 37) · ×1
  • cartesianOption.optionOf (cyclomatic 37) typescript/wow-view-engine/src/ui/charts/cartesianOption.ts:74 — cartesianOption.optionOf has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 14 of the 37 points are its own statements and the rest belongs to 5 function items inside it that branch (valueAxis, tick, axisIndex, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ContentEditor.ContentForm (cyclomatic 37) · ×1
  • ContentEditor.ContentForm (cyclomatic 37) typescript/wow-view-engine/src/ui/dashboard/ContentEditor.tsx:204 — ContentEditor.ContentForm has cyclomatic complexity 37 (threshold 15). Of this number, 24 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ClickHouseFilterCompiler.compile (cyclomatic 35) · ×1
  • ClickHouseFilterCompiler.compile (cyclomatic 35) backends/clickhouse/src/main/kotlin/me/ahoo/wow/clickhouse/query/ClickHouseFilterCompiler.kt:89 — ClickHouseFilterCompiler.compile has cyclomatic complexity 35 (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 · ViewExpansion.useViewExpansion (cyclomatic 34) · ×1
  • ViewExpansion.useViewExpansion (cyclomatic 34) typescript/wow-view-engine/src/ui/kit/ViewExpansion.tsx:269 — ViewExpansion.useViewExpansion has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 387, 429, 320, …). 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 · Cartesian.Cartesian (cyclomatic 34) · ×1
  • Cartesian.Cartesian (cyclomatic 34) typescript/wow-view-engine/src/ui/charts/Cartesian.tsx:42 — Cartesian.Cartesian has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 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.
D1 · Cyclomatic Complexity · RecordParts.RecordParts (cyclomatic 34) · ×1
  • RecordParts.RecordParts (cyclomatic 34) typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx:202 — RecordParts.RecordParts has cyclomatic complexity 34 (threshold 15). Of this number, 18 points are the body's own statements and 16 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 · streams.resumableQueryRows (cyclomatic 33) · ×1
  • streams.resumableQueryRows (cyclomatic 33) typescript/wow-client/src/streams.ts:172 — streams.resumableQueryRows has cyclomatic complexity 33 (threshold 15). Of this number, 21 points are the body's own statements and 12 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useAnalysisResult.useAnalysisResult (cyclomatic 33) · ×1
  • useAnalysisResult.useAnalysisResult (cyclomatic 33) typescript/wow-view-engine/src/react/useAnalysisResult.ts:251 — useAnalysisResult.useAnalysisResult has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · aggregate.metricOf (cyclomatic 33) · ×1
  • aggregate.metricOf (cyclomatic 33) typescript/wow-view-engine/src/testing/aggregate.ts:290 — aggregate.metricOf has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validateMetrics.metricTypeIssues (cyclomatic 32) · ×1
  • validateMetrics.metricTypeIssues (cyclomatic 32) typescript/wow-view-engine/src/analysis/validateMetrics.ts:168 — validateMetrics.metricTypeIssues has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · fields.buildField (cyclomatic 32) · ×1
  • fields.buildField (cyclomatic 32) typescript/wow-view-engine/src/runtime/define/fields.ts:89 — fields.buildField has cyclomatic complexity 32 (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 · useWorkbench.useWorkbench (cyclomatic 32) · ×1
  • useWorkbench.useWorkbench (cyclomatic 32) typescript/wow-view-engine/src/react/useWorkbench.ts:408 — useWorkbench.useWorkbench has cyclomatic complexity 32 (threshold 15). Of this number, 30 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 · NewAnalysisDialog.NewAnalysisForm (cyclomatic 32) · ×1
  • NewAnalysisDialog.NewAnalysisForm (cyclomatic 32) typescript/wow-view-engine/src/ui/dashboard/NewAnalysisDialog.tsx:154 — NewAnalysisDialog.NewAnalysisForm has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CommandGateway.admit (cyclomatic 31) · ×1
  • CommandGateway.admit (cyclomatic 31) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:413 — CommandGateway.admit has cyclomatic complexity 31 (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 · Resolution.type (cyclomatic 31) · ×1
  • Resolution.type (cyclomatic 31) typescript/wow-generator/src/types/typeResolver.ts:616 — Resolution.type has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent 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 · metricCard.metricCard (cyclomatic 31) · ×1
  • metricCard.metricCard (cyclomatic 31) typescript/wow-view-engine/src/analysis/metricCard.ts:160 — metricCard.metricCard has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · date.DateValue (cyclomatic 31) · ×1
  • date.DateValue (cyclomatic 31) typescript/wow-view-engine/src/ui/filter/inputs/date.tsx:70 — date.DateValue has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ColumnRow.ColumnRow (cyclomatic 31) · ×1
  • ColumnRow.ColumnRow (cyclomatic 31) typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151 — ColumnRow.ColumnRow has cyclomatic complexity 31 (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 · SortableHeader.SortableHeader (cyclomatic 30) · ×1
  • SortableHeader.SortableHeader (cyclomatic 30) typescript/wow-view-engine/src/ui/record/SortableHeader.tsx:97 — SortableHeader.SortableHeader has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · cells.cellValue (cyclomatic 30) · ×1
  • cells.cellValue (cyclomatic 30) typescript/wow-view-engine/src/ui/record/cells.tsx:86 — cells.cellValue has cyclomatic complexity 30 (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 · RecordDetail.RecordDetail (cyclomatic 30) · ×1
  • RecordDetail.RecordDetail (cyclomatic 30) typescript/wow-view-engine/src/ui/record/RecordDetail.tsx:128 — RecordDetail.RecordDetail has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Board.DashboardBoard (cyclomatic 30) · ×1
  • Board.DashboardBoard (cyclomatic 30) typescript/wow-view-engine/src/ui/dashboard/Board.tsx:91 — Board.DashboardBoard has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 13 function items inside it that branch (add, a function literal at line 139, a function literal at line 244, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ChartPicker.ChartPicker (cyclomatic 30) · ×1
  • ChartPicker.ChartPicker (cyclomatic 30) typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx:112 — ChartPicker.ChartPicker has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 217, a function literal at line 273, nameOf, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · InMemoryFilters.compare (cyclomatic 29) · ×1
  • InMemoryFilters.compare (cyclomatic 29) query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt:163 — InMemoryFilters.compare has cyclomatic complexity 29 (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 · QueryStorageFamiliesKt.storageFamilies (cyclomatic 29) · ×1
  • QueryStorageFamiliesKt.storageFamilies (cyclomatic 29) query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryStorageFamilies.kt:94 — QueryStorageFamiliesKt.storageFamilies has cyclomatic complexity 29 (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 · PanelMenu.PanelMenu (cyclomatic 29) · ×1
  • PanelMenu.PanelMenu (cyclomatic 29) typescript/wow-view-engine/src/ui/dashboard/PanelMenu.tsx:112 — PanelMenu.PanelMenu has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · ViewManagerRow.ViewManagerRow (cyclomatic 28) · ×1
  • ViewManagerRow.ViewManagerRow (cyclomatic 28) typescript/wow-view-engine/src/ui/manage/ViewManagerRow.tsx:131 — ViewManagerRow.ViewManagerRow has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SaveAsDialog.SaveAsForm (cyclomatic 28) · ×1
  • SaveAsDialog.SaveAsForm (cyclomatic 28) typescript/wow-view-engine/src/ui/workbench/SaveAsDialog.tsx:230 — SaveAsDialog.SaveAsForm has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PanelBodies.AnalysisPanel (cyclomatic 28) · ×1
  • PanelBodies.AnalysisPanel (cyclomatic 28) typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx:293 — PanelBodies.AnalysisPanel has cyclomatic complexity 28 (threshold 15). Of this number, 21 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 · DashboardPanelCard.DashboardPanelCard (cyclomatic 28) · ×1
  • DashboardPanelCard.DashboardPanelCard (cyclomatic 28) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx:257 — DashboardPanelCard.DashboardPanelCard has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · address.useAddressedInstance (cyclomatic 28) · ×1
  • address.useAddressedInstance (cyclomatic 28) typescript/wow-view-engine/src/ui/workbench/address.ts:197 — address.useAddressedInstance has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 271, 237, 222, …). 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 · kotlinDuration.parseDefault (cyclomatic 27) · ×1
  • kotlinDuration.parseDefault (cyclomatic 27) platform/ops/console/src/views/kotlinDuration.ts:159 — kotlinDuration.parseDefault has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MoreViewActions.MoreViewActions (cyclomatic 27) · ×1
  • MoreViewActions.MoreViewActions (cyclomatic 27) typescript/wow-view-engine/src/ui/workbench/MoreViewActions.tsx:52 — MoreViewActions.MoreViewActions has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · datasetRecord.notJsonAt (cyclomatic 26) · ×1
  • datasetRecord.notJsonAt (cyclomatic 26) platform/analytics/catalog/console/src/detail/datasetRecord.ts:60 — datasetRecord.notJsonAt has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (value, string, items, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · cartesian.shapeCartesian (cyclomatic 26) · ×1
  • cartesian.shapeCartesian (cyclomatic 26) typescript/wow-view-engine/src/analysis/cartesian.ts:156 — cartesian.shapeCartesian has cyclomatic complexity 26 (threshold 15). Of this number, 16 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useSaveCommands.useSaveCommands (cyclomatic 26) · ×1
  • useSaveCommands.useSaveCommands (cyclomatic 26) typescript/wow-view-engine/src/react/useSaveCommands.ts:211 — useSaveCommands.useSaveCommands has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · DrillMenu.DrillMenu (cyclomatic 26) · ×1
  • DrillMenu.DrillMenu (cyclomatic 26) typescript/wow-view-engine/src/ui/analysis/DrillMenu.tsx:105 — DrillMenu.DrillMenu has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 241, 141, 127, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ResultToolbar.ResultToolbar (cyclomatic 26) · ×1
  • ResultToolbar.ResultToolbar (cyclomatic 26) typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx:157 — ResultToolbar.ResultToolbar has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · EmbeddedDashboard.EmbeddedBoard (cyclomatic 26) · ×1
  • EmbeddedDashboard.EmbeddedBoard (cyclomatic 26) typescript/wow-view-engine/src/ui/EmbeddedDashboard.tsx:230 — EmbeddedDashboard.EmbeddedBoard has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EmbeddedRecord.EmbeddedRecord (cyclomatic 26) · ×1
  • EmbeddedRecord.EmbeddedRecord (cyclomatic 26) typescript/wow-view-engine/src/ui/embed/EmbeddedRecord.tsx:52 — EmbeddedRecord.EmbeddedRecord has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · project.projectAnalysis · ×1
  • project.projectAnalysis::describe (cyclomatic 25) typescript/wow-view-engine/src/analysis/project.ts:533 — project.projectAnalysis::describe has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (project.projectAnalysis) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · actionRunner.useActionRunner.run (cyclomatic 25) · ×1
  • actionRunner.useActionRunner.run (cyclomatic 25) typescript/wow-view-engine/src/react/actionRunner.ts:278 — actionRunner.useActionRunner.run has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (judge, finish, settle, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · source.scoped (cyclomatic 25) · ×1
  • source.scoped (cyclomatic 25) typescript/wow-view-engine/src/testing/source.ts:204 — source.scoped has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DisplayTab.ValueLabelsField (cyclomatic 25) · ×1
  • DisplayTab.ValueLabelsField (cyclomatic 25) typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx:142 — DisplayTab.ValueLabelsField has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · building.useDashboardExtensions (cyclomatic 25) · ×1
  • building.useDashboardExtensions (cyclomatic 25) typescript/wow-view-engine/src/ui/dashboard/building.tsx:83 — building.useDashboardExtensions has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Resolution.objectConstrained (cyclomatic 24) · ×1
  • Resolution.objectConstrained (cyclomatic 24) typescript/wow-generator/src/types/typeResolver.ts:564 — Resolution.objectConstrained has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · validateGroups.groupIssues (cyclomatic 24) · ×1
  • validateGroups.groupIssues (cyclomatic 24) typescript/wow-view-engine/src/analysis/validateGroups.ts:94 — validateGroups.groupIssues 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 one function literal inside it that branches (line 104). 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.
D1 · Cyclomatic Complexity · open.aggregation (cyclomatic 24) · ×1
  • open.aggregation (cyclomatic 24) typescript/wow-view-engine/src/capabilities/open.ts:161 — open.aggregation has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · unavailable.without1 (cyclomatic 24) · ×1
  • unavailable.without1 (cyclomatic 24) typescript/wow-view-engine/src/runtime/failure/unavailable.ts:103 — unavailable.without1 has cyclomatic complexity 24 (threshold 15). Of this number, 22 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 · Funnel.Funnel (cyclomatic 24) · ×1
  • Funnel.Funnel (cyclomatic 24) typescript/wow-view-engine/src/ui/charts/Funnel.tsx:50 — Funnel.Funnel has cyclomatic complexity 24 (threshold 15). Of this number, 15 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 · datePattern.validateDatePattern (cyclomatic 23) · ×1
  • datePattern.validateDatePattern (cyclomatic 23) typescript/wow-client/src/dsl/filter/datePattern.ts:112 — datePattern.validateDatePattern has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · click.validatePanelClick (cyclomatic 23) · ×1
  • click.validatePanelClick (cyclomatic 23) typescript/wow-view-engine/src/dashboard/click.ts:162 — click.validatePanelClick has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · summary.summaryWords (cyclomatic 23) · ×1
  • summary.summaryWords (cyclomatic 23) typescript/wow-view-engine/src/ui/kit/summary.ts:72 — summary.summaryWords has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MetricCard.MetricCard (cyclomatic 23) · ×1
  • MetricCard.MetricCard (cyclomatic 23) typescript/wow-view-engine/src/ui/charts/MetricCard.tsx:341 — MetricCard.MetricCard has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TimeCharts.TimeCharts (cyclomatic 23) · ×1
  • TimeCharts.TimeCharts (cyclomatic 23) typescript/wow-view-engine/src/ui/charts/TimeCharts.tsx:39 — TimeCharts.TimeCharts has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 101, 99, 57, …). 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 · RecordKanban.KanbanLane (cyclomatic 23) · ×1
  • RecordKanban.KanbanLane (cyclomatic 23) typescript/wow-view-engine/src/ui/record/RecordKanban.tsx:169 — RecordKanban.KanbanLane has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · RecordPagination.RecordPagination (cyclomatic 23) · ×1
  • RecordPagination.RecordPagination (cyclomatic 23) typescript/wow-view-engine/src/ui/record/RecordPagination.tsx:83 — RecordPagination.RecordPagination has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · issueNames.analysisIssueNamer.<returned closure> (cyclomatic 23) · ×1
  • issueNames.analysisIssueNamer.<returned closure> (cyclomatic 23) typescript/wow-view-engine/src/ui/analysis/issueNames.ts:101 — issueNames.analysisIssueNamer.<returned closure> has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FilterBar.FilterBar (cyclomatic 23) · ×1
  • FilterBar.FilterBar (cyclomatic 23) typescript/wow-view-engine/src/ui/dashboard/FilterBar.tsx:170 — FilterBar.FilterBar has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · kotlinDuration.parseIso (cyclomatic 22) · ×1
  • kotlinDuration.parseIso (cyclomatic 22) platform/ops/console/src/views/kotlinDuration.ts:103 — kotlinDuration.parseIso has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · derived.derivedGap (cyclomatic 22) · ×1
  • derived.derivedGap (cyclomatic 22) typescript/wow-view-engine/src/analysis/derived.ts:130 — derived.derivedGap has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · fields.narrowField (cyclomatic 22) · ×1
  • fields.narrowField (cyclomatic 22) typescript/wow-view-engine/src/capabilities/fields.ts:99 — fields.narrowField has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · validateFields.validateFields (cyclomatic 22) · ×1
  • validateFields.validateFields (cyclomatic 22) typescript/wow-view-engine/src/runtime/validateFields.ts:41 — validateFields.validateFields has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 61, 151, 165). 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 · useRecordDetail.useRecordDetail (cyclomatic 22) · ×1
  • useRecordDetail.useRecordDetail (cyclomatic 22) typescript/wow-view-engine/src/react/useRecordDetail.ts:121 — useRecordDetail.useRecordDetail has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: 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 · cartesianTooltip.cartesianTooltip (cyclomatic 22) · ×1
  • cartesianTooltip.cartesianTooltip (cyclomatic 22) typescript/wow-view-engine/src/ui/charts/cartesianTooltip.ts:30 — cartesianTooltip.cartesianTooltip has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (rowAt, a function literal at line 85, earlierChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FilterPanel.FilterPanel (cyclomatic 22) · ×1
  • FilterPanel.FilterPanel (cyclomatic 22) typescript/wow-view-engine/src/ui/filter/FilterPanel.tsx:82 — FilterPanel.FilterPanel has cyclomatic complexity 22 (threshold 15). Of this number, 14 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 · DashboardTabs.DashboardTabs (cyclomatic 22) · ×1
  • DashboardTabs.DashboardTabs (cyclomatic 22) typescript/wow-view-engine/src/ui/dashboard/DashboardTabs.tsx:63 — DashboardTabs.DashboardTabs has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (move, remove, add, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · resolve.createResolver.declared (cyclomatic 22) · ×1
  • resolve.createResolver.declared (cyclomatic 22) typescript/wow-view-engine/theme-check/resolve.ts:553 — resolve.createResolver.declared has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (layered, link, read, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · manifestClients.emitCommandClient (cyclomatic 21) · ×1
  • manifestClients.emitCommandClient (cyclomatic 21) typescript/wow-generator/src/emitters/manifestClients.ts:635 — manifestClients.emitCommandClient has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · compile.recordProjection (cyclomatic 21) · ×1
  • compile.recordProjection (cyclomatic 21) typescript/wow-view-engine/src/record/compile.ts:118 — compile.recordProjection has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent 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 · analysis.narrowAnalysis (cyclomatic 21) · ×1
  • analysis.narrowAnalysis (cyclomatic 21) typescript/wow-view-engine/src/capabilities/analysis.ts:49 — analysis.narrowAnalysis has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ChartLegend.ChartLegend (cyclomatic 21) · ×1
  • ChartLegend.ChartLegend (cyclomatic 21) typescript/wow-view-engine/src/ui/charts/ChartLegend.tsx:55 — ChartLegend.ChartLegend has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, 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 · virtualRows.useVirtualRows (cyclomatic 21) · ×1
  • virtualRows.useVirtualRows (cyclomatic 21) typescript/wow-view-engine/src/ui/analysis/virtualRows.ts:128 — virtualRows.useVirtualRows has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 171, 169, 201, …). 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 · remote.CandidateValue (cyclomatic 21) · ×1
  • remote.CandidateValue (cyclomatic 21) typescript/wow-view-engine/src/ui/filter/inputs/remote.tsx:114 — remote.CandidateValue has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ActionSurface.useActionSurface (cyclomatic 21) · ×1
  • ActionSurface.useActionSurface (cyclomatic 21) typescript/wow-view-engine/src/ui/actions/ActionSurface.tsx:99 — ActionSurface.useActionSurface has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 177, a function literal at line 157, a function literal at line 168, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · EmbeddedAnalysis.EmbeddedAnalysis (cyclomatic 21) · ×1
  • EmbeddedAnalysis.EmbeddedAnalysis (cyclomatic 21) typescript/wow-view-engine/src/ui/embed/EmbeddedAnalysis.tsx:50 — EmbeddedAnalysis.EmbeddedAnalysis has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EmbeddedView.EmbeddedData (cyclomatic 21) · ×1
  • EmbeddedView.EmbeddedData (cyclomatic 21) typescript/wow-view-engine/src/ui/EmbeddedView.tsx:168 — EmbeddedView.EmbeddedData has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DatasetExpressionParser.tokenize (cyclomatic 20) · ×1
  • DatasetExpressionParser.tokenize (cyclomatic 20) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetExpression.kt:292 — DatasetExpressionParser.tokenize 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 · scope.requireElementScopedFilter (cyclomatic 20) · ×1
  • scope.requireElementScopedFilter (cyclomatic 20) typescript/wow-client/src/dsl/filter/scope.ts:34 — scope.requireElementScopedFilter 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 · ReferenceLabels.want (cyclomatic 20) · ×1
  • ReferenceLabels.want (cyclomatic 20) typescript/wow-view-engine/src/runtime/referenceLabels.ts:224 — ReferenceLabels.want has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useViewList.useViewList (cyclomatic 20) · ×1
  • useViewList.useViewList (cyclomatic 20) typescript/wow-view-engine/src/react/useViewList.ts:152 — useViewList.useViewList has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 188, 262, 186, …). 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 · scatterOption.scatterOption (cyclomatic 20) · ×1
  • scatterOption.scatterOption (cyclomatic 20) typescript/wow-view-engine/src/ui/charts/scatterOption.ts:68 — scatterOption.scatterOption has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (axis, diameter, a function literal at line 193, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · WriteOutcome.WriteOutcome (cyclomatic 20) · ×1
  • WriteOutcome.WriteOutcome (cyclomatic 20) typescript/wow-view-engine/src/ui/workbench/WriteOutcome.tsx:101 — WriteOutcome.WriteOutcome has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (notify, a function literal at line 128, a function literal at line 179, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · check.checkBounds (cyclomatic 20) · ×1
  • check.checkBounds (cyclomatic 20) typescript/wow-view-engine/theme-check/check.ts:529 — check.checkBounds 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 · admit.validateHaving (cyclomatic 19) · ×1
  • admit.validateHaving (cyclomatic 19) typescript/wow-client/src/dsl/aggregation/admit.ts:271 — admit.validateHaving has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · manifestClients.commandMethods (cyclomatic 19) · ×1
  • manifestClients.commandMethods (cyclomatic 19) typescript/wow-generator/src/emitters/manifestClients.ts:571 — manifestClients.commandMethods has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · timeAxis.withoutHoles (cyclomatic 19) · ×1
  • timeAxis.withoutHoles (cyclomatic 19) typescript/wow-view-engine/src/analysis/timeAxis.ts:208 — timeAxis.withoutHoles has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · familySlots.cartesianSlots (cyclomatic 19) · ×1
  • familySlots.cartesianSlots (cyclomatic 19) typescript/wow-view-engine/src/analysis/familySlots.ts:111 — familySlots.cartesianSlots has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · validateReferences.referenceIssues (cyclomatic 19) · ×1
  • validateReferences.referenceIssues (cyclomatic 19) typescript/wow-view-engine/src/analysis/validateReferences.ts:37 — validateReferences.referenceIssues 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 80, 45, 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 · panels.clickOf (cyclomatic 19) · ×1
  • panels.clickOf (cyclomatic 19) typescript/wow-view-engine/src/dashboard/panels.ts:126 — panels.clickOf 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 · wire-literals.wireLiterals (cyclomatic 19) · ×1
  • wire-literals.wireLiterals (cyclomatic 19) typescript/wow-view-engine/scripts/wire-literals.mjs:332 — wire-literals.wireLiterals has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (visit, note, isWire). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · OffscreenSummary.OffscreenSummary (cyclomatic 19) · ×1
  • OffscreenSummary.OffscreenSummary (cyclomatic 19) typescript/wow-view-engine/src/ui/record/OffscreenSummary.tsx:68 — OffscreenSummary.OffscreenSummary has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FilterActions.FilterActions (cyclomatic 19) · ×1
  • FilterActions.FilterActions (cyclomatic 19) typescript/wow-view-engine/src/ui/filter/FilterActions.tsx:37 — FilterActions.FilterActions has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · scrollMore.measurePort (cyclomatic 19) · ×1
  • scrollMore.measurePort (cyclomatic 19) typescript/wow-view-engine/src/ui/dashboard/scrollMore.ts:169 — scrollMore.measurePort has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DashboardPanelCard.PanelHeader (cyclomatic 19) · ×1
  • DashboardPanelCard.PanelHeader (cyclomatic 19) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx:449 — DashboardPanelCard.PanelHeader has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · DataTab.MetricData (cyclomatic 19) · ×1
  • DataTab.MetricData (cyclomatic 19) typescript/wow-view-engine/src/ui/analysis/DataTab.tsx:440 — DataTab.MetricData has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 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 · DashboardWorkbench.DashboardWorkbenchBody (cyclomatic 19) · ×1
  • DashboardWorkbench.DashboardWorkbenchBody (cyclomatic 19) typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:213 — DashboardWorkbench.DashboardWorkbenchBody has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · analyze.aggregateModel.commands (cyclomatic 18) · ×1
  • analyze.aggregateModel.commands (cyclomatic 18) typescript/wow-generator/src/manifest/analyze.ts:928 — analyze.aggregateModel.commands has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · metricCard.lastPeriod (cyclomatic 18) · ×1
  • metricCard.lastPeriod (cyclomatic 18) typescript/wow-view-engine/src/analysis/metricCard.ts:355 — metricCard.lastPeriod has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · validateMetrics.derivedFormatIssues (cyclomatic 18) · ×1
  • validateMetrics.derivedFormatIssues (cyclomatic 18) typescript/wow-view-engine/src/analysis/validateMetrics.ts:357 — validateMetrics.derivedFormatIssues has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · validate.validateBindings (cyclomatic 18) · ×1
  • validate.validateBindings (cyclomatic 18) typescript/wow-view-engine/src/dashboard/validate.ts:471 — validate.validateBindings 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 one function literal inside it that branches (line 484). 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.
D1 · Cyclomatic Complexity · wire-literals.wireVocabularies (cyclomatic 18) · ×1
  • wire-literals.wireVocabularies (cyclomatic 18) typescript/wow-view-engine/scripts/wire-literals.mjs:73 — wire-literals.wireVocabularies 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 3 function items inside it that branch (visit, a function literal at line 80, a function literal at line 99). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · DashboardArrange.PanelHandle (cyclomatic 18) · ×1
  • DashboardArrange.PanelHandle (cyclomatic 18) typescript/wow-view-engine/src/ui/dashboard/DashboardArrange.tsx:103 — DashboardArrange.PanelHandle 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 items inside it that branch (a function literal at line 155, end, a function literal at line 127, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · cartesianMarks.extremePoints (cyclomatic 18) · ×1
  • cartesianMarks.extremePoints (cyclomatic 18) typescript/wow-view-engine/src/ui/charts/cartesianMarks.ts:416 — cartesianMarks.extremePoints 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 3 function items inside it that branch (point, align, beyond). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · PieSlices.PieSlices (cyclomatic 18) · ×1
  • PieSlices.PieSlices (cyclomatic 18) typescript/wow-view-engine/src/ui/charts/PieSlices.tsx:53 — PieSlices.PieSlices has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 156, 79, 81, …). 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 · ViewPicker.Catalogue (cyclomatic 18) · ×1
  • ViewPicker.Catalogue (cyclomatic 18) typescript/wow-view-engine/src/ui/dashboard/ViewPicker.tsx:216 — ViewPicker.Catalogue has cyclomatic complexity 18 (threshold 15). 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, separate the cases: extract each independent 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 · DimensionCard.DimensionCard (cyclomatic 18) · ×1
  • DimensionCard.DimensionCard (cyclomatic 18) typescript/wow-view-engine/src/ui/analysis/DimensionCard.tsx:167 — DimensionCard.DimensionCard has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · generate.generateRetail.requestAfterSales (cyclomatic 17) · ×1
  • generate.generateRetail.requestAfterSales (cyclomatic 17) typescript/storybook/stories/view-engine/retail/generate.ts:1330 — generate.generateRetail.requestAfterSales has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ModelEmitter.process (cyclomatic 17) · ×1
  • ModelEmitter.process (cyclomatic 17) typescript/wow-generator/src/emitters/models.ts:177 — ModelEmitter.process has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · timeAxis.appliedWindow (cyclomatic 17) · ×1
  • timeAxis.appliedWindow (cyclomatic 17) typescript/wow-view-engine/src/analysis/timeAxis.ts:307 — timeAxis.appliedWindow has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · timeAxis.bucketSpan (cyclomatic 17) · ×1
  • timeAxis.bucketSpan (cyclomatic 17) typescript/wow-view-engine/src/analysis/timeAxis.ts:393 — timeAxis.bucketSpan has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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 · filters.admitFilters (cyclomatic 17) · ×1
  • filters.admitFilters (cyclomatic 17) typescript/wow-view-engine/src/dashboard/filters.ts:214 — filters.admitFilters has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · click.validateBoardClick (cyclomatic 17) · ×1
  • click.validateBoardClick (cyclomatic 17) typescript/wow-view-engine/src/dashboard/click.ts:273 — click.validateBoardClick has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · wiring.bindPanel (cyclomatic 17) · ×1
  • wiring.bindPanel (cyclomatic 17) typescript/wow-view-engine/src/dashboard/wiring.ts:146 — wiring.bindPanel has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · metricOrder.moveMetric (cyclomatic 17) · ×1
  • metricOrder.moveMetric (cyclomatic 17) typescript/wow-view-engine/src/analysis/metricOrder.ts:54 — metricOrder.moveMetric has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: 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 · useReshape.useReshape.reshape (cyclomatic 17) · ×1
  • useReshape.useReshape.reshape (cyclomatic 17) typescript/wow-view-engine/src/react/useReshape.ts:126 — useReshape.useReshape.reshape has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 132). 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.
D1 · Cyclomatic Complexity · display.displayValue (cyclomatic 17) · ×1
  • display.displayValue (cyclomatic 17) typescript/wow-view-engine/src/ui/kit/display.ts:157 — display.displayValue has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ViewHeader.ViewHeader (cyclomatic 17) · ×1
  • ViewHeader.ViewHeader (cyclomatic 17) typescript/wow-view-engine/src/ui/workbench/ViewHeader.tsx:143 — ViewHeader.ViewHeader has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · history.useBoardHistory (cyclomatic 17) · ×1
  • history.useBoardHistory (cyclomatic 17) typescript/wow-view-engine/src/ui/dashboard/history.ts:114 — history.useBoardHistory has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 146, 152, 150). 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 · DatasetCompiler.expression (cyclomatic 16) · ×1
  • DatasetCompiler.expression (cyclomatic 16) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetCompiler.kt:189 — DatasetCompiler.expression has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Parser.object (cyclomatic 16) · ×1
  • Parser.object (cyclomatic 16) typescript/wow-client/src/exactJson.ts:201 — Parser.object has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · exactJson.replace (cyclomatic 16) · ×1
  • exactJson.replace (cyclomatic 16) typescript/wow-client/src/exactJson.ts:409 — exactJson.replace has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · typeResolver.schemaKind (cyclomatic 16) · ×1
  • typeResolver.schemaKind (cyclomatic 16) typescript/wow-generator/src/types/typeResolver.ts:201 — typeResolver.schemaKind has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · document.validateManifest (cyclomatic 16) · ×1
  • document.validateManifest (cyclomatic 16) typescript/wow-generator/src/manifest/document.ts:96 — document.validateManifest has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 122, 117, 132, …). 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 · SchemaTypes.textNumbers (cyclomatic 16) · ×1
  • SchemaTypes.textNumbers (cyclomatic 16) typescript/wow-generator/src/manifest/analyze.ts:574 — SchemaTypes.textNumbers has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · candlestick.ohlcMetrics (cyclomatic 16) · ×1
  • candlestick.ohlcMetrics (cyclomatic 16) typescript/wow-view-engine/src/analysis/candlestick.ts:166 — candlestick.ohlcMetrics has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, 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 · serverLines.serverLineMetrics (cyclomatic 16) · ×1
  • serverLines.serverLineMetrics (cyclomatic 16) typescript/wow-view-engine/src/analysis/serverLines.ts:85 — serverLines.serverLineMetrics has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · metricWindow.metricReach (cyclomatic 16) · ×1
  • metricWindow.metricReach (cyclomatic 16) typescript/wow-view-engine/src/analysis/metricWindow.ts:44 — metricWindow.metricReach has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · familySlots.cardSlots (cyclomatic 16) · ×1
  • familySlots.cardSlots (cyclomatic 16) typescript/wow-view-engine/src/analysis/familySlots.ts:446 — familySlots.cardSlots has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · project.projectAnalysis (cyclomatic 16) · ×1
  • project.projectAnalysis (cyclomatic 16) typescript/wow-view-engine/src/analysis/project.ts:415 — project.projectAnalysis has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (project.projectAnalysis::describe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · expressions.expressionIssues (cyclomatic 16) · ×1
  • expressions.expressionIssues (cyclomatic 16) typescript/wow-view-engine/src/analysis/expressions.ts:36 — expressions.expressionIssues has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · actionReads.watchingReads (cyclomatic 16) · ×1
  • actionReads.watchingReads (cyclomatic 16) typescript/wow-view-engine/src/runtime/actionReads.ts:201 — actionReads.watchingReads has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · treemapOption.treemapOption (cyclomatic 16) · ×1
  • treemapOption.treemapOption (cyclomatic 16) typescript/wow-view-engine/src/ui/charts/treemapOption.ts:131 — treemapOption.treemapOption has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (node, a function literal at line 201, a function literal at line 233, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · offscreenSummaries.hintHost (cyclomatic 16) · ×1
  • offscreenSummaries.hintHost (cyclomatic 16) typescript/wow-view-engine/src/ui/record/offscreenSummaries.ts:142 — offscreenSummaries.hintHost has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ActionButtons.RowActionButtons (cyclomatic 16) · ×1
  • ActionButtons.RowActionButtons (cyclomatic 16) typescript/wow-view-engine/src/ui/actions/ActionButtons.tsx:231 — ActionButtons.RowActionButtons has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SortSettings.SortSettings (cyclomatic 16) · ×1
  • SortSettings.SortSettings (cyclomatic 16) typescript/wow-view-engine/src/ui/sort/SortSettings.tsx:196 — SortSettings.SortSettings has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FieldChecklist.FieldChecklist (cyclomatic 16) · ×1
  • FieldChecklist.FieldChecklist (cyclomatic 16) typescript/wow-view-engine/src/ui/filter/FieldChecklist.tsx:86 — FieldChecklist.FieldChecklist has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 7 function items inside it that branch (toggle, a function literal at line 181, a function literal at line 262, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · StatusLine.StatusLine (cyclomatic 16) · ×1
  • StatusLine.StatusLine (cyclomatic 16) typescript/wow-view-engine/src/ui/workbench/StatusLine.tsx:61 — StatusLine.StatusLine has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · RefreshControl.RefreshControl (cyclomatic 16) · ×1
  • RefreshControl.RefreshControl (cyclomatic 16) typescript/wow-view-engine/src/ui/workbench/RefreshControl.tsx:111 — RefreshControl.RefreshControl has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · EditBar.EditBar (cyclomatic 16) · ×1
  • EditBar.EditBar (cyclomatic 16) typescript/wow-view-engine/src/ui/dashboard/EditBar.tsx:82 — EditBar.EditBar has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FilterBar.FilterChip (cyclomatic 16) · ×1
  • FilterBar.FilterChip (cyclomatic 16) typescript/wow-view-engine/src/ui/dashboard/FilterBar.tsx:447 — FilterBar.FilterChip has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FormulaCard.DerivedFormatControls (cyclomatic 16) · ×1
  • FormulaCard.DerivedFormatControls (cyclomatic 16) typescript/wow-view-engine/src/ui/analysis/FormulaCard.tsx:472 — FormulaCard.DerivedFormatControls has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 523, styled, a function literal at line 550, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · MetricSlot.MetricSlot (cyclomatic 16) · ×1
  • MetricSlot.MetricSlot (cyclomatic 16) typescript/wow-view-engine/src/ui/analysis/MetricSlot.tsx:68 — MetricSlot.MetricSlot 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 5 function items inside it that branch (moveTo, nameOf, a function literal at line 158, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Failure.code (cyclomatic 16) · ×1
  • Failure.code (cyclomatic 16) typescript/wow-view-store/src/errors.ts:100 — Failure.code has cyclomatic complexity 16 (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.
D2 · Cognitive Complexity · generate.generateRetail.project (cognitive 146) · ×1
  • generate.generateRetail.project (cognitive 146) typescript/storybook/stories/view-engine/retail/generate.ts:1476 — generate.generateRetail.project has cognitive complexity 146 (threshold 15). Drivers by points: ternaries 41 (72 pts), if/else 28 (41 pts), boolean chains 20, loops 11 (13 pts) (nesting depth added 46). Of this number, 134 points are the body's own statements and 12 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 · generate.generateRetail (cognitive 143) · ×1
  • generate.generateRetail (cognitive 143) typescript/storybook/stories/view-engine/retail/generate.ts:766 — generate.generateRetail has cognitive complexity 143 (threshold 15). Drivers by points: ternaries 24 (79 pts), if/else 10 (32 pts), loops 9 (23 pts), boolean chains 9 (nesting depth added 91). Of this number, 132 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · check.checkTheme (cognitive 139) · ×1
  • check.checkTheme (cognitive 139) typescript/wow-view-engine/theme-check/check.ts:132 — check.checkTheme has cognitive complexity 139 (threshold 15). Drivers by points: if/else 39 (61 pts), loops 18 (48 pts), boolean chains 17, ternaries 4 (8 pts), error handling 2 (5 pts) (nesting depth added 59). Of this number, 92 points are the body's own statements and 47 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AnalysisTable.AnalysisTable (cognitive 62) · ×1
  • AnalysisTable.AnalysisTable (cognitive 62) typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:121 — AnalysisTable.AnalysisTable has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 28 (29 pts), boolean chains 21, if/else 8 (12 pts) (nesting depth added 5). Of this number, 21 points are the body's own statements and 41 belong to 10 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DashboardGrid.DashboardGrid (cognitive 62) · ×1
  • DashboardGrid.DashboardGrid (cognitive 62) typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:167 — DashboardGrid.DashboardGrid has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 18 (40 pts), boolean chains 14, if/else 7, loops 1 (nesting depth added 22). Of this number, 30 points are the body's own statements and 32 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EChart.EChart (cognitive 58) · ×1
  • EChart.EChart (cognitive 58) typescript/wow-view-engine/src/ui/charts/EChart.tsx:205 — EChart.EChart has cognitive complexity 58 (threshold 15). Drivers by points: if/else 26 (28 pts), boolean chains 19, ternaries 8 (9 pts), error handling 1 (2 pts) (nesting depth added 4). Of this number, 17 points are the body's own statements and 41 belong to 21 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 · streams.resumableQueryRows (cognitive 52) · ×1
  • streams.resumableQueryRows (cognitive 52) typescript/wow-client/src/streams.ts:172 — streams.resumableQueryRows has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (53 pts), ternaries 3 (7 pts), boolean chains 6, error handling 2 (4 pts), loops 2 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (streams.resumableQueryRows::resume) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · cartesianFit.cartesianFit (cognitive 49) · ×1
  • cartesianFit.cartesianFit (cognitive 49) typescript/wow-view-engine/src/ui/charts/cartesianFit.ts:230 — cartesianFit.cartesianFit has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 12, if/else 7 (9 pts), loops 1 (nesting depth added 12). Of this number, 25 points are the body's own statements and 24 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · datePattern.validateDatePattern (cognitive 48) · ×1
  • datePattern.validateDatePattern (cognitive 48) typescript/wow-client/src/dsl/filter/datePattern.ts:112 — datePattern.validateDatePattern has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 4 (12 pts), boolean chains 4 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · aggregate.metricOf (cognitive 48) · ×1
  • aggregate.metricOf (cognitive 48) typescript/wow-view-engine/src/testing/aggregate.ts:290 — aggregate.metricOf has cognitive complexity 48 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (9 pts), ternaries 3 (9 pts), boolean chains 7, match/switch 1 (nesting depth added 25). 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 · WorkbenchShell.WorkbenchShell (cognitive 48) · ×1
  • WorkbenchShell.WorkbenchShell (cognitive 48) typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344 — WorkbenchShell.WorkbenchShell has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 35, ternaries 7, if/else 6. Of this number, 35 points are the body's own statements and 13 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ActionDialog.ActionDialog (cognitive 45) · ×1
  • ActionDialog.ActionDialog (cognitive 45) typescript/wow-view-engine/src/ui/actions/ActionDialog.tsx:81 — ActionDialog.ActionDialog has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 16 (19 pts), boolean chains 18, if/else 8 (nesting depth added 3). Of this number, 37 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Resolution.type (cognitive 43) · ×1
  • Resolution.type (cognitive 43) typescript/wow-generator/src/types/typeResolver.ts:616 — Resolution.type has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 9 (19 pts), boolean chains 5 (nesting depth added 14). Of this number, 32 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CommandGateway.admit (cognitive 42) · ×1
  • CommandGateway.admit (cognitive 42) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/admission/CommandGateway.kt:413 — CommandGateway.admit has cognitive complexity 42 (threshold 15). Drivers by points: if/else 23 (26 pts), boolean chains 7, error handling 3 (5 pts), match/switch 2 (4 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · kotlinDuration.parseDefault (cognitive 42) · ×1
  • kotlinDuration.parseDefault (cognitive 42) platform/ops/console/src/views/kotlinDuration.ts:159 — kotlinDuration.parseDefault has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 6, loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validateMetrics.metricTypeIssues (cognitive 41) · ×1
  • validateMetrics.metricTypeIssues (cognitive 41) typescript/wow-view-engine/src/analysis/validateMetrics.ts:168 — validateMetrics.metricTypeIssues has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 5, match/switch 1 (nesting depth added 18). 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 · kotlinDuration.parseIso (cognitive 40) · ×1
  • kotlinDuration.parseIso (cognitive 40) platform/ops/console/src/views/kotlinDuration.ts:103 — kotlinDuration.parseIso has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 5, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cartesianOption.optionOf (cognitive 39) · ×1
  • cartesianOption.optionOf (cognitive 39) typescript/wow-view-engine/src/ui/charts/cartesianOption.ts:74 — cartesianOption.optionOf has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 23 (32 pts), boolean chains 7 (nesting depth added 9). Most of this is not in the body itself: 13 of the 39 points are its own statements and the rest belongs to 5 function items inside it that branch (valueAxis, axisIndex, tick, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · RecordTable.RecordTable (cognitive 39) · ×1
  • RecordTable.RecordTable (cognitive 39) typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209 — RecordTable.RecordTable has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 22, ternaries 10 (15 pts), if/else 2 (nesting depth added 5). Of this number, 30 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.
D2 · Cognitive Complexity · ViewExpansion.useViewExpansion (cognitive 38) · ×1
  • ViewExpansion.useViewExpansion (cognitive 38) typescript/wow-view-engine/src/ui/kit/ViewExpansion.tsx:269 — ViewExpansion.useViewExpansion has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 7, loops 3 (5 pts), ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 429, 387, 320, …). 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 · ChartPicker.ChartPicker (cognitive 38) · ×1
  • ChartPicker.ChartPicker (cognitive 38) typescript/wow-view-engine/src/ui/analysis/ChartPicker.tsx:112 — ChartPicker.ChartPicker has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 16, if/else 6 (11 pts), ternaries 7 (11 pts) (nesting depth added 9). Most of this is not in the body itself: 3 of the 38 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 217, a function literal at line 273, a function literal at line 253, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · DatasetBinder.bind (cognitive 37) · ×1
  • DatasetBinder.bind (cognitive 37) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetBinder.kt:97 — DatasetBinder.bind has cognitive complexity 37 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 10, match/switch 4, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · analysis.narrowAggregation (cognitive 37) · ×1
  • analysis.narrowAggregation (cognitive 37) typescript/wow-view-engine/src/capabilities/analysis.ts:263 — analysis.narrowAggregation has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 17, if/else 11, ternaries 9. Of this number, 32 points are the body's own statements and 5 belong to 3 function items 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 · fields.buildField (cognitive 37) · ×1
  • fields.buildField (cognitive 37) typescript/wow-view-engine/src/runtime/define/fields.ts:89 — fields.buildField has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 6, loops 2 (4 pts), ternaries 2 (nesting depth added 8). 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 · ConditionPill.ConditionPill (cognitive 36) · ×1
  • ConditionPill.ConditionPill (cognitive 36) typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:80 — ConditionPill.ConditionPill has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 30, if/else 3, ternaries 3. Of this number, 34 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Resolution.objectConstrained (cognitive 34) · ×1
  • Resolution.objectConstrained (cognitive 34) typescript/wow-generator/src/types/typeResolver.ts:564 — Resolution.objectConstrained has cognitive complexity 34 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 9, loops 5 (9 pts), ternaries 2 (nesting depth added 13). Of this number, 31 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SaveActions.SaveActions (cognitive 34) · ×1
  • SaveActions.SaveActions (cognitive 34) typescript/wow-view-engine/src/ui/workbench/SaveActions.tsx:87 — SaveActions.SaveActions has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 22, if/else 11, ternaries 1. Of this number, 18 points are the body's own statements and 16 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · PanelBodies.AnalysisPanel (cognitive 34) · ×1
  • PanelBodies.AnalysisPanel (cognitive 34) typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx:293 — PanelBodies.AnalysisPanel has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 9, ternaries 6 (9 pts) (nesting depth added 9). Of this number, 20 points are the body's own statements and 14 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 · validateGroups.groupIssues (cognitive 33) · ×1
  • validateGroups.groupIssues (cognitive 33) typescript/wow-view-engine/src/analysis/validateGroups.ts:94 — validateGroups.groupIssues has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (27 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 10). None of this is in the body itself: all 33 points belong to one function literal inside it that branches (line 104). 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 · cells.cellValue (cognitive 33) · ×1
  • cells.cellValue (cognitive 33) typescript/wow-view-engine/src/ui/record/cells.tsx:86 — cells.cellValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (20 pts), ternaries 3 (7 pts), boolean chains 6 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ContentEditor.ContentForm (cognitive 33) · ×1
  • ContentEditor.ContentForm (cognitive 33) typescript/wow-view-engine/src/ui/dashboard/ContentEditor.tsx:204 — ContentEditor.ContentForm has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 21, ternaries 7 (8 pts), if/else 4 (nesting depth added 1). Of this number, 21 points are the body's own statements and 12 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · cartesian.shapeCartesian (cognitive 32) · ×1
  • cartesian.shapeCartesian (cognitive 32) typescript/wow-view-engine/src/analysis/cartesian.ts:156 — cartesian.shapeCartesian has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 10 (18 pts), if/else 5 (6 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 10). Of this number, 24 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SortableHeader.SortableHeader (cognitive 32) · ×1
  • SortableHeader.SortableHeader (cognitive 32) typescript/wow-view-engine/src/ui/record/SortableHeader.tsx:97 — SortableHeader.SortableHeader has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 15 (18 pts), boolean chains 9, if/else 5 (nesting depth added 3). Of this number, 26 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · RecordDetail.RecordDetail (cognitive 32) · ×1
  • RecordDetail.RecordDetail (cognitive 32) typescript/wow-view-engine/src/ui/record/RecordDetail.tsx:128 — RecordDetail.RecordDetail has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 13, if/else 2 (nesting depth added 7). Of this number, 26 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent 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 · issueNames.analysisIssueNamer.<returned closure> (cognitive 32) · ×1
  • issueNames.analysisIssueNamer.<returned closure> (cognitive 32) typescript/wow-view-engine/src/ui/analysis/issueNames.ts:101 — issueNames.analysisIssueNamer.<returned closure> has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 4, ternaries 3 (4 pts), loops 2 (3 pts) (nesting depth added 10). Of this number, 30 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MetricCard.MetricCard (cognitive 32) · ×1
  • MetricCard.MetricCard (cognitive 32) typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78 — MetricCard.MetricCard has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 26, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 31 points are the body's own statements and 1 belongs to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · click.validatePanelClick (cognitive 31) · ×1
  • click.validatePanelClick (cognitive 31) typescript/wow-view-engine/src/dashboard/click.ts:162 — click.validatePanelClick has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 5 (10 pts), boolean chains 3, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · source.scoped (cognitive 31) · ×1
  • source.scoped (cognitive 31) typescript/wow-view-engine/src/testing/source.ts:204 — source.scoped has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 8, match/switch 1 (2 pts), loops 1, ternaries 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 · SaveAsDialog.SaveAsForm (cognitive 31) · ×1
  • SaveAsDialog.SaveAsForm (cognitive 31) typescript/wow-view-engine/src/ui/workbench/SaveAsDialog.tsx:230 — SaveAsDialog.SaveAsForm has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (18 pts), boolean chains 11, if/else 2 (nesting depth added 10). Of this number, 24 points are the body's own statements and 7 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AnalysisParts.AnalysisParts (cognitive 31) · ×1
  • AnalysisParts.AnalysisParts (cognitive 31) typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx:126 — AnalysisParts.AnalysisParts has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 18, ternaries 9 (12 pts), if/else 1 (nesting depth added 3). Of this number, 30 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · metricCard.metricCard (cognitive 30) · ×1
  • metricCard.metricCard (cognitive 30) typescript/wow-view-engine/src/analysis/metricCard.ts:160 — metricCard.metricCard has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 16 (21 pts), boolean chains 9 (nesting depth added 5). Of this number, 27 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DatasetExpressionParser.tokenize (cognitive 29) · ×1
  • DatasetExpressionParser.tokenize (cognitive 29) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetExpression.kt:292 — DatasetExpressionParser.tokenize has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ElasticsearchQuerySchemaAdapterKt.supports (cognitive 29) · ×1
  • ElasticsearchQuerySchemaAdapterKt.supports (cognitive 29) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/query/schema/ElasticsearchQuerySchemaAdapter.kt:469 — ElasticsearchQuerySchemaAdapterKt.supports has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 26, if/else 2, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · datasetRecord.notJsonAt (cognitive 29) · ×1
  • datasetRecord.notJsonAt (cognitive 29) platform/analytics/catalog/console/src/detail/datasetRecord.ts:60 — datasetRecord.notJsonAt has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 3, loops 3, error handling 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (value, string, items, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · manifestClients.emitCommandClient (cognitive 29) · ×1
  • manifestClients.emitCommandClient (cognitive 29) typescript/wow-generator/src/emitters/manifestClients.ts:635 — manifestClients.emitCommandClient has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (17 pts), if/else 6 (8 pts), boolean chains 3, loops 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RecordParts.RecordParts (cognitive 29) · ×1
  • RecordParts.RecordParts (cognitive 29) typescript/wow-view-engine/src/ui/workbench/RecordParts.tsx:202 — RecordParts.RecordParts has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 13 (16 pts), boolean chains 9, if/else 3, match/switch 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · scale.sharedScales (cognitive 28) · ×1
  • scale.sharedScales (cognitive 28) typescript/wow-view-engine/src/ui/charts/scale.ts:82 — scale.sharedScales has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 3 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 15). Of this number, 19 points are the body's own statements and 9 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 · admit.validateHaving (cognitive 27) · ×1
  • admit.validateHaving (cognitive 27) typescript/wow-client/src/dsl/aggregation/admit.ts:271 — admit.validateHaving has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 14). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · unavailable.without1 (cognitive 27) · ×1
  • unavailable.without1 (cognitive 27) typescript/wow-view-engine/src/runtime/failure/unavailable.ts:103 — unavailable.without1 has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 8, ternaries 3 (6 pts) (nesting depth added 6). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useWorkbench.useWorkbench (cognitive 27) · ×1
  • useWorkbench.useWorkbench (cognitive 27) typescript/wow-view-engine/src/react/useWorkbench.ts:408 — useWorkbench.useWorkbench has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 7, loops 1 (nesting depth added 5). Of this number, 25 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 · ColumnRow.ColumnRow (cognitive 27) · ×1
  • ColumnRow.ColumnRow (cognitive 27) typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151 — ColumnRow.ColumnRow has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 11 (13 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · address.useAddressedInstance (cognitive 27) · ×1
  • address.useAddressedInstance (cognitive 27) typescript/wow-view-engine/src/ui/workbench/address.ts:197 — address.useAddressedInstance has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13, boolean chains 7, ternaries 5 (6 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 271, 237, 222, …). 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 · check.checkBounds (cognitive 27) · ×1
  • check.checkBounds (cognitive 27) typescript/wow-view-engine/theme-check/check.ts:529 — check.checkBounds has cognitive complexity 27 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 4 (8 pts), boolean chains 5, ternaries 1 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WowViewStore.write (cognitive 27) · ×1
  • WowViewStore.write (cognitive 27) typescript/wow-view-store/src/wowViewStore.ts:494 — WowViewStore.write has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (2 pts), loops 1 (nesting depth added 14). None of this is in the body itself: all 27 points belong to one function literal inside it that branches (line 500). 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 · open.aggregation (cognitive 26) · ×1
  • open.aggregation (cognitive 26) typescript/wow-view-engine/src/capabilities/open.ts:161 — open.aggregation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 10, loops 2, ternaries 2 (nesting depth added 4). Of this number, 20 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent 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 · ReferenceLabels.want (cognitive 26) · ×1
  • ReferenceLabels.want (cognitive 26) typescript/wow-view-engine/src/runtime/referenceLabels.ts:224 — ReferenceLabels.want has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (6 pts), boolean chains 3 (nesting depth added 7). Of this number, 22 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · actionRunner.useActionRunner.run (cognitive 26) · ×1
  • actionRunner.useActionRunner.run (cognitive 26) typescript/wow-view-engine/src/react/actionRunner.ts:278 — actionRunner.useActionRunner.run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 7, boolean chains 4, error handling 2 (3 pts), loops 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (judge, worker, finish, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · date.DateValue (cognitive 26) · ×1
  • date.DateValue (cognitive 26) typescript/wow-view-engine/src/ui/filter/inputs/date.tsx:70 — date.DateValue has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, ternaries 7 (8 pts), if/else 6 (7 pts) (nesting depth added 2). Of this number, 15 points are the body's own statements and 11 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ViewPicker.Catalogue (cognitive 26) · ×1
  • ViewPicker.Catalogue (cognitive 26) typescript/wow-view-engine/src/ui/dashboard/ViewPicker.tsx:216 — ViewPicker.Catalogue has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (16 pts), boolean chains 7, if/else 1 (3 pts) (nesting depth added 12). Of this number, 18 points are the body's own statements and 8 belong to 5 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 · Board.DashboardBoard (cognitive 26) · ×1
  • Board.DashboardBoard (cognitive 26) typescript/wow-view-engine/src/ui/dashboard/Board.tsx:91 — Board.DashboardBoard has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 6, ternaries 6, match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 13 function items inside it that branch (add, a function literal at line 139, a function literal at line 331, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · NewAnalysisDialog.NewAnalysisForm (cognitive 26) · ×1
  • NewAnalysisDialog.NewAnalysisForm (cognitive 26) typescript/wow-view-engine/src/ui/dashboard/NewAnalysisDialog.tsx:154 — NewAnalysisDialog.NewAnalysisForm has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 9, if/else 6 (7 pts) (nesting depth added 2). Of this number, 18 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · resolve.createResolver.declared (cognitive 26) · ×1
  • resolve.createResolver.declared (cognitive 26) typescript/wow-view-engine/theme-check/resolve.ts:553 — resolve.createResolver.declared has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 7 (8 pts), boolean chains 2, loops 2 (nesting depth added 4). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (layered, link, read, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · tree.sameValue (cognitive 25) · ×1
  • tree.sameValue (cognitive 25) typescript/wow-view-engine/src/filter/tree.ts:455 — tree.sameValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (6 pts), boolean chains 3 (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 · metricWindow.metricReach (cognitive 25) · ×1
  • metricWindow.metricReach (cognitive 25) typescript/wow-view-engine/src/analysis/metricWindow.ts:44 — metricWindow.metricReach has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · verify-package.classNames (cognitive 25) · ×1
  • verify-package.classNames (cognitive 25) typescript/wow-view-engine/scripts/verify-package.mjs:866 — verify-package.classNames has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Parser.string (cognitive 24) · ×1
  • Parser.string (cognitive 24) typescript/wow-client/src/exactJson.ts:266 — Parser.string has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate.validateFilter (cognitive 24) · ×1
  • validate.validateFilter (cognitive 24) typescript/wow-view-engine/src/filter/validate.ts:68 — validate.validateFilter has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compile.recordProjection (cognitive 24) · ×1
  • compile.recordProjection (cognitive 24) typescript/wow-view-engine/src/record/compile.ts:118 — compile.recordProjection has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 5, loops 5 (nesting depth added 5). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · derived.derivedGap (cognitive 24) · ×1
  • derived.derivedGap (cognitive 24) typescript/wow-view-engine/src/analysis/derived.ts:130 — derived.derivedGap has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, ternaries 4 (5 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · project.projectAnalysis · ×1
  • project.projectAnalysis::describe (cognitive 24) typescript/wow-view-engine/src/analysis/project.ts:533 — project.projectAnalysis::describe has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 14 (15 pts), boolean chains 8, if/else 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · click.validateBoardClick (cognitive 24) · ×1
  • click.validateBoardClick (cognitive 24) typescript/wow-view-engine/src/dashboard/click.ts:273 — click.validateBoardClick has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (5 pts), boolean chains 4, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · display.displayValue (cognitive 24) · ×1
  • display.displayValue (cognitive 24) typescript/wow-view-engine/src/ui/kit/display.ts:157 — display.displayValue has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 6 (7 pts), boolean chains 3, 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 · cartesianMarks.extremePoints (cognitive 24) · ×1
  • cartesianMarks.extremePoints (cognitive 24) typescript/wow-view-engine/src/ui/charts/cartesianMarks.ts:416 — cartesianMarks.extremePoints has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 13 (20 pts), boolean chains 3, if/else 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function items inside it that branch (point, align, beyond). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Cartesian.Cartesian (cognitive 24) · ×1
  • Cartesian.Cartesian (cognitive 24) typescript/wow-view-engine/src/ui/charts/Cartesian.tsx:42 — Cartesian.Cartesian has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 15, ternaries 7 (8 pts), if/else 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 9 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 · MetricCard.MetricCard (cognitive 24) · ×1
  • MetricCard.MetricCard (cognitive 24) typescript/wow-view-engine/src/ui/charts/MetricCard.tsx:341 — MetricCard.MetricCard has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 10 (nesting depth added 5). Of this number, 14 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DisplayTab.ValueLabelsField (cognitive 24) · ×1
  • DisplayTab.ValueLabelsField (cognitive 24) typescript/wow-view-engine/src/ui/analysis/DisplayTab.tsx:142 — DisplayTab.ValueLabelsField has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11 (16 pts), boolean chains 6, if/else 2 (nesting depth added 5). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · exactJson.resolve (cognitive 23) · ×1
  • exactJson.resolve (cognitive 23) typescript/wow-client/src/exactJson.ts:100 — exactJson.resolve has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (13 pts), loops 2 (4 pts), boolean chains 3, if/else 3 (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 · panels.clickOf (cognitive 23) · ×1
  • panels.clickOf (cognitive 23) typescript/wow-view-engine/src/dashboard/panels.ts:126 — panels.clickOf has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (7 pts), boolean chains 3, loops 1 (2 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 · analysis.narrowAnalysis (cognitive 23) · ×1
  • analysis.narrowAnalysis (cognitive 23) typescript/wow-view-engine/src/capabilities/analysis.ts:49 — analysis.narrowAnalysis has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15, boolean chains 8. 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 · summary.summaryWords (cognitive 23) · ×1
  • summary.summaryWords (cognitive 23) typescript/wow-view-engine/src/ui/kit/summary.ts:72 — summary.summaryWords has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · MetricCard.PeriodChange (cognitive 23) · ×1
  • MetricCard.PeriodChange (cognitive 23) typescript/wow-view-engine/src/ui/charts/MetricCard.tsx:199 — MetricCard.PeriodChange has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (21 pts), boolean chains 1, if/else 1 (nesting depth added 12). 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 · WriteOutcome.WriteOutcome (cognitive 23) · ×1
  • WriteOutcome.WriteOutcome (cognitive 23) typescript/wow-view-engine/src/ui/workbench/WriteOutcome.tsx:101 — WriteOutcome.WriteOutcome has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 4 (7 pts), boolean chains 3, match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (notify, a function literal at line 128, a function literal at line 179, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PanelMenu.PanelMenu (cognitive 23) · ×1
  • PanelMenu.PanelMenu (cognitive 23) typescript/wow-view-engine/src/ui/dashboard/PanelMenu.tsx:112 — PanelMenu.PanelMenu has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 23. 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 · DashboardTabs.DashboardTabs (cognitive 23) · ×1
  • DashboardTabs.DashboardTabs (cognitive 23) typescript/wow-view-engine/src/ui/dashboard/DashboardTabs.tsx:63 — DashboardTabs.DashboardTabs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, ternaries 6 (9 pts), boolean chains 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (remove, move, a function literal at line 89, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · match.describedField (cognitive 22) · ×1
  • match.describedField (cognitive 22) typescript/wow-view-engine/src/capabilities/match.ts:80 — match.describedField has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (17 pts), if/else 3, boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useRecordDetail.useRecordDetail (cognitive 22) · ×1
  • useRecordDetail.useRecordDetail (cognitive 22) typescript/wow-view-engine/src/react/useRecordDetail.ts:121 — useRecordDetail.useRecordDetail has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 5, if/else 5 (nesting depth added 3). Of this number, 16 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DrillMenu.DrillMenu (cognitive 22) · ×1
  • DrillMenu.DrillMenu (cognitive 22) typescript/wow-view-engine/src/ui/analysis/DrillMenu.tsx:105 — DrillMenu.DrillMenu has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (7 pts), ternaries 3 (5 pts), match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 241, 141, 127, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · cartesianTooltip.cartesianTooltip (cognitive 22) · ×1
  • cartesianTooltip.cartesianTooltip (cognitive 22) typescript/wow-view-engine/src/ui/charts/cartesianTooltip.ts:30 — cartesianTooltip.cartesianTooltip has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 4, if/else 2 (nesting depth added 2). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 5 function items inside it that branch (rowAt, a function literal at line 85, earlierChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · remote.CandidateValue (cognitive 22) · ×1
  • remote.CandidateValue (cognitive 22) typescript/wow-view-engine/src/ui/filter/inputs/remote.tsx:114 — remote.CandidateValue has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 7, if/else 4 (nesting depth added 3). Of this number, 13 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MongoQuerySchemaAdapter.supportsUnion (cognitive 21) · ×1
  • MongoQuerySchemaAdapter.supportsUnion (cognitive 21) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoQuerySchemaAdapter.kt:268 — MongoQuerySchemaAdapter.supportsUnion has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generate.generateRetail.requestAfterSales (cognitive 21) · ×1
  • generate.generateRetail.requestAfterSales (cognitive 21) typescript/storybook/stories/view-engine/retail/generate.ts:1330 — generate.generateRetail.requestAfterSales has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 6 (8 pts), boolean chains 2, 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 · metricFit.misfits (cognitive 21) · ×1
  • metricFit.misfits (cognitive 21) typescript/storybook/stories/view-engine/metricFit.ts:79 — metricFit.misfits has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · timeAxis.withoutHoles (cognitive 21) · ×1
  • timeAxis.withoutHoles (cognitive 21) typescript/wow-view-engine/src/analysis/timeAxis.ts:208 — timeAxis.withoutHoles has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 5, loops 3, boolean chains 2 (nesting depth added 3). Of this number, 20 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · familySlots.cartesianSlots (cognitive 21) · ×1
  • familySlots.cartesianSlots (cognitive 21) typescript/wow-view-engine/src/analysis/familySlots.ts:111 — familySlots.cartesianSlots has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 16 (20 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · filters.admitFilters (cognitive 21) · ×1
  • filters.admitFilters (cognitive 21) typescript/wow-view-engine/src/dashboard/filters.ts:214 — filters.admitFilters has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, ternaries 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validateFields.validateFields (cognitive 21) · ×1
  • validateFields.validateFields (cognitive 21) typescript/wow-view-engine/src/runtime/validateFields.ts:41 — validateFields.validateFields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 6 (nesting depth added 1). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 61, 151, 165). 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 · useViewList.useViewList (cognitive 21) · ×1
  • useViewList.useViewList (cognitive 21) typescript/wow-view-engine/src/react/useViewList.ts:152 — useViewList.useViewList has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (15 pts), if/else 5, boolean chains 1 (nesting depth added 3). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 188, 262, 186, …). 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 · scatterOption.scatterOption (cognitive 21) · ×1
  • scatterOption.scatterOption (cognitive 21) typescript/wow-view-engine/src/ui/charts/scatterOption.ts:68 — scatterOption.scatterOption has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 4, if/else 1 (nesting depth added 4). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (axis, diameter, a function literal at line 193, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · virtualRows.useVirtualRows (cognitive 21) · ×1
  • virtualRows.useVirtualRows (cognitive 21) typescript/wow-view-engine/src/ui/analysis/virtualRows.ts:128 — virtualRows.useVirtualRows has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 7, boolean chains 5, loops 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 171, 169, 201, …). 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 · FilterPanel.FilterPanel (cognitive 21) · ×1
  • FilterPanel.FilterPanel (cognitive 21) typescript/wow-view-engine/src/ui/filter/FilterPanel.tsx:82 — FilterPanel.FilterPanel has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 5 (7 pts), if/else 4 (nesting depth added 2). Of this number, 14 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · scrollMore.measurePort (cognitive 21) · ×1
  • scrollMore.measurePort (cognitive 21) typescript/wow-view-engine/src/ui/dashboard/scrollMore.ts:169 — scrollMore.measurePort has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FilterBar.FilterBar (cognitive 21) · ×1
  • FilterBar.FilterBar (cognitive 21) typescript/wow-view-engine/src/ui/dashboard/FilterBar.tsx:170 — FilterBar.FilterBar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 13, ternaries 4 (6 pts), if/else 2 (nesting depth added 2). Of this number, 18 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, 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 · EmbeddedDashboard.EmbeddedBoard (cognitive 21) · ×1
  • EmbeddedDashboard.EmbeddedBoard (cognitive 21) typescript/wow-view-engine/src/ui/EmbeddedDashboard.tsx:230 — EmbeddedDashboard.EmbeddedBoard has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 13, ternaries 7, if/else 1. Of this number, 17 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, 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 · QueryStorageFamiliesKt.storageFamilies (cognitive 20) · ×1
  • QueryStorageFamiliesKt.storageFamilies (cognitive 20) query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryStorageFamilies.kt:94 — QueryStorageFamiliesKt.storageFamilies has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, match/switch 3 (5 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DatasetCompiler.expression (cognitive 20) · ×1
  • DatasetCompiler.expression (cognitive 20) platform/analytics/catalog/domain/src/main/kotlin/me/ahoo/wow/analytics/catalog/domain/dataset/DatasetCompiler.kt:189 — DatasetCompiler.expression has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 2 (3 pts) (nesting depth added 7). 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 · generate.generateRetail.lifecycle (cognitive 20) · ×1
  • generate.generateRetail.lifecycle (cognitive 20) typescript/storybook/stories/view-engine/retail/generate.ts:1220 — generate.generateRetail.lifecycle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8, ternaries 4 (8 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Parser.object (cognitive 20) · ×1
  • Parser.object (cognitive 20) typescript/wow-client/src/exactJson.ts:201 — Parser.object has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (8 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fieldGroups.fieldGroups (cognitive 20) · ×1
  • fieldGroups.fieldGroups (cognitive 20) typescript/wow-view-engine/src/filter/fieldGroups.ts:31 — fieldGroups.fieldGroups has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5 (7 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fields.narrowField (cognitive 20) · ×1
  • fields.narrowField (cognitive 20) typescript/wow-view-engine/src/capabilities/fields.ts:99 — fields.narrowField has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, ternaries 4 (5 pts), boolean chains 2 (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 · wire-literals.slotValues (cognitive 20) · ×1
  • wire-literals.slotValues (cognitive 20) typescript/wow-view-engine/scripts/wire-literals.mjs:246 — wire-literals.slotValues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 2 (6 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ActionSurface.useActionSurface (cognitive 20) · ×1
  • ActionSurface.useActionSurface (cognitive 20) typescript/wow-view-engine/src/ui/actions/ActionSurface.tsx:99 — ActionSurface.useActionSurface has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 4. Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 177, a function literal at line 157, a function literal at line 168, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · DashboardPanelCard.DashboardPanelCard (cognitive 20) · ×1
  • DashboardPanelCard.DashboardPanelCard (cognitive 20) typescript/wow-view-engine/src/ui/dashboard/DashboardPanelCard.tsx:257 — DashboardPanelCard.DashboardPanelCard has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, ternaries 5. 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 · EntityTags.parse (cognitive 19) · ×1
  • EntityTags.parse (cognitive 19) edge/http/src/main/kotlin/me/ahoo/wow/http/EntityTags.kt:57 — EntityTags.parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exactJson.replace (cognitive 19) · ×1
  • exactJson.replace (cognitive 19) typescript/wow-client/src/exactJson.ts:409 — exactJson.replace has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (7 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 · admit.validateDerivedExpression (cognitive 19) · ×1
  • admit.validateDerivedExpression (cognitive 19) typescript/wow-client/src/dsl/aggregation/admit.ts:153 — admit.validateDerivedExpression has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · configuration.validateApiClients (cognitive 19) · ×1
  • configuration.validateApiClients (cognitive 19) typescript/wow-generator/src/input/configuration.ts:274 — configuration.validateApiClients has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaTypes.name (cognitive 19) · ×1
  • SchemaTypes.name (cognitive 19) typescript/wow-generator/src/manifest/analyze.ts:332 — SchemaTypes.name has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (12 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 11). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. 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 · manifestClients.commandMethods (cognitive 19) · ×1
  • manifestClients.commandMethods (cognitive 19) typescript/wow-generator/src/emitters/manifestClients.ts:571 — manifestClients.commandMethods has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 14 (15 pts), boolean chains 3, if/else 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · candlestick.ohlcSets (cognitive 19) · ×1
  • candlestick.ohlcSets (cognitive 19) typescript/wow-view-engine/src/analysis/candlestick.ts:88 — candlestick.ohlcSets has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 7). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · drill.drillSpan (cognitive 19) · ×1
  • drill.drillSpan (cognitive 19) typescript/wow-view-engine/src/analysis/drill.ts:251 — drill.drillSpan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · publish.requireSystemPanels (cognitive 19) · ×1
  • publish.requireSystemPanels (cognitive 19) typescript/wow-view-engine/src/runtime/publish.ts:93 — publish.requireSystemPanels has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (6 pts), boolean chains 4, loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useSaveCommands.useSaveCommands (cognitive 19) · ×1
  • useSaveCommands.useSaveCommands (cognitive 19) typescript/wow-view-engine/src/react/useSaveCommands.ts:211 — useSaveCommands.useSaveCommands has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, ternaries 6. 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 · useAnalysisResult.useAnalysisResult (cognitive 19) · ×1
  • useAnalysisResult.useAnalysisResult (cognitive 19) typescript/wow-view-engine/src/react/useAnalysisResult.ts:251 — useAnalysisResult.useAnalysisResult has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, ternaries 7, if/else 1. Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · cartesianOption.markOf (cognitive 19) · ×1
  • cartesianOption.markOf (cognitive 19) typescript/wow-view-engine/src/ui/charts/cartesianOption.ts:341 — cartesianOption.markOf has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 2 (3 pts), boolean chains 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResultToolbar.ResultToolbar (cognitive 19) · ×1
  • ResultToolbar.ResultToolbar (cognitive 19) typescript/wow-view-engine/src/ui/workbench/ResultToolbar.tsx:157 — ResultToolbar.ResultToolbar has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, ternaries 5. 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 · MoreViewActions.MoreViewActions (cognitive 19) · ×1
  • MoreViewActions.MoreViewActions (cognitive 19) typescript/wow-view-engine/src/ui/workbench/MoreViewActions.tsx:52 — MoreViewActions.MoreViewActions has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, ternaries 4 (6 pts), if/else 2 (nesting depth added 2). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · SubscriptionWorker.retried (cognitive 18) · ×1
  • SubscriptionWorker.retried (cognitive 18) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt:484 — SubscriptionWorker.retried has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (4 pts), boolean chains 1, 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 · CronExpression.nextLocal (cognitive 18) · ×1
  • CronExpression.nextLocal (cognitive 18) core/kernel/src/main/kotlin/me/ahoo/wow/kernel/schedule/CronExpression.kt:73 — CronExpression.nextLocal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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 · SharedTopicConsumer.run (cognitive 18) · ×1
  • SharedTopicConsumer.run (cognitive 18) backends/kafka/src/main/kotlin/me/ahoo/wow/kafka/SharedTopicConsumer.kt:151 — SharedTopicConsumer.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 5 (7 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 · document.validateManifest (cognitive 18) · ×1
  • document.validateManifest (cognitive 18) typescript/wow-generator/src/manifest/document.ts:96 — document.validateManifest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (nesting depth added 2). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 122, 117, 132, …). 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 · typeText.compound (cognitive 18) · ×1
  • typeText.compound (cognitive 18) typescript/wow-generator/src/manifest/typeText.ts:28 — typeText.compound has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, 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 · SchemaTypes.type (cognitive 18) · ×1
  • SchemaTypes.type (cognitive 18) typescript/wow-generator/src/manifest/analyze.ts:448 — SchemaTypes.type has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaTypes.textNumbers (cognitive 18) · ×1
  • SchemaTypes.textNumbers (cognitive 18) typescript/wow-generator/src/manifest/analyze.ts:574 — SchemaTypes.textNumbers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 1 (2 pts), ternaries 2 (nesting depth added 4). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · dateTime.createDateKind.validate (cognitive 18) · ×1
  • dateTime.createDateKind.validate (cognitive 18) typescript/wow-view-engine/src/filter/kinds/dateTime.ts:424 — dateTime.createDateKind.validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · currency.currencyIssues (cognitive 18) · ×1
  • currency.currencyIssues (cognitive 18) typescript/wow-view-engine/src/analysis/currency.ts:215 — currency.currencyIssues has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · queryFilter.saysNothingIssues (cognitive 18) · ×1
  • queryFilter.saysNothingIssues (cognitive 18) typescript/wow-view-engine/src/analysis/queryFilter.ts:148 — queryFilter.saysNothingIssues has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, ternaries 1 (2 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 · open.unionFields (cognitive 18) · ×1
  • open.unionFields (cognitive 18) typescript/wow-view-engine/src/capabilities/open.ts:327 — open.unionFields has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PanelChildren.sync (cognitive 18) · ×1
  • PanelChildren.sync (cognitive 18) typescript/wow-view-engine/src/runtime/dashboard/children.ts:169 — PanelChildren.sync has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · summaries.storedSummaries (cognitive 18) · ×1
  • summaries.storedSummaries (cognitive 18) typescript/wow-view-engine/src/runtime/summaries.ts:54 — summaries.storedSummaries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 4 (6 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · wire-literals.wireVocabularies · ×1
  • wire-literals.wireVocabularies::visit (cognitive 18) typescript/wow-view-engine/scripts/wire-literals.mjs:76 — wire-literals.wireVocabularies::visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · wire-literals.enumsNamed · ×1
  • wire-literals.enumsNamed::visit (cognitive 18) typescript/wow-view-engine/scripts/wire-literals.mjs:285 — wire-literals.enumsNamed::visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DashboardArrange.PanelHandle (cognitive 18) · ×1
  • DashboardArrange.PanelHandle (cognitive 18) typescript/wow-view-engine/src/ui/dashboard/DashboardArrange.tsx:103 — DashboardArrange.PanelHandle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, boolean chains 3, ternaries 3. Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 155, end, a function literal at line 127, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · RecordKanban.KanbanLane (cognitive 18) · ×1
  • RecordKanban.KanbanLane (cognitive 18) typescript/wow-view-engine/src/ui/record/RecordKanban.tsx:169 — RecordKanban.KanbanLane has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 6 (7 pts), if/else 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · VisualizationPanel.visualizationPanel (cognitive 18) · ×1
  • VisualizationPanel.visualizationPanel (cognitive 18) typescript/wow-view-engine/src/ui/analysis/VisualizationPanel.tsx:123 — VisualizationPanel.visualizationPanel has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 6, if/else 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InMemoryFilters.expression (cognitive 17) · ×1
  • InMemoryFilters.expression (cognitive 17) query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryFilters.kt:238 — InMemoryFilters.expression has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 7). 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 · EventStreamImporter.append (cognitive 17) · ×1
  • EventStreamImporter.append (cognitive 17) migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/EventStreamImporter.kt:561 — EventStreamImporter.append has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (5 pts), boolean chains 1, 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 · NineXEventSource.tagged (cognitive 17) · ×1
  • NineXEventSource.tagged (cognitive 17) migration/migrate-data/src/main/kotlin/me/ahoo/wow/migrate/NineXEventSource.kt:171 — NineXEventSource.tagged has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (7 pts) (nesting depth added 11). 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 · SubscriptionWorker.runRetry (cognitive 17) · ×1
  • SubscriptionWorker.runRetry (cognitive 17) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/subscription/SubscriptionWorker.kt:671 — SubscriptionWorker.runRetry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 3, 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 · http.send (cognitive 17) · ×1
  • http.send (cognitive 17) typescript/wow-client/src/http.ts:139 — http.send has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 3 (5 pts), boolean chains 2, error handling 1, 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 · typeResolver.schemaKind (cognitive 17) · ×1
  • typeResolver.schemaKind (cognitive 17) typescript/wow-generator/src/types/typeResolver.ts:201 — typeResolver.schemaKind has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · describe.joinSegments (cognitive 17) · ×1
  • describe.joinSegments (cognitive 17) typescript/wow-view-engine/src/filter/describe.ts:337 — describe.joinSegments has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), boolean chains 2, loops 2 (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · validate.walkShape (cognitive 17) · ×1
  • validate.walkShape (cognitive 17) typescript/wow-view-engine/src/filter/validate.ts:320 — validate.walkShape has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · metricCard.lastPeriod (cognitive 17) · ×1
  • metricCard.lastPeriod (cognitive 17) typescript/wow-view-engine/src/analysis/metricCard.ts:355 — metricCard.lastPeriod has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10, boolean chains 5, if/else 1, loops 1. Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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 · validateFamilies.cardIssues (cognitive 17) · ×1
  • validateFamilies.cardIssues (cognitive 17) typescript/wow-view-engine/src/analysis/validateFamilies.ts:399 — validateFamilies.cardIssues has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, 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 · metricFormat.reading (cognitive 17) · ×1
  • metricFormat.reading (cognitive 17) typescript/wow-view-engine/src/analysis/metricFormat.ts:263 — metricFormat.reading has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 8). 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 · expressions.expressionIssues (cognitive 17) · ×1
  • expressions.expressionIssues (cognitive 17) typescript/wow-view-engine/src/analysis/expressions.ts:36 — expressions.expressionIssues has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · wiring.bindPanel (cognitive 17) · ×1
  • wiring.bindPanel (cognitive 17) typescript/wow-view-engine/src/dashboard/wiring.ts:146 — wiring.bindPanel has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 6, boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 163, 190). 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 · metricOrder.moveMetric (cognitive 17) · ×1
  • metricOrder.moveMetric (cognitive 17) typescript/wow-view-engine/src/analysis/metricOrder.ts:54 — metricOrder.moveMetric has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 5, if/else 5 (nesting depth added 2). Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: 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 · deprecated.namedFields (cognitive 17) · ×1
  • deprecated.namedFields (cognitive 17) typescript/wow-view-engine/src/runtime/deprecated.ts:57 — deprecated.namedFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · open.describedAnalysis (cognitive 17) · ×1
  • open.describedAnalysis (cognitive 17) typescript/wow-view-engine/src/capabilities/open.ts:89 — open.describedAnalysis has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 3, boolean chains 2, loops 1 (2 pts) (nesting depth added 3). Of this number, 10 points are the body's own statements and 7 belong to 4 function items 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 · analysis.analysisPlan (cognitive 17) · ×1
  • analysis.analysisPlan (cognitive 17) typescript/wow-view-engine/src/runtime/define/analysis.ts:36 — analysis.analysisPlan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), ternaries 2 (3 pts) (nesting depth added 8). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent 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 · aggregate.summarise (cognitive 17) · ×1
  • aggregate.summarise (cognitive 17) typescript/wow-view-engine/src/testing/aggregate.ts:68 — aggregate.summarise has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 4, loops 2 (3 pts), boolean chains 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent 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 · cartesianSeries.reachOf (cognitive 17) · ×1
  • cartesianSeries.reachOf (cognitive 17) typescript/wow-view-engine/src/ui/charts/cartesianSeries.ts:171 — cartesianSeries.reachOf has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Funnel.Funnel (cognitive 17) · ×1
  • Funnel.Funnel (cognitive 17) typescript/wow-view-engine/src/ui/charts/Funnel.tsx:50 — Funnel.Funnel has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, ternaries 6. Of this number, 12 points are the body's own statements and 5 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 · time.TimeOfDay (cognitive 17) · ×1
  • time.TimeOfDay (cognitive 17) typescript/wow-view-engine/src/ui/filter/inputs/time.tsx:56 — time.TimeOfDay has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (6 pts), ternaries 3 (4 pts) (nesting depth added 3). Of this number, 9 points are the body's own statements and 8 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 · SortSettings.SortSettings (cognitive 17) · ×1
  • SortSettings.SortSettings (cognitive 17) typescript/wow-view-engine/src/ui/sort/SortSettings.tsx:196 — SortSettings.SortSettings has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 4 (5 pts), boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 231, named, moveTo, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · FieldChecklist.FieldChecklist (cognitive 17) · ×1
  • FieldChecklist.FieldChecklist (cognitive 17) typescript/wow-view-engine/src/ui/filter/FieldChecklist.tsx:86 — FieldChecklist.FieldChecklist has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 6 (7 pts), boolean chains 3 (nesting depth added 2). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (toggle, a function literal at line 226, a function literal at line 262, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ViewManagerRow.ViewManagerRow (cognitive 17) · ×1
  • ViewManagerRow.ViewManagerRow (cognitive 17) typescript/wow-view-engine/src/ui/manage/ViewManagerRow.tsx:131 — ViewManagerRow.ViewManagerRow has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 14, ternaries 2, if/else 1. Of this number, 16 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ClickSettings.GoFields (cognitive 17) · ×1
  • ClickSettings.GoFields (cognitive 17) typescript/wow-view-engine/src/ui/dashboard/ClickSettings.tsx:302 — ClickSettings.GoFields has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 7, if/else 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · history.useBoardHistory (cognitive 17) · ×1
  • history.useBoardHistory (cognitive 17) typescript/wow-view-engine/src/ui/dashboard/history.ts:114 — history.useBoardHistory has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 146, 152, 150). 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 · filterOutcome.useFilterOutcome (cognitive 17) · ×1
  • filterOutcome.useFilterOutcome (cognitive 17) typescript/wow-view-engine/src/ui/dashboard/filterOutcome.ts:67 — filterOutcome.useFilterOutcome has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 82, 111). 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 · DashboardWorkbench.DashboardWorkbenchBody (cognitive 17) · ×1
  • DashboardWorkbench.DashboardWorkbenchBody (cognitive 17) typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:213 — DashboardWorkbench.DashboardWorkbenchBody has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 7, if/else 3. Of this number, 9 points are the body's own statements and 8 belong to 4 function items 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 · EmbeddedView.EmbeddedData (cognitive 17) · ×1
  • EmbeddedView.EmbeddedData (cognitive 17) typescript/wow-view-engine/src/ui/EmbeddedView.tsx:168 — EmbeddedView.EmbeddedData has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 6, if/else 2 (nesting depth added 3). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent 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 · resolve.createResolver.resolveTokens (cognitive 17) · ×1
  • resolve.createResolver.resolveTokens (cognitive 17) typescript/wow-view-engine/theme-check/resolve.ts:622 — resolve.createResolver.resolveTokens has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (evaluate, token, evaluate::weighted). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · QueryValueLookupKt.lookup (cognitive 16) · ×1
  • QueryValueLookupKt.lookup (cognitive 16) query/query/src/main/kotlin/me/ahoo/wow/query/schema/QueryValueLookup.kt:33 — QueryValueLookupKt.lookup has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, match/switch 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 · Comparison.compareBound (cognitive 16) · ×1
  • Comparison.compareBound (cognitive 16) compiler/manifest-tools/src/main/kotlin/me/ahoo/wow/manifest/tools/SchemaCompatibility.kt:329 — Comparison.compareBound has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · generate.generateRetail.addCase (cognitive 16) · ×1
  • generate.generateRetail.addCase (cognitive 16) typescript/storybook/stories/view-engine/retail/generate.ts:1407 — generate.generateRetail.addCase has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · streams.resumableQueryRows · ×1
  • streams.resumableQueryRows::resume (cognitive 16) typescript/wow-client/src/streams.ts:216 — streams.resumableQueryRows::resume has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (streams.resumableQueryRows) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · analyze.aggregateModel.commands (cognitive 16) · ×1
  • analyze.aggregateModel.commands (cognitive 16) typescript/wow-generator/src/manifest/analyze.ts:928 — analyze.aggregateModel.commands has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9, if/else 3 (4 pts), boolean chains 3 (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 · text.withText (cognitive 16) · ×1
  • text.withText (cognitive 16) typescript/wow-view-engine/src/model/text.ts:126 — text.withText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 2 function items inside it that branch (walk, a function literal at line 139). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · validateReferences.referenceIssues (cognitive 16) · ×1
  • validateReferences.referenceIssues (cognitive 16) typescript/wow-view-engine/src/analysis/validateReferences.ts:37 — validateReferences.referenceIssues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 5 (nesting depth added 1). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 45, 80, 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 · validateShape.validateShape (cognitive 16) · ×1
  • validateShape.validateShape (cognitive 16) typescript/wow-view-engine/src/analysis/validateShape.ts:32 — validateShape.validateShape has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (nesting depth added 3). Of this number, 8 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · validate.validateBindings (cognitive 16) · ×1
  • validate.validateBindings (cognitive 16) typescript/wow-view-engine/src/dashboard/validate.ts:471 — validate.validateBindings has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, loops 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 484). 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 · fields.narrowSearch (cognitive 16) · ×1
  • fields.narrowSearch (cognitive 16) typescript/wow-view-engine/src/capabilities/fields.ts:540 — fields.narrowSearch has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 6 (7 pts), boolean chains 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: 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 · actions.nextChange (cognitive 16) · ×1
  • actions.nextChange (cognitive 16) typescript/wow-view-engine/src/runtime/actions.ts:486 — actions.nextChange has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (5 pts), ternaries 2 (4 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · issueReport.consoleIssueReporter · ×1
  • issueReport.consoleIssueReporter::flush (cognitive 16) typescript/wow-view-engine/src/runtime/failure/issueReport.ts:127 — issueReport.consoleIssueReporter::flush has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 3 (5 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pending.comparePending (cognitive 16) · ×1
  • pending.comparePending (cognitive 16) typescript/wow-view-engine/src/runtime/pending.ts:87 — pending.comparePending has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 1 (3 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 · wire-literals.admitted (cognitive 16) · ×1
  • wire-literals.admitted (cognitive 16) typescript/wow-view-engine/scripts/wire-literals.mjs:201 — wire-literals.admitted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · wire-literals.wireLiterals (cognitive 16) · ×1
  • wire-literals.wireLiterals (cognitive 16) typescript/wow-view-engine/scripts/wire-literals.mjs:332 — wire-literals.wireLiterals has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (visit, note, isWire). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · image.headElements (cognitive 16) · ×1
  • image.headElements (cognitive 16) typescript/wow-view-engine/src/ui/charts/image.ts:209 — image.headElements has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (5 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetailStructure.Tree (cognitive 16) · ×1
  • DetailStructure.Tree (cognitive 16) typescript/wow-view-engine/src/ui/record/DetailStructure.tsx:197 — DetailStructure.Tree has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RecordPagination.RecordPagination (cognitive 16) · ×1
  • RecordPagination.RecordPagination (cognitive 16) typescript/wow-view-engine/src/ui/record/RecordPagination.tsx:83 — RecordPagination.RecordPagination has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, ternaries 3, if/else 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FilterActions.FilterActions (cognitive 16) · ×1
  • FilterActions.FilterActions (cognitive 16) typescript/wow-view-engine/src/ui/filter/FilterActions.tsx:37 — FilterActions.FilterActions has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · EditBar.EditBar (cognitive 16) · ×1
  • EditBar.EditBar (cognitive 16) typescript/wow-view-engine/src/ui/dashboard/EditBar.tsx:82 — EditBar.EditBar has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 1. Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ReferenceOptions.ReferenceLines (cognitive 16) · ×1
  • ReferenceOptions.ReferenceLines (cognitive 16) typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:69 — ReferenceOptions.ReferenceLines has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 4, if/else 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 128, setLines, a function literal at line 90, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · EmbeddedAnalysis.EmbeddedAnalysis (cognitive 16) · ×1
  • EmbeddedAnalysis.EmbeddedAnalysis (cognitive 16) typescript/wow-view-engine/src/ui/embed/EmbeddedAnalysis.tsx:50 — EmbeddedAnalysis.EmbeddedAnalysis has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 5, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · EmbeddedRecord.EmbeddedRecord (cognitive 16) · ×1
  • EmbeddedRecord.EmbeddedRecord (cognitive 16) typescript/wow-view-engine/src/ui/embed/EmbeddedRecord.tsx:52 — EmbeddedRecord.EmbeddedRecord has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 3. 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt:104 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/command/MessageEntries.kt:104-118 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/source/TopicEntries.kt:100-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • Duplicated block (9–13 lines × 2) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:83 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:83-91 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt:303-315 — before extracting anything, compare `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt` and `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:83` 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 (5–8 lines × 3) · ×1
  • Duplicated block (5–8 lines × 3) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:67 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:67-71 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt:284-291 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryQueryBackend.kt:226-230 — before extracting anything, compare `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt` and `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:67` 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 (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/aggregate/AccessResolver.kt:259 — compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/aggregate/AccessResolver.kt:259-265 | compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SendsResolver.kt:179-185 | compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/subscription/SubscriptionResolver.kt:671-677 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `compiler/compiler/src/main/kotlin/me/ahoo/wow/compiler/model/aggregate/AccessResolver.kt:259` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:564 — backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:564-568 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:778-783 — 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 `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresEventLog.kt:778` 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 (3–16 lines × 3) · ×1
  • Duplicated block (3–16 lines × 3) backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/ElasticsearchNames.kt:61 — backends/elasticsearch/src/main/kotlin/me/ahoo/wow/elasticsearch/ElasticsearchNames.kt:61-63 | backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/MongoNames.kt:29-44 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/PostgresIdentifiers.kt:30-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt:586 — core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt:586-595 | core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt:805-814 — 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 `core/runtime/src/main/kotlin/me/ahoo/wow/runtime/wait/WaitCoordinator.kt:586` 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 (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:103 — backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:103-108 | backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt:327-332 | query/query/src/main/kotlin/me/ahoo/wow/query/memory/InMemoryQueryBackend.kt:260-265 — before extracting anything, compare `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt` and `backends/postgres/src/main/kotlin/me/ahoo/wow/postgres/query/PostgresQueryBackend.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/query/MongoProjections.kt:103` 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: @ahoo-wang/wow-client — @ahoo-wang/wow-client: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: DatasetWording (LCOM4 4) skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-domain/src/main/kotlin/me/ahoo/wow/viewstore/domain/wording/DatasetWording.kt:41 — DatasetWording'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.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to typescript/wow-generator/src/naming/paths.ts:25 — The guard above `return relative;` also returns `relative`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
R10 · Code Duplication · Forked directory tree (56 identical files, ~2585 lines × 2 trees) · ×1
  • Forked directory tree (56 identical files, ~2585 lines × 2 trees) typescript/wow-generator/expected/eshop-manifest/catalog/eshop-catalog/types.ts:1 — examples/eshop/web/src/generated/ and typescript/wow-generator/expected/eshop-manifest/ are near-verbatim copies of each other: 56 files are byte-identical under the same relative paths (~2585 lines; the trees hold 63 and 63 files). That is one structural fact, not 56 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (45 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (45 clone groups) platform/analytics/catalog/console/src/app/CallerForm.tsx:14 — 45 duplicated blocks under platform/ have copies in at least two of the sibling directories analytics, ops — 34 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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 11 sibling directories (32 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (32 clone groups) typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:412 — 32 duplicated blocks under typescript/wow-view-engine/src/ui/ have copies in at least two of the sibling directories analysis, charts, columns, dashboard, embed, filter (+5 more sibling(s) not listed) — 17 of them are reported below, and 15 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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 10 sibling directories (22 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (22 clone groups) typescript/wow-view-engine/src/analysis/validate.ts:40 — 22 duplicated blocks under typescript/wow-view-engine/src/ have copies in at least two of the sibling directories analysis, capabilities, dashboard, filter, model, react (+4 more sibling(s) not listed) — 13 of them are reported below, and 9 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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 (20 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (20 clone groups) typescript/wow-client/scripts/api-report.mjs:40 — 20 duplicated blocks under typescript/ have copies in at least two of the sibling directories storybook, wow-client, wow-generator, wow-react, wow-view-engine, wow-view-store — 12 of them are reported below, and 8 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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 · Wholesale file copy (145 identical lines × 2 files) · ×1
  • Wholesale file copy (145 identical lines × 2 files) platform/analytics/catalog/console/src/app/CallerForm.tsx:14 — platform/analytics/catalog/console/src/app/CallerForm.tsx:14 · platform/ops/console/src/app/CallerForm.tsx:14 — these 2 files are line-for-line copies of one another — 145 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (134 lines × 2 locations) · ×1
  • Duplicated block (134 lines × 2 locations) platform/analytics/catalog/console/src/services/caller.ts:74 — platform/analytics/catalog/console/src/services/caller.ts:74 · platform/ops/console/src/services/caller.ts:62 — 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 · Wholesale file copy (132 identical lines × 2 files) · ×1
  • Wholesale file copy (132 identical lines × 2 files) platform/analytics/catalog/console/src/components/ui/dropdown-menu.tsx:14 — platform/analytics/catalog/console/src/components/ui/dropdown-menu.tsx:14 · platform/ops/console/src/components/ui/dropdown-menu.tsx:14 — these 2 files are line-for-line copies of one another — 132 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (110 identical lines × 3 files) · ×1
  • Wholesale file copy (110 identical lines × 3 files) typescript/wow-client/scripts/api-report.mjs:40 — typescript/wow-client/scripts/api-report.mjs:40 · typescript/wow-react/scripts/api-report.mjs:40 · typescript/wow-view-store/scripts/api-report.mjs:40 — these 3 files are line-for-line copies of one another — 110 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (93 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (93 matched lines × 2 locations) typescript/wow-view-engine/src/ui/charts/funnelFit.ts:212 — typescript/wow-view-engine/src/ui/charts/funnelFit.ts:212 · typescript/wow-view-engine/src/ui/charts/funnelFit.ts:378 — the two spans are one implementation copied and then locally edited — 584 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (92 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (92 matched lines × 2 locations) typescript/wow-view-engine/src/analysis/boxplot.ts:84 — typescript/wow-view-engine/src/analysis/boxplot.ts:84 · typescript/wow-view-engine/src/analysis/candlestick.ts:72 — the two spans are one implementation copied and then locally edited — 561 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 (85 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (85 matched lines × 2 locations) typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:70 — typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:70 · typescript/wow-view-engine/src/ui/analysis/ReferenceOptions.tsx:264 — the two spans are one implementation copied and then locally edited — 474 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (80 identical lines × 2 files) · ×1
  • Wholesale file copy (80 identical lines × 2 files) platform/analytics/catalog/console/src/components/ui/field.tsx:8 — platform/analytics/catalog/console/src/components/ui/field.tsx:8 · platform/ops/console/src/components/ui/field.tsx:8 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (80 lines × 2 locations) · ×1
  • Duplicated block (80 lines × 2 locations) platform/analytics/catalog/console/src/i18n.tsx:276 — platform/analytics/catalog/console/src/i18n.tsx:276 · platform/ops/console/src/i18n.tsx:166 — 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 (66 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (66 matched lines × 2 locations) typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:114 — typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:114 · typescript/wow-view-engine/src/ui/DataWorkbench.tsx:107 — the two spans are one implementation copied and then locally edited — 365 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 (62 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (62 matched lines × 2 locations) typescript/wow-view-engine/src/ui/charts/PieSlices.tsx:66 — typescript/wow-view-engine/src/ui/charts/PieSlices.tsx:66 · typescript/wow-view-engine/src/ui/charts/ScatterPoints.tsx:40 — the two spans are one implementation copied and then locally edited — 295 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 (59 lines × 4 locations) · ×1
  • Duplicated block (59 lines × 4 locations) typescript/wow-client/scripts/api-report.mjs:102 — typescript/wow-client/scripts/api-report.mjs:102 · typescript/wow-react/scripts/api-report.mjs:90 · typescript/wow-view-engine/scripts/api-report.mjs:103 · typescript/wow-view-store/scripts/api-report.mjs:90 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Wholesale file copy (55 identical lines × 2 files) · ×1
  • Wholesale file copy (55 identical lines × 2 files) platform/analytics/catalog/console/src/setupTests.ts:14 — platform/analytics/catalog/console/src/setupTests.ts:14 · platform/ops/console/src/setupTests.ts:14 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (50 lines × 2 locations) · ×1
  • Duplicated block (50 lines × 2 locations) platform/analytics/catalog/console/src/components/ui/button.tsx:19 — platform/analytics/catalog/console/src/components/ui/button.tsx:19 · platform/ops/console/src/components/ui/button.tsx:19 — 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 (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) typescript/storybook/stories/view-engine/compensationEvents.ts:382 — typescript/storybook/stories/view-engine/compensationEvents.ts:382 · typescript/storybook/stories/view-engine/customerEvents.ts:466 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) platform/analytics/catalog/console/src/app/App.tsx:124 — platform/analytics/catalog/console/src/app/App.tsx:124 · platform/ops/console/src/app/App.tsx:105 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) typescript/wow-view-engine/src/filter/kinds/number.ts:73 — typescript/wow-view-engine/src/filter/kinds/number.ts:73 · typescript/wow-view-engine/src/filter/kinds/string.ts:69 — the two spans are one implementation copied and then locally edited — 369 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 (40 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (40 matched lines × 2 locations) typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:126 — typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:126 · typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx:281 — the two spans are one implementation copied and then locally edited — 202 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 (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) platform/analytics/catalog/console/src/views/datasets.ts:173 — platform/analytics/catalog/console/src/views/datasets.ts:173 · platform/analytics/catalog/console/src/views/sources.ts:196 — 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 (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) platform/analytics/catalog/console/src/app/App.tsx:43 — platform/analytics/catalog/console/src/app/App.tsx:43 · platform/ops/console/src/app/App.tsx:33 — 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 (35 lines × 3 locations) · ×1
  • Duplicated block (35 lines × 3 locations) typescript/storybook/stories/view-engine/compensationEvents.ts:340 — typescript/storybook/stories/view-engine/compensationEvents.ts:340 · typescript/storybook/stories/view-engine/customerEvents.ts:423 · typescript/storybook/stories/view-engine/tradeOrderEvents.ts:355 — 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 (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) platform/analytics/catalog/console/eslint.config.js:11 — platform/analytics/catalog/console/eslint.config.js:11 · platform/ops/console/eslint.config.js:11 — 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 (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) platform/analytics/catalog/console/src/services/cosec.ts:36 — platform/analytics/catalog/console/src/services/cosec.ts:36 · platform/ops/console/src/services/cosec.ts:36 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (26 matched lines × 2 locations) typescript/wow-view-engine/src/ui/charts/Boxplot.tsx:40 — typescript/wow-view-engine/src/ui/charts/Boxplot.tsx:40 · typescript/wow-view-engine/src/ui/charts/Candlestick.tsx:39 — the two spans are one implementation copied and then locally edited — 166 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 (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) typescript/wow-client/scripts/verify-package.mjs:122 — typescript/wow-client/scripts/verify-package.mjs:122 · typescript/wow-client/scripts/verify-package.mjs: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.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:58 — typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:58 · typescript/wow-view-engine/src/ui/filter/inputs/candidates.ts:92 — the two spans are one implementation copied and then locally edited — 141 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) typescript/wow-client/scripts/verify-package.mjs:85 — typescript/wow-client/scripts/verify-package.mjs:85 · typescript/wow-generator/scripts/verify-package.mjs:72 — 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.
R2 · Cyclomatic Complexity · Complex function project (cyclomatic 100, cognitive 137) · ×1
  • Complex function project (cyclomatic 100, cognitive 137) typescript/storybook/stories/view-engine/retail/generate.ts:1476 — project has cyclomatic complexity 100 and cognitive complexity 137; 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 WorkbenchShell (cyclomatic 62, cognitive 55) · ×1
  • Complex function WorkbenchShell (cyclomatic 62, cognitive 55) typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:344 — WorkbenchShell has cyclomatic complexity 62 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AnalysisParts (cyclomatic 50, cognitive 43) · ×1
  • Complex function AnalysisParts (cyclomatic 50, cognitive 43) typescript/wow-view-engine/src/ui/workbench/AnalysisParts.tsx:126 — AnalysisParts has cyclomatic complexity 50 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 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 generateRetail (cyclomatic 48, cognitive 128) · ×1
  • Complex function generateRetail (cyclomatic 48, cognitive 128) typescript/storybook/stories/view-engine/retail/generate.ts:766 — generateRetail has cyclomatic complexity 48 and cognitive complexity 128; 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 MetricCard (cyclomatic 48, cognitive 35) · ×1
  • Complex function MetricCard (cyclomatic 48, cognitive 35) typescript/wow-view-engine/src/ui/analysis/MetricCard.tsx:78 — MetricCard has cyclomatic complexity 48 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 ConditionPill (cyclomatic 46, cognitive 40) · ×1
  • Complex function ConditionPill (cyclomatic 46, cognitive 40) typescript/wow-view-engine/src/ui/filter/ConditionPill.tsx:80 — ConditionPill has cyclomatic complexity 46 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 44, cognitive 43) · ×1
  • Complex function (anonymous) (cyclomatic 44, cognitive 43) typescript/wow-view-engine/src/runtime/viewRuntime.ts:283 — (anonymous) has cyclomatic complexity 44 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 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 checkTheme (cyclomatic 43, cognitive 94) · ×1
  • Complex function checkTheme (cyclomatic 43, cognitive 94) typescript/wow-view-engine/theme-check/check.ts:132 — checkTheme has cyclomatic complexity 43 and cognitive complexity 94; 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 ActionDialog (cyclomatic 41, cognitive 37) · ×1
  • Complex function ActionDialog (cyclomatic 41, cognitive 37) typescript/wow-view-engine/src/ui/actions/ActionDialog.tsx:81 — ActionDialog has cyclomatic complexity 41 and cognitive complexity 37; 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 narrowAggregation (cyclomatic 40, cognitive 34) · ×1
  • Complex function narrowAggregation (cyclomatic 40, cognitive 34) typescript/wow-view-engine/src/capabilities/analysis.ts:263 — narrowAggregation has cyclomatic complexity 40 and cognitive complexity 34; 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 dataContext (cyclomatic 40, cognitive 30) · ×1
  • Complex function dataContext (cyclomatic 40, cognitive 30) typescript/wow-view-engine/test/prefixedClasses.test.ts:111 — dataContext has cyclomatic complexity 40 and cognitive complexity 30; 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 criteria (cyclomatic 39, cognitive 13) · ×1
  • Complex function criteria (cyclomatic 39, cognitive 13) typescript/wow-view-engine/src/testing/filter.ts:114 — criteria has cyclomatic complexity 39 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 buildField (cyclomatic 38, cognitive 44) · ×1
  • Complex function buildField (cyclomatic 38, cognitive 44) typescript/wow-view-engine/src/runtime/define/fields.ts:89 — buildField has cyclomatic complexity 38 and cognitive complexity 44; 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 useWorkbench (cyclomatic 37, cognitive 29) · ×1
  • Complex function useWorkbench (cyclomatic 37, cognitive 29) typescript/wow-view-engine/src/react/useWorkbench.ts:408 — useWorkbench has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function RecordTable (cyclomatic 35, cognitive 32) · ×1
  • Complex function RecordTable (cyclomatic 35, cognitive 32) typescript/wow-view-engine/src/ui/record/RecordTable.tsx:209 — RecordTable has cyclomatic complexity 35 and cognitive complexity 32; 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 metricOf (cyclomatic 34, cognitive 55) · ×1
  • Complex function metricOf (cyclomatic 34, cognitive 55) typescript/wow-view-engine/src/testing/aggregate.ts:290 — metricOf has cyclomatic complexity 34 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 34, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 38) typescript/wow-view-engine/theme-check/check.ts:222 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 38; 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 34, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 36) typescript/wow-view-engine/src/runtime/dashboardRuntime.ts:416 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 36; 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 serve (cyclomatic 33, cognitive 36) · ×1
  • Complex function serve (cyclomatic 33, cognitive 36) typescript/wow-view-store/test/support/fakeViewStore.ts:1234 — serve has cyclomatic complexity 33 and cognitive complexity 36; 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 ColumnRow (cyclomatic 33, cognitive 31) · ×1
  • Complex function ColumnRow (cyclomatic 33, cognitive 31) typescript/wow-view-engine/src/ui/columns/ColumnRow.tsx:151 — ColumnRow has cyclomatic complexity 33 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/generate.ts · ×1
  • typescript/storybook/stories/view-engine/retail/generate.ts: 2103 lines of code typescript/storybook/stories/view-engine/retail/generate.ts:1 — typescript/storybook/stories/view-engine/retail/generate.ts has 2103 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/views.ts · ×1
  • typescript/storybook/stories/view-engine/retail/views.ts: 1831 lines of code typescript/storybook/stories/view-engine/retail/views.ts:1 — typescript/storybook/stories/view-engine/retail/views.ts has 1831 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-client/src/dsl/filter/builders.ts · ×1
  • typescript/wow-client/src/dsl/filter/builders.ts: 1438 lines of code typescript/wow-client/src/dsl/filter/builders.ts:1 — typescript/wow-client/src/dsl/filter/builders.ts has 1438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/fixtures.ts · ×1
  • typescript/storybook/stories/view-engine/fixtures.ts: 1312 lines of code typescript/storybook/stories/view-engine/fixtures.ts:1 — typescript/storybook/stories/view-engine/fixtures.ts has 1312 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/boards.ts · ×1
  • typescript/storybook/stories/view-engine/retail/boards.ts: 1236 lines of code typescript/storybook/stories/view-engine/retail/boards.ts:1 — typescript/storybook/stories/view-engine/retail/boards.ts has 1236 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx · ×1
  • typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx: 1214 lines of code typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx:1 — typescript/storybook/stories/view-engine/RecordWorkbench.stories.tsx has 1214 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/definitions.ts · ×1
  • typescript/storybook/stories/view-engine/retail/definitions.ts: 1059 lines of code typescript/storybook/stories/view-engine/retail/definitions.ts:1 — typescript/storybook/stories/view-engine/retail/definitions.ts has 1059 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/catalog.ts · ×1
  • typescript/storybook/stories/view-engine/retail/catalog.ts: 1021 lines of code typescript/storybook/stories/view-engine/retail/catalog.ts:1 — typescript/storybook/stories/view-engine/retail/catalog.ts has 1021 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/kit/variants.tsx · ×1
  • typescript/wow-view-engine/src/ui/kit/variants.tsx: 1001 lines of code typescript/wow-view-engine/src/ui/kit/variants.tsx:1 — typescript/wow-view-engine/src/ui/kit/variants.tsx has 1001 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-generator/src/manifest/analyze.ts · ×1
  • typescript/wow-generator/src/manifest/analyze.ts: 994 lines of code typescript/wow-generator/src/manifest/analyze.ts:1 — typescript/wow-generator/src/manifest/analyze.ts has 994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/Dashboard.stories.tsx · ×1
  • typescript/storybook/stories/view-engine/Dashboard.stories.tsx: 987 lines of code typescript/storybook/stories/view-engine/Dashboard.stories.tsx:1 — typescript/storybook/stories/view-engine/Dashboard.stories.tsx has 987 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx · ×1
  • typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx: 876 lines of code typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx:1 — typescript/storybook/stories/view-engine/AnalysisWorkbench.stories.tsx has 876 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/analysis/project.ts · ×1
  • typescript/wow-view-engine/src/analysis/project.ts: 841 lines of code typescript/wow-view-engine/src/analysis/project.ts:1 — typescript/wow-view-engine/src/analysis/project.ts has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx · ×1
  • typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx: 841 lines of code typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx:1 — typescript/wow-view-engine/src/ui/workbench/WorkbenchShell.tsx has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/react/useWorkbench.ts · ×1
  • typescript/wow-view-engine/src/react/useWorkbench.ts: 829 lines of code typescript/wow-view-engine/src/react/useWorkbench.ts:1 — typescript/wow-view-engine/src/react/useWorkbench.ts has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/kit/display.ts · ×1
  • typescript/wow-view-engine/src/ui/kit/display.ts: 809 lines of code typescript/wow-view-engine/src/ui/kit/display.ts:1 — typescript/wow-view-engine/src/ui/kit/display.ts has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-generator/src/types/typeResolver.ts · ×1
  • typescript/wow-generator/src/types/typeResolver.ts: 803 lines of code typescript/wow-generator/src/types/typeResolver.ts:1 — typescript/wow-generator/src/types/typeResolver.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/record/project.ts · ×1
  • typescript/wow-view-engine/src/record/project.ts: 796 lines of code typescript/wow-view-engine/src/record/project.ts:1 — typescript/wow-view-engine/src/record/project.ts has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-generator/src/emitters/manifestClients.ts · ×1
  • typescript/wow-generator/src/emitters/manifestClients.ts: 795 lines of code typescript/wow-generator/src/emitters/manifestClients.ts:1 — typescript/wow-generator/src/emitters/manifestClients.ts has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/react/useFilterEditor.ts · ×1
  • typescript/wow-view-engine/src/react/useFilterEditor.ts: 782 lines of code typescript/wow-view-engine/src/react/useFilterEditor.ts:1 — typescript/wow-view-engine/src/react/useFilterEditor.ts has 782 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/customer.ts · ×1
  • typescript/storybook/stories/view-engine/customer.ts: 779 lines of code typescript/storybook/stories/view-engine/customer.ts:1 — typescript/storybook/stories/view-engine/customer.ts has 779 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/runtime/viewEngine.ts · ×1
  • typescript/wow-view-engine/src/runtime/viewEngine.ts: 779 lines of code typescript/wow-view-engine/src/runtime/viewEngine.ts:1 — typescript/wow-view-engine/src/runtime/viewEngine.ts has 779 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/kit/popups.tsx · ×1
  • typescript/wow-view-engine/src/ui/kit/popups.tsx: 766 lines of code typescript/wow-view-engine/src/ui/kit/popups.tsx:1 — typescript/wow-view-engine/src/ui/kit/popups.tsx has 766 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-client/src/dsl/aggregation/types.ts · ×1
  • typescript/wow-client/src/dsl/aggregation/types.ts: 762 lines of code typescript/wow-client/src/dsl/aggregation/types.ts:1 — typescript/wow-client/src/dsl/aggregation/types.ts has 762 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/retail/showcase.ts · ×1
  • typescript/storybook/stories/view-engine/retail/showcase.ts: 760 lines of code typescript/storybook/stories/view-engine/retail/showcase.ts:1 — typescript/storybook/stories/view-engine/retail/showcase.ts has 760 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/tradeOrder.ts · ×1
  • typescript/storybook/stories/view-engine/tradeOrder.ts: 748 lines of code typescript/storybook/stories/view-engine/tradeOrder.ts:1 — typescript/storybook/stories/view-engine/tradeOrder.ts has 748 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/dashboard/layout.ts · ×1
  • typescript/wow-view-engine/src/dashboard/layout.ts: 736 lines of code typescript/wow-view-engine/src/dashboard/layout.ts:1 — typescript/wow-view-engine/src/dashboard/layout.ts has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-store/src/wowViewStore.ts · ×1
  • typescript/wow-view-store/src/wowViewStore.ts: 731 lines of code typescript/wow-view-store/src/wowViewStore.ts:1 — typescript/wow-view-store/src/wowViewStore.ts has 731 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/react/useRecordTable.ts · ×1
  • typescript/wow-view-engine/src/react/useRecordTable.ts: 727 lines of code typescript/wow-view-engine/src/react/useRecordTable.ts:1 — typescript/wow-view-engine/src/react/useRecordTable.ts has 727 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/theme-check/resolve.ts · ×1
  • typescript/wow-view-engine/theme-check/resolve.ts: 715 lines of code typescript/wow-view-engine/theme-check/resolve.ts:1 — typescript/wow-view-engine/theme-check/resolve.ts has 715 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/runtime/dashboardRuntime.ts · ×1
  • typescript/wow-view-engine/src/runtime/dashboardRuntime.ts: 709 lines of code typescript/wow-view-engine/src/runtime/dashboardRuntime.ts:1 — typescript/wow-view-engine/src/runtime/dashboardRuntime.ts has 709 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/charts/EChart.tsx · ×1
  • typescript/wow-view-engine/src/ui/charts/EChart.tsx: 708 lines of code typescript/wow-view-engine/src/ui/charts/EChart.tsx:1 — typescript/wow-view-engine/src/ui/charts/EChart.tsx has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts · ×1
  • typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts: 708 lines of code typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts:1 — typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/model/field.ts · ×1
  • typescript/wow-view-engine/src/model/field.ts: 704 lines of code typescript/wow-view-engine/src/model/field.ts:1 — typescript/wow-view-engine/src/model/field.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-client/src/dsl/aggregation/builders.ts · ×1
  • typescript/wow-client/src/dsl/aggregation/builders.ts: 698 lines of code typescript/wow-client/src/dsl/aggregation/builders.ts:1 — typescript/wow-client/src/dsl/aggregation/builders.ts has 698 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/react/useAnalysisResult.ts · ×1
  • typescript/wow-view-engine/src/react/useAnalysisResult.ts: 694 lines of code typescript/wow-view-engine/src/react/useAnalysisResult.ts:1 — typescript/wow-view-engine/src/react/useAnalysisResult.ts has 694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx · ×1
  • typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx: 675 lines of code typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx:1 — typescript/storybook/stories/view-engine/EmbeddedView.stories.tsx has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/runtime/viewRuntime.ts · ×1
  • typescript/wow-view-engine/src/runtime/viewRuntime.ts: 674 lines of code typescript/wow-view-engine/src/runtime/viewRuntime.ts:1 — typescript/wow-view-engine/src/runtime/viewRuntime.ts has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx · ×1
  • typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx: 669 lines of code typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx:1 — typescript/wow-view-engine/src/ui/dashboard/DashboardGrid.tsx has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · platform/ops/console/src/views/parked.ts · ×1
  • platform/ops/console/src/views/parked.ts: 662 lines of code platform/ops/console/src/views/parked.ts:1 — platform/ops/console/src/views/parked.ts has 662 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded typescript/storybook/scripts/verify-storybook.mjs:20 — This repository declares test tooling, and the ✓ above records that declaration — but typescript/storybook/scripts/verify-storybook.mjs and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~214 LoC) · ×1
  • Dead file (~214 LoC) typescript/storybook/scripts/verify-storybook-browser.mjs — no import path from any entry point (117 application, 47 tooling, 755 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 (~191 LoC) · ×1
  • Dead file (~191 LoC) typescript/storybook/stories/view-engine/IntroBlocks.tsx — no import path from any entry point (117 application, 47 tooling, 755 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 (~67 LoC) · ×1
  • Dead file (~67 LoC) typescript/storybook/stories/view-engine/integration/wowCommands.ts — no import path from any entry point (117 application, 47 tooling, 755 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 (~27 LoC) · ×1
  • Dead file (~27 LoC) typescript/storybook/stories/view-engine/integration/wowSource.ts — no import path from any entry point (117 application, 47 tooling, 755 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
X29 · Per-element action decided by a fixed element · Per-element action decided by a fixed element · ×1
  • Per-element action decided by a fixed element typescript/wow-view-engine/src/analysis/funnel.ts:149 — This loop runs once per element of `stages`, and the statement it guards acts on the element it is on — `stage`. The test deciding whether that statement runs does not: `first === 0` reads `stages[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 147, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Minor — 104 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate typescript/wow-client/scripts/api-report.mjs:221 — `!existsSync(committed) || readFileSync(committed, 'utf8') !== rendered` appears character-identically in 4 files — typescript/wow-client/scripts/api-report.mjs, typescript/wow-react/scripts/api-report.mjs, typescript/wow-view-engine/scripts/api-report.mjs, typescript/wow-view-store/scripts/api-report.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/analysis/dangling.ts:125 — `!isValueMetric(metric) && !moments.has(metric.alias)` appears character-identically in 2 files — typescript/wow-view-engine/src/analysis/dangling.ts, typescript/wow-view-engine/src/react/analysisEditing.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/record/RecordCards.tsx:108 — `!table.hasResult && table.status !== 'loading'` appears character-identically in 3 files — typescript/wow-view-engine/src/ui/record/RecordCards.tsx, typescript/wow-view-engine/src/ui/record/RecordKanban.tsx, typescript/wow-view-engine/src/ui/record/RecordTable.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/analysis/ResultSlot.tsx:253 — `Number.isInteger(value) && value >= 1 && value <= max` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/analysis/ResultSlot.tsx, typescript/wow-view-engine/src/ui/analysis/TopRow.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/dashboard/Board.tsx:142 — `active === null || active === document.body` appears character-identically in 3 files — typescript/wow-view-engine/src/ui/dashboard/Board.tsx, typescript/wow-view-engine/src/ui/dashboard/DashboardArrange.tsx, typescript/wow-view-engine/src/ui/dashboard/buildShell.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/filter/conditionFocus.ts:72 — `active === null || active === document.body || !active.isConnected || (active as HTMLButtonElement).disabled === true` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/filter/conditionFocus.ts, typescript/wow-view-engine/src/ui/kit/focus.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx:387 — `analysis.layout === 'chart' && chartData` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/dashboard/PanelBodies.tsx, typescript/wow-view-engine/src/ui/embed/EmbeddedAnalysis.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate platform/analytics/catalog/console/src/services/caller.ts:164 — `caller.expiresAt !== undefined && caller.expiresAt <= Date.now()` appears character-identically in 2 files — platform/analytics/catalog/console/src/services/caller.ts, platform/ops/console/src/services/caller.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/record/RecordTable.tsx:491 — `column.width !== undefined && CLIPPED_CELL` appears character-identically in 3 files — typescript/wow-view-engine/src/ui/record/RecordTable.tsx, typescript/wow-view-engine/src/ui/record/SkeletonRows.tsx, typescript/wow-view-engine/src/ui/record/SummaryRows.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx:399 — `dashboard.resolving || dashboard.status === 'loading'` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/DashboardWorkbench.tsx, typescript/wow-view-engine/src/ui/EmbeddedDashboard.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:129 — `details.reason === 'input-clear' && !details.isItemPress` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx, typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx:104 — `draft !== null && Object.is(value, draft.over)` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/filter/inputs/chips.tsx, typescript/wow-view-engine/src/ui/filter/inputs/suggested.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/capabilities/match.ts:87 — `entry.path === path && entry.scope === scope` appears character-identically in 2 files — typescript/wow-view-engine/src/capabilities/match.ts, typescript/wow-view-engine/src/runtime/define/fields.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:449 — `event.altKey || event.ctrlKey || event.metaKey || event.shiftKey` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx, typescript/wow-view-engine/src/ui/kit/roving.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx:431 — `event.key === 'Enter' || event.key === ' '` appears character-identically in 2 files — typescript/wow-view-engine/src/ui/analysis/AnalysisTable.tsx, typescript/wow-view-engine/src/ui/record/openRows.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/capabilities/analysis.ts:419 — `field.functions.length > 0 || field.any === true || field.distinctCount === true || field.percentile === true || field.firstLast === true` appears character-identically in 2 files — typescript/wow-view-engine/src/capabilities/analysis.ts, typescript/wow-view-engine/src/runtime/validateDefinition.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/record/project.ts:351 — `field.sortable === true && readsAsNames(field)` appears character-identically in 2 files — typescript/wow-view-engine/src/record/project.ts, typescript/wow-view-engine/src/ui/sort/SortSettings.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/analysis/chartSlots.ts:111 — `group.type === AggregationGroupTypes.DATE_HISTOGRAM && group.unit === AggregationDateUnits.DAY` appears character-identically in 2 files — typescript/wow-view-engine/src/analysis/chartSlots.ts, typescript/wow-view-engine/src/ui/analysis/ChartOptions.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/analysis/validateGroups.ts:168 — `group.type === AggregationGroupTypes.DATE_HISTOGRAM || group.type === AggregationGroupTypes.DATE_PART` appears character-identically in 2 files — typescript/wow-view-engine/src/analysis/validateGroups.ts, typescript/wow-view-engine/src/ui/analysis/DimensionCard.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/dashboard/edit.ts:250 — `isPlainObject(entry) && entry.derived === true` appears character-identically in 2 files — typescript/wow-view-engine/src/dashboard/edit.ts, typescript/wow-view-engine/src/dashboard/timeBindings.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/react/recordDraft.ts:52 — `isPlainObject(entry) && typeof entry.field === 'string'` appears character-identically in 2 files — typescript/wow-view-engine/src/react/recordDraft.ts, typescript/wow-view-engine/src/record/validate.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/dashboard/panels.ts:224 — `isPlainObject(tab) && typeof tab.id === 'string'` appears character-identically in 2 files — typescript/wow-view-engine/src/dashboard/panels.ts, typescript/wow-view-engine/src/dashboard/validate.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/filter/kinds/metadata.ts:102 — `isReferenceFilterValue(value) && value.items.length === 0` appears character-identically in 2 files — typescript/wow-view-engine/src/filter/kinds/metadata.ts, typescript/wow-view-engine/src/filter/kinds/reference.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-view-engine/src/dashboard/filters.ts:278 — `isViewPanel(entry) && entry.id === panelId` appears character-identically in 2 files — typescript/wow-view-engine/src/dashboard/filters.ts, typescript/wow-view-engine/src/runtime/dashboard/panelRun.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate typescript/wow-client/scripts/api-report.mjs:178 — `message.logLevel === 'error' || message.logLevel === 'warning'` appears character-identically in 4 files — typescript/wow-client/scripts/api-report.mjs, typescript/wow-react/scripts/api-report.mjs, typescript/wow-view-engine/scripts/api-report.mjs, typescript/wow-view-store/scripts/api-report.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D31 · IaC & Container Security · Low IaC · ×22
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D24 · Comment Value · redundant comment · ×12
  • redundant comment platform/analytics/catalog/console/src/setupTests.ts:50 — "Mock window.matchMedia" repeats the code it sits on: 4 of its 4 words (mock, window, match, media) are already in `Object.defineProperty(window, "matchMedia", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment platform/ops/console/src/setupTests.ts:50 — "Mock window.matchMedia" repeats the code it sits on: 4 of its 4 words (mock, window, match, media) are already in `Object.defineProperty(window, "matchMedia", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/storybook/stories/view-engine/retail/guide.ts:336 — "The first week after the peak back under the red line." repeats the code it sits on: 5 of its 6 words (week, peak, back, red, line) are already in `const back = rows.find(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-generator/src/analysis/modelInfo.ts:58 — "Construct the path from parts before the model name" repeats the code it sits on: 4 of its 5 words (path, parts, model, name) are already in `const pathParts = parts.slice(0, modelNameIndex);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-generator/test/cli/program.test.ts:34 — "Mock generateAction" repeats the code it sits on: 3 of its 3 words (mock, generate, action) are already in `vi.mock('../../src/cli/runGenerate', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-generator/test/input/resources.test.ts:22 — "Mock fs.readFile" repeats the code it sits on: 4 of its 4 words (mock, fs, read, file) are already in `vi.mock('fs', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/scripts/verify-package.mjs:605 — "The reset empties exactly the preset layer." repeats the code it sits on: 4 of its 5 words (reset, exactly, preset, layer) are already in `assert.deepEqual(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/src/ui/analysis/AnalysisChart.tsx:201 — "A derived line is switched on its own key, as a series is." repeats the code it sits on: 4 of its 5 words (derived, switched, key, series) are already in `const kept = [...data.series, ...(data.derived ?? [])].filter(entry =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/src/ui/colorMode.tsx:124 — "The mode the host starts from, where the engine paints at all." repeats the code it sits on: 4 of its 5 words (mode, host, starts, paints) are already in `const starting: ColorMode | null =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/test/cartesianOption.test.ts:629 — "In a stacked combo the bars stack and the line stands on its own." repeats the code it sits on: 5 of its 6 words (stacked, combo, bars, stack, line) are already in `const combo = as('combo', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/test/storeLimits.test.ts:33 — "The view store service's ViewConfigs.kt." repeats the code it sits on: 4 of its 5 words (view, store, configs, kt) are already in `const VIEW_CONFIGS = resolve(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment typescript/wow-view-engine/test/themeRoles.test.ts:204 — "A preset that sets the role, or links it to another token." repeats the code it sits on: 4 of its 5 words (preset, sets, role, links) are already in `const own = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D10 · Test Quality · Mock-dominated test · ×10
  • Mock-dominated test: hands the drag handlers the library gives it to its button typescript/wow-view-engine/test/dashboardUi.test.tsx:1117 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: hands the library the button itself typescript/wow-view-engine/test/dragHandle.test.tsx:127 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: writes to the console in development when the host gives no onIssue, and not otherwise typescript/wow-view-engine/test/engineResources.test.ts:320 — This test sets up 3 test doubles (for example `vi .spyOn`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: keeps a trimmed name on Enter, and the key stops at the field typescript/wow-view-engine/test/renameInput.test.tsx:80 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: puts the name back on Escape, which goes no further typescript/wow-view-engine/test/renameInput.test.tsx:92 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: prints the outcome, warnings and errors by default, without the details typescript/wow-generator/test/api/logger.test.ts:41 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: prints only warnings and errors when quiet typescript/wow-generator/test/api/logger.test.ts:49 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: prints every detail with a timestamp when verbose typescript/wow-generator/test/api/logger.test.ts:57 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: decorates lines with symbols on a terminal typescript/wow-generator/test/api/logger.test.ts:73 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: prints nothing typescript/wow-generator/test/api/logger.test.ts:101 — This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
AX6 · Interface segregation · Fat interface · ×7
  • Fat interface: DashboardEditing (19 required operations) typescript/wow-view-engine/src/runtime/dashboard/editing.ts:94 — `DashboardEditing` declares 19 required operations: `addPanel`, `removePanel`, `duplicatePanel`, `renamePanel`, `replacePanelView`, `editPanelContent`, `movePanelToTab`, `setPresentation`, `referToSaved`, `setPanelClick`, `addTab`, `renameTab`, `moveTab`, `removeTab`, `place`, `reorderPanel`, `setWidth`, `undo`, `redo`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DashboardRuntime (21 required operations) typescript/wow-view-engine/src/runtime/dashboard/contract.ts:115 — `DashboardRuntime` declares 21 required operations: `getSnapshot`, `ready`, `panelRuntime`, `refreshPanel`, `setBuilding`, `setRefreshInterval`, `preload`, `showTab`, `setFilterValue`, `setGroupingUnit`, `clearFilters`, `holdFilters`, `setFilters`, `wiredOptions`, `crossFilter`, `pressed`, `spanFilters`, `pressSpan`, `destination`, `destinationBoard`, `handOver`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: QuestionEditing (22 required operations) typescript/wow-view-engine/src/react/analysisEditing.ts:74 — `QuestionEditing` declares 22 required operations: `addGroup`, `updateGroup`, `removeGroup`, `renameGroup`, `setMissingBucket`, `setDense`, `addMetric`, `updateMetric`, `replaceMetric`, `renameMetric`, `setMetricFilter`, `duplicateMetric`, `addFiveNumbers`, `addOhlc`, `moveMetric`, `removeMetric`, `addFormula`, `addDuration`, `groupByDuration`, `addDerived`, `setHaving`, `setTop`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AnalysisEditorController (19 required operations) typescript/wow-view-engine/src/react/useAnalysisEditor.ts:82 — `AnalysisEditorController` declares 19 required operations: `undoDrop`, `dismissDrop`, `metricRemoval`, `elementLabel`, `elementFields`, `expand`, `collapse`, `setElementFilter`, `dateUnitFor`, `setSort`, `sortNow`, `setLimit`, `setLayout`, `setChartType`, `updateChart`, `setTotals`, `submit`, `focus`, `blur`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DashboardController (20 required operations) typescript/wow-view-engine/src/react/useDashboard.ts:84 — `DashboardController` declares 20 required operations: `showTab`, `place`, `refresh`, `refreshPanel`, `setBuilding`, `setFilterValue`, `setGroupingUnit`, `clearFilters`, `setAwaiting`, `filterCandidates`, `filterChoices`, `filterOptions`, `preload`, `crossFilter`, `pressed`, `spanFilters`, `pressSpan`, `destination`, `destinationBoard`, `handOver`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: RecordTableController (23 required operations) typescript/wow-view-engine/src/react/useRecordTable.ts:83 — `RecordTableController` declares 23 required operations: `setCard`, `sortOf`, `toggleSort`, `setSort`, `setLayout`, `hiddenOf`, `setColumns`, `setColumnOrder`, `pinnedOf`, `setPinned`, `setColumnWidth`, `summaryOf`, `setSummary`, `setPageSize`, `isSelected`, `toggle`, `toggleAll`, `clearSelection`, `select`, `goTo`, `next`, `previous`, `refresh`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: CartesianPlan (18 required operations) typescript/wow-view-engine/src/ui/charts/cartesianPlan.ts:244 — `CartesianPlan` declares 18 required operations: `tickOf`, `stackOf`, `stacked`, `asShares`, `shareAt`, `drawnAt`, `drawnText`, `labelled`, `peaksOnly`, `filledAt`, `insideText`, `span`, `reach`, `wholeOn`, `sharesOn`, `logOn`, `valuesOn`, `extremesOf`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D41 · Kernel & Syscall Confinement · No seccomp profile · ×4
  • No seccomp profile REDACTED:6 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:7 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:4 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:6 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
IC1 · Incompleteness & stubs · Empty method body · ×3
  • Empty method body typescript/wow-view-engine/src/ui/analysis/virtualRows.ts:258 — `noMeasure` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body typescript/wow-view-engine/src/ui/colorMode.tsx:51 — `setMode` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body typescript/wow-view-engine/src/ui/filter/conditionFocus.ts:87 — `removing` has an empty body — confirm it's an intentional no-op and not an unfinished method.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch typescript/wow-view-engine/examples/FetcherViewStore.ts:393 — `heldBy` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch typescript/wow-view-engine/src/ui/filter/inputs/unsupported.tsx:94 — `rawValueText` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch typescript/wow-view-engine/src/ui/workbench/address.ts:79 — `boardsOf` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
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 — 11 of 60 project(s) overshoot their size bounds, lowering Project Cohesion to 6.6/10. The most over is `typescript/wow-view-engine` (165293 LoC, 1464 module-visible types across 37 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
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
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 23/27 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `migration/migrate-data`, `platform/ops/ops-server`, `skills/wow-migrate/evals/h5-inputs/view-store/wow-view-store-server`, `typescript/wow-view-engine`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:27 — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 19 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused export 'ManifestEvent' · ×1
  • Unused export 'ManifestEvent' typescript/wow-generator/src/manifest/document.ts:42 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ManifestError' · ×1
  • Unused export 'ManifestError' typescript/wow-generator/src/manifest/document.ts:45 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'MANIFEST_FORMAT' · ×1
  • Unused export 'MANIFEST_FORMAT' typescript/wow-generator/src/manifest/document.ts:51 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'RunningFunctions' · ×1
  • Unused export 'RunningFunctions' typescript/wow-view-engine/src/model/wire.ts:93 — Nothing ultimately consumes this binding: its only referrer is the re-export in typescript/wow-view-engine/src/model/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in typescript/wow-view-engine/src/model/index.ts in the same commit, or the barrel will import a name that no longer exists.
R8 · Dependency Hygiene · Type-only dependency 'react-day-picker' in production deps · ×1
  • Type-only dependency 'react-day-picker' in production deps typescript/wow-view-engine/src/ui/filter/inputs/daterange.tsx:17 — Every import is type-only — move it to devDependencies.
X2 · Cancellation propagation · Not all functions that make a request accept an AbortSignal or the coroutine's cancellation · ×1
  • Not all functions that make a request accept an AbortSignal or the coroutine's cancellation — Only 6/9 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1
  • Diagnostic log message is built whether or not it is wanted backends/mongo/src/main/kotlin/me/ahoo/wow/mongo/MongoSharding.kt:172 — `debug` at line 172 is called with an argument built by `command.toJson()` (line 172), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.5 `!` null assertions per 1k TypeScript source lines — 114 assertion(s) across the 230885 source line(s) of the 999 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: typescript/wow-view-engine/src/dashboard/layout.ts (10), typescript/wow-generator/src/analysis/apiClients.ts (9), typescript/storybook/stories/view-engine/themeContrast.tsx (7). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 160 finding(s)
D12 · Dependency Hygiene · Outdated (compile) · ×140
  • Outdated (compile): org.jetbrains:annotations — org.jetbrains:annotations 13.0 → 26.1.0 available.
  • Outdated (compile): org.jcommander:jcommander — org.jcommander:jcommander 1.85 → 3.0 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common — org.jetbrains.kotlin:kotlin-stdlib-common 2.0.21 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8 — org.jetbrains.kotlin:kotlin-stdlib-jdk8 1.8.0 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7 — org.jetbrains.kotlin:kotlin-stdlib-jdk7 1.8.0 → 2.4.21 available.
  • Outdated (compile): dev.drewhamilton.poko:poko-annotations — dev.drewhamilton.poko:poko-annotations 0.17.1 → 0.23.2 available.
  • Outdated (compile): dev.drewhamilton.poko:poko-annotations-jvm — dev.drewhamilton.poko:poko-annotations-jvm 0.17.1 → 0.23.2 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-compiler-embeddable — org.jetbrains.kotlin:kotlin-compiler-embeddable 2.0.21 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-script-runtime — org.jetbrains.kotlin:kotlin-script-runtime 2.0.21 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-reflect — org.jetbrains.kotlin:kotlin-reflect 2.0.21 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlin:kotlin-daemon-embeddable — org.jetbrains.kotlin:kotlin-daemon-embeddable 2.0.21 → 2.4.21 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm — org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm 1.6.4 → 1.11.0 available.
  • Outdated (compile): org.snakeyaml:snakeyaml-engine — org.snakeyaml:snakeyaml-engine 2.7 → 3.2 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-html-jvm — org.jetbrains.kotlinx:kotlinx-html-jvm 0.8.1 → 0.12.0 available.
  • Outdated (compile): io.github.detekt.sarif4k:sarif4k — io.github.detekt.sarif4k:sarif4k 0.6.0 → 0.8.0 available.
  • Outdated (compile): io.github.detekt.sarif4k:sarif4k-jvm — io.github.detekt.sarif4k:sarif4k-jvm 0.6.0 → 0.8.0 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-json — org.jetbrains.kotlinx:kotlinx-serialization-json 1.4.1 → 1.12.0 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-json-jvm — org.jetbrains.kotlinx:kotlinx-serialization-json-jvm 1.4.1 → 1.12.0 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core — org.jetbrains.kotlinx:kotlinx-serialization-core 1.4.1 → 1.12.0 available.
  • Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core-jvm — org.jetbrains.kotlinx:kotlinx-serialization-core-jvm 1.4.1 → 1.12.0 available.
  • Outdated (compile): com.pinterest.ktlint:ktlint-ruleset-standard — com.pinterest.ktlint:ktlint-ruleset-standard 0.50.0 → 1.8.0 available.
  • Outdated (compile): com.pinterest.ktlint:ktlint-logger — com.pinterest.ktlint:ktlint-logger 0.50.0 → 1.8.0 available.
  • Outdated (compile): com.pinterest.ktlint:ktlint-cli-ruleset-core — com.pinterest.ktlint:ktlint-cli-ruleset-core 0.50.0 → 1.8.0 available.
  • Outdated (compile): com.pinterest.ktlint:ktlint-rule-engine-core — com.pinterest.ktlint:ktlint-rule-engine-core 0.50.0 → 1.8.0 available.
  • Outdated (compile): org.ec4j.core:ec4j-core — org.ec4j.core:ec4j-core 0.3.0 → 1.2.0 available.
  • + 115 more in this group — see findings.md.
D10 · Test Quality · Skipped (documented) · ×15
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:375 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:396 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:426 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:449 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:480 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:491 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:664 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:699 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:754 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:919 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:948 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:980 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:1035 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:1067 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) typescript/wow-view-engine/test/conformance/viewStoreConformance.ts:1097 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
D24 · Comment Value · doc comments repeat the names · ×5
  • doc comments repeat the names typescript/wow-client/src/developmentCaller.ts:55 — 2 of 142 documented parameters and 29 of 1010 summaries in `@ahoo-wang/wow-client` only repeat the member or parameter name (e.g. "Its roles." for `roles`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names typescript/wow-generator/src/emit/imports.ts:63 — 7 of 196 documented parameters and 3 of 534 summaries in `@ahoo-wang/wow-generator` only repeat the member or parameter name (e.g. "The model" for `model`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names typescript/wow-react/src/types.ts:159 — 0 of 0 documented parameters and 1 of 144 summaries in `@ahoo-wang/wow-react` only repeat the member or parameter name (e.g. "The current query." for `getQuery`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names typescript/wow-view-engine/src/analysis/chartFamilies.ts:72 — 0 of 8 documented parameters and 4 of 8256 summaries in `@ahoo-wang/wow-view-engine` only repeat the member or parameter name (e.g. "How many metrics." for `metrics`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names typescript/storybook/stories/view-engine/retail/guide.ts:99 — 0 of 0 documented parameters and 1 of 439 summaries in `wow-storybook` only repeat the member or parameter name (e.g. "A board's own title." for `boardTitle`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5ab591e43d884d85b4aeb47893602f27/history.json --exit-code 0 --source .194artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5ab591e43d884d85b4aeb47893602f27/tree.json --exit-code 0 --source .34artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude examples/eshop/web/src/generated/basket/eshop-basket --exclude examples/eshop/web/src/generated/catalog/eshop-catalog --exclude examples/eshop/web/src/generated/inventory/eshop-inventory --exclude examples/eshop/web/src/generated/ordering/eshop-ordering --exclude examples/eshop/web/src/generated/payment/eshop-payment --exclude platform/analytics/catalog/console/src/generated/analytics-catalog --exclude platform/ops/console/src/generated/ops --exclude typescript/wow-client/test/api --exclude typescript/wow-client/test/golden --exclude typescript/wow-generator/expected/eshop-manifest --exclude typescript/wow-generator/expected/openai-spec --exclude typescript/wow-react/test/api --exclude typescript/wow-view-engine/src/ui/components --exclude typescript/wow-view-engine/src/ui/lib --exclude typescript/wow-view-engine/test/api --exclude typescript/wow-view-store/src/generated --exclude typescript/wow-view-store/test/api .94artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .5artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .43artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 242 file(s) — `.github/scripts/breaking-label.mjs`, `.github/scripts/release-admission.mjs`, `api/api/src/main/kotlin/me/ahoo/wow/api/wire/WaitHeader.kt`, `api/manifest/src/main/kotlin/me/ahoo/wow/manifest/AccessAttributeName.kt`, `api/query-api/src/main/kotlin/me/ahoo/wow/api/query/AggregationQuery.kt`, … (+237 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1c319-0a81-7b25-abfc-a9c11d78890b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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