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

Wx-Chevalier/ddd-Examples

Measured 20 September 2026, 20:53 UTC

42% At Risk
Event Sourcing 100% Exemplary Code Health 81% Strong Maturity 76% Strong Architecture 69% Adequate Domain Modelling 63% Adequate Security 60% Adequate Accessibility 35% Weak Readiness 30% Weak

REDACTED · 59,044 LoC · rebuild ~0.8 person-years · weakest lens: Readiness (30%)

Findings by grade

220 critical 922 serious 186 minor 41 could not be resolved — could be critical — see Limitations

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
20 September 2026, 20:53 UTC

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

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

61/64dimensions tool-verifieddeterministic · confidence 1.0 · 3 LLM-assisted, advisory
1298findings with an exact file:lineof 1328 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
64/141dimensions across the health lenses59044 LoC — wide & deep
Chapters

Executive summary

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

The system holds a 42% health score, placing it in the At Risk category. While the underlying code is well-structured and the domain logic is sound, the platform’s operational readiness is critically low. This gap creates a fragile foundation where routine changes or unexpected outages could disrupt business continuity, despite the system’s moderate size and manageable rebuild cost of approximately €110,000.

The most pressing concern is Operational Fragility. With a readiness score of just 30%, the system lacks the safety nets required for stable production. There is no codified disaster recovery plan, meaning a data loss event could halt operations for an extended period. This exposure threatens reliability and increases the potential cost of downtime, as the team cannot guarantee rapid restoration of services. The absence of performance and event-driven metrics further obscures how the system behaves under load, leaving leadership blind to potential bottlenecks.

A secondary risk is Security Exposure. Six leaked secrets were detected in configuration files, indicating that sensitive credentials are currently accessible in plain text. This is a critical vulnerability that could lead to unauthorized access or data breaches. While the code architecture is mature and the domain modeling is strong, these security lapses undermine trust in the platform. The high score in event sourcing suggests good internal consistency, but it does not compensate for the external security risks posed by exposed keys.

On the positive side, the codebase is clean, with no boilerplate or straight-line logic, and the domain model is well-defined. This means that when changes are made, they are likely to be stable and understandable. However, the lack of documentation maturity means a new team would struggle to onboard quickly, increasing long-term maintenance costs.

Focus first on resolving the six leaked secrets. This action offers the highest return on effort, immediately reducing security risk with minimal engineering time. Once credentials are secured, prioritize establishing a formal disaster recovery procedure to address the critical readiness gap. This two-step approach stabilizes the platform’s security and operational resilience, protecting the business from the most immediate threats.

Code Health 81% Strong Architecture 69% Adequate · gated by R9 Maturity 76% Strong Readiness 30% Weak · gated by D13, R8, P5 Security 60% Adequate · gated by D29, D30, D31 Domain Modelling 63% Adequate Event Sourcing 100% ★ Exemplary Accessibility 35% Weak · gated by AC3, AC4
How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Readiness 30% · 45% weightAccessibility 35% · 25% weightSecurity 60% · 14% weightDomain Modelling 63% · 8% weightArchitecture 69% · 4% weightMaturity 76% · 2% weightCode Health 81% · 1% weightEvent Sourcing 100% · 1% weight

Raise Readiness 30 → 70 (the Healthy floor) ⇒ headline 42 → ~51.

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

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

  • D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java
  • D4 · Duplicated block (143 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java
  • D4 · Duplicated block (102 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java
  • D4 · Duplicated block (33 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java
  • D4 · Duplicated block (23 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java
  • D4 · Duplicated block (21 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (17–19 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (19 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (17 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (17 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (16 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/model/ResourceModel.java
  • D4 · Duplicated block (14 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (13–14 lines × 2) REDACTED
  • D4 · Duplicated block (13 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java
  • D4 · Duplicated block (9–13 lines × 2) REDACTED
  • D4 · Duplicated block (12 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java
  • D4 · Duplicated block (12 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java
  • D4 · Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java
  • D4 · Duplicated block (9 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (8 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (8 lines × 2) java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/Financing.java
  • D4 · Duplicated block (28 lines × 2) java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/weight/DevWeight.java
  • D4 · Duplicated block (18 lines × 2) java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java
  • D4 · Duplicated block (13 lines × 3) java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java
  • D4 · Duplicated block (43 lines × 3) java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/events/incoming/applicant/Address.java
  • D4 · Duplicated block (37 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/OwnResources.java
  • D4 · Duplicated block (45 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/PurchaseCosts.java
  • D4 · Duplicated block (77 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/EarningCapacity.java
  • D4 · Duplicated block (68 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/MonthlyExpenses.java
  • D4 · Duplicated block (34 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/ApartmentInformation.java
  • D4 · Duplicated block (61 lines × 2) java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/AgencyResultArrivedEvent.java
  • D4 · Duplicated block (7 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java
  • D4 · Duplicated block (8 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/application/Application.java
  • D4 · Duplicated block (13 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java
  • D4 · Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (12 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (5 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (8 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java
  • D4 · Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java
  • D4 · Duplicated block (13 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java
  • D4 · Duplicated block (6 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/Product.java
  • D4 · Duplicated block (5 lines × 2) java-spring/2020~cola/craftsman/craftsman-app/src/main/java/com/alibaba/craftsman/command/UserProfileAddCmdExe.java
  • D4 · Duplicated block (7 lines × 3) java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java
  • D4 · Duplicated block (6 lines × 2) java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java
  • D4 · Duplicated block (10 lines × 2) java-spring/2021~baiyan_lou~ddd-demo/baiyan-ddd-domain/src/main/java/com/baiyan/ddd/domain/aggregate/user/event/UserDeleteEvent.java
  • D10 · No assertions: cannotPlaceAnOrderTwice java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java
  • D10 · No assertions: requireOrderLinesWhenPlacingAnOrder java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java
  • D10 · No assertions: testCreateOrderRequest java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResourceTest.java
  • D10 · No assertions: feeCannotBeNegative java-spring/2014~bookstore-cqrs-example/order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/AccumulatedFeeTest.java
  • D10 · No assertions: testCannotRegisterTwice java-spring/2014~bookstore-cqrs-example/order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/PublisherContractTest.java
  • D10 · No assertions: shouldClearCart java-spring/2014~bookstore-cqrs-example/shopping-context/src/test/java/se/citerus/cqrs/bookstore/shopping/resource/CartResourceTest.java
  • D10 · No assertions: customerSiteCanTrackValidCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java
  • D10 · No assertions: customerSiteErrorsOnInvalidCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java
  • D10 · No assertions: customerSiteNotifiesOnMisdirectedCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java
  • D10 · No assertions (empty test): testNextExpectedEvent java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/domain/model/cargo/ItineraryTest.java
  • D10 · No assertions: testSave java-spring/2020~cola/charge/src/test/java/com/huawei/charging/ChargeRecordRepoTest.java
  • D10 · No assertions: protect_clean_arch java-spring/2020~cola/charge/src/test/java/com/huawei/charging/CleanArchTest.java
  • D10 · No assertions: test java-spring/2020~cola/charge/src/test/java/com/huawei/charging/PropertyTest.java
  • D10 · No assertions: testNoOperatorContext java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java
  • D10 · No assertions: testOperatorContext java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java
  • D10 · No assertions: testNPE java-spring/2020~cola/craftsman/craftsman-domain/src/test/java/com/alibaba/craftsman/domain/UserProfileTest.java
  • D10 · No assertions (empty test): contextLoads java-spring/2020~yanglao-system/gateway-management/src/test/java/com/yanglao/gateway/GatewayApplicationTests.java
  • D10 · No assertions (empty test): contextLoads java-spring/2020~yanglao-system/pay-management/src/test/java/com/yanglao/paymanagement/PayManagementApplicationTests.java
  • D10 · No assertions: aggregateAnnotationRules java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java
  • D10 · No assertions: aggregateToRootEntityReference java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java
  • D10 · No assertions: aggregateVisibilityRule java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java
  • D10 · No assertions: entityAndValueObjectVisibilityRule java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java
  • D10 · No assertions: test java-spring/spring-simple-ddd/src/test/java/com/baeldung/ddd/order/jpa/ViolateOrderBusinessRulesUnitTest.java
  • D10 · No assertions: createNothingFindAllClients java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/domain/BankServiceTest.java
  • D10 · No assertions: exceptionToStatus java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/rest_interface/ExceptionAdviceTest.java
  • D10 · No assertions: testLoginWithVerifyCode reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java
  • D10 · No assertions: testLoginWithVerifyCode reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerTest.java
  • D10 · No assertions: testGet reinvent-wheels/udma/realworld/infra/src/test/java/icu/ngte/realworld/infra/http/OkHttpClientTest.java
  • D10 · Test project verifies nothing: api reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java
  • D10 · Test project verifies nothing: craftsman-app java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java
  • D10 · Test project verifies nothing: gateway java-spring/2020~yanglao-system/gateway-management/src/test/java/com/yanglao/gateway/GatewayApplicationTests.java
  • D10 · Test project verifies nothing: pay-management java-spring/2020~yanglao-system/pay-management/src/test/java/com/yanglao/paymanagement/PayManagementApplicationTests.java
  • D11 · Test suite cannot be installed from its own lockfile: node/domain-driven-hexagon/
  • D12 · Deprecated module: go.opentelemetry.io/otel/exporters/jaeger
  • D17 · TodoComment REDACTED
  • D17 · TodoComment REDACTED
  • D17 · TodoComment REDACTED
  • D17 · TodoComment REDACTED
  • D17 · TodoComment REDACTED
  • D17 · TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java
  • D17 · TodoComment reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java
  • D17 · TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java
  • D17 · TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java
  • D17 · TodoComment reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java

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

Rebuild cost & value ~ Modeled — €38,000–€190,000
Cost to rebuild€38,000–€190,000 (0.4–1.2 person-years (627–1,990 h), ~1–2 engineers)
Domain complexityREDACTED — harder problems cost more per line
Quality factor0.7× (at 42% quality) — the last 20% of quality is most of the work
Size & shapeREDACTED · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
Dead frontend code~405 LoC unreachable (13 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)

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

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

Top priorities

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

1
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
+9.9 pts · REDACTED effort · REDACTED Scanning
2
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
+9.9 pts · REDACTED effort · DR & Backup
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
+9.9 pts · REDACTED effort · Dependency Hygiene

Diagnosis — what's actually going on

Value concentrated against a weak lens · REDACTED · Value at risk
This is a REDACTED asset (~0.8 person-years to rebuild), and its weakest lens is Readiness at 30%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: REDACTED, ~0.8 person-years rebuild (59,044 LoC) · weakest lens: Readiness 30%
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · REDACTED · Leverage
Of everything flagged, the best return on effort is: Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.

Architecture — module dependency matrix

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

747 modules, 1084 dependencies. 19 dependency cycles across 61 modules, marked above the diagonal.

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

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →1 CodelyTv.Shared.Domain.Bus.Event2 CodelyTv.Shared.Domain.ValueObject3 com.alibaba.craftsman.domain.user4 com.baiyan.ddd.base.model.ddd5 com.baiyan.ddd.base.model.result6 ddd.plus.showcase.wms.domain.common.publisher7 io.github.dddplus.ast.model8 io.github.dddplus.model.spcification9 node.ddd-hexagonal-cqrs-es-eda.backend.src.lib.bounded-contexts.iam.authentication.domain.UserEntity10 node.ddd-hexagonal-cqrs-es-eda.backend.src.lib.bounded-contexts.iam.authentication.ports.UserWriteRepoPort11 se.citerus.cqrs.bookstore.event12 se.citerus.cqrs.bookstore.ordercontext.order13 se.citerus.dddsample.domain.model.location14 CodelyTv.Mooc.Shared.Domain.Courses15 CodelyTv.Shared.Domain16 com.baiyan.ddd.domain.aggregate.user.model17 io.github.dddplus.ext18 se.citerus.dddsample.domain.model.voyage19 CodelyTv.Mooc.Courses.Domain20 CodelyTv.Shared.Domain.Criteria21 io.github.dddplus.model22 se.citerus.dddsample.domain.model.handling23 CodelyTv.Mooc.Videos.Domain24 CodelyTv.Shared.Infrastructure.Persistence.Doctrine25 ddd.plus.showcase.wms.domain.common26 io.github.dddplus.runtime.registry.mock.model27 se.citerus.dddsample.domain.model.cargo28 io.github.dddplus.runtime.registry29 io.github.dddplus.runtime.registry.mock.ext30 se.citerus.dddsample.application31 io.github.dddplus.runtime32 se.citerus.dddsample.interfaces33 io.github.design34 ddd.plus.showcase.wms.domain.task35 ddd.plus.showcase.wms.domain.order36 ddd.plus.showcase.wms.domain.common.gateway37 ddd.plus.showcase.wms.infrastructure.domain.task38 ddd.plus.showcase.wms.domain.carton39 ddd.plus.showcase.wms.application.service40 ddd.plus.showcase.wms.infrastructure.domain.carton
1 CodelyTv.Shared.Domain.Bus.Event
2 CodelyTv.Shared.Domain.ValueObject
3 com.alibaba.craftsman.domain.user
4 com.baiyan.ddd.base.model.ddd
5 com.baiyan.ddd.base.model.result
6 ddd.plus.showcase.wms.domain.common.publisher
7 io.github.dddplus.ast.model
8 io.github.dddplus.model.spcification
9 node.ddd-hexagonal-cqrs-es-eda.backend.src.lib.bounded-contexts.iam.authentication.domain.UserEntity
10 node.ddd-hexagonal-cqrs-es-eda.backend.src.lib.bounded-contexts.iam.authentication.ports.UserWriteRepoPort
11 se.citerus.cqrs.bookstore.event
12 se.citerus.cqrs.bookstore.ordercontext.order
13 se.citerus.dddsample.domain.model.location
14 CodelyTv.Mooc.Shared.Domain.Courses1
15 CodelyTv.Shared.Domain1
16 com.baiyan.ddd.domain.aggregate.user.model3
17 io.github.dddplus.ext3
18 se.citerus.dddsample.domain.model.voyage2
19 CodelyTv.Mooc.Courses.Domain1231
20 CodelyTv.Shared.Domain.Criteria51
21 io.github.dddplus.model52
22 se.citerus.dddsample.domain.model.handling557
23 CodelyTv.Mooc.Videos.Domain13121
24 CodelyTv.Shared.Infrastructure.Persistence.Doctrine3
25 ddd.plus.showcase.wms.domain.common14
26 io.github.dddplus.runtime.registry.mock.model21
27 se.citerus.dddsample.domain.model.cargo835
28 io.github.dddplus.runtime.registry17124
29 io.github.dddplus.runtime.registry.mock.ext115
30 se.citerus.dddsample.application2125
31 io.github.dddplus.runtime1511
32 se.citerus.dddsample.interfaces11112
33 io.github.design2133
34 ddd.plus.showcase.wms.domain.task1116182121
35 ddd.plus.showcase.wms.domain.order1211911
36 ddd.plus.showcase.wms.domain.common.gateway4512
37 ddd.plus.showcase.wms.infrastructure.domain.task47161
38 ddd.plus.showcase.wms.domain.carton111011442
39 ddd.plus.showcase.wms.application.service12412212
40 ddd.plus.showcase.wms.infrastructure.domain.carton131124
Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself
…ared.Domain.Bus.Event…ed.Domain.ValueObject…craftsman.domain.user…an.ddd.base.model.ddd…ddd.base.model.result…main.common.publisher…hub.dddplus.ast.model…us.model.spcification…ion.domain.UserEntity…rts.UserWriteRepoPort….cqrs.bookstore.event…re.ordercontext.order…domain.model.location…Shared.Domain.CoursesCodelyTv.Shared.Domain….aggregate.user.modelio.github.dddplus.ext…e.domain.model.voyage…v.Mooc.Courses.Domain…hared.Domain.Criteria….github.dddplus.model…domain.model.handling…Tv.Mooc.Videos.Domain….Persistence.Doctrine…ase.wms.domain.common…e.registry.mock.model…le.domain.model.cargo…plus.runtime.registry…ime.registry.mock.ext…dddsample.application…ithub.dddplus.runtime….dddsample.interfacesio.github.design…wcase.wms.domain.task…case.wms.domain.order…domain.common.gateway…structure.domain.task…ase.wms.domain.carton…s.application.service…ructure.domain.carton…ared.Domain.Bus.Event1…ed.Domain.ValueObject2…craftsman.domain.user3…an.ddd.base.model.ddd4…ddd.base.model.result5…main.common.publisher6…hub.dddplus.ast.model7…us.model.spcification8…ion.domain.UserEntity9…rts.UserWriteRepoPort10….cqrs.bookstore.event11…re.ordercontext.order12…domain.model.location13…Shared.Domain.Courses14CodelyTv.Shared.Domain15….aggregate.user.model16io.github.dddplus.ext17…e.domain.model.voyage18…v.Mooc.Courses.Domain19…hared.Domain.Criteria20….github.dddplus.model21…domain.model.handling22…Tv.Mooc.Videos.Domain23….Persistence.Doctrine24…ase.wms.domain.common25…e.registry.mock.model26…le.domain.model.cargo27…plus.runtime.registry28…ime.registry.mock.ext29…dddsample.application30…ithub.dddplus.runtime31….dddsample.interfaces32io.github.design33…wcase.wms.domain.task34…case.wms.domain.order35…domain.common.gateway36…structure.domain.task37…ase.wms.domain.carton38…s.application.service39…ructure.domain.carton401133212315152557131213142183517124115212515111111221331116182121121191145124716111101144212412212131124+707 more modules (most-connected shown)

At a glance — Code Health · 81% · Strong ·

The Good
D1 · .NET / C# Cyclomatic Complexity 9.3 D2 · .NET / C# Cognitive Complexity 7.9 D3 · .NET / C# God Classes 9.9 D4 · .NET / C# Code Duplication 9.6 D17 · .NET / C# Explicit Debt 10.0 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 7.9 R3 · React / TS Large Files 9.3 R7 · React / TS Dead Code 9.4
The Bad
R2 · React / TS Cyclomatic Complexity 6.0

At a glance — Architecture · 69% · Adequate · gated by R9 ·

The Good
D27 · .NET / C# Navigability 9.2 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 8.3 AX5 · Repo Architecture & structure 10.0
The Ugly
R9 · React / TS Circular Imports 3.0

At a glance — Maturity · 76% · Strong ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 10.0 M1 · Repo Documentation (README) 7.1 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
M2 · Repo Architecture documentation 5.0
The Ugly
D20 · .NET / C# ADR Quality 0.0

At a glance — Readiness · 30% · Weak · gated by D13, R8, P5 ·

The Good
D10 · .NET / C# Test Quality 8.5 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 9.2 P1 · Repo CI/CD gates 10.0 P11 · Repo BDD / executable specs 10.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P9 · Repo Domain vs controller coverage 7.1
The Bad
D9 · .NET / C# Test Distribution 6.4 R4 · React / TS Test Coverage 6.8 R6 · React / TS Tooling 6.7
The Ugly
D13 · .NET / C# REDACTED Scanning 0.0 P5 · Repo DR & Backup 0.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 60% · Adequate · gated by D29, D30, D31 ·

The Good
D28 · .NET / C# Secrets (history) 9.0 D43 · .NET / C# Malicious Dependencies 10.0 S1 · Repo Web-Security Posture 8.0
The Bad
D40 · .NET / C# Network Egress Confinement 6.0 D41 · .NET / C# Kernel & Syscall Confinement 6.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.6 D30 · .NET / C# Dependency Vulnerabilities 0.0 D31 · .NET / C# IaC & Container Security 0.0

At a glance — Domain Modelling · 63% · Adequate ·

The Good
DM11 · Repo Constructible invalid state 8.0 DM12 · Repo Ambient inputs in the domain 10.0 DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 9.8 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM4 · Repo Rich vs anemic model 6.7
The Ugly
DM1 · Repo Aggregate boundaries 4.7 DM7 · Repo Repository granularity 4.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good
ES2 · Repo Immutable events 10.0 ES3 · Repo PII in the event store 10.0

At a glance — Accessibility · 35% · Weak · gated by AC3, AC4 ·

The Good
AC5 · Repo ARIA correctness 10.0
The Bad
AC1 · Repo Text alternatives 5.1 AC2 · Repo Forms & labels 5.2 AC6 · Repo Visual & motion safety 5.3
The Ugly
AC3 · Repo Page structure 2.5 AC4 · Repo Keyboard semantics 1.0 AC7 · Repo A11y enforcement 4.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2021 — Security Misconfiguration747REDACTED / Critical
A06:2021 — Vulnerable & Outdated Components124REDACTED / Critical
A03:2021 — Injection48REDACTED / Critical
A02:2021 — Cryptographic Failures8REDACTED / Critical

Roadmap

Immediately resolve the six leaked secrets in configuration files to eliminate security risks, then codify disaster recovery and backup procedures in infrastructure as code to ensure business continuity. Strengthen the codebase by removing unused dependencies and explicitly declaring imports, while integrating missing linting and type-checking tools into the CI pipeline. Finally, improve test coverage by refactoring entry points to be importable and adding direct tests for the remaining modules to ensure comprehensive validation.

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

Do thisHelpsEffortDimension
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.+9.9 ptsREDACTEDREDACTED Scanning
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+9.9 ptsREDACTEDDR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+9.9 ptsREDACTEDDependency Hygiene
Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI.+8.8 ptsREDACTEDTooling
5 of the 66 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 61 — directly or through their public entry.+8.7 ptsREDACTEDTest Coverage
Dependabot is configured but does not watch `gomod`, `gradle`, `composer` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.+8.4 ptsREDACTEDSecurity & performance tooling
Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.+8.1 ptsREDACTEDDomain vs controller coverage
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+7.9 ptsREDACTEDPage structure

File quality

Per-file score 0–10 — a quality signature. Of 129 files carrying findings, judged against the Production bar: 26% slop · 47% mixed · 27% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED0.2SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED0.2SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED0.2SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.4SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: REDACTED IaC: REDACTED

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

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

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

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

Could not be resolved — 41

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 61 of 64 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 64 dimensions across the health lenses
D1D2D3D4D9D10D11D12D13D15D17D19D20D21D27D28D29D30D31D35D40D41D43AC1AC2AC3AC4AC5AC6AC7AX10AX5DM1DM11DM12DM4DM5DM6DM7DM8DM9ES2ES3M1M2M3M4P1P11P3P4P5P6P9R1R10R2R3R4R6R7R8R9S1

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, 1298 of 1328 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a0c097-fab0-7b3b-a2e3-0eede2f25848.

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.

  • D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 53 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .php (4,762 lines, 21% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .java, and our analyzer cannot run the .java 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 18.5% — 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 (JaCoCo XML — `mvn jacoco:report` or 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 — `mvn jacoco:report` or 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 317 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 139 test source file(s) (.ts, .php) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language 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.
  • D14 License Compliance — evaluation did not complete — License Compliance not included (check did not complete) — excluded from the score.
  • D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 6 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 6 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: D22 has no public-API collector for any other ecosystem, and the remedy is to write one — no change to the scan image can close it.
  • D27 Navigability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 170 sampled here came from .java files. This repository's .php source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (6 commit(s) sampled).
  • D35 Change Coupling — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 6 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (REDACTED, a Gemfile's ruby directive, a REDACTED) is simply not read here yet.
  • AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 123 further occurrence(s) are not listed individually; the score already reflects all 163.
  • AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
  • AX4 Dependency direction — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the direction each project reference points — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
  • AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not declare whether a construction is produced or passed, which arm two needs to tell a producer from a mapping, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
  • X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • 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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • 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").
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • 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.
  • 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.
  • 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.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity9.3 / 10Stronggated by 2 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Entity.wrapperReflect at 25.

Entity.wrapperReflect (cyclomatic 25) · ×2reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:60

What to do

  1. Resolve the 2 Entity.wrapperReflect (cyclomatic 25) finding(s) in Cyclomatic Complexity — start with Entity.java (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity7.9 / 10Strong✓ 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 7.9 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cognitive complexity threshold of 15; the worst was Entity.wrapperReflect at 75.

Entity.wrapperReflect (cognitive 75) · ×2reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:60
Entity.toJsonStringAuto (cognitive 31) · ×2reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:217
DispatcherController.dispather_user (cognitive 16)reinvent-wheels/spring-rarf/api/src/main/java/wx/controller/DispatcherController.java:36

What to do

  1. Resolve the 2 Entity.wrapperReflect (cognitive 75) finding(s) in Cognitive Complexity — start with Entity.java (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 2 Entity.toJsonStringAuto (cognitive 31) finding(s) in Cognitive Complexity — start with Entity.java (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 DispatcherController.dispather_user (cognitive 16) finding(s) in Cognitive Complexity — start with DispatcherController.java. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.9 / 10Stronggated by 1 serious finding✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

TooManyMethods: RealEstatePropertyjava-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/realEstate/RealEstateProperty.java:7

What to do

  1. Resolve the 1 TooManyMethods finding(s) in God Classes — start with RealEstateProperty.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.6 / 10Stronggated by 56 serious findings✓ Tool-verified

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

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

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

53 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 56 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .php (21% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (10 lines × 2) · ×6reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:96
Duplicated block (11 lines × 2) · ×4reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:468
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:271
Duplicated block (22 lines × 2) · ×3reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:65
Duplicated block (12 lines × 2) · ×3java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:27

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

What to do

  1. Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ResourceBag.java (3), AbstractHandler.java, Resource.java. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ResourceBag.java (2), Resource.java, Entity.java. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AbstractHandler.java, ResourceBag.java, RARFThrowable.java. — One of this dimension's main actionable groups (3 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution6.4 / 10Adequate✓ 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 6.4 / 10 · rule-coverage 100% · ceiling Documented

320 test methods: 206 unit, 0 integration, 111 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 3 `it`/`test` case(s) across 2 test file(s) declaring at least one beside 317 .NET test method(s); its tier split is read from package names and paths only.

What to do

  1. Improve Test Distribution — currently 6.4/10. — 320 test methods: 206 unit, 0 integration, 111 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 3 `it`/`test` case(s) across 2 test file(s) declaring at least one beside 317 .NET test method(s); its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality8.5 / 10Adequategated by 3 critical 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 8.5 / 10 · rule-coverage 100% · ceiling Prevented

3 skipped (3 with a documented reason), 28 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 317 tests. Measured on the .java suite only — at least 139 test source file(s) (.ts, .php) went unread, so its test quality is unmeasured and is not in these counts.

No assertions (empty test): testNextExpectedEvent · ×3java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/domain/model/cargo/ItineraryTest.java:93
No assertions: cannotPlaceAnOrderTwice · ×25java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java:59
Test project verifies nothing: api · ×4reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java:45
Skipped (documented): shouldReturn201ResponseWhenHandlingReportIsSubmitted · ×3java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/handling/HandlingReportIntegrationTest.java:51

What to do

  1. Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ItineraryTest.java, GatewayApplicationTests.java, PayManagementApplicationTests.java. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 25 No assertions finding(s) in Test Quality — start with AggregateArchitectureTest.java (4), CustomerAcceptanceTest.java (3), OrderTest.java (2). — One of this dimension's main actionable groups (25 warning-level).
  3. Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with LoginControllerIntegrationTest.java, ContextInterceptorTest.java, GatewayApplicationTests.java. — One of this dimension's main actionable groups (4 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D11 · Test Reliability10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in node/ddd-hexagonal-cqrs-es-eda/backend/ (44 tests); jest via `npm install --ignore-scripts` (no lockfile) in node/domain-driven-hexagon/): measured (0 flaky); Java/Kotlin (11 builds): measured (0 flaky).

Test suite cannot be installed from its own lockfile: node/domain-driven-hexagon/

What to do

  1. Resolve the 1 Test suite cannot be installed from its own lockfile finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).

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

D12 · Dependency Hygiene9.2 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

5 outdated, 1 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.

Deprecated module: go.opentelemetry.io/otel/exporters/jaeger
Outdated: github.com/nats-io/nats.go · ×5

What to do

  1. Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

6 secret(s) detected.

REDACTED

What to do

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

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

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Stronggated by 11 serious findings✓ Tool-verified

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

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

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

11 deducted task-comment markers across 59044 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.

TodoComment · ×11REDACTED:29

What to do

  1. Resolve the 11 TodoComment finding(s) in Explicit Debt — start with HJSONObject.java (6), REDACTED (5). — One of this dimension's main actionable groups (11 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The documentation is comprehensive and well-structured for a software project: the READMEs cover an extensive overview of each repository (project name, description, roadmap), include installation/build/run steps, usage examples, architecture/design rationale, and contribute/contributing guidance. The READMEs are clipped mid-documentation by the scanner but the outline lists every named section present in the visible text; no missing sections were flagged as defects. There is a strong emphasis on explaining what the project does (domain-driven design with hexagonal/cqrs/es/eda) rather than just listing technologies, and each repository has its own unique focus (e.g., Spring MVC boilerplate vs. DDD banking). The documentation is comprehensive and well-structured for a Spring DDD project: it includes an excellent rationale for adopting DDD (why MVC is bad under iteration pressure), a detailed architecture covering both internal system interaction (system-intra) and external interaction (system-outside), the core DDD concepts of 'domain model' vs '贫血模型', and practical examples for each, plus architecture/design docs. It also documents installation/run commands, test coverage, and an extensive configuration table. The READMEs are well written with clear headings and a strong rationale; the only unshown section is the one that explains how to run the demo (the call graph/tech details in 3.5 were clipped by the scanner).

Documentation: no project overview · ×4README.md

What to do

  1. Resolve the 4 Documentation finding(s) in Documentation Quality — start with README.md (4). — One of this dimension's main actionable groups (4 recommendation-level).

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

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D27 · Navigability9.2 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

59 % of calls cross a namespace and 15 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .php was not sampled for call sites, so this score covers part of the tree, not all of it.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

48 finding(s): 0 critical, 4 high, 38 medium, 6 low. semgrep hit a parse error in 12 file(s) — `java-spring/2014~dddsample-core/gradlew` (line 177), `java-spring/2020~yanglao-system/docker/yanglaoyuan-swagger.yaml`, `java-spring/2020~yanglao-system/security-management/src/main/resources/templates/login.html` (line 1), `reinvent-wheels/udma/gradlew` (line 177), `REDACTED`, … (+7 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 38 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (38 warning-level).
  2. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 recommendation-level).

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

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

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

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

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

124 finding(s): 13 critical, 58 high, 39 medium, 14 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 57 REDACTED CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (53), REDACTED (4). — One of this dimension's main actionable groups (57 issue-level).
  2. Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
  3. Resolve the 1 REDACTED vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

747 finding(s): 4 critical, 56 high, 545 medium, 142 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 545 REDACTED IaC finding(s) in IaC & Container Security — start with REDACTED (28), REDACTED (28), REDACTED (28). — One of this dimension's main actionable groups (545 warning-level).
  2. Resolve the 56 REDACTED IaC finding(s) in IaC & Container Security — start with REDACTED (17), REDACTED (8), REDACTED (3). — One of this dimension's main actionable groups (56 issue-level).
  3. Resolve the 4 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D40 · Network Egress Confinement6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

  1. Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d40_recommendation.md · top locations in Appendix A, every location in findings.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/2 syscall-confinement controls present (seccomp, AppArmor/SELinux).

No seccomp profile
No AppArmor/SELinux confinement

What to do

  1. Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 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. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.1 / 10Adequate✓ Tool-verified

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — REDACTED:9, java-spring/2014~dddsample-core/target/classes/static/REDACTED:9, java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/REDACTED:8

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified

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

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

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

  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×2) — java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:58, java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:58
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×22) — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1181, java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:2582, java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:4050, …
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:2569, java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:2569
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — java-spring/2020~yanglao-system/security-management/src/main/resources/templates/login.html:16, java-spring/2020~yanglao-system/security-management/src/main/resources/templates/login.html:17
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×2) — node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:22, node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:54
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:45, node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:60, node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:62

What to do

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

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×14) — REDACTED:2, java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/main/resources/assets/admin.html:2, java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/target/classes/assets/admin.html:2, …
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — REDACTED:9
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×14) — java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/main/resources/assets/admin.html:2, java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/target/classes/assets/admin.html:2, java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:2, …
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:33, java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:33
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×9) — java-spring/2014~dddsample-core/src/main/java/com/pathfinder/api/package.html:1, java-spring/2014~dddsample-core/src/main/java/com/pathfinder/internal/package.html:1, java-spring/2014~dddsample-core/src/main/java/com/pathfinder/package.html:1, …

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 semantics1.0 / 10Critical✓ Tool-verified

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

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

Coverage: Population: interactive elements plus elements the markup gives a click/key handler or the repo's own CSS styles `cursor: pointer`, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:77

What to do

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

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

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

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

AC6 · Visual & motion safety5.3 / 10Adequate✓ 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.

  • This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference). — REDACTED:53
  • `body` sets color: #555 on background-color: #8599f7 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — java-spring/2014~dddsample-core/target/classes/static/style.css:5, java-spring/2014~dddsample-core/src/main/resources/static/style.css:5
  • `.datepicker table tr td.selected, .datepicker table tr td.selected:hover, .datepicker table tr td.selected.disabled, .datepicker table tr td.selected.disabled:hover` sets color: #fff on background-color: #9e9e9e — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — java-spring/2014~dddsample-core/target/classes/static/css/bootstrap-datepicker.css:240, java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap-datepicker.css:240
  • `.btn-info` sets color: #fff on background-color: #5bc0de — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — java-spring/2014~dddsample-core/target/classes/static/css/bootstrap.css:3233, java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3233

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 enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

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

What to do

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

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

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

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

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

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

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

DM1 · Aggregate boundaries4.7 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

  • `CheckTask` references the aggregate root `ShipmentOrder` directly (via `shipmentOrders`) — hold its `ShipmentOrderId` instead.
  • `Cargo` references the aggregate root `Location` directly (via `origin`) — hold its `LocationId` instead.
  • `Leg` references the aggregate root `Voyage` directly (via `voyage`) — hold its `VoyageId` instead.
  • `Leg` references the aggregate root `Location` directly (via `loadLocation`) — hold its `LocationId` instead.
  • `Leg` references the aggregate root `Location` directly (via `unloadLocation`) — hold its `LocationId` instead.
  • `HandlingEvent` references the aggregate root `Voyage` directly (via `voyage`) — hold its `VoyageId` instead.
  • `HandlingEvent` references the aggregate root `Location` directly (via `location`) — hold its `LocationId` instead.
  • `HandlingEvent` references the aggregate root `Cargo` directly (via `cargo`) — hold its `CargoId` instead.
  • `CarrierMovement` references the aggregate root `Location` directly (via `arrivalLocation`) — hold its `LocationId` instead.
  • `CarrierMovement` references the aggregate root `Location` directly (via `departureLocation`) — hold its `LocationId` instead.

What to do

  • Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM11 · Constructible invalid state8.0 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `ScoringResultEntity`'s public constructor takes `applicationNumber`, `scorePoints`, `scoreColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ScoringResultEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultEntity.java:21
  • `Applicant`'s public constructor takes `applicationNumber`, `applicantNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Applicant` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/applicant/Applicant.java:63
  • `Financing`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Financing` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/Financing.java:41
  • `Household`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Household` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/Household.java:47
  • `RealEstateProperty`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `RealEstateProperty` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/RealEstateProperty.java:77
  • `Account`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Account` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Account.java:22
  • `Client`'s public constructor takes `username` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Client` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:45
  • `Users`'s public constructor takes `id`, `password`, `name`, `phone`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Users` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~yanglao-system/user-management/src/main/java/com/yanglao/user/domain/Users.java:19
  • `Rooms`'s public constructor takes `room`, `detail`, `price` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Rooms` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~yanglao-system/room-management/src/main/java/com/yanglao/room/domain/Rooms.java:32
  • `Orders`'s public constructor takes `userid`, `username`, `roomid`, `term`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Orders` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/domain/Orders.java:27
  • `UserProfile`'s public constructor takes `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `UserProfile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/user/UserProfile.java:90
  • `Account`'s public constructor takes `phoneNo` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Account` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:47
  • `ChargeRecord`'s public constructor takes `phoneNo`, `chargeDuration` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ChargeRecord` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/ChargeRecord.java:50
  • `TrackingId`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TrackingId` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/TrackingId.java:19
  • `Location`'s public constructor takes `unloCode`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Location` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/location/Location.java:51
  • `BackofficeCourse`'s public constructor takes `id`, `name`, `duration` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `BackofficeCourse` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — php/php-ddd-example/src/Backoffice/Courses/Domain/BackofficeCourse.php:11

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

DM4 · Rich vs anemic model6.7 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `AgencyResultAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/agencyResult/AgencyResultAggregate.java:14
  • `ApplicantAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/applicant/ApplicantAggregate.java:11
  • `FinancialSituationAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/financialSituation/FinancialSituationAggregate.java:9
  • `ScoringResultAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultAggregate.java:9
  • `AccountAccess` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/AccountAccess.java:15
  • `Client` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:26
  • `Student` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/BaseAggregateRootTest.java:63
  • `Book` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/ListBagTest.java:39, java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/SetBagTest.java:40
  • `CheckTask` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/design/CheckTask.java:27
  • `ShipmentOrder` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/design/ShipmentOrder.java:17
  • `ContainerDiff` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/domain/diff/ContainerDiff.java:15
  • `Pays` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2020~yanglao-system/pay-management/src/main/java/com/yanglao/paymanagement/domain/Pays.java:9
  • `UserProfile` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/user/UserProfile.java:22
  • `Account` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:23
  • `ChargeRecord` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/ChargeRecord.java:12
  • `Itinerary` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/Itinerary.java:17
  • `Leg` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/Leg.java:18
  • `CarrierMovement` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/voyage/CarrierMovement.java:18
  • `Voyage` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/voyage/Voyage.java:17

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM7 · Repository granularity4.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

  • `JpaOrderRepository` is a repository over `JpaOrder`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `JpaOrder` through its owning aggregate instead. — java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/jpa/JpaOrderRepository.java:5
  • `AgencyResultDAO` is a repository over `AgencyResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AgencyResultProjection` through its owning aggregate instead. — java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/agencyResult/AgencyResultDAO.java:5
  • `ApplicantResultDAO` is a repository over `ApplicantResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ApplicantResultProjection` through its owning aggregate instead. — java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/applicant/ApplicantResultDAO.java:6
  • `FinancialSituationResultDAO` is a repository over `FinancialSituationResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `FinancialSituationResultProjection` through its owning aggregate instead. — java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/financialSituation/FinancialSituationResultDAO.java:5
  • `ScoringResultDAO` is a repository over `ScoringResultEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ScoringResultEntity` through its owning aggregate instead. — java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultDAO.java:5
  • `ApplicantRepository` is a repository over `Applicant`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Applicant` through its owning aggregate instead. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/ApplicantRepository.java:8
  • `FinancingRepository` is a repository over `Financing`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Financing` through its owning aggregate instead. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/FinancingRepository.java:6
  • `HouseholdRepository` is a repository over `Household`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Household` through its owning aggregate instead. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/HouseholdRepository.java:6
  • `RealEstatePropertyRepository` is a repository over `RealEstateProperty`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `RealEstateProperty` through its owning aggregate instead. — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/RealEstatePropertyRepository.java:6
  • `PersonRatingRepository` is a repository over `PersonRating`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PersonRating` through its owning aggregate instead. — java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/repository/PersonRatingRepository.java:11
  • `ImportedAccountAccessJpaRepository` is a repository over `AccountAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AccountAccess` through its owning aggregate instead. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedAccountAccessJpaRepository.java:24
  • `ImportedAccountJpaRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedAccountJpaRepository.java:16
  • `ImportedClientJpaRepository` is a repository over `Client`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Client` through its owning aggregate instead. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedClientJpaRepository.java:16
  • `ChargeGateway` is a repository over `ChargeRecord`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ChargeRecord` through its owning aggregate instead. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/gateway/ChargeGateway.java:10

What to do

  • Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM8 · Value-object opportunities9.8 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

  • The parameters [body, description, title] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — reinvent-wheels/udma/realworld/domain/src/main/java/icu/ngte/realworld/domain/article/ArticleDO.java:53
  • The parameters [aggregateid, eventid, occurredon] travel together across 5 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — php/php-ddd-example/src/Mooc/Courses/Domain/CourseCreatedDomainEvent.php:26

What to do

  • Extract recurring primitive parameter clusters into value objects so the concept (and its rules) lives in one place.
DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether persisted events are immutable facts (init-only/readonly) — a settable event member lets stored history be rewritten.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

ES3 · PII in the event store10.0 / 10Exemplary○ Nothing flagged

Other · Event Sourcing — Whether the append-only event log avoids un-erasable personal data (or has a crypto-shredding strategy) — a GDPR right-to-erasure risk.

Method: Roslyn (event-sourcing gated): high-confidence PII flagged Warning; ambiguous name-like fields adjudicated by language model as person versus fictional. Advisory without model, definitive with.

M1 · Documentation (README)7.1 / 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

  • Add a 'Testing' section to the root README — how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 60 of 77 project(s) that lack one — worth up to 1.6 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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

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

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

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

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

P11 · BDD / executable specs10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.

Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Dependabot is configured but does not watch `gomod`, `gradle`, `composer` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ 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.

  • Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup0.0 / 10Critical✓ 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.

  • A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

  • Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P9 · Domain vs controller coverage7.1 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.

Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.

What to do

  • Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
R1 · Type Safety9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication7.9 / 10Strong✓ 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.

  • java-spring/2014~dddsample-core/src/main/resources/ and java-spring/2014~dddsample-core/target/classes/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~19345 lines; the trees hold 17 and 17 files). That is one structural fact, not 17 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. — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1
  • 22 duplicated blocks under node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/ have copies in at least two of the sibling directories iam, marketing, todo — 17 of them are reported below, and 5 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25
  • 10 duplicated blocks under node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/ have copies in at least two of the sibling directories iam, marketing, todo — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57
  • java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:7 · java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:7 — these 2 files are line-for-line copies of one another — 1333 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. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:7
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-uncompleted.integration-handler.ts:25 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:25
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:9 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:11 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:9 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:9
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-modified-title.integration-handler.ts:6 · +1 more site(s) not listed — the 5 copies are spread across 5 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts:6
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:69 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-write.repository.ts:39 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:69
  • node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:25 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:62 — 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. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:25
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:47 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:16 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts:21 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:16
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-deleted.event.ts:4 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-modified-title.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-uncompleted.event.ts:3 — the 4 copies are spread across 4 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:3
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-updated-email.event.ts:3 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:3
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:30 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts:30 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:30
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts:8
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:163 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:189 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:163
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:24 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:24 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts:24 · +3 more site(s) not listed — the 7 copies are spread across 7 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:36 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:35 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:37 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:35 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:36
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/email.vo.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/TitleVO.ts:5 — the 3 copies are spread across 3 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:5
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:52 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:56 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:54 — the 4 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. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:52
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:56 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:54 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/iam.module.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/marketing.module.ts:8 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/iam.module.ts:8
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/complete-todo.command.ts:7 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/delete-todo.command.ts:4 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/uncomplete-todo.command.ts:7 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/complete-todo.command.ts:7
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:236 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:277 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:306 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:334 · +2 more site(s) not listed — all 6 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:236
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:21 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:23 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts:28 — the 3 copies are spread across 3 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:21
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/completed-todos.vo.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/email.vo.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/TitleVO.ts:2 — the 4 copies are spread across 4 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:2
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:286 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:315 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:343 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:371 — all 4 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:286
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:18 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:17 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:18
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-deleted.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:8 — the 4 copies are spread across 4 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:8
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts:13 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/commands/create-user.command.ts:13 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts:13
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/UserEntity.ts:17 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/user.entity.ts:16 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/UserEntity.ts:17
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts:43 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:47 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48
  • node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.request.dto.ts:21 · node/domain-driven-hexagon/src/modules/user/queries/find-users/find-users.request.dto.ts:11 — the two spans are one implementation copied and then locally edited — 68 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. — node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.request.dto.ts:21
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:114 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:31 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:114
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:112 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:53 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:112
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:64 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:62 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:59 — 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:58
  • node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:5 · +4 more site(s) not listed — the 8 copies are spread across 8 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. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:5
  • node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:375 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:389 — 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. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:375
  • node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.command.ts:3 · node/domain-driven-hexagon/src/modules/user/domain/events/user-created.domain-event.ts:3 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.command.ts:3

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.
R2 · Cyclomatic Complexity6.0 / 10Adequate✓ 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.

  • keydown has cyclomatic complexity 39 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1392, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1392
  • click has cyclomatic complexity 38 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1133, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1133
  • _process_options has cyclomatic complexity 33 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:168, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:168
  • fill has cyclomatic complexity 31 and cognitive complexity 42; 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:933, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:933
  • getClassNames has cyclomatic complexity 23 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:830, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:830
  • parseDate has cyclomatic complexity 19 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 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1767, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1767
  • updateNavArrows has cyclomatic complexity 19 and cognitive complexity 22; 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1091, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1091
  • (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — node/ddd-hexagonal-cqrs-es-eda/backend/src/config/configuration.ts:33
  • _resolveViewName has cyclomatic complexity 17 and cognitive complexity 11; 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:149, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:149
  • _fill_yearsView has cyclomatic complexity 15 and cognitive complexity 27; 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. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:876, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:876
  • place has cyclomatic complexity 15 and cognitive complexity 21; 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. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:644

What to do

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

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

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

What to do

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

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js, java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js, node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts, …

What to do

  • 5 of the 66 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 61 — directly or through their public entry.
R6 · Tooling6.7 / 10Adequate✓ 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.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI.
R7 · Dead Code9.4 / 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.

  • Unreachable from the 11 application, 7 tooling and 65 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (11 application, 7 tooling, 65 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 (×10) — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/notification-template.entity.ts, node/ddd-hexagonal-cqrs-es-eda/backend/src/logging.interceptor.ts, …
  • no import path from any entry point (11 application, 7 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (node/domain-driven-hexagon/src/libs/decorators/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — node/domain-driven-hexagon/src/libs/decorators/final.decorator.ts, node/domain-driven-hexagon/src/libs/decorators/frozen.decorator.ts
  • no import path from any entry point (11 application, 7 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/error-events/email-not-found.integration-event.ts
  • Nothing imports this binding — it is safe to review for removal. (×3) — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/index.ts:14, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/index.ts:21, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/index.ts:21

What to do

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

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

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

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:11
  • Declared in node/ddd-hexagonal-cqrs-es-eda/backend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

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

  • node/domain-driven-hexagon/src/libs/ddd/entity.base.ts → node/domain-driven-hexagon/src/libs/utils/index.ts → node/domain-driven-hexagon/src/libs/utils/convert-props-to-object.util.ts → node/domain-driven-hexagon/src/libs/ddd/entity.base.ts (one verified cycle inside a mutually-dependent group of 4 files) — node/domain-driven-hexagon/src/libs/ddd/entity.base.ts
  • node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts → node/domain-driven-hexagon/src/libs/exceptions/index.ts → node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts — node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts
  • node/domain-driven-hexagon/src/modules/user/database/user.repository.ts → node/domain-driven-hexagon/src/modules/user/user.mapper.ts → node/domain-driven-hexagon/src/modules/user/database/user.repository.ts — node/domain-driven-hexagon/src/modules/user/database/user.repository.ts
  • node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts → node/domain-driven-hexagon/src/modules/wallet/wallet.mapper.ts → node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts — node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts

What to do

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

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

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

  • `//unpkg.com/docsify/lib/docsify.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 25 such include(s) across the repository's markup. — REDACTED:107

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.

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 Health81%StrongSolid.
Architecture69%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity76%StrongSolid.
Readiness30%Weak — gated by D13, R8, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security60%Adequate — gated by D29, D30, D31Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling63%AdequateAcceptable, with room to improve.
Event Sourcing100%ExemplaryStrongest area.
Accessibility35%Weak — gated by AC3, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
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: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 74 check(s) not relevant to this codebase

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

  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
  • 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.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — License Compliance not included (check did not complete)
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — Production source is present (.go, .java, .php, .ts, .tsx) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D34 Knowledge Freshness — too few commits to judge knowledge freshness
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is .java, .php, .ts, .tsx, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 event handler(s))
  • ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • ES1 Fold determinism — no Apply/When folds detected — fold-determinism check not applicable
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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.
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 — 220 finding(s)
D30 · Dependency Vulnerabilities · REDACTED CVE · ×57
  • 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
  • + 32 more in this group — see findings.md.
D31 · IaC & Container Security · REDACTED IaC · ×56
  • 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
  • + 31 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×15
  • <input> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:2582 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/templates/admin/registrationForm.html:43 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label REDACTED:26 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:2582 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/2014~dddsample-core/target/classes/templates/admin/registrationForm.html:43 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/2014~dddsample-core/target/classes/templates/track.html:26 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/2020~yanglao-system/security-management/src/main/resources/templates/login.html:16 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label java-spring/2020~yanglao-system/security-management/src/main/resources/templates/login.html:17 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/financing.html:101 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/financing.html:103 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:22 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:54 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:45 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:60 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:62 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <html> without a lang · ×14
  • <html> without a lang java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/main/resources/assets/admin.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/target/classes/assets/admin.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/com/pathfinder/api/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/com/pathfinder/internal/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/com/pathfinder/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/impl/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/util/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/handling/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/location/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/package.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D30 · Dependency Vulnerabilities · Critical CVE · ×13
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×12
  • <select> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1181 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:4928 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/templates/admin/pickNewDestination.html:32 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/templates/admin/registrationForm.html:23 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/templates/admin/registrationForm.html:33 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:1181 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:4928 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/target/classes/templates/admin/pickNewDestination.html:32 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/target/classes/templates/admin/registrationForm.html:23 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/2014~dddsample-core/target/classes/templates/admin/registrationForm.html:33 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/financing.html:106 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/financing.html:121 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×10
  • Aggregate holds a reference to another aggregate: CheckTask.shipmentOrders — `CheckTask` references the aggregate root `ShipmentOrder` directly (via `shipmentOrders`) — hold its `ShipmentOrderId` instead.
  • Aggregate holds a reference to another aggregate: Cargo.origin — `Cargo` references the aggregate root `Location` directly (via `origin`) — hold its `LocationId` instead.
  • Aggregate holds a reference to another aggregate: Leg.voyage — `Leg` references the aggregate root `Voyage` directly (via `voyage`) — hold its `VoyageId` instead.
  • Aggregate holds a reference to another aggregate: Leg.loadLocation — `Leg` references the aggregate root `Location` directly (via `loadLocation`) — hold its `LocationId` instead.
  • Aggregate holds a reference to another aggregate: Leg.unloadLocation — `Leg` references the aggregate root `Location` directly (via `unloadLocation`) — hold its `LocationId` instead.
  • Aggregate holds a reference to another aggregate: HandlingEvent.voyage — `HandlingEvent` references the aggregate root `Voyage` directly (via `voyage`) — hold its `VoyageId` instead.
  • Aggregate holds a reference to another aggregate: HandlingEvent.location — `HandlingEvent` references the aggregate root `Location` directly (via `location`) — hold its `LocationId` instead.
  • Aggregate holds a reference to another aggregate: HandlingEvent.cargo — `HandlingEvent` references the aggregate root `Cargo` directly (via `cargo`) — hold its `CargoId` instead.
  • Aggregate holds a reference to another aggregate: CarrierMovement.arrivalLocation — `CarrierMovement` references the aggregate root `Location` directly (via `arrivalLocation`) — hold its `LocationId` instead.
  • Aggregate holds a reference to another aggregate: CarrierMovement.departureLocation — `CarrierMovement` references the aggregate root `Location` directly (via `departureLocation`) — hold its `LocationId` instead.
AC3 · Page structure · Document without a <title> · ×9
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/com/pathfinder/api/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/com/pathfinder/internal/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/com/pathfinder/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/impl/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/util/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/handling/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/location/package.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D13 · REDACTED Scanning · Leaked secret · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Critical IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×3
  • <img> without a text alternative REDACTED:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative java-spring/2014~dddsample-core/target/classes/static/REDACTED:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative java-spring/spring-ddd-credit/credit-sales-funnel/src/main/resources/templates/REDACTED:8 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D10 · Test Quality · No assertions (empty test) · ×3
  • No assertions (empty test): testNextExpectedEvent java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/domain/model/cargo/ItineraryTest.java:93 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): contextLoads java-spring/2020~yanglao-system/gateway-management/src/test/java/com/yanglao/gateway/GatewayApplicationTests.java:10 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): contextLoads java-spring/2020~yanglao-system/pay-management/src/test/java/com/yanglao/paymanagement/PayManagementApplicationTests.java:10 — Test method has an empty body — it asserts nothing and exercises no code.
R9 · Circular Imports · Import cycle (2 files) · ×3
  • Import cycle (2 files) node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts — node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts → node/domain-driven-hexagon/src/libs/exceptions/index.ts → node/domain-driven-hexagon/src/libs/exceptions/exceptions.ts
  • Import cycle (2 files) node/domain-driven-hexagon/src/modules/user/database/user.repository.ts — node/domain-driven-hexagon/src/modules/user/database/user.repository.ts → node/domain-driven-hexagon/src/modules/user/user.mapper.ts → node/domain-driven-hexagon/src/modules/user/database/user.repository.ts
  • Import cycle (2 files) node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts — node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts → node/domain-driven-hexagon/src/modules/wallet/wallet.mapper.ts → node/domain-driven-hexagon/src/modules/wallet/database/wallet.repository.ts
AC2 · Forms & labels · Link with no accessible name · ×2
  • Link with no accessible name java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:2569 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:2569 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:4050 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label java-spring/2014~dddsample-core/target/classes/static/js/jquery-2.1.4.js:4050 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom REDACTED:9 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics · Click handler on a non-interactive <p> · ×1
  • Click handler on a non-interactive <p> node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:77 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×1
  • Test suite cannot be installed from its own lockfile: node/domain-driven-hexagon/ — The jest suite in node/domain-driven-hexagon/ was never exercised because its dependency install refused the committed lockfile — the dependency install for node/domain-driven-hexagon/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · REDACTED vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'jquery' · ×1
  • Unlisted import 'jquery' java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:11 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) node/domain-driven-hexagon/src/libs/ddd/entity.base.ts — node/domain-driven-hexagon/src/libs/ddd/entity.base.ts → node/domain-driven-hexagon/src/libs/utils/index.ts → node/domain-driven-hexagon/src/libs/utils/convert-props-to-object.util.ts → node/domain-driven-hexagon/src/libs/ddd/entity.base.ts (one verified cycle inside a mutually-dependent group of 4 files)
Serious — 922 finding(s)
D31 · IaC & Container Security · REDACTED IaC · ×545
  • 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
  • + 520 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js — 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 java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js — 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 node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-write.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/authentication.controller.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/api.module.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.rest.controller.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-modified-title.integration-handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-uncompleted.integration-handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/todo.module.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/main.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · REDACTED CVE · ×39
  • 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
  • + 14 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×38
  • 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
  • + 13 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×25
  • No assertions: cannotPlaceAnOrderTwice java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java:59 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: requireOrderLinesWhenPlacingAnOrder java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCreateOrderRequest java-spring/2014~bookstore-cqrs-example/order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResourceTest.java:39 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: feeCannotBeNegative java-spring/2014~bookstore-cqrs-example/order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/AccumulatedFeeTest.java:51 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCannotRegisterTwice java-spring/2014~bookstore-cqrs-example/order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/PublisherContractTest.java:36 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: shouldClearCart java-spring/2014~bookstore-cqrs-example/shopping-context/src/test/java/se/citerus/cqrs/bookstore/shopping/resource/CartResourceTest.java:115 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: customerSiteCanTrackValidCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: customerSiteErrorsOnInvalidCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java:25 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: customerSiteNotifiesOnMisdirectedCargo java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/acceptance/CustomerAcceptanceTest.java:32 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSave java-spring/2020~cola/charge/src/test/java/com/huawei/charging/ChargeRecordRepoTest.java:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: protect_clean_arch java-spring/2020~cola/charge/src/test/java/com/huawei/charging/CleanArchTest.java:12 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: test java-spring/2020~cola/charge/src/test/java/com/huawei/charging/PropertyTest.java:32 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testNoOperatorContext java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java:16 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testOperatorContext java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java:25 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testNPE java-spring/2020~cola/craftsman/craftsman-domain/src/test/java/com/alibaba/craftsman/domain/UserProfileTest.java:86 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: aggregateAnnotationRules java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java:38 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: aggregateToRootEntityReference java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java:57 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: aggregateVisibilityRule java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java:48 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: entityAndValueObjectVisibilityRule java-spring/spring-ddd-credit/scoring/aggregates/src/test/java/com/mploed/dddwithspring/scoring/archunit/AggregateArchitectureTest.java: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: test java-spring/spring-simple-ddd/src/test/java/com/baeldung/ddd/order/jpa/ViolateOrderBusinessRulesUnitTest.java:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: createNothingFindAllClients java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/domain/BankServiceTest.java:87 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: exceptionToStatus java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/rest_interface/ExceptionAdviceTest.java:48 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testLoginWithVerifyCode reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testLoginWithVerifyCode reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerTest.java:38 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testGet reinvent-wheels/udma/realworld/infra/src/test/java/icu/ngte/realworld/infra/http/OkHttpClientTest.java:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
DM4 · Rich vs anemic model · Anemic entity · ×20
  • Anemic entity: AgencyResultAggregate java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/agencyResult/AgencyResultAggregate.java:14 — `AgencyResultAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ApplicantAggregate java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/applicant/ApplicantAggregate.java:11 — `ApplicantAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: FinancialSituationAggregate java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/financialSituation/FinancialSituationAggregate.java:9 — `FinancialSituationAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ScoringResultAggregate java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultAggregate.java:9 — `ScoringResultAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AccountAccess java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/AccountAccess.java:15 — `AccountAccess` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Client java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:26 — `Client` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Student java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/BaseAggregateRootTest.java:63 — `Student` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/ListBagTest.java:39 — `Book` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/SetBagTest.java:40 — `Book` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CheckTask java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/design/CheckTask.java:27 — `CheckTask` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ShipmentOrder java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/design/ShipmentOrder.java:17 — `ShipmentOrder` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ContainerDiff java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/domain/diff/ContainerDiff.java:15 — `ContainerDiff` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Pays java-spring/2020~yanglao-system/pay-management/src/main/java/com/yanglao/paymanagement/domain/Pays.java:9 — `Pays` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: UserProfile java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/user/UserProfile.java:22 — `UserProfile` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Account java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:23 — `Account` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ChargeRecord java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/ChargeRecord.java:12 — `ChargeRecord` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Itinerary java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/Itinerary.java:17 — `Itinerary` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Leg java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/Leg.java:18 — `Leg` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CarrierMovement java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/voyage/CarrierMovement.java:18 — `CarrierMovement` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Voyage java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/voyage/Voyage.java:17 — `Voyage` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
DM11 · Constructible invalid state · Constructible in an invalid state · ×16
  • Constructible in an invalid state: ScoringResultEntity java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultEntity.java:21 — `ScoringResultEntity`'s public constructor takes `applicationNumber`, `scorePoints`, `scoreColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ScoringResultEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Applicant java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/applicant/Applicant.java:63 — `Applicant`'s public constructor takes `applicationNumber`, `applicantNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Applicant` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Financing java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/Financing.java:41 — `Financing`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Financing` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Household java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/Household.java:47 — `Household`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Household` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: RealEstateProperty java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/RealEstateProperty.java:77 — `RealEstateProperty`'s public constructor takes `applicationNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `RealEstateProperty` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Account java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Account.java:22 — `Account`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Account` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Client java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:45 — `Client`'s public constructor takes `username` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Client` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Users java-spring/2020~yanglao-system/user-management/src/main/java/com/yanglao/user/domain/Users.java:19 — `Users`'s public constructor takes `id`, `password`, `name`, `phone`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Users` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Rooms java-spring/2020~yanglao-system/room-management/src/main/java/com/yanglao/room/domain/Rooms.java:32 — `Rooms`'s public constructor takes `room`, `detail`, `price` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Rooms` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Orders java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/domain/Orders.java:27 — `Orders`'s public constructor takes `userid`, `username`, `roomid`, `term`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Orders` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: UserProfile java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/user/UserProfile.java:90 — `UserProfile`'s public constructor takes `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `UserProfile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Account java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:47 — `Account`'s public constructor takes `phoneNo` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Account` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ChargeRecord java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/ChargeRecord.java:50 — `ChargeRecord`'s public constructor takes `phoneNo`, `chargeDuration` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ChargeRecord` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: TrackingId java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/TrackingId.java:19 — `TrackingId`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TrackingId` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Location java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/location/Location.java:51 — `Location`'s public constructor takes `unloCode`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Location` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BackofficeCourse php/php-ddd-example/src/Backoffice/Courses/Domain/BackofficeCourse.php:11 — `BackofficeCourse`'s public constructor takes `id`, `name`, `duration` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `BackofficeCourse` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
AC3 · Page structure · Page without a main landmark · ×14
  • Page without a main landmark REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/main/resources/assets/admin.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/target/classes/assets/admin.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/com/pathfinder/api/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/com/pathfinder/internal/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/com/pathfinder/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/impl/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/application/util/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/cargo/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/handling/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/location/package.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
DM7 · Repository granularity · Repository for a non-root entity · ×14
  • Repository for a non-root entity: JpaOrderRepository → JpaOrder java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/jpa/JpaOrderRepository.java:5 — `JpaOrderRepository` is a repository over `JpaOrder`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `JpaOrder` through its owning aggregate instead.
  • Repository for a non-root entity: AgencyResultDAO → AgencyResultProjection java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/agencyResult/AgencyResultDAO.java:5 — `AgencyResultDAO` is a repository over `AgencyResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AgencyResultProjection` through its owning aggregate instead.
  • Repository for a non-root entity: ApplicantResultDAO → ApplicantResultProjection java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/applicant/ApplicantResultDAO.java:6 — `ApplicantResultDAO` is a repository over `ApplicantResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ApplicantResultProjection` through its owning aggregate instead.
  • Repository for a non-root entity: FinancialSituationResultDAO → FinancialSituationResultProjection java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/financialSituation/FinancialSituationResultDAO.java:5 — `FinancialSituationResultDAO` is a repository over `FinancialSituationResultProjection`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `FinancialSituationResultProjection` through its owning aggregate instead.
  • Repository for a non-root entity: ScoringResultDAO → ScoringResultEntity java-spring/spring-ddd-credit/scoring/adapters-output/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultDAO.java:5 — `ScoringResultDAO` is a repository over `ScoringResultEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ScoringResultEntity` through its owning aggregate instead.
  • Repository for a non-root entity: ApplicantRepository → Applicant java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/ApplicantRepository.java:8 — `ApplicantRepository` is a repository over `Applicant`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Applicant` through its owning aggregate instead.
  • Repository for a non-root entity: FinancingRepository → Financing java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/FinancingRepository.java:6 — `FinancingRepository` is a repository over `Financing`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Financing` through its owning aggregate instead.
  • Repository for a non-root entity: HouseholdRepository → Household java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/HouseholdRepository.java:6 — `HouseholdRepository` is a repository over `Household`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Household` through its owning aggregate instead.
  • Repository for a non-root entity: RealEstatePropertyRepository → RealEstateProperty java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/repository/RealEstatePropertyRepository.java:6 — `RealEstatePropertyRepository` is a repository over `RealEstateProperty`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `RealEstateProperty` through its owning aggregate instead.
  • Repository for a non-root entity: PersonRatingRepository → PersonRating java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/repository/PersonRatingRepository.java:11 — `PersonRatingRepository` is a repository over `PersonRating`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PersonRating` through its owning aggregate instead.
  • Repository for a non-root entity: ImportedAccountAccessJpaRepository → AccountAccess java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedAccountAccessJpaRepository.java:24 — `ImportedAccountAccessJpaRepository` is a repository over `AccountAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AccountAccess` through its owning aggregate instead.
  • Repository for a non-root entity: ImportedAccountJpaRepository → Account java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedAccountJpaRepository.java:16 — `ImportedAccountJpaRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead.
  • Repository for a non-root entity: ImportedClientJpaRepository → Client java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/infrastructure/imports/ImportedClientJpaRepository.java:16 — `ImportedClientJpaRepository` is a repository over `Client`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Client` through its owning aggregate instead.
  • Repository for a non-root entity: ChargeGateway → ChargeRecord java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/gateway/ChargeGateway.java:10 — `ChargeGateway` is a repository over `ChargeRecord`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ChargeRecord` through its owning aggregate instead.
D17 · Explicit Debt · TodoComment · ×11
  • TodoComment REDACTED:29 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:37 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:144 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:158 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:163 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java:26 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java:27 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java:11 — // TODO Auto-generated constructor stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java:22 — // TODO Auto-generated constructor stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java:12 — // TODO Auto-generated constructor stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java:23 — // TODO Auto-generated constructor stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:96 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:96-105 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:91-100 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:96` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:103` calls `getDispatcherController`, `getRelationProxy`, `combinedReduce` and `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:112` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:144 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:144-153 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:143-152 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:96 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:96-105 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java:95-104 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:127 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:127-136 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:126-135 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:388 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:388-397 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:390-399 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) java-spring/2021~baiyan_lou~ddd-demo/baiyan-ddd-domain/src/main/java/com/baiyan/ddd/domain/aggregate/user/event/UserDeleteEvent.java:17 — java-spring/2021~baiyan_lou~ddd-demo/baiyan-ddd-domain/src/main/java/com/baiyan/ddd/domain/aggregate/user/event/UserDeleteEvent.java:17-26 | java-spring/2021~baiyan_lou~ddd-demo/baiyan-ddd-domain/src/main/java/com/baiyan/ddd/domain/aggregate/user/event/UserUpdateEvent.java:18-27 — 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.
D10 · Test Quality · Test project verifies nothing · ×4
  • Test project verifies nothing: api reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java:45 — No conventional assertion call was detected in 2 of 2 tests in `api` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: craftsman-app java-spring/2020~cola/craftsman/craftsman-app/src/test/java/com/alibaba/craftsman/app/ContextInterceptorTest.java:16 — No conventional assertion call was detected in 2 of 2 tests in `craftsman-app` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: gateway java-spring/2020~yanglao-system/gateway-management/src/test/java/com/yanglao/gateway/GatewayApplicationTests.java:10 — No conventional assertion call was detected in 1 of 1 tests in `gateway` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: pay-management java-spring/2020~yanglao-system/pay-management/src/test/java/com/yanglao/paymanagement/PayManagementApplicationTests.java:10 — No conventional assertion call was detected in 1 of 1 tests in `pay-management` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:468 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:468-478 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:474-484 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:37 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:37-47 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java:36-46 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:192 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:192-202 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:191-201 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:327 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:327-337 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:327-337 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 256 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.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×4
  • Duplicated block (13 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:114 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:114 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:31 — 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 (13 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:112 — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:112 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:53 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:375 — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:375 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:389 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.command.ts:3 — node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.command.ts:3 · node/domain-driven-hexagon/src/modules/user/domain/events/user-created.domain-event.ts:3 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:271 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:271-287 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:480-495 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:268-284 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:486-501 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:505 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:505-529 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:539-563 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:511-535 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:545-569 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:141 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:141-158 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:171-197 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:141-158 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:171-197 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×3
  • Duplicated block (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:65 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:65-86 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:60-81 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:65` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:52` calls `getDispatcherController`, `getRelationProxy`, `combinedReduce` and `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:54` 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 (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:345 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:345-366 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:344-365 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:176 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:176-197 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:176-197 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:176` 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 (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:27 — java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:27-38 | java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/jpa/JpaOrderLine.java:35-46 — 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 `java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:27` 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 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 (12 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:175 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:175-186 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:174-185 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:160 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:160-171 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:159-170 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/Financing.java:23 — java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/Financing.java:23-30 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/Financing.java:33-40 — 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 `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/Financing.java:23` 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 × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/application/Application.java:56 — reinvent-wheels/spring-rarf/api/src/main/java/wx/application/Application.java:56-63 | reinvent-wheels/spring-rarf/api/src/main/java/wx/application/Application4Deploy.java:32-39 — 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. 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 (8 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:315 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:315-322 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:314-321 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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. 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 (21 lines × 2 locations) · ×3
  • Duplicated block (21 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:3 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-updated-email.event.ts:3 — 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 (21 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:30 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:30 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts:30 — 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 (21 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts:8 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
AC2 · Forms & labels · <fieldset> without a <legend> · ×2
  • <fieldset> without a <legend> java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:58 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:58 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC3 · Page structure · Heading level jumps from h2 to h5 · ×2
  • Heading level jumps from h2 to h5 java-spring/2014~bookstore-cqrs-example/shopping-context/src/main/resources/assets/REDACTED:33 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 java-spring/2014~bookstore-cqrs-example/shopping-context/target/classes/assets/REDACTED:33 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · REDACTED contrast colour pair in CSS (2.8 · ×2
  • REDACTED contrast colour pair in CSS (2.8:1) java-spring/2014~dddsample-core/target/classes/static/style.css:5 — `body` sets color: #555 on background-color: #8599f7 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • REDACTED contrast colour pair in CSS (2.8:1) java-spring/2014~dddsample-core/src/main/resources/static/style.css:5 — `body` sets color: #555 on background-color: #8599f7 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · REDACTED contrast colour pair in CSS (2.7 · ×2
  • REDACTED contrast colour pair in CSS (2.7:1) java-spring/2014~dddsample-core/target/classes/static/css/bootstrap-datepicker.css:240 — `.datepicker table tr td.selected, .datepicker table tr td.selected:hover, .datepicker table tr td.selected.disabled, .datepicker table tr td.selected.disabled:hover` sets color: #fff on background-color: #9e9e9e — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • REDACTED contrast colour pair in CSS (2.7:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap-datepicker.css:240 — `.datepicker table tr td.selected, .datepicker table tr td.selected:hover, .datepicker table tr td.selected.disabled, .datepicker table tr td.selected.disabled:hover` sets color: #fff on background-color: #9e9e9e — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · REDACTED contrast colour pair in CSS (2.1 · ×2
  • REDACTED contrast colour pair in CSS (2.1:1) java-spring/2014~dddsample-core/target/classes/static/css/bootstrap.css:3233 — `.btn-info` sets color: #fff on background-color: #5bc0de — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • REDACTED contrast colour pair in CSS (2.1:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3233 — `.btn-info` sets color: #fff on background-color: #5bc0de — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · Entity.wrapperReflect (cyclomatic 25) · ×2
  • Entity.wrapperReflect (cyclomatic 25) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:60 — Entity.wrapperReflect 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.
  • Entity.wrapperReflect (cyclomatic 25) reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:60 — Entity.wrapperReflect 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.
D2 · Cognitive Complexity · Entity.wrapperReflect (cognitive 75) · ×2
  • Entity.wrapperReflect (cognitive 75) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:60 — Entity.wrapperReflect has cognitive complexity 75 (threshold 15). Drivers by points: if/else 15 (42 pts), error handling 8 (32 pts), loops 1 (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Entity.wrapperReflect (cognitive 75) reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:60 — Entity.wrapperReflect has cognitive complexity 75 (threshold 15). Drivers by points: if/else 15 (42 pts), error handling 8 (32 pts), loops 1 (nesting depth added 51). To reduce it, split the body into named stages: move each independent 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 · Entity.toJsonStringAuto (cognitive 31) · ×2
  • Entity.toJsonStringAuto (cognitive 31) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:217 — Entity.toJsonStringAuto has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Entity.toJsonStringAuto (cognitive 31) reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:217 — Entity.toJsonStringAuto has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:513 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:513-529 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:519-535 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:513` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (17 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:547 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:547-563 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:553-569 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:547` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:173 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:173-185 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:170-182 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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. 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 (13 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:97 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:97-109 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:97-109 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:103 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:103-107 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:102-106 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) java-spring/2020~cola/craftsman/craftsman-app/src/main/java/com/alibaba/craftsman/command/UserProfileAddCmdExe.java:24 — java-spring/2020~cola/craftsman/craftsman-app/src/main/java/com/alibaba/craftsman/command/UserProfileAddCmdExe.java:24-28 | java-spring/2020~cola/craftsman/craftsman-app/src/main/java/com/alibaba/craftsman/command/UserProfileUpdateCmdExe.java:18-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 first that the copies are not typed on the same thing: the declarations holding them bind `cmd` to `UserProfileAddCmd` in one and `UserProfileUpdateCmd` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/Product.java:36 — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/AccountNo.java:68-73 | java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/Product.java:36-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java:50 — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java:50-55 | java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/SingleResponse.java:31-36 — 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. 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 first that the copies are not typed on the same thing: the declarations holding them bind `data` to `Collection<T>` in one and `T` 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.
R10 · Code Duplication · Duplicated block (18 lines × 4 locations) · ×2
  • Duplicated block (18 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:36 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:36 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:35 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:37 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:35 — 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.
  • Duplicated block (18 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:52 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:52 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:56 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:54 — the 4 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. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (18 lines × 3 locations) · ×2
  • Duplicated block (18 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:5 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/email.vo.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/TitleVO.ts:5 — the 3 copies are spread across 3 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 (18 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:56 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:54 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (15 lines × 4 locations) · ×2
  • Duplicated block (15 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:286 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:286 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:315 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:343 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:371 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (15 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:8 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/contracts/integration-events/user-email-changed.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-deleted.integration-event.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:8 — the 4 copies are spread across 4 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 (14 lines × 2 locations) · ×2
  • Duplicated block (14 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts:13 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts:13 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/commands/create-user.command.ts:13 — 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 (14 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/UserEntity.ts:17 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/UserEntity.ts:17 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/user.entity.ts:16 — 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.
R2 · Cyclomatic Complexity · Complex function keydown (cyclomatic 39, cognitive 52) · ×2
  • Complex function keydown (cyclomatic 39, cognitive 52) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1392 — keydown has cyclomatic complexity 39 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function keydown (cyclomatic 39, cognitive 52) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1392 — keydown has cyclomatic complexity 39 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function click (cyclomatic 38, cognitive 81) · ×2
  • Complex function click (cyclomatic 38, cognitive 81) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1133 — click has cyclomatic complexity 38 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function click (cyclomatic 38, cognitive 81) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1133 — click has cyclomatic complexity 38 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _process_options (cyclomatic 33, cognitive 44) · ×2
  • Complex function _process_options (cyclomatic 33, cognitive 44) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:168 — _process_options has cyclomatic complexity 33 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.
  • Complex function _process_options (cyclomatic 33, cognitive 44) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:168 — _process_options has cyclomatic complexity 33 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 fill (cyclomatic 31, cognitive 42) · ×2
  • Complex function fill (cyclomatic 31, cognitive 42) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:933 — fill has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function fill (cyclomatic 31, cognitive 42) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:933 — fill has cyclomatic complexity 31 and cognitive complexity 42; 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 getClassNames (cyclomatic 23, cognitive 24) · ×2
  • Complex function getClassNames (cyclomatic 23, cognitive 24) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:830 — getClassNames has cyclomatic complexity 23 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function getClassNames (cyclomatic 23, cognitive 24) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:830 — getClassNames has cyclomatic complexity 23 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseDate (cyclomatic 19, cognitive 30) · ×2
  • Complex function parseDate (cyclomatic 19, cognitive 30) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1767 — parseDate has cyclomatic complexity 19 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function parseDate (cyclomatic 19, cognitive 30) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1767 — parseDate has cyclomatic complexity 19 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 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 updateNavArrows (cyclomatic 19, cognitive 22) · ×2
  • Complex function updateNavArrows (cyclomatic 19, cognitive 22) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1091 — updateNavArrows has cyclomatic complexity 19 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function updateNavArrows (cyclomatic 19, cognitive 22) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:1091 — updateNavArrows has cyclomatic complexity 19 and cognitive complexity 22; 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 _resolveViewName (cyclomatic 17, cognitive 11) · ×2
  • Complex function _resolveViewName (cyclomatic 17, cognitive 11) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:149 — _resolveViewName has cyclomatic complexity 17 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function _resolveViewName (cyclomatic 17, cognitive 11) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:149 — _resolveViewName has cyclomatic complexity 17 and cognitive complexity 11; 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 _fill_yearsView (cyclomatic 15, cognitive 27) · ×2
  • Complex function _fill_yearsView (cyclomatic 15, cognitive 27) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:876 — _fill_yearsView has cyclomatic complexity 15 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function _fill_yearsView (cyclomatic 15, cognitive 27) java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:876 — _fill_yearsView has cyclomatic complexity 15 and cognitive complexity 27; 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.
R7 · Dead Code · Dead file (~12 LoC) · ×2
  • Dead file (~12 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/error-events/email-not-found.integration-event.ts — no import path from any entry point (11 application, 7 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~12 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/errors/empty-notification-template.error.ts — no import path from any entry point (11 application, 7 tooling, 65 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
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1
  • Animation without a prefers-reduced-motion guard REDACTED:53 — This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference).
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 72 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D12 · Dependency Hygiene · Deprecated module · ×1
  • Deprecated module: go.opentelemetry.io/otel/exporters/jaeger — `go.opentelemetry.io/otel/exporters/jaeger` is required at v1.14.0 in REDACTED, and its author has DEPRECATED the module: "This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp] or [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc] instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
D2 · Cognitive Complexity · DispatcherController.dispather_user (cognitive 16) · ×1
  • DispatcherController.dispather_user (cognitive 16) reinvent-wheels/spring-rarf/api/src/main/java/wx/controller/DispatcherController.java:36 — DispatcherController.dispather_user has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (3 pts), boolean chains 2 (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.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: RealEstateProperty java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/realEstate/RealEstateProperty.java:7 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 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.
D4 · Code Duplication · Duplicated block (143 lines × 2) · ×1
  • Duplicated block (143 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:62 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:62-204 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:62-204 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 256 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Attribute` names `rarf.resource.annotation.Attribute` in one and `wx.rarf.resource.entity.annotation.Attribute` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (102 lines × 2) · ×1
  • Duplicated block (102 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:219 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:219-320 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java:219-320 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 256 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Attribute` names `rarf.resource.annotation.Attribute` in one and `wx.rarf.resource.entity.annotation.Attribute` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:56 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:56-88 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java:55-87 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:129 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:129-151 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:124-146 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:78 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:78-98 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:77-97 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `HJSONObject` names `rarf.utils.HJSONObject` in one and `wx.rarf.utils.HJSONObject` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:434 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:434-452 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:442-458 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:434` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:569 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:569-587 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:575-593 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/model/ResourceModel.java:29 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/model/ResourceModel.java:29-44 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/model/ResourceModel.java:28-43 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/model/ResourceModel.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/model/ResourceModel.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:507 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:507-520 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:541-554 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:513-526 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:547-560 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) REDACTED:58 — REDACTED:58-71 | REDACTED:87-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:143 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:143-155 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:173-185 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:143-155 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:173-185 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • Duplicated block (9–13 lines × 2) REDACTED:91 — REDACTED:91-99 | REDACTED:107-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:279 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:279-287 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:276-284 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:279` 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 (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:276 — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:276-283 | reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:485-492 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java:273-280 | reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java:491-498 — before extracting anything, compare `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java` and `reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/handler/AbstractHandler.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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 `reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/handler/AbstractHandler.java:276` 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 (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/weight/DevWeight.java:1 — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/weight/DevWeight.java:1-28 | java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/weight/QAWeight.java:1-28 — 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 `java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/weight/DevWeight.java:1` 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. 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11 — java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11-28 | java-spring/2020~yanglao-system/room-management/src/main/java/com/yanglao/room/adapter/outbound/JpaRoomRepository.java:12-29 — 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 `java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `orders` to `Orders` in one and `Rooms` 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11 — java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11-28 | java-spring/2020~yanglao-system/room-management/src/main/java/com/yanglao/room/adapter/outbound/JpaRoomRepository.java:12-29 | java-spring/2020~yanglao-system/user-management/src/main/java/com/yanglao/user/adapter/outbound/JpaUserRepository.java:9-21 — 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 `java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/adapter/outbound/JpaOrderRepository.java:11` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `orders` to `Orders` in one and `Rooms` 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.
D4 · Code Duplication · Duplicated block (43 lines × 3) · ×1
  • Duplicated block (43 lines × 3) java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/events/incoming/applicant/Address.java:1 — java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/events/incoming/applicant/Address.java:1-43 | java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/applicant/Address.java:1-55 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/applicant/Address.java:1-43 — before extracting anything, compare `java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/events/incoming/applicant/Address.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/applicant/Address.java` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/credit-agency/src/main/java/com/mploed/dddwithspring/creditagency/events/incoming/applicant/Address.java:1` 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. 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 (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/OwnResources.java:1 — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/OwnResources.java:1-38 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/OwnResources.java:1-37 — before extracting anything, compare `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/OwnResources.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/OwnResources.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/OwnResources.java:1` 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 (45 lines × 2) · ×1
  • Duplicated block (45 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/PurchaseCosts.java:1 — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/PurchaseCosts.java:1-46 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/PurchaseCosts.java:1-45 — before extracting anything, compare `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/PurchaseCosts.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/financing/PurchaseCosts.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/financing/PurchaseCosts.java:1` 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 (77 lines × 2) · ×1
  • Duplicated block (77 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/EarningCapacity.java:1 — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/EarningCapacity.java:1-79 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/household/EarningCapacity.java:1-77 — before extracting anything, compare `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/EarningCapacity.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/household/EarningCapacity.java` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/EarningCapacity.java:1` 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 (68 lines × 2) · ×1
  • Duplicated block (68 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/MonthlyExpenses.java:1 — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/MonthlyExpenses.java:1-74 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/household/MonthlyExpenses.java:1-68 — before extracting anything, compare `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/MonthlyExpenses.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/household/MonthlyExpenses.java` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/household/MonthlyExpenses.java:1` 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 (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/ApartmentInformation.java:1 — java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/ApartmentInformation.java:1-45 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/realEstate/ApartmentInformation.java:1-34 — 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 `java-spring/spring-ddd-credit/credit-sales-funnel/src/main/java/com/mploed/dddwithspring/creditsalesfunnel/model/realEstate/ApartmentInformation.java:1` 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 (61 lines × 2) · ×1
  • Duplicated block (61 lines × 2) java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/AgencyResultArrivedEvent.java:1 — java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/AgencyResultArrivedEvent.java:1-80 | java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/creditAgency/AgencyRating.java:1-61 — before extracting anything, compare `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/AgencyResultArrivedEvent.java` and `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/creditAgency/AgencyRating.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/incoming/AgencyResultArrivedEvent.java:1` 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 (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:41 — java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/OrderLine.java:41-47 | java-spring/spring-simple-ddd/src/main/java/com/baeldung/ddd/order/jpa/JpaOrderLine.java:49-55 — 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 (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java:42 — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/MultiResponse.java:42-48 | java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/Response.java:45-51 | java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/dto/SingleResponse.java:23-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
R10 · Code Duplication · Forked directory tree (17 identical files, ~19345 lines × 2 trees) · ×1
  • Forked directory tree (17 identical files, ~19345 lines × 2 trees) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1 — java-spring/2014~dddsample-core/src/main/resources/ and java-spring/2014~dddsample-core/target/classes/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~19345 lines; the trees hold 17 and 17 files). That is one structural fact, not 17 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 3 sibling directories (22 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (22 clone groups) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25 — 22 duplicated blocks under node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/ have copies in at least two of the sibling directories iam, marketing, todo — 17 of them are reported below, and 5 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 3 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (10 clone groups) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57 — 10 duplicated blocks under node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/ have copies in at least two of the sibling directories iam, marketing, todo — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (1333 identical lines × 2 files) · ×1
  • Wholesale file copy (1333 identical lines × 2 files) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:7 — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:7 · java-spring/2014~dddsample-core/target/classes/static/js/bootstrap-datepicker.js:7 — these 2 files are line-for-line copies of one another — 1333 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 (43 lines × 3 locations) · ×1
  • Duplicated block (43 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:25 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-uncompleted.integration-handler.ts:25 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (41 lines × 3 locations) · ×1
  • Duplicated block (41 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:9 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-completed.integration-event.ts:9 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:11 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-uncompleted.integration-event.ts:9 — 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57 — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:57 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.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 · Duplicated block (37 lines × 5 locations) · ×1
  • Duplicated block (37 lines × 5 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts:6 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts:6 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-modified-title.integration-handler.ts:6 · +1 more site(s) not listed — the 5 copies are spread across 5 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 (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:69 — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:69 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-write.repository.ts:39 — 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 (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:25 — node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:25 · node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:62 — 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 (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:16 — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:16 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts:21 — 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 (22 lines × 4 locations) · ×1
  • Duplicated block (22 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:3 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-deleted.event.ts:4 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-modified-title.event.ts:3 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-uncompleted.event.ts:3 — the 4 copies are spread across 4 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 (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:163 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:163 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:189 — 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 (18 lines × 7 locations) · ×1
  • Duplicated block (18 lines × 7 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:25 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:24 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:24 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts:24 · +3 more site(s) not listed — the 7 copies are spread across 7 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 (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/iam.module.ts:8 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/iam.module.ts:8 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/marketing.module.ts:8 — 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 (17 lines × 3 locations) · ×1
  • Duplicated block (17 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/complete-todo.command.ts:7 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/complete-todo.command.ts:7 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/delete-todo.command.ts:4 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/uncomplete-todo.command.ts:7 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (16 lines × 6 locations) · ×1
  • Duplicated block (16 lines × 6 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:236 — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:236 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:277 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:306 · node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:334 · +2 more site(s) not listed — all 6 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 (16 lines × 3 locations) · ×1
  • Duplicated block (16 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:21 — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:21 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:23 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts:28 — the 3 copies are spread across 3 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 (16 lines × 4 locations) · ×1
  • Duplicated block (16 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:2 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/EmailVO.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/completed-todos.vo.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/email.vo.ts:2 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/TitleVO.ts:2 — the 4 copies are spread across 4 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 (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:18 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:18 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:17 — 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 (14 lines × 3 locations) · ×1
  • Duplicated block (14 lines × 3 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:48 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts:43 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:47 — 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 with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.request.dto.ts:21 — node/domain-driven-hexagon/src/modules/user/commands/create-user/create-user.request.dto.ts:21 · node/domain-driven-hexagon/src/modules/user/queries/find-users/find-users.request.dto.ts:11 — the two spans are one implementation copied and then locally edited — 68 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 (13 lines × 4 locations) · ×1
  • Duplicated block (13 lines × 4 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:58 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:58 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:64 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:62 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:59 — 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 · Duplicated block (13 lines × 8 locations) · ×1
  • Duplicated block (13 lines × 8 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:5 — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts:5 · node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:5 · +4 more site(s) not listed — the 8 copies are spread across 8 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 16) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 16) node/ddd-hexagonal-cqrs-es-eda/backend/src/config/configuration.ts:33 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function place (cyclomatic 15, cognitive 21) · ×1
  • Complex function place (cyclomatic 15, cognitive 21) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:644 — place has cyclomatic complexity 15 and cognitive complexity 21; 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.
R6 · Tooling · Tooling · ×1
  • Tooling — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~144 LoC) · ×1
  • Dead file (~144 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~57 LoC) · ×1
  • Dead file (~57 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/notification-template.entity.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~52 LoC) · ×1
  • Dead file (~52 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/logging.interceptor.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~41 LoC) · ×1
  • Dead file (~41 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts — no import path from any entry point (11 application, 7 tooling, 65 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) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~22 LoC) · ×1
  • Dead file (~22 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/setup-jest.js — no import path from any entry point (11 application, 7 tooling, 65 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 (~18 LoC) · ×1
  • Dead file (~18 LoC) node/domain-driven-hexagon/src/libs/decorators/final.decorator.ts — no import path from any entry point (11 application, 7 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (node/domain-driven-hexagon/src/libs/decorators/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~11 LoC) · ×1
  • Dead file (~11 LoC) node/domain-driven-hexagon/src/libs/decorators/frozen.decorator.ts — no import path from any entry point (11 application, 7 tooling, 65 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (node/domain-driven-hexagon/src/libs/decorators/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~4 LoC) · ×1
  • Dead file (~4 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/dtos/register-command.dto.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~3 LoC) · ×1
  • Dead file (~3 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/dtos/increment-todos.dto.ts — no import path from any entry point (11 application, 7 tooling, 65 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 (~2 LoC) · ×1
  • Dead file (~2 LoC) node/domain-driven-hexagon/src/libs/decorators/index.ts — no import path from any entry point (11 application, 7 tooling, 65 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
R8 · Dependency Hygiene · Unused dependency '@bitloops/bl-boilerplate-core' · ×1
  • Unused dependency '@bitloops/bl-boilerplate-core' — Declared in node/ddd-hexagonal-cqrs-es-eda/backend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@bitloops/bl-boilerplate-infra-mongo' · ×1
  • Unused dependency '@bitloops/bl-boilerplate-infra-mongo' — Declared in node/ddd-hexagonal-cqrs-es-eda/backend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@bitloops/bl-boilerplate-infra-nest-auth-passport' · ×1
  • Unused dependency '@bitloops/bl-boilerplate-infra-nest-auth-passport' — Declared in node/ddd-hexagonal-cqrs-es-eda/backend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity REDACTED:107 — `//unpkg.com/docsify/lib/docsify.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 25 such include(s) across the repository's markup.
Minor — 178 finding(s)
D31 · IaC & Container Security · REDACTED IaC · ×142
  • 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
  • + 117 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · REDACTED CVE · ×14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D19 · Documentation Quality · Documentation · ×4
  • Documentation: no project overview README.md — The README is a single blank template with no description of what the project does or what it is. Add an Introduction section explaining the project's purpose and the DDD principles it applies.
  • Documentation: no installation or build instructions README.md — There are installation/run steps but no build/setup instructions for a new contributor starting from scratch. Document prerequisites (e.g. Node, Docker) plus full install/build commands and how to run the app.
  • Documentation: no usage examples README.md — Usage is only a one-line 'To avoid retyping too much info' placeholder; no real examples. Expand with concrete usage examples (e.g. running the ToDo app, invoking REST endpoints) and how to run tests.
  • Documentation: no architecture or design documentation java-spring/2021~baiyan_lou~ddd-demo/README.md — The DDD demo README is a single narrative explaining why DDD and how it solves MVC pain points, with no architecture or design documentation. Add an architecture document covering the layered structure (domain, application, infrastructure) and the DDD concepts illustrated in the demo.
DM8 · Value-object opportunities · Primitive data clump · ×2
  • Primitive data clump: [body, description, title] reinvent-wheels/udma/realworld/domain/src/main/java/icu/ngte/realworld/domain/article/ArticleDO.java:53 — The parameters [body, description, title] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
  • Primitive data clump: [aggregateid, eventid, occurredon] php/php-ddd-example/src/Mooc/Courses/Domain/CourseCreatedDomainEvent.php:26 — The parameters [aggregateid, eventid, occurredon] travel together across 5 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
R7 · Dead Code · Unused export 'StreamingErrorEventHandlers' · ×2
  • Unused export 'StreamingErrorEventHandlers' node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/index.ts:14 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'StreamingErrorEventHandlers' node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/index.ts:21 — Nothing imports this binding — it is safe to review for removal.
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/`.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D40 · Network Egress Confinement · No network policy · ×1
  • No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
D41 · Kernel & Syscall Confinement · No seccomp profile · ×1
  • No seccomp profile — Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
D41 · Kernel & Syscall Confinement · No AppArmor/SELinux confinement · ×1
  • No AppArmor/SELinux confinement — Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
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.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
R7 · Dead Code · Unused export 'StreamingCommandHandlers' · ×1
  • Unused export 'StreamingCommandHandlers' node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/index.ts:21 — Nothing imports this binding — it is safe to review for removal.
Minor — 8 finding(s)
D12 · Dependency Hygiene · Outdated · ×5
  • Outdated: github.com/nats-io/nats.go — `github.com/nats-io/nats.go` is required at v1.24.0 in REDACTED, but v1.54.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/nats-io/nats.go@v1.54.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/prometheus/client_golang — `github.com/prometheus/client_golang` is required at v1.14.0 in REDACTED, but v1.24.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/prometheus/client_golang@v1.24.1 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: go.opentelemetry.io/otel — `go.opentelemetry.io/otel` is required at v1.14.0 in REDACTED, but v1.46.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get go.opentelemetry.io/otel@v1.46.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: go.opentelemetry.io/otel/sdk — `go.opentelemetry.io/otel/sdk` is required at v1.14.0 in REDACTED, but v1.46.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get go.opentelemetry.io/otel/sdk@v1.46.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: go.opentelemetry.io/otel/trace — `go.opentelemetry.io/otel/trace` is required at v1.14.0 in REDACTED, but v1.46.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get go.opentelemetry.io/otel/trace@v1.46.0 && go mod tidy` and commit the updated REDACTED and go.sum.
D10 · Test Quality · Skipped (documented) · ×3
  • Skipped (documented): shouldReturn201ResponseWhenHandlingReportIsSubmitted java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/handling/HandlingReportIntegrationTest.java:51 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
  • Skipped (documented): shouldConvertDescriptionCorrectlyForGivenParamsWithVoyage java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/tracking/ws/CargoTrackingDTOConverterTest.java:105 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
  • Skipped (documented): shouldConvertDescriptionCorrectlyForGivenParamsWithoutVoyage java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/tracking/ws/CargoTrackingDTOConverterTest.java:119 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2a9d68ed18c643809ad70cf992da7f8a/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2a9d68ed18c643809ad70cf992da7f8a/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .48artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update124artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .747artifacts/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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
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/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a0c097-fab0-7b3b-a2e3-0eede2f25848 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 220 · Warnings: 922 · Recommendations: 178 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 20-09-2026 @ 20:53 UTC.

Downloadable artifacts

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

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