Public report of wx-chevalier/ddd-examples, published 8 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 8 November 2026, 00:02 UTC · Survey ID cd_8677a6ac07eb4ff399fdfbeb8e5500dc
wx-chevalier/ddd-examples
Measured 8 November 2026, 00:02 UTC, at code version 457d904
Test reliability is not measured: No runner for the .php half of a polyglot repository.
CAI scoreAt riskNo change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 59,032 lines of product code in 53 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Production Readiness, 23
Findings by how serious they are
354 critical1059 serious315 minor
12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
8 November 2026, 00:02 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
106of 106 dimensions measured by tools.
1691of 1728 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
106dimensions across 9 lenses, read from 59,032 lines of product code in 53 projects.
wx-chevalier/ddd-examples is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because 13 passwords or keys sit in the current code. It scores 33 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 23, is the weakest lens and counts most in the score. The best first step is replacing the 13 exposed passwords or keys and switching the old ones off, worth about 8 points. Making the three tests that check nothing check their results comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 40.
187 known security holes in the packages the code depends on can be used by attackers. Sixty settings leave the servers or containers unsafe, and thirteen passwords or keys in the code and one in the code's history are open to anyone who can read the repository. Updating the vulnerable packages, correcting the unsafe settings and replacing each exposed password or key would close these risks. Setting a waiting period for automatic updates would fix the two automatic dependency updates that take new releases at once, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code. The 20 form fields without a label need a label.
The product code is 59,032 lines, about €130,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 23 to 70, the lowest score rated Strong, the score would rise from 33 to about 40.
Code composition: what the lines of code are
Product code 71%Tests 29%
New since the last survey: 177 findings
These 177 critical or serious findings weren't in the previous survey, on 21 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 166 findings
These 166 critical or serious findings were in the previous survey, on 21 October 2026, and are gone from this one. The first 100 are listed here.
Test Quality · No assertions: createNothingFindAllClients java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/domain/BankServiceTest.java
Test Quality · No assertions: exceptionToStatus java-spring/spring-ddd-bank/src/test/java/de/beuth/knabe/spring_ddd_bank/rest_interface/ExceptionAdviceTest.java
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts
Test Coverage · No test reaches this file node/domain-driven-hexagon/database/seed.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/todo.module.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/register.command.ts
Test Coverage · No test reaches this file node/domain-driven-hexagon/database/getMigrator.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/iam.module.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/marketing.module.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/index.tsx
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/log-in.command.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/commands/delete-todo.command.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/setup-jest.js
Test Coverage · No test reaches this file node/domain-driven-hexagon/src/main.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/Header.tsx
Test Coverage · No test reaches this file node/domain-driven-hexagon/src/libs/decorators/final.decorator.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/service/mock-email.service.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/reportWebVitals.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/error-events/email-not-found.integration-event.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/errors/empty-notification-template.error.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/dto/register.dto.ts
Test Coverage · No test reaches this file node/domain-driven-hexagon/src/libs/decorators/frozen.decorator.ts
Test Coverage · No test reaches this file node/domain-driven-hexagon/database/migrate.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/dto/add-todo.dto.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/constants.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/constants.ts
Test Coverage · No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/config/index.ts
PII in the event store · PII in event: UserCreatedDomainEvent node/domain-driven-hexagon/src/modules/user/domain/events/user-created.domain-event.ts
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/service/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/service/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/service/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/experimental/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/experimental/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/experimental/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/shared/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/messaging/jms/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/messaging/jms/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/messaging/jms/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/persistence/jpa/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/persistence/jpa/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/persistence/jpa/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/routing/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/routing/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/routing/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/dto/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/dto/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/dto/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/internal/assembler/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/internal/assembler/package.html
Page structure · Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/internal/assembler/package.html
Page structure · <html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/internal/package.html
Page structure · Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/interfaces/booking/facade/internal/package.html
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€42,000 to €210,000, for 702 to 2,227 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 59,032 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 13 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2), REDACTED.
Raises the score by about 8 points · Medium effort · REDACTED Scanning
2
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ItineraryTest.java, GatewayApplicationTests.java, PayManagementApplicationTests.java.
Raises the score by about 3 points · Low effort · Test Quality
3
Resolve the 1 Banned license finding(s) in License Compliance.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Production Readiness, at 23 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 26 Domain Modelling findings · Common cause
26 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Rich vs anemic model (21 findings) · Strongly-typed ids (5 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 13 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort, because it clears the 13 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
613 modules, with 786 dependencies between them. 15 loops run through 44 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 573 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
CodelyTv.Mooc.Shared.Domain.Courses uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Mooc.Shared.Domain.Courses, while a change to CodelyTv.Mooc.Shared.Domain.Courses can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Mooc.Shared.Domain.Courses uses a module listed above it, which is the healthy direction.
CodelyTv.Shared.Domain uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Shared.Domain, while a change to CodelyTv.Shared.Domain can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Shared.Domain uses a module listed above it, which is the healthy direction.
com.alibaba.craftsman.domain.metrics uses com.alibaba.craftsman.domain.user, so a change to com.alibaba.craftsman.domain.user can break com.alibaba.craftsman.domain.metrics, while a change to com.alibaba.craftsman.domain.metrics can't break com.alibaba.craftsman.domain.user.
Position
Below the diagonal: com.alibaba.craftsman.domain.metrics uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.application.ability.user uses com.baiyan.ddd.base.model.result, so a change to com.baiyan.ddd.base.model.result can break com.baiyan.ddd.application.ability.user, while a change to com.baiyan.ddd.application.ability.user can't break com.baiyan.ddd.base.model.result.
Position
Below the diagonal: com.baiyan.ddd.application.ability.user uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.application.query uses com.baiyan.ddd.base.model.ddd, so a change to com.baiyan.ddd.base.model.ddd can break com.baiyan.ddd.application.query, while a change to com.baiyan.ddd.application.query can't break com.baiyan.ddd.base.model.ddd.
Position
Below the diagonal: com.baiyan.ddd.application.query uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.application.query uses com.baiyan.ddd.base.model.result, so a change to com.baiyan.ddd.base.model.result can break com.baiyan.ddd.application.query, while a change to com.baiyan.ddd.application.query can't break com.baiyan.ddd.base.model.result.
Position
Below the diagonal: com.baiyan.ddd.application.query uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.domain.aggregate.user.model uses com.baiyan.ddd.base.model.ddd, so a change to com.baiyan.ddd.base.model.ddd can break com.baiyan.ddd.domain.aggregate.user.model, while a change to com.baiyan.ddd.domain.aggregate.user.model can't break com.baiyan.ddd.base.model.ddd.
Position
Below the diagonal: com.baiyan.ddd.domain.aggregate.user.model uses a module listed above it, which is the healthy direction.
20→31 com.huawei.charging.domain.charge uses com.huawei.charging.domain.accountpart of a loop✕
Connections
1 pair of types, where a type in com.huawei.charging.domain.charge uses a type in com.huawei.charging.domain.account.
com.huawei.charging.domain.charge uses com.huawei.charging.domain.account, so a change to com.huawei.charging.domain.account can break com.huawei.charging.domain.charge, while a change to com.huawei.charging.domain.charge can't break com.huawei.charging.domain.account.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
com.mploed.dddwithspring.scoring.appservices uses com.mploed.dddwithspring.scoring, so a change to com.mploed.dddwithspring.scoring can break com.mploed.dddwithspring.scoring.appservices, while a change to com.mploed.dddwithspring.scoring.appservices can't break com.mploed.dddwithspring.scoring.
Position
Below the diagonal: com.mploed.dddwithspring.scoring.appservices uses a module listed above it, which is the healthy direction.
se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.event, while a change to se.citerus.cqrs.bookstore.event can't break se.citerus.cqrs.bookstore.
Position
Below the diagonal: se.citerus.cqrs.bookstore.event uses a module listed above it, which is the healthy direction.
22→32 se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore.domainpart of a loop✕
Connections
1 pair of types, where a type in se.citerus.cqrs.bookstore.event uses a type in se.citerus.cqrs.bookstore.domain.
se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.event, while a change to se.citerus.cqrs.bookstore.event can't break se.citerus.cqrs.bookstore.domain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
se.citerus.cqrs.bookstore.ordercontext.order uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.ordercontext.order, while a change to se.citerus.cqrs.bookstore.ordercontext.order can't break se.citerus.cqrs.bookstore.
Position
Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.voyage uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.domain.model.voyage, while a change to se.citerus.dddsample.domain.model.voyage can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.domain.model.voyage uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Courses.Domain uses CodelyTv.Shared.Domain.Bus.Event, so a change to CodelyTv.Shared.Domain.Bus.Event can break CodelyTv.Mooc.Courses.Domain, while a change to CodelyTv.Mooc.Courses.Domain can't break CodelyTv.Shared.Domain.Bus.Event.
Position
Below the diagonal: CodelyTv.Mooc.Courses.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Courses.Domain uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Mooc.Courses.Domain, while a change to CodelyTv.Mooc.Courses.Domain can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Mooc.Courses.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Courses.Domain uses CodelyTv.Mooc.Shared.Domain.Courses, so a change to CodelyTv.Mooc.Shared.Domain.Courses can break CodelyTv.Mooc.Courses.Domain, while a change to CodelyTv.Mooc.Courses.Domain can't break CodelyTv.Mooc.Shared.Domain.Courses.
Position
Below the diagonal: CodelyTv.Mooc.Courses.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Courses.Domain uses CodelyTv.Shared.Domain, so a change to CodelyTv.Shared.Domain can break CodelyTv.Mooc.Courses.Domain, while a change to CodelyTv.Mooc.Courses.Domain can't break CodelyTv.Shared.Domain.
Position
Below the diagonal: CodelyTv.Mooc.Courses.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.CoursesCounter.Domain uses CodelyTv.Shared.Domain.Bus.Event, so a change to CodelyTv.Shared.Domain.Bus.Event can break CodelyTv.Mooc.CoursesCounter.Domain, while a change to CodelyTv.Mooc.CoursesCounter.Domain can't break CodelyTv.Shared.Domain.Bus.Event.
Position
Below the diagonal: CodelyTv.Mooc.CoursesCounter.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.CoursesCounter.Domain uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Mooc.CoursesCounter.Domain, while a change to CodelyTv.Mooc.CoursesCounter.Domain can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Mooc.CoursesCounter.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.CoursesCounter.Domain uses CodelyTv.Mooc.Shared.Domain.Courses, so a change to CodelyTv.Mooc.Shared.Domain.Courses can break CodelyTv.Mooc.CoursesCounter.Domain, while a change to CodelyTv.Mooc.CoursesCounter.Domain can't break CodelyTv.Mooc.Shared.Domain.Courses.
Position
Below the diagonal: CodelyTv.Mooc.CoursesCounter.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Shared.Domain.Criteria uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Shared.Domain.Criteria, while a change to CodelyTv.Shared.Domain.Criteria can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Shared.Domain.Criteria uses a module listed above it, which is the healthy direction.
CodelyTv.Shared.Domain.Criteria uses CodelyTv.Shared.Domain, so a change to CodelyTv.Shared.Domain can break CodelyTv.Shared.Domain.Criteria, while a change to CodelyTv.Shared.Domain.Criteria can't break CodelyTv.Shared.Domain.
Position
Below the diagonal: CodelyTv.Shared.Domain.Criteria uses a module listed above it, which is the healthy direction.
com.alibaba.craftsman.gatewayimpl uses com.alibaba.craftsman.domain.user, so a change to com.alibaba.craftsman.domain.user can break com.alibaba.craftsman.gatewayimpl, while a change to com.alibaba.craftsman.gatewayimpl can't break com.alibaba.craftsman.domain.user.
Position
Below the diagonal: com.alibaba.craftsman.gatewayimpl uses a module listed above it, which is the healthy direction.
com.alibaba.craftsman.gatewayimpl uses com.alibaba.craftsman.domain.metrics, so a change to com.alibaba.craftsman.domain.metrics can break com.alibaba.craftsman.gatewayimpl, while a change to com.alibaba.craftsman.gatewayimpl can't break com.alibaba.craftsman.domain.metrics.
Position
Below the diagonal: com.alibaba.craftsman.gatewayimpl uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.application.query.impl uses com.baiyan.ddd.base.model.result, so a change to com.baiyan.ddd.base.model.result can break com.baiyan.ddd.application.query.impl, while a change to com.baiyan.ddd.application.query.impl can't break com.baiyan.ddd.base.model.result.
Position
Below the diagonal: com.baiyan.ddd.application.query.impl uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.application.query.impl uses com.baiyan.ddd.application.query, so a change to com.baiyan.ddd.application.query can break com.baiyan.ddd.application.query.impl, while a change to com.baiyan.ddd.application.query.impl can't break com.baiyan.ddd.application.query.
Position
Below the diagonal: com.baiyan.ddd.application.query.impl uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.interaction.controller uses com.baiyan.ddd.base.model.result, so a change to com.baiyan.ddd.base.model.result can break com.baiyan.ddd.interaction.controller, while a change to com.baiyan.ddd.interaction.controller can't break com.baiyan.ddd.base.model.result.
Position
Below the diagonal: com.baiyan.ddd.interaction.controller uses a module listed above it, which is the healthy direction.
com.baiyan.ddd.interaction.controller uses com.baiyan.ddd.application.query, so a change to com.baiyan.ddd.application.query can break com.baiyan.ddd.interaction.controller, while a change to com.baiyan.ddd.interaction.controller can't break com.baiyan.ddd.application.query.
Position
Below the diagonal: com.baiyan.ddd.interaction.controller uses a module listed above it, which is the healthy direction.
com.huawei.charging.domain.account uses com.huawei.charging.domain.charge, so a change to com.huawei.charging.domain.charge can break com.huawei.charging.domain.account, while a change to com.huawei.charging.domain.account can't break com.huawei.charging.domain.charge.
Position
Below the diagonal: com.huawei.charging.domain.account uses a module listed above it, which is the healthy direction.
se.citerus.cqrs.bookstore.domain uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.domain, while a change to se.citerus.cqrs.bookstore.domain can't break se.citerus.cqrs.bookstore.event.
Position
Below the diagonal: se.citerus.cqrs.bookstore.domain uses a module listed above it, which is the healthy direction.
se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.order.
Position
Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.handling uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.domain.model.handling, while a change to se.citerus.dddsample.domain.model.handling can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.domain.model.handling uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.handling uses se.citerus.dddsample.domain.model.voyage, so a change to se.citerus.dddsample.domain.model.voyage can break se.citerus.dddsample.domain.model.handling, while a change to se.citerus.dddsample.domain.model.handling can't break se.citerus.dddsample.domain.model.voyage.
Position
Below the diagonal: se.citerus.dddsample.domain.model.handling uses a module listed above it, which is the healthy direction.
34→37 se.citerus.dddsample.domain.model.handling uses se.citerus.dddsample.domain.model.cargopart of a loop✕
Connections
7 pairs of types, where a type in se.citerus.dddsample.domain.model.handling uses a type in se.citerus.dddsample.domain.model.cargo.
se.citerus.dddsample.domain.model.handling uses se.citerus.dddsample.domain.model.cargo, so a change to se.citerus.dddsample.domain.model.cargo can break se.citerus.dddsample.domain.model.handling, while a change to se.citerus.dddsample.domain.model.handling can't break se.citerus.dddsample.domain.model.cargo.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
CodelyTv.Mooc.Videos.Domain uses CodelyTv.Shared.Domain.Bus.Event, so a change to CodelyTv.Shared.Domain.Bus.Event can break CodelyTv.Mooc.Videos.Domain, while a change to CodelyTv.Mooc.Videos.Domain can't break CodelyTv.Shared.Domain.Bus.Event.
Position
Below the diagonal: CodelyTv.Mooc.Videos.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Videos.Domain uses CodelyTv.Shared.Domain.ValueObject, so a change to CodelyTv.Shared.Domain.ValueObject can break CodelyTv.Mooc.Videos.Domain, while a change to CodelyTv.Mooc.Videos.Domain can't break CodelyTv.Shared.Domain.ValueObject.
Position
Below the diagonal: CodelyTv.Mooc.Videos.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Videos.Domain uses CodelyTv.Mooc.Shared.Domain.Courses, so a change to CodelyTv.Mooc.Shared.Domain.Courses can break CodelyTv.Mooc.Videos.Domain, while a change to CodelyTv.Mooc.Videos.Domain can't break CodelyTv.Mooc.Shared.Domain.Courses.
Position
Below the diagonal: CodelyTv.Mooc.Videos.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Videos.Domain uses CodelyTv.Shared.Domain, so a change to CodelyTv.Shared.Domain can break CodelyTv.Mooc.Videos.Domain, while a change to CodelyTv.Mooc.Videos.Domain can't break CodelyTv.Shared.Domain.
Position
Below the diagonal: CodelyTv.Mooc.Videos.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Mooc.Videos.Domain uses CodelyTv.Shared.Domain.Criteria, so a change to CodelyTv.Shared.Domain.Criteria can break CodelyTv.Mooc.Videos.Domain, while a change to CodelyTv.Mooc.Videos.Domain can't break CodelyTv.Shared.Domain.Criteria.
Position
Below the diagonal: CodelyTv.Mooc.Videos.Domain uses a module listed above it, which is the healthy direction.
CodelyTv.Shared.Infrastructure.Persistence.Doctrine uses CodelyTv.Shared.Domain.Criteria, so a change to CodelyTv.Shared.Domain.Criteria can break CodelyTv.Shared.Infrastructure.Persistence.Doctrine, while a change to CodelyTv.Shared.Infrastructure.Persistence.Doctrine can't break CodelyTv.Shared.Domain.Criteria.
Position
Below the diagonal: CodelyTv.Shared.Infrastructure.Persistence.Doctrine uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.cargo uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.domain.model.cargo, while a change to se.citerus.dddsample.domain.model.cargo can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.domain.model.cargo uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.cargo uses se.citerus.dddsample.domain.model.voyage, so a change to se.citerus.dddsample.domain.model.voyage can break se.citerus.dddsample.domain.model.cargo, while a change to se.citerus.dddsample.domain.model.cargo can't break se.citerus.dddsample.domain.model.voyage.
Position
Below the diagonal: se.citerus.dddsample.domain.model.cargo uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.domain.model.cargo uses se.citerus.dddsample.domain.model.handling, so a change to se.citerus.dddsample.domain.model.handling can break se.citerus.dddsample.domain.model.cargo, while a change to se.citerus.dddsample.domain.model.cargo can't break se.citerus.dddsample.domain.model.handling.
Position
Below the diagonal: se.citerus.dddsample.domain.model.cargo uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.application uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.application, while a change to se.citerus.dddsample.application can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.application uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.application uses se.citerus.dddsample.domain.model.voyage, so a change to se.citerus.dddsample.domain.model.voyage can break se.citerus.dddsample.application, while a change to se.citerus.dddsample.application can't break se.citerus.dddsample.domain.model.voyage.
Position
Below the diagonal: se.citerus.dddsample.application uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.application uses se.citerus.dddsample.domain.model.handling, so a change to se.citerus.dddsample.domain.model.handling can break se.citerus.dddsample.application, while a change to se.citerus.dddsample.application can't break se.citerus.dddsample.domain.model.handling.
Position
Below the diagonal: se.citerus.dddsample.application uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.application uses se.citerus.dddsample.domain.model.cargo, so a change to se.citerus.dddsample.domain.model.cargo can break se.citerus.dddsample.application, while a change to se.citerus.dddsample.application can't break se.citerus.dddsample.domain.model.cargo.
Position
Below the diagonal: se.citerus.dddsample.application uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.config uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.config, while a change to se.citerus.dddsample.config can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.config uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.config uses se.citerus.dddsample.domain.model.voyage, so a change to se.citerus.dddsample.domain.model.voyage can break se.citerus.dddsample.config, while a change to se.citerus.dddsample.config can't break se.citerus.dddsample.domain.model.voyage.
Position
Below the diagonal: se.citerus.dddsample.config uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.config uses se.citerus.dddsample.domain.model.handling, so a change to se.citerus.dddsample.domain.model.handling can break se.citerus.dddsample.config, while a change to se.citerus.dddsample.config can't break se.citerus.dddsample.domain.model.handling.
Position
Below the diagonal: se.citerus.dddsample.config uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.config uses se.citerus.dddsample.domain.model.cargo, so a change to se.citerus.dddsample.domain.model.cargo can break se.citerus.dddsample.config, while a change to se.citerus.dddsample.config can't break se.citerus.dddsample.domain.model.cargo.
Position
Below the diagonal: se.citerus.dddsample.config uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.config uses se.citerus.dddsample.application, so a change to se.citerus.dddsample.application can break se.citerus.dddsample.config, while a change to se.citerus.dddsample.config can't break se.citerus.dddsample.application.
Position
Below the diagonal: se.citerus.dddsample.config uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.interfaces uses se.citerus.dddsample.domain.model.location, so a change to se.citerus.dddsample.domain.model.location can break se.citerus.dddsample.interfaces, while a change to se.citerus.dddsample.interfaces can't break se.citerus.dddsample.domain.model.location.
Position
Below the diagonal: se.citerus.dddsample.interfaces uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.interfaces uses se.citerus.dddsample.domain.model.voyage, so a change to se.citerus.dddsample.domain.model.voyage can break se.citerus.dddsample.interfaces, while a change to se.citerus.dddsample.interfaces can't break se.citerus.dddsample.domain.model.voyage.
Position
Below the diagonal: se.citerus.dddsample.interfaces uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.interfaces uses se.citerus.dddsample.domain.model.handling, so a change to se.citerus.dddsample.domain.model.handling can break se.citerus.dddsample.interfaces, while a change to se.citerus.dddsample.interfaces can't break se.citerus.dddsample.domain.model.handling.
Position
Below the diagonal: se.citerus.dddsample.interfaces uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.interfaces uses se.citerus.dddsample.domain.model.cargo, so a change to se.citerus.dddsample.domain.model.cargo can break se.citerus.dddsample.interfaces, while a change to se.citerus.dddsample.interfaces can't break se.citerus.dddsample.domain.model.cargo.
Position
Below the diagonal: se.citerus.dddsample.interfaces uses a module listed above it, which is the healthy direction.
se.citerus.dddsample.interfaces uses se.citerus.dddsample.application, so a change to se.citerus.dddsample.application can break se.citerus.dddsample.interfaces, while a change to se.citerus.dddsample.interfaces can't break se.citerus.dddsample.application.
Position
Below the diagonal: se.citerus.dddsample.interfaces uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
747
High / Critical
A03:2025 — Software Supply Chain Failures
289
High / Critical
A05:2025 — Injection
63
High / Critical
A07:2025 — Authentication Failures
15
High / Critical
Roadmap
Top priorities: Resolve the 13 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2), REDACTED; Improve Test Distribution — currently 6.4/10; Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ItineraryTest.java, GatewayApplicationTests.java, PayManagementApplicationTests.java.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 13 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2), REDACTED.
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ItineraryTest.java, GatewayApplicationTests.java, PayManagementApplicationTests.java.
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 — 354
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 — 1059
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 — 315
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 106 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 106 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1691 of 1728 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .java, .php, and our analyzer cannot run the .java, .php 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 (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) 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, or Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 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) (.php, .ts) 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.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .php, and the built-in reliability runner cannot re-run the .php test suite(s) — so reliability was not measured for the repository as a whole. The 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) suite(s) did re-run, and came back with 0 flaky across 2 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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: it declares a published package (reinvent-wheels/udma/build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D26 Project Cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Project size and spread are measured over build units whose source a code model reads. This repository's .php source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Reinvent-wheels/udma/scripts/chart/templates/deployment.yaml:3 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 93 further occurrence(s) are not listed individually; the score already reflects all 133.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
AX1 Captive dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository also uses Symfony DependencyInjection, whose singleton and shorter-lived bindings can capture one another the same way, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that those bindings are free of it.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — mooc_mysql Pulling shared_rabbitmq Pulling backoffice_elasticsearch Pulling shared_prometheus Pulling backoffice_elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden mooc_mysql Error context canceled shared_rabbitmq Error context canceled shared_prometheus Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: backoffice_elasticsearch Pulling shared_rabbitmq Pulling shared_prometheus Pulling mooc_mysql Pulling backoffice_elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden shared_rabbitmq Error context canceled mooc_mysql Error context canceled shared_prometheus Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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.
DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
ES3 PII in the event store — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Java is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Entity.wrapperReflect (cyclomatic 25), Entity.wrapperReflect (cyclomatic 25). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
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.
Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with Entity.wrapperReflect (cognitive 75), Entity.wrapperReflect (cognitive 75), Entity.toJsonStringAuto (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
Do you agree with this assessment?
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.
Resolve the 1 TooManyMethods finding(s) in God Classes — start with RealEstateProperty.java. — One of this dimension's main actionable groups (1 warning-level).
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.
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.
56 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. 5 of the 59 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 31 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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).
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).
Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Financing.java, Application.java, ResourceBag.java. — One of this dimension's main actionable groups (4 warning-level).
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.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
53 production modules (Gradle+Maven+npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 3 module(s) off the main sequence, with abstractness counted on 25 of the 53 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: craftsman-client · ×2
Off the main sequence: sharedmodel
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with ApplicantAggregate.java, GlobalExceptionHandler.java, LFThrowable.java. — One of this dimension's main actionable groups (6 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
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
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.
Do you agree with this assessment?
D10 · Test Quality8.7 / 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.
3 skipped (3 with a documented reason), 25 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) (.php, .ts) 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 · ×22java-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: reinvent-wheels/spring-rarf/api · ×4reinvent-wheels/spring-rarf/api/src/test/java/wx/user/LoginControllerIntegrationTest.java:45
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).
Resolve the 22 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 (22 warning-level).
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).
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.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
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.
Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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.
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.
Resolve the 13 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
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.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
1 of 126 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 72 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 259 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. 5 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 7 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. 2 name a copyleft licence without stating its version (e.g. "GNU Lesser General Public Licence"), which this policy bans only at specific versions; they are reported here and not charged, because guessing the version would either accuse an LGPL-2.1 artifact or clear an LGPL-3.0 one.
Banned license: mysql:mysql-connector-java
What to do
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
11 deducted task-comment markers across 59032 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.
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).
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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 34 document(s) read across 5 unit(s).
Documentation: no build, run or usage example · ×2node/ddd-hexagonal-cqrs-es-eda/envoy/README.md:1
What to do
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namesnode/domain-driven-hexagon/src/libs/utils/convert-props-to-object.util.ts:31
What to do
Resolve the 2 redundant comment finding(s) in Comment Value — start with bootstrap-datepicker.js, index.ts. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 43 build units (Go, Gradle, Maven, npm) flagged as possibly oversized/incoherent. This repository's .php source was read by no build unit, so this covers part of the tree, not all of it.
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. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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).
63 finding(s): 0 critical, 4 high, 53 medium, 6 low. semgrep hit a parse error in 87 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), `php/php-ddd-example/src/Analytics/DomainEvents/Application/Store/DomainEventStorer.php` (line 16), `php/php-ddd-example/src/Analytics/DomainEvents/Application/Store/StoreDomainEventOnOccurred.php` (line 16), … (+82 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 135 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (70), REDACTED (60), REDACTED (5). — One of this dimension's main actionable groups (135 issue-level).
Resolve the 49 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (33), REDACTED (13), REDACTED (2). — One of this dimension's main actionable groups (49 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 545 Medium 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).
Resolve the 56 High 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).
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.
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.
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.
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.
0/23 workload(s) run every container under a seccomp profile; 0/23 declare an AppArmor/SELinux profile.
No seccomp profile · ×23REDACTED:14
What to do
Resolve the 23 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (23 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 2 end-of-life framework(s), read from 27 platform declaration(s) and 263 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
End-of-life framework: Spring Boot 1 · ×2REDACTED:1
What to do
Resolve the 2 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED, build.gradle. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.0 / 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. (×2) — 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.
Do you agree with this assessment?
AC2 · Forms & labels5.4 / 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. — REDACTED:58
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×13) — 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. — java-spring/2014~dddsample-core/src/main/resources/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.
Do you agree with this assessment?
AC3 · Page structure3.0 / 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, REDACTED:2, REDACTED: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"). (×13) — REDACTED:2, REDACTED:2, java-spring/2014~dddsample-core/src/main/java/com/pathfinder/api/package.html:1, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — 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>. (×11) — 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.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — 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.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.github-corner:hover .octo-arm` moves (`animation: octocat-wave 560ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:55
`.github-corner .octo-arm` moves (`animation: octocat-wave 560ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:82
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×4) — php/php-ddd-example/apps/backoffice/frontend/templates/master.html.twig:17, php/php-ddd-example/apps/backoffice/frontend/templates/pages/courses/partials/list_courses.html.twig:10, php/php-ddd-example/apps/backoffice/frontend/templates/pages/courses/partials/list_courses.html.twig:16, …
`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. — java-spring/2014~dddsample-core/src/main/resources/static/style.css:5
`input.button` sets color: #fff on background-color: #ccc — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/style.css:158
`.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. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap-datepicker.css:240
`.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3176
`.btn-success:focus, .btn-success.focus` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3182
`.btn-success:hover` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3187
`.btn-success:active, .btn-success.active, .open > .dropdown-toggle.btn-success` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3194
`.btn-success .badge` sets color: #5cb85c on background-color: #fff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3229
`.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. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3233
`.btn-info:focus, .btn-info.focus` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3239
`.btn-info:hover` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3244
`.btn-info:active, .btn-info.active, .open > .dropdown-toggle.btn-info` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3251
`.btn-info:active:hover, .btn-info.active:hover, .open > .dropdown-toggle.btn-info:hover, .btn-info:active:focus, .btn-info.active:focus, .open > .dropdown-toggle.btn-info:focus, .btn-info:active.focus, .btn-info.active.focus, .open > .dropdown-toggle.btn-info.focus` sets color: #fff on background-color: #269abc — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3264
`.btn-info .badge` sets color: #5bc0de on background-color: #fff — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3286
`.btn-warning:active, .btn-warning.active, .open > .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ec971f — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3308
`.btn-warning:active:hover, .btn-warning.active:hover, .open > .dropdown-toggle.btn-warning:hover, .btn-warning:active:focus, .btn-warning.active:focus, .open > .dropdown-toggle.btn-warning:focus, .btn-warning:active.focus, .btn-warning.active.focus, .open > .dropdown-toggle.btn-warning.focus` sets color: #fff on background-color: #d58512 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3321
`a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5344
`a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5373
`a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5402
`a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5431
`*` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.css:6
`.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3521
`.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3576
`.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3595
`.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3720
`.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:4310
`.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5882
`.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5916
`.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:6357
`.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3503
`.progress-bar` moves (`transition: width .6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5151
`.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5165
`.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5887
`.carousel-inner > .item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:6253
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.
Do you agree with this assessment?
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 61 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. — node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:5
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.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`AccountGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (accountMap; e.g. `accountMap` in `getAccount` at line 22). — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/infrastructure/AccountGatewayImpl.java:15
`SessionGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (sessionMap; e.g. `sessionMap` in `create` at line 16). — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/infrastructure/SessionGatewayImpl.java:12
`SyncContext` is a singleton (@Configuration: the container shares one instance across every request thread) but mutates instance state outside any lock (stopTime, currentStepIndex; e.g. `stopTime` in `responseHandler` at line 165). — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/context/SyncContext.java:26
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`ms-java-spring-app:realworld:application` is a Application project but references `ms-java-spring-app:realworld:infra`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
`craftsman-app` is a Application project but references `craftsman-infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
`application-services` is a Application project but references `adapters-output`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation2.5 / 10Weak✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`todo-frontend` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:6
`todo-frontend` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:7
`todo-frontend` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:8
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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.
`Cargo` references the aggregate root `Delivery` directly (via `delivery`) — hold its `DeliveryId` 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.
`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.
`Delivery` references the aggregate root `Voyage` directly (via `currentVoyage`) — hold its `VoyageId` instead.
`Delivery` references the aggregate root `Location` directly (via `lastKnownLocation`) — 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.
Do you agree with this assessment?
DM10 · One transaction, one aggregate9.4 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
`BankService.deleteClient` saves `AccountAccess`, `Client` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/BankService.java:81
`Client.createAccount` saves `Account`, `AccountAccess` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:85
`UnitOfWork.persist` saves `ShipManifest`, `Order` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:70
`UnitOfWork.persist` saves `ITaskRepository`, `ICartonRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:34
`UnitOfWork.persist` saves `Order`, `TaskOfOrderPending`, `CartonBag` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:40
`SampleDataGenerator.loadHibernateData` saves `Location`, `Voyage`, `Cargo`, `HandlingEvent` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/sampledata/SampleDataGenerator.java:64
`1.doInTransactionWithoutResult` saves `Location`, `Voyage`, `Cargo`, `HandlingEvent` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/sampledata/SampleDataGenerator.java:68
What to do
Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
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 / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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.
Do you agree with this assessment?
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.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`UserLoggedInDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:12
`TodoCompletionsIncrementedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/events/todo-completions-incremented.event.ts:13
`TodoAddedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-added.event.ts:13
`TodoCompletedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:12
`WalletCreatedDomainEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — node/domain-driven-hexagon/src/modules/wallet/domain/events/wallet-created.domain-event.ts:4
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
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
`UserEntity` 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. — node/domain-driven-hexagon/src/modules/user/domain/user.entity.ts:15
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
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.
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.
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
`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
`HandlingEventRepositoryJPA` is a repository over `HandlingEvent`, 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 `HandlingEvent` through its owning aggregate instead. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/persistence/jpa/HandlingEventRepositoryJPA.java:16
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.
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.
Do you agree with this assessment?
ES2 · Immutable events4.1 / 10Weak✓ 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.
This persisted event exposes settable member(s) (id, voyage, location, cargo, completionTime, registrationTime, type) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. — java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/handling/HandlingEvent.java:34
This persisted event exposes settable member(s) (metadata, aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. (×3) — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:8, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-updated-email.event.ts:8, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/events/todo-completions-incremented.event.ts:9
This persisted event exposes settable member(s) (aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-added.event.ts:10
This persisted event exposes settable member(s) (aggregateId, metadata) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. (×4) — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-modified-title.event.ts:9, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:9, node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-uncompleted.event.ts:9, …
What to do
Make every event type immutable: records with init-only properties, or classes with readonly fields set only in the constructor.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×13) — java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestContractDataImporter.java:14, java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestHttpClient.java:17, java-spring/2014~bookstore-cqrs-example/product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestHttpClient.java:17, …
What to do
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
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
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 27 of 77 project(s) that lack one — worth up to 0.7 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Do you agree with this assessment?
P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
278/335 types (83%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
No explicit version was found for the Maven/Gradle library declared by `build.gradle`. This check read a `<version>` in REDACTED, or `version` in build.gradle(.kts) or gradle.properties, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes. (×3) — reinvent-wheels/udma/udma/starter/build.gradle, reinvent-wheels/udma/udma/starter/autoconfigure/build.gradle, reinvent-wheels/udma/udma/starter/starters/build.gradle
What to do
Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes.
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.
Only 32/43 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `java-spring/2020~cola/craftsman/craftsman-adapter`, `java-spring/2020~yanglao-system/gateway-management`, `java-spring/2020~yanglao-system/order-management`, `java-spring/2020~yanglao-system/pay-management`, `java-spring/2020~yanglao-system/room-management` and 6 more.
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/query-handlers/get-todos.handler.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/query-handlers/get-todos.handler.ts:42
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-deleted-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-deleted-publish-pubsub.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-modified-title-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-modified-title-publish-pubsub.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-uncompleted-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-uncompleted-publish-pubsub.handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/add-todo.handler.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/add-todo.handler.ts:50
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:54
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts:49
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:53
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts:31
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts:36
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/todo-completed.integration-handler.ts` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/todo-completed.integration-handler.ts:43
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:46
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts:46
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:50
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/create-user.command-handler.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/create-user.command-handler.ts:51
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:55
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/send-email.command-handler.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/send-email.command-handler.ts:40
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:38
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:48
`node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:47
`node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/service/mock-email.service.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/service/mock-email.service.ts:13
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/authentication.controller.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/authentication.controller.ts:55
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 162 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:162
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 172 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:172
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:185
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 198 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:198
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 212 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:212
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 240 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:240
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 281 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:281
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 310 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:310
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 338 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:338
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 366 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:366
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 397 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:397
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 427 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:427
`node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts` reports through `console.*` at line 474 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:474
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, `gradle`, `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
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.
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.
Do you agree with this assessment?
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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`WebClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — java-spring/2020~yanglao-system/gateway-management/src/main/java/com/yanglao/gateway/RoomHandler.java:16, java-spring/2020~yanglao-system/gateway-management/src/main/java/com/yanglao/gateway/RoomHandler.java:21
`new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/OrderApplication.java:19, java-spring/2020~yanglao-system/security-management/src/main/java/com/yanglao/security/SecurityApplication.java:21, java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/InputAdaptersConfiguration.java:19
`.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — reinvent-wheels/udma/udma/core/src/main/java/icu/ngte/udma/core/tools/resourcebundle/UTF8Control.java:25
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema. (×7) — java-spring/spring-ddd-bank/src/main/resources/application.properties:21, REDACTED:12, REDACTED:58, …
What to do
Turn off Hibernate ddl-auto in production and let the versioned migrations own the schema.
Do you agree with this assessment?
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.readFileSync` in `callback to fs.readdir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — node/domain-driven-hexagon/database/seed.ts:22
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.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.
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.
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
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
java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:295 · java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:309 — 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. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:295
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
node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:82 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:106 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:82
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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. — java-spring/2014~dddsample-core/src/main/resources/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
update has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:731
_setDate has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1270
isEmpty has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — node/domain-driven-hexagon/src/libs/guard.ts:5
(top-level) has cyclomatic complexity 11 and cognitive complexity 10; 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/domain-driven-hexagon/src/libs/ddd/entity.base.ts:1
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files9.5 / 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.
java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js has 1854 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1
node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts has 491 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:1
node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test 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:1, node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:1, node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
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 `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.1 / 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 10 application, 6 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 (10 application, 6 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 (10 application, 6 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 (10 application, 6 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. (×5) — node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/change-email.command.ts:7, 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, …
Nothing ultimately consumes this binding: its only referrer is the re-export in node/domain-driven-hexagon/src/libs/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in node/domain-driven-hexagon/src/libs/types/index.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — node/domain-driven-hexagon/src/libs/types/non-function-properties.type.ts:9, node/domain-driven-hexagon/src/libs/types/require-one.type.ts:4, node/domain-driven-hexagon/src/libs/types/require-one.type.ts:13
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:11, node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts: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.
Do you agree with this assessment?
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:7
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. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`//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. 20 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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`loginWithEmailPassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:67
`registerWithEmailPassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:83
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.7 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1180, java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1181
`wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:5114
`value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:5322
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java:55, reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java:53, java-spring/2020~yanglao-system/security-management/src/main/java/com/yanglao/security/application/LoginApplicationService.java:32
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/ApplicationContextHelper.java:22, java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:844, java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1422, …
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 111 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/spring-ddd-credit/scoring/application-services/src/main/java/com/mploed/dddwithspring/scoring/appservices/ScoringApplicationService.java:111
`info` at line 121 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/spring-ddd-credit/scoring/application-services/src/main/java/com/mploed/dddwithspring/scoring/appservices/ScoringApplicationService.java:121
`info` at line 62 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/feeds/CreditAgencyPoller.java:62
`info` at line 28 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/start/src/main/java/com/alibaba/craftsman/Application.java:28
`debug` at line 59 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:59
`error` at line 89 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:89
`error` at line 121 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:121
`warn` at line 42 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/UserProfileGatewayImpl.java:42
`debug` at line 43 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/MetricItem.java:43
`debug` at line 52 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/techinfluence/ATAMetricItem.java:52
`debug` at line 58 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/techinfluence/ATAMetricItem.java:58
`debug` at line 28 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/appquality/AppMetricItem.java:28
`debug` at line 15 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/BasicChargeRule.java:15
`debug` at line 20 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FamilyChargeRule.java:20
`debug` at line 17 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:17
`debug` at line 24 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:24
`debug` at line 31 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:31
`debug` at line 73 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:73
`debug` at line 41 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/ChargeServiceImpl.java:41
`debug` at line 47 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/ChargeServiceImpl.java:47
`debug` at line 21 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:21
`debug` at line 29 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:29
`debug` at line 37 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:37
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: 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 — 35 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.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — mooc_mysql Pulling shared_rabbitmq Pulling backoffice_elasticsearch Pulling shared_prometheus Pulling backoffice_elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden mooc_mysql Error context canceled shared_rabbitmq Error context canceled shared_prometheus Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: backoffice_elasticsearch Pulling shared_rabbitmq Pulling shared_prometheus Pulling mooc_mysql Pulling backoffice_elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden shared_rabbitmq Error context canceled mooc_mysql Error context canceled shared_prometheus Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
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.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go, Java, JavaScript, PHP, html not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D25 ADR Conformance — no ADRs to check
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.
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
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 event handler(s); 2 CQRS handler(s)
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Fold determinism — no Apply/When folds detected — fold-determinism check not applicable
ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
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.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
<html> without a lang 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 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").
<html> without a lang java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/voyage/package.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· <input> without a programmatic label · ×12
<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 REDACTED: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/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· Document without a <title> · ×11
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>.
Document without a <title> java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/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/voyage/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>.
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: Cargo.delivery — `Cargo` references the aggregate root `Delivery` directly (via `delivery`) — hold its `DeliveryId` 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: 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.
Aggregate holds a reference to another aggregate: Delivery.currentVoyage — `Delivery` references the aggregate root `Voyage` directly (via `currentVoyage`) — hold its `VoyageId` instead.
Aggregate holds a reference to another aggregate: Delivery.lastKnownLocation — `Delivery` references the aggregate root `Location` directly (via `lastKnownLocation`) — hold its `LocationId` instead.
Mutable event: HandlingEvent java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/handling/HandlingEvent.java:34— This persisted event exposes settable member(s) (id, voyage, location, cargo, completionTime, registrationTime, type) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: UserLoggedInDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:8— This persisted event exposes settable member(s) (metadata, aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: UserUpdatedEmailDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-updated-email.event.ts:8— This persisted event exposes settable member(s) (metadata, aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoCompletionsIncrementedDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/events/todo-completions-incremented.event.ts:9— This persisted event exposes settable member(s) (metadata, aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoAddedDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-added.event.ts:10— This persisted event exposes settable member(s) (aggregateId) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoModifiedTitleDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-modified-title.event.ts:9— This persisted event exposes settable member(s) (aggregateId, metadata) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoCompletedDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:9— This persisted event exposes settable member(s) (aggregateId, metadata) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoUncompletedDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-uncompleted.event.ts:9— This persisted event exposes settable member(s) (aggregateId, metadata) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: TodoDeletedDomainEvent node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-deleted.event.ts:10— This persisted event exposes settable member(s) (aggregateId, metadata) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
AC2 · Forms & labels· <select> without a programmatic label · ×7
<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 REDACTED: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 REDACTED: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 REDACTED: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.
Dependency-rule violation: ms-java-spring-app:realworld:application (Application) → ms-java-spring-app:realworld:infra (Infrastructure) — `ms-java-spring-app:realworld:application` is a Application project but references `ms-java-spring-app:realworld:infra`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Dependency-rule violation: craftsman-app (Application) → craftsman-infrastructure (Infrastructure) — `craftsman-app` is a Application project but references `craftsman-infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Dependency-rule violation: application-services (Application) → adapters-output (Infrastructure) — `application-services` is a Application project but references `adapters-output`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
AX8 · Test isolation· Production project references a test package · ×3
Production project references a test package: todo-frontend → @testing-library/jest-dom node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:6— `todo-frontend` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`.
Production project references a test package: todo-frontend → @testing-library/react node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:7— `todo-frontend` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`.
Production project references a test package: todo-frontend → @testing-library/user-event node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:8— `todo-frontend` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `todo-frontend` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`.
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.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
AC1 · Text alternatives· <img> without a text alternative · ×2
<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/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.
AC2 · Forms & labels· Link with no accessible name · ×1
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.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<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.
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.
Banned license: mysql:mysql-connector-java — `mysql:mysql-connector-java` 8.0.20 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
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.
Unlisted import 'uuid' node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:11— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
D30 · Dependency Vulnerabilities· Medium CVE · ×80
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
+ 55 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:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/LoginForm.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-write.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/notification-template.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/repository/user-write.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/frontend/src/components/TodoPanel.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/authentication.controller.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/repository/todo-read.repository.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/api.module.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.rest.controller.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-added.integration-handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-modified-title.integration-handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-completed.integration-handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-deleted.integration-handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/api/pub-sub-handlers/todo-uncompleted.integration-handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/todo/todo/todo.module.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-added.integration-event.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/contracts/integration-events/todo-modified-title.integration-event.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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 was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, 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.
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.
Anemic entity: UserEntity node/domain-driven-hexagon/src/modules/user/domain/user.entity.ts:15— `UserEntity` 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.
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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, 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 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 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>.
Page without a main landmark java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/domain/model/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/voyage/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: 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.
Repository for a non-root entity: HandlingEventRepositoryJPA → HandlingEvent java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/persistence/jpa/HandlingEventRepositoryJPA.java:16— `HandlingEventRepositoryJPA` is a repository over `HandlingEvent`, 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 `HandlingEvent` through its owning aggregate instead.
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.
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: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: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 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×9
Focus outline removed in CSS without a :focus replacement node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.css:6— `*` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3521— `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3576— `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3595— `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3720— `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:4310— `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5882— `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5916— `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:6357— `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard REDACTED:55— `.github-corner:hover .octo-arm` moves (`animation: octocat-wave 560ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:82— `.github-corner .octo-arm` moves (`animation: octocat-wave 560ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3503— `.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5151— `.progress-bar` moves (`transition: width .6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5165— `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5887— `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:6253— `.carousel-inner > .item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
P8 · Schema migrations· Schema created by Hibernate ddl-auto outside the migrations · ×7
Schema created by Hibernate ddl-auto outside the migrations java-spring/spring-ddd-bank/src/main/resources/application.properties:21— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations REDACTED:12— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations REDACTED:58— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations REDACTED:58— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations REDACTED:58— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations REDACTED:58— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Schema created by Hibernate ddl-auto outside the migrations java-spring/2020~cola/charge/src/main/resources/application.yml:11— This repository versions its schema (Flyway), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Flyway own the schema.
Swallowed exception (empty catch) java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/ApplicationContextHelper.java:22— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:844— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1422— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:3744— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:4077— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:5329— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:8522— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
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/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: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/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.
Low cohesion: ApplicantAggregateBuilder (LCOM4 6) java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/applicant/ApplicantAggregate.java:37— ApplicantAggregateBuilder's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: GlobalExceptionHandler (LCOM4 5) java-spring/2021~baiyan_lou~ddd-demo/baiyan-ddd-interaction/src/main/java/com/baiyan/ddd/interaction/config/GlobalExceptionHandler.java:27— GlobalExceptionHandler's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 5) reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/throwable/LFThrowable.java:35— Builder's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 5) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/throwable/RARFThrowable.java:35— Builder's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FinancialSituationBuilder (LCOM4 4) java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/financialSituation/FinancialSituationAggregate.java:38— FinancialSituationBuilder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 4) java-spring/spring-ddd-credit/scoring/aggregates/src/main/java/com/mploed/dddwithspring/scoring/scoringResult/ScoringResultAggregate.java:28— Builder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Outbound HTTP without resilience java-spring/2020~yanglao-system/gateway-management/src/main/java/com/yanglao/gateway/RoomHandler.java:16— `WebClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience java-spring/2020~yanglao-system/gateway-management/src/main/java/com/yanglao/gateway/RoomHandler.java:21— `WebClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience java-spring/2020~yanglao-system/order-management/src/main/java/com/yanglao/orders/OrderApplication.java:19— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience java-spring/2020~yanglao-system/security-management/src/main/java/com/yanglao/security/SecurityApplication.java:21— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/InputAdaptersConfiguration.java:19— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience reinvent-wheels/udma/udma/core/src/main/java/icu/ngte/udma/core/tools/resourcebundle/UTF8Control.java:25— `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Low contrast colour pair in CSS (2.5:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3176— `.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3229— `.btn-success .badge` sets color: #5cb85c on background-color: #fff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3239— `.btn-info:focus, .btn-info.focus` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3244— `.btn-info:hover` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3251— `.btn-info:active, .btn-info.active, .open > .dropdown-toggle.btn-info` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Duplicated block (13 lines × 2 locations) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:295— java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:295 · java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:309 — 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/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.
D10 · Test Quality· Test project verifies nothing · ×4
Test project verifies nothing: reinvent-wheels/spring-rarf/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 `reinvent-wheels/spring-rarf/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.
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: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/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.
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.
Duplicated block (8 lines × 2) php/php-ddd-example/src/Mooc/Shared/Infrastructure/Doctrine/DbalTypesSearcher.php:34— php/php-ddd-example/src/Mooc/Shared/Infrastructure/Doctrine/DbalTypesSearcher.php:34-41 | php/php-ddd-example/src/Mooc/Shared/Infrastructure/Doctrine/DoctrinePrefixesSearcher.php:33-40 — 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.
DM10 · One transaction, one aggregate· One operation mutates 2 aggregates · ×4
One operation mutates 2 aggregates: BankService.deleteClient java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/BankService.java:81— `BankService.deleteClient` saves `AccountAccess`, `Client` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: Client.createAccount java-spring/spring-ddd-bank/src/main/java/de/beuth/knabe/spring_ddd_bank/domain/Client.java:85— `Client.createAccount` saves `Account`, `AccountAccess` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: UnitOfWork.persist java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:70— `UnitOfWork.persist` saves `ShipManifest`, `Order` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: UnitOfWork.persist java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:34— `UnitOfWork.persist` saves `ITaskRepository`, `ICartonRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1180— `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:1181— `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:5114— `wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped java-spring/2014~dddsample-core/src/main/resources/static/js/jquery-2.1.4.js:5322— `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Low contrast Tailwind colour pair (3.8:1) php/php-ddd-example/apps/backoffice/frontend/templates/master.html.twig:17— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) php/php-ddd-example/apps/backoffice/frontend/templates/pages/courses/partials/list_courses.html.twig:10— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) php/php-ddd-example/apps/backoffice/frontend/templates/pages/courses/partials/new_course_form.html.twig:43— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast colour pair in CSS (3.4:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3182— `.btn-success:focus, .btn-success.focus` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3187— `.btn-success:hover` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3194— `.btn-success:active, .btn-success.active, .open > .dropdown-toggle.btn-success` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Stateful singleton: AccountGatewayImpl java-spring/2020~cola/charge/src/main/java/com/huawei/charging/infrastructure/AccountGatewayImpl.java:15— `AccountGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (accountMap; e.g. `accountMap` in `getAccount` at line 22).
Stateful singleton: SessionGatewayImpl java-spring/2020~cola/charge/src/main/java/com/huawei/charging/infrastructure/SessionGatewayImpl.java:12— `SessionGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (sessionMap; e.g. `sessionMap` in `create` at line 16).
Stateful singleton: SyncContext reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/context/SyncContext.java:26— `SyncContext` is a singleton (@Configuration: the container shares one instance across every request thread) but mutates instance state outside any lock (stopTime, currentStepIndex; e.g. `stopTime` in `responseHandler` at line 165).
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.
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.
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.
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.
Duplicated block (5 lines × 2) php/php-ddd-example/src/Backoffice/Courses/Application/SearchAll/AllBackofficeCoursesSearcher.php:26— php/php-ddd-example/src/Backoffice/Courses/Application/SearchAll/AllBackofficeCoursesSearcher.php:26-30 | php/php-ddd-example/src/Backoffice/Courses/Application/SearchByCriteria/BackofficeCoursesByCriteriaSearcher.php:31-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (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.
Swallowed exception (caught, then discarded) reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/utils/HJSONObject.java:55— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/utils/HJSONObject.java:53— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) java-spring/2020~yanglao-system/security-management/src/main/java/com/yanglao/security/application/LoginApplicationService.java:32— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Low 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.
Low contrast colour pair in CSS (2.1:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3286— `.btn-info .badge` sets color: #5bc0de on background-color: #fff — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
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.
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 (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.
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.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.
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.
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.
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.
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.
Duplicated block (7 lines × 3) php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php:37— php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php:37-43 | php/php-ddd-example/apps/backoffice/frontend/src/BackofficeFrontendKernel.php:37-43 | php/php-ddd-example/apps/mooc/backend/src/MoocBackendKernel.php:37-43 — before extracting anything, compare `php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php` and `php/php-ddd-example/apps/backoffice/frontend/src/BackofficeFrontendKernel.php` as WHOLE FILES: 84% 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 2 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 `php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) 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.
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.
End-of-life framework: Spring Boot 1 REDACTED:1— REDACTED depends on `org.springframework.boot` at a version that pins Spring Boot 1, and Spring Boot 1.x, open-source support ended 2019-08-01. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
End-of-life framework: Spring Boot 2 java-spring/2014~dddsample-core/build.gradle:1— java-spring/2014~dddsample-core/build.gradle depends on `org.springframework.boot` at a version that pins Spring Boot 2, and Spring Boot 2.x, open-source support ended 2023-11-24. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
Off the main sequence: craftsman-client — craftsman-client: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: craftsman-domain — craftsman-domain: abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
DM10 · One transaction, one aggregate· One operation mutates 4 aggregates · ×2
One operation mutates 4 aggregates: SampleDataGenerator.loadHibernateData java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/sampledata/SampleDataGenerator.java:64— `SampleDataGenerator.loadHibernateData` saves `Location`, `Voyage`, `Cargo`, `HandlingEvent` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 4 aggregates: 1.doInTransactionWithoutResult java-spring/2014~dddsample-core/src/main/java/se/citerus/dddsample/infrastructure/sampledata/SampleDataGenerator.java:68— `1.doInTransactionWithoutResult` saves `Location`, `Voyage`, `Cargo`, `HandlingEvent` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
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.
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.
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.
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.
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 (10 application, 6 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 (10 application, 6 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
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: loginWithEmailPassword node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:67— `loginWithEmailPassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`.
Async function without AbortSignal: registerWithEmailPassword node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:83— `registerWithEmailPassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`.
AC2 · Forms & labels· <fieldset> without a <legend> · ×1
<fieldset> without a <legend> 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 · ×1
Heading level jumps from h2 to h5 REDACTED:33— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast Tailwind colour pair (2.3:1) php/php-ddd-example/apps/backoffice/frontend/templates/pages/courses/partials/list_courses.html.twig:16— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low 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.
Low contrast colour pair in CSS (1.6:1) java-spring/2014~dddsample-core/src/main/resources/static/style.css:158— `input.button` sets color: #fff on background-color: #ccc — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.3:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:3308— `.btn-warning:active, .btn-warning.active, .open > .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ec971f — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5344— `a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5373— `a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5402— `a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) java-spring/2014~dddsample-core/src/main/resources/static/css/bootstrap.css:5431— `a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung node/ddd-hexagonal-cqrs-es-eda/frontend/package.json:5— 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 61 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Duplicated block (6 lines × 3) php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php:22— php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php:22-27 | php/php-ddd-example/apps/backoffice/frontend/src/BackofficeFrontendKernel.php:22-27 | php/php-ddd-example/apps/mooc/backend/src/MoocBackendKernel.php:22-27 — before extracting anything, compare `php/php-ddd-example/apps/backoffice/backend/src/BackofficeBackendKernel.php` and `php/php-ddd-example/apps/backoffice/frontend/src/BackofficeFrontendKernel.php` as WHOLE FILES: 84% 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 2 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.
DM10 · One transaction, one aggregate· One operation mutates 3 aggregates · ×1
One operation mutates 3 aggregates: UnitOfWork.persist java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/wms/application/UnitOfWork.java:40— `UnitOfWork.persist` saves `Order`, `TaskOfOrderPending`, `CartonBag` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
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.
Sync-over-async blocking node/domain-driven-hexagon/database/seed.ts:22— `fs.readFileSync` in `callback to fs.readdir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Duplicated block (12 lines × 2 locations) node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:82— node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:82 · node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/iam/iam/repository/user-write.pg.repository.ts:106 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
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 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 _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.
R2 · Cyclomatic Complexity· Complex function fill (cyclomatic 31, cognitive 42) · ×1
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 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 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 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 (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.
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 _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.
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.
Complex function update (cyclomatic 15, cognitive 20) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:731— update has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _setDate (cyclomatic 15, cognitive 14) java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1270— _setDate has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isEmpty (cyclomatic 12, cognitive 13) node/domain-driven-hexagon/src/libs/guard.ts:5— isEmpty has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (top-level) (cyclomatic 11, cognitive 10) node/domain-driven-hexagon/src/libs/ddd/entity.base.ts:1— (top-level) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js · ×1
java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js: 1854 lines of code java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:1— java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js has 1854 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts · ×1
node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts: 491 lines of code node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts:1— node/ddd-hexagonal-cqrs-es-eda/backend/src/api/todo.grpc.controller.ts has 491 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx · ×1
node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx: 444 lines of code node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx:1— node/ddd-hexagonal-cqrs-es-eda/frontend/src/App.tsx has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No typecheck script — 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.
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 (10 application, 6 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
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 (10 application, 6 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
Dead file (~52 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/logging.interceptor.ts— no import path from any entry point (10 application, 6 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
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 (10 application, 6 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
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 (10 application, 6 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
Dead file (~22 LoC) node/ddd-hexagonal-cqrs-es-eda/backend/src/setup-jest.js— no import path from any entry point (10 application, 6 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
Dead file (~18 LoC) node/domain-driven-hexagon/src/libs/decorators/final.decorator.ts— no import path from any entry point (10 application, 6 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
Dead file (~11 LoC) node/domain-driven-hexagon/src/libs/decorators/frozen.decorator.ts— no import path from any entry point (10 application, 6 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
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 (10 application, 6 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
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 (10 application, 6 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
Dead file (~2 LoC) node/domain-driven-hexagon/src/libs/decorators/index.ts— no import path from any entry point (10 application, 6 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
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.
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.
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.
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. 20 such include(s) across the repository's markup.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked node/domain-driven-hexagon/package.json:37— node/domain-driven-hexagon/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/query-handlers/get-todos.handler.ts:42— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/query-handlers/get-todos.handler.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-added.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-completed.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-deleted-publish-pubsub.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-deleted-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-modified-title-publish-pubsub.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-modified-title-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-uncompleted-publish-pubsub.handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/event-handlers/domain/todo-uncompleted-publish-pubsub.handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/add-todo.handler.ts:50— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/add-todo.handler.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts:54— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/complete-todo.handler.ts` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts:49— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/delete-todo.handler.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts:53— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/uncomplete-todo.handler.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts:31— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts:36— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/email-not-found.integration-handler.ts` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/todo-completed.integration-handler.ts:43— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/todo-completed.integration-handler.ts` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts:46— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-email-changed.integration-handler.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts:46— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/event-handlers/integration/user-registered.integration-handler.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts:50— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/change-user-email.command-handler.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/create-user.command-handler.ts:51— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/create-user.command-handler.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts:55— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/increment-todos.command-handler.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/send-email.command-handler.ts:40— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/application/command-handlers/send-email.command-handler.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts:38— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/event-handlers/updated-email-publish.event-handler.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts:48— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/change-email.handler.ts` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts:47— `node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/application/command-handlers/log-in.handler.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/service/mock-email.service.ts:13— `node/ddd-hexagonal-cqrs-es-eda/backend/src/bounded-contexts/marketing/marketing/service/mock-email.service.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
No seccomp profile REDACTED:14— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:14— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:14— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:12— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:14— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
Interpolated log message defeats structured logging java-spring/spring-ddd-credit/scoring/application-services/src/main/java/com/mploed/dddwithspring/scoring/appservices/ScoringApplicationService.java:111— `info` at line 111 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/spring-ddd-credit/scoring/application-services/src/main/java/com/mploed/dddwithspring/scoring/appservices/ScoringApplicationService.java:121— `info` at line 121 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/spring-ddd-credit/scoring/adapters-input/src/main/java/com/mploed/dddwithspring/scoring/feeds/CreditAgencyPoller.java:62— `info` at line 62 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/start/src/main/java/com/alibaba/craftsman/Application.java:28— `info` at line 28 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:59— `debug` at line 59 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:89— `error` at line 89 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/MetricGatewayImpl.java:121— `error` at line 121 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-infrastructure/src/main/java/com/alibaba/craftsman/gatewayimpl/UserProfileGatewayImpl.java:42— `warn` at line 42 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/MetricItem.java:43— `debug` at line 43 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/techinfluence/ATAMetricItem.java:52— `debug` at line 52 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/techinfluence/ATAMetricItem.java:58— `debug` at line 58 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/craftsman/craftsman-domain/src/main/java/com/alibaba/craftsman/domain/metrics/appquality/AppMetricItem.java:28— `debug` at line 28 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/BasicChargeRule.java:15— `debug` at line 15 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FamilyChargeRule.java:20— `debug` at line 20 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:17— `debug` at line 17 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:24— `debug` at line 24 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/charge/chargerule/FixedTimeChargeRule.java:31— `debug` at line 31 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/domain/account/Account.java:73— `debug` at line 73 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/ChargeServiceImpl.java:41— `debug` at line 41 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/application/ChargeServiceImpl.java:47— `debug` at line 47 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:21— `debug` at line 21 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:29— `debug` at line 29 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-spring/2020~cola/charge/src/main/java/com/huawei/charging/adapter/ChargeController.java:37— `debug` at line 37 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Disabled test java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestContractDataImporter.java:14— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~bookstore-cqrs-example/order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestHttpClient.java:17— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~bookstore-cqrs-example/product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestHttpClient.java:17— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~bookstore-cqrs-example/product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestProductDataImporter.java:14— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/handling/HandlingReportIntegrationTest.java:48— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/tracking/ws/CargoTrackingDTOConverterTest.java:102— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2014~dddsample-core/src/test/java/se/citerus/dddsample/interfaces/tracking/ws/CargoTrackingDTOConverterTest.java:116— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/ddd/plus/showcase/reverse/WmsReverseModelingTest.java:74— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/ast/DomainModelAnalyzerTest.java:54— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/model/AbstractBusinessNoTest.java:58— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/runtime/registry/DDDBootstrapTest.java:48— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/runtime/registry/ErrorOnPurposeTest.java:104— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test java-spring/2022~cp-ddd-framework/dddplus-test/src/test/java/io/github/dddplus/runtime/registry/RegistryFactoryTest.java:67— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Duplicated predicate java-spring/2020~yanglao-system/gateway-management/.mvn/wrapper/MavenWrapperDownloader.java:99— `System.getenv("MVNW_USERNAME") != null && System.getenv("MVNW_PASSWORD") != null` appears character-identically in 6 files — java-spring/2020~yanglao-system/gateway-management/.mvn/wrapper/MavenWrapperDownloader.java, java-spring/2020~yanglao-system/order-management/.mvn/wrapper/MavenWrapperDownloader.java, java-spring/2020~yanglao-system/pay-management/.mvn/wrapper/MavenWrapperDownloader.java, java-spring/2020~yanglao-system/room-management/.mvn/wrapper/MavenWrapperDownloader.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java:232— `f.getName().equals("resourceIntegration") || f.getName().equals("resourceIntegrationSingle")` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/entity/Entity.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/entity/Entity.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:407— `jsonObject.containsKey("code") && jsonObject.get("code").equals(0)` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:429— `responseJSONObject == null && jsonObject.get("code").equals(ErrorConfig.CODE_INTERNEL_EXCEPTION)` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java:64— `temp.length > flag && temp.length > flag + 1` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/Resource.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/Resource.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:377— `this.deferredResult != null && !this.deferredResult.hasResult() && this.flowIndex.get() == (this.uriMapping.size() - 1)` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:391— `this.deferredResult != null && this.deferredResult.hasResult()` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java:470— `this.requestDataJSONObject != null && this.requestDataJSONObject.containsKey("resource_integration")` appears character-identically in 2 files — reinvent-wheels/spring-rarf/api/src/main/java/wx/rarf/resource/bag/ResourceBag.java, reinvent-wheels/spring-rarf/rarf/src/main/java/rarf/resource/bag/ResourceBag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×5
Primitive id on a domain type: UserLoggedInDomainEvent.aggregateId node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:12— `UserLoggedInDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TodoCompletionsIncrementedDomainEvent.aggregateId node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/marketing/marketing/domain/events/todo-completions-incremented.event.ts:13— `TodoCompletionsIncrementedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TodoAddedDomainEvent.aggregateId node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-added.event.ts:13— `TodoAddedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TodoCompletedDomainEvent.aggregateId node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/domain/events/todo-completed.event.ts:12— `TodoCompletedDomainEvent.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: WalletCreatedDomainEvent.userId node/domain-driven-hexagon/src/modules/wallet/domain/events/wallet-created.domain-event.ts:4— `WalletCreatedDomainEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
P10 · Library API & versioning· No explicit versioning · ×3
No explicit versioning reinvent-wheels/udma/udma/starter/build.gradle— No explicit version was found for the Maven/Gradle library declared by `build.gradle`. This check read a `<version>` in REDACTED, or `version` in build.gradle(.kts) or gradle.properties, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
No explicit versioning reinvent-wheels/udma/udma/starter/autoconfigure/build.gradle— No explicit version was found for the Maven/Gradle library declared by `build.gradle`. This check read a `<version>` in REDACTED, or `version` in build.gradle(.kts) or gradle.properties, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
No explicit versioning reinvent-wheels/udma/udma/starter/starters/build.gradle— No explicit version was found for the Maven/Gradle library declared by `build.gradle`. This check read a `<version>` in REDACTED, or `version` in build.gradle(.kts) or gradle.properties, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
Documentation: no build, run or usage example node/ddd-hexagonal-cqrs-es-eda/envoy/README.md:1— `envoy` is runnable (a `start` script in `package.json`) and neither `node/ddd-hexagonal-cqrs-es-eda/envoy/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no map of the repository's parts README.md:1— The repository has 4 units (`backend`, `envoy`, `frontend`, `domain-driven-hexagon`); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
redundant comment java-spring/2014~dddsample-core/src/main/resources/static/js/bootstrap-datepicker.js:189— "Check that the start view is between min and max" repeats the code it sits on: 4 of its 5 words (start, view, min, max) are already in `o.startView = Math.min(o.startView, o.maxViewMode);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/todo/todo/application/command-handlers/index.ts:6— "export const CommandHandlers = [ AddTodoHandler, CompleteTodoHandler, UncompleteTodoHandler, ModifyTodoTitleHandler, ];" repeats the code it sits on: 9 of its 11 words (command, handlers, add, todo, handler, complete, uncomplete, modify, title) are already in `export const PubSubCommandHandlers = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
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.
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
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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 278/335 types (83%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 32/43 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `java-spring/2020~cola/craftsman/craftsman-adapter`, `java-spring/2020~yanglao-system/gateway-management`, `java-spring/2020~yanglao-system/order-management`, `java-spring/2020~yanglao-system/pay-management`, `java-spring/2020~yanglao-system/room-management` and 6 more.
P3 · Security & performance tooling· Dependabot does not watch gomod/gradle/composer · ×1
Dependabot does not watch gomod/gradle/composer REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, `gradle`, `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
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 'TChangeEmailCommand' · ×1
Unused export 'TChangeEmailCommand' node/ddd-hexagonal-cqrs-es-eda/backend/src/lib/bounded-contexts/iam/authentication/commands/change-email.command.ts:7— Nothing imports this binding — it is safe to review for removal.
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.
R7 · Dead Code· Unused export 'NonFunctionProperties' · ×1
Unused export 'NonFunctionProperties' node/domain-driven-hexagon/src/libs/types/non-function-properties.type.ts:9— Nothing ultimately consumes this binding: its only referrer is the re-export in node/domain-driven-hexagon/src/libs/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in node/domain-driven-hexagon/src/libs/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'RequireAtLeastOne' · ×1
Unused export 'RequireAtLeastOne' node/domain-driven-hexagon/src/libs/types/require-one.type.ts:4— Nothing ultimately consumes this binding: its only referrer is the re-export in node/domain-driven-hexagon/src/libs/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in node/domain-driven-hexagon/src/libs/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'RequireOnlyOne' · ×1
Unused export 'RequireOnlyOne' node/domain-driven-hexagon/src/libs/types/require-one.type.ts:13— Nothing ultimately consumes this binding: its only referrer is the re-export in node/domain-driven-hexagon/src/libs/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in node/domain-driven-hexagon/src/libs/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'FindUsersParams' · ×1
Unused export 'FindUsersParams' node/domain-driven-hexagon/src/modules/user/database/user.repository.port.ts:4— Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated: github.com/nats-io/nats.go — `github.com/nats-io/nats.go` is required at v1.24.0 in REDACTED, but v1.55.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.55.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.25.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/prometheus/client_golang@v1.25.0 && 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.47.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.47.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.47.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.47.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.47.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.47.0 && go mod tidy` and commit the updated REDACTED and go.sum.
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
doc comments repeat the names node/domain-driven-hexagon/src/libs/utils/convert-props-to-object.util.ts:31— 0 of 4 documented parameters and 0 of 60 summaries in `domain-driven-hexagon` only repeat the member or parameter name (e.g. "" for `props`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Off the main sequence: sharedmodel — sharedmodel: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
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.
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.
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.
Run 01a1b876-a189-7303-9dbc-79c4f5851174 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 354 · Warnings: 1059 · Recommendations: 305 · Info: 10 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 08-11-2026 @ 00:02 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.