Public report of ardalis/VerticalCleanModularMicroservices, published 22 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 22 October 2026, 05:44 UTC · Survey ID cd_506f31797c1e4587b77d37849c32c8ca
ardalis/VerticalCleanModularMicroservices
Measured 22 October 2026, 05:15 UTC, at code version 42dcbd5
Test reliability is not measured: No test run produced results.
CAI scoreProvisionalDown 7 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 small codebase: 12,959 lines of product code in 49 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 24
Findings by how serious they are
17 critical295 serious155 minor
8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 05:15 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 6 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0452: The type 'ProductId' must be a reference type in order to use it as parameter 'T' in the generic type or method 'ShouldBeNullExtensions.ShouldNotBeNull<T>(T?, string?)'; CS0234: The type or namespace name 'CleanArch' does not exist in the namespace 'OrderDemo' (are you missing an assembly reference?); CS0246: The type or namespace name 'ProductId' could not be found (are you missing a using directive or an assembly reference?)
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
89of 95 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
397of 467 findings point to an exact file and line, so you can open each one in the code. The other 70 concern the repository as a whole, such as missing documentation.
95dimensions across 8 lenses, read from 12,959 lines of product code in 49 projects.
ardalis/VerticalCleanModularMicroservices scores 47 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 24 and is rated Critical. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 4 Leaked secret finding(s) in Secret Scanning and to resolve the 7 Prerelease dependency finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 47 to about 66.
17 findings are critical: eight in Outbox / dual-write, four in Secret Scanning, two in Dependency Hygiene, two in Explicit Debt and one in Dependency direction.
Watchdog couldn't measure Code Coverage, IL Efficiency and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 12,959 lines, which would take an estimated 0.2 person-years, around €27,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.
Cancellation propagation · Async method without CancellationToken: ListAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs
Cancellation propagation · Async method without CancellationToken: SendEmailAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs
Cancellation propagation · Async method without CancellationToken: SendEmailAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs
Cancellation propagation · Async method without CancellationToken: ListAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Queries/ListProductsQueryService.cs
Cancellation propagation · Async method without CancellationToken: SendEmailAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/MimeKitEmailSender.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /cart 01-VerticalSlice/src/OrderDemo.Api/CartFeature/AddToCart.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /checkout 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /confirm-purchase 01-VerticalSlice/src/OrderDemo.Api/CartFeature/ConfirmPurchase.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /cart/{cartId} 01-VerticalSlice/src/OrderDemo.Api/CartFeature/ViewCart.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /orders 01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /products/{id} 01-VerticalSlice/src/OrderDemo.Api/ProductFeature/GetProductById.cs
Cancellation propagation · Async endpoint handler without CancellationToken: /products 01-VerticalSlice/src/OrderDemo.Api/ProductFeature/ListProducts.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/FakeEmailSender.cs
Incompleteness & stubs · Both branches are identical — the condition decides nothing 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs
Incompleteness & stubs · Both branches are identical — the condition decides nothing 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/FakeEmailSender.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 10 findings
These 10 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
Coupling · Off the main sequence: Nimble.Modulith.ServiceDefaults (04-Microservices/src/Nimble.Modulith.ServiceDefaults)
Coupling · Off the main sequence: Nimble.Modulith.ServiceDefaults (03-ModularMonolith/src/Nimble.Modulith.ServiceDefaults)
Coupling · Off the main sequence: OrderDemo.CleanArch.ServiceDefaults (02-CleanArchitecture/src/OrderDemo.CleanArch.ServiceDefaults)
Coupling · Off the main sequence: OrderDemo.CleanArch.ServiceDefaults (05-CleanVertical/src/OrderDemo.CleanArch.ServiceDefaults)
Boundary Type-Coupling · Cross-context type SendEmailCommand (03-ModularMonolith → 04-Microservices)
Boundary Type-Coupling · Cross-context type SendEmailCommand (03-ModularMonolith → 04-Microservices)
Rebuild cost: about €27,000 · Estimate
Cost to rebuild
€8,900 to €45,000, for 148 to 469 hours of work, about 0.2 person-years for one engineer
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 47. 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
Small: 12,959 lines of product code, of which 37% is declarations and boilerplate, 44% straight logic and 19% logic with branches
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
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 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (4).
Raises the score by about 19 points · Low effort · Secret Scanning
2
Resolve the 7 Prerelease dependency finding(s) in Dependency Hygiene.
Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (8), OrderDemo.AppHost.csproj (2), OrderDemo.Api.csproj.
Raises the score by about 19 points · Medium effort · Dependency Hygiene
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0452: The type 'ProductId' must be a reference type in order to use it as parameter 'T' in the generic type or method 'ShouldBeNullExtensions.ShouldNotBeNull<T>(T?, string?)'; CS0234: The type or namespace name 'CleanArch' does not exist in the namespace 'OrderDemo' (are you missing an assembly reference?); CS0246: The type or namespace name 'ProductId' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €27,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 24 (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 29 Domain Modelling findings · Common cause
29 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. Other code can change an object's data directly, so it can put an order into a state the rules forbid. 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: Encapsulated state (6 findings) · Rich vs anemic model (9 findings) · Strongly-typed ids (14 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.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph 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.
135 modules, with 130 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 95 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.
Nimble.Modulith.Customers.Infrastructure.Data uses Nimble.Modulith.Customers.Domain.CustomerAggregate, so a change to Nimble.Modulith.Customers.Domain.CustomerAggregate can break Nimble.Modulith.Customers.Infrastructure.Data, while a change to Nimble.Modulith.Customers.Infrastructure.Data can't break Nimble.Modulith.Customers.Domain.CustomerAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.Infrastructure.Data uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.Infrastructure.Data uses Nimble.Modulith.Customers.Domain.Interfaces, so a change to Nimble.Modulith.Customers.Domain.Interfaces can break Nimble.Modulith.Customers.Infrastructure.Data, while a change to Nimble.Modulith.Customers.Infrastructure.Data can't break Nimble.Modulith.Customers.Domain.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Customers.Infrastructure.Data uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.Infrastructure.Data uses Nimble.Modulith.Customers.Domain.OrderAggregate, so a change to Nimble.Modulith.Customers.Domain.OrderAggregate can break Nimble.Modulith.Customers.Infrastructure.Data, while a change to Nimble.Modulith.Customers.Infrastructure.Data can't break Nimble.Modulith.Customers.Domain.OrderAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.Infrastructure.Data uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Nimble.Modulith.Customers.UseCases.Customers.Commands uses a type in Nimble.Modulith.Customers.Domain.CustomerAggregate.
Nimble.Modulith.Customers.UseCases.Customers.Commands uses Nimble.Modulith.Customers.Domain.CustomerAggregate, so a change to Nimble.Modulith.Customers.Domain.CustomerAggregate can break Nimble.Modulith.Customers.UseCases.Customers.Commands, while a change to Nimble.Modulith.Customers.UseCases.Customers.Commands can't break Nimble.Modulith.Customers.Domain.CustomerAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Customers.Commands uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Customers.Commands uses Nimble.Modulith.Customers.Domain.Interfaces, so a change to Nimble.Modulith.Customers.Domain.Interfaces can break Nimble.Modulith.Customers.UseCases.Customers.Commands, while a change to Nimble.Modulith.Customers.UseCases.Customers.Commands can't break Nimble.Modulith.Customers.Domain.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Customers.Commands uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in Nimble.Modulith.Customers.UseCases.Customers.Queries uses a type in Nimble.Modulith.Customers.Domain.CustomerAggregate.
Nimble.Modulith.Customers.UseCases.Customers.Queries uses Nimble.Modulith.Customers.Domain.CustomerAggregate, so a change to Nimble.Modulith.Customers.Domain.CustomerAggregate can break Nimble.Modulith.Customers.UseCases.Customers.Queries, while a change to Nimble.Modulith.Customers.UseCases.Customers.Queries can't break Nimble.Modulith.Customers.Domain.CustomerAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Customers.Queries uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Customers.Queries uses Nimble.Modulith.Customers.Domain.Interfaces, so a change to Nimble.Modulith.Customers.Domain.Interfaces can break Nimble.Modulith.Customers.UseCases.Customers.Queries, while a change to Nimble.Modulith.Customers.UseCases.Customers.Queries can't break Nimble.Modulith.Customers.Domain.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Customers.Queries uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Orders.Commands uses Nimble.Modulith.Customers.Domain.CustomerAggregate, so a change to Nimble.Modulith.Customers.Domain.CustomerAggregate can break Nimble.Modulith.Customers.UseCases.Orders.Commands, while a change to Nimble.Modulith.Customers.UseCases.Orders.Commands can't break Nimble.Modulith.Customers.Domain.CustomerAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Orders.Commands uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Orders.Commands uses Nimble.Modulith.Customers.Domain.Interfaces, so a change to Nimble.Modulith.Customers.Domain.Interfaces can break Nimble.Modulith.Customers.UseCases.Orders.Commands, while a change to Nimble.Modulith.Customers.UseCases.Orders.Commands can't break Nimble.Modulith.Customers.Domain.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Orders.Commands uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Orders.Commands uses Nimble.Modulith.Customers.Domain.OrderAggregate, so a change to Nimble.Modulith.Customers.Domain.OrderAggregate can break Nimble.Modulith.Customers.UseCases.Orders.Commands, while a change to Nimble.Modulith.Customers.UseCases.Orders.Commands can't break Nimble.Modulith.Customers.Domain.OrderAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Orders.Commands uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Orders.Queries uses Nimble.Modulith.Customers.Domain.Interfaces, so a change to Nimble.Modulith.Customers.Domain.Interfaces can break Nimble.Modulith.Customers.UseCases.Orders.Queries, while a change to Nimble.Modulith.Customers.UseCases.Orders.Queries can't break Nimble.Modulith.Customers.Domain.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Orders.Queries uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Customers.UseCases.Orders.Queries uses Nimble.Modulith.Customers.Domain.OrderAggregate, so a change to Nimble.Modulith.Customers.Domain.OrderAggregate can break Nimble.Modulith.Customers.UseCases.Orders.Queries, while a change to Nimble.Modulith.Customers.UseCases.Orders.Queries can't break Nimble.Modulith.Customers.Domain.OrderAggregate.
Position
Below the diagonal: Nimble.Modulith.Customers.UseCases.Orders.Queries uses a module listed above it, which is the healthy direction.
Nimble.Modulith.Email.Integrations uses Nimble.Modulith.Email.Interfaces, so a change to Nimble.Modulith.Email.Interfaces can break Nimble.Modulith.Email.Integrations, while a change to Nimble.Modulith.Email.Integrations can't break Nimble.Modulith.Email.Interfaces.
Position
Below the diagonal: Nimble.Modulith.Email.Integrations uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Core.OrderAggregate uses OrderDemo.CleanArch.Core.ProductAggregate, so a change to OrderDemo.CleanArch.Core.ProductAggregate can break OrderDemo.CleanArch.Core.OrderAggregate, while a change to OrderDemo.CleanArch.Core.OrderAggregate can't break OrderDemo.CleanArch.Core.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Core.OrderAggregate uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart uses OrderDemo.CleanArch.Core.CartAggregate, so a change to OrderDemo.CleanArch.Core.CartAggregate can break OrderDemo.CleanArch.UseCases.Cart, while a change to OrderDemo.CleanArch.UseCases.Cart can't break OrderDemo.CleanArch.Core.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Products uses OrderDemo.CleanArch.Core.ProductAggregate, so a change to OrderDemo.CleanArch.Core.ProductAggregate can break OrderDemo.CleanArch.UseCases.Products, while a change to OrderDemo.CleanArch.UseCases.Products can't break OrderDemo.CleanArch.Core.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Products uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.UseCases.Cart, while a change to OrderDemo.CleanVertical.UseCases.Cart can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.CartFeatures uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.Web.CartFeatures, while a change to OrderDemo.CleanVertical.Web.CartFeatures can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in OrderDemo.CleanVertical.Web.Domain.OrderAggregate uses a type in OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
OrderDemo.CleanVertical.Web.Domain.OrderAggregate uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.Web.Domain.OrderAggregate, while a change to OrderDemo.CleanVertical.Web.Domain.OrderAggregate can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Domain.OrderAggregate uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.ProductFeatures uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.Web.ProductFeatures, while a change to OrderDemo.CleanVertical.Web.ProductFeatures can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.ProductFeatures uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data uses OrderDemo.CleanArch.Core.CartAggregate, so a change to OrderDemo.CleanArch.Core.CartAggregate can break OrderDemo.CleanArch.Infrastructure.Data, while a change to OrderDemo.CleanArch.Infrastructure.Data can't break OrderDemo.CleanArch.Core.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data uses OrderDemo.CleanArch.Core.GuestUserAggregate, so a change to OrderDemo.CleanArch.Core.GuestUserAggregate can break OrderDemo.CleanArch.Infrastructure.Data, while a change to OrderDemo.CleanArch.Infrastructure.Data can't break OrderDemo.CleanArch.Core.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data uses OrderDemo.CleanArch.Core.ProductAggregate, so a change to OrderDemo.CleanArch.Core.ProductAggregate can break OrderDemo.CleanArch.Infrastructure.Data, while a change to OrderDemo.CleanArch.Infrastructure.Data can't break OrderDemo.CleanArch.Core.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data uses OrderDemo.CleanArch.Core.OrderAggregate, so a change to OrderDemo.CleanArch.Core.OrderAggregate can break OrderDemo.CleanArch.Infrastructure.Data, while a change to OrderDemo.CleanArch.Infrastructure.Data can't break OrderDemo.CleanArch.Core.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Config uses OrderDemo.CleanArch.Core.CartAggregate, so a change to OrderDemo.CleanArch.Core.CartAggregate can break OrderDemo.CleanArch.Infrastructure.Data.Config, while a change to OrderDemo.CleanArch.Infrastructure.Data.Config can't break OrderDemo.CleanArch.Core.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Config uses OrderDemo.CleanArch.Core.GuestUserAggregate, so a change to OrderDemo.CleanArch.Core.GuestUserAggregate can break OrderDemo.CleanArch.Infrastructure.Data.Config, while a change to OrderDemo.CleanArch.Infrastructure.Data.Config can't break OrderDemo.CleanArch.Core.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Config uses OrderDemo.CleanArch.Core.ProductAggregate, so a change to OrderDemo.CleanArch.Core.ProductAggregate can break OrderDemo.CleanArch.Infrastructure.Data.Config, while a change to OrderDemo.CleanArch.Infrastructure.Data.Config can't break OrderDemo.CleanArch.Core.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Config uses OrderDemo.CleanArch.Core.OrderAggregate, so a change to OrderDemo.CleanArch.Core.OrderAggregate can break OrderDemo.CleanArch.Infrastructure.Data.Config, while a change to OrderDemo.CleanArch.Infrastructure.Data.Config can't break OrderDemo.CleanArch.Core.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.AddToCart uses OrderDemo.CleanArch.Core.CartAggregate, so a change to OrderDemo.CleanArch.Core.CartAggregate can break OrderDemo.CleanArch.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanArch.UseCases.Cart.AddToCart can't break OrderDemo.CleanArch.Core.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.AddToCart uses OrderDemo.CleanArch.Core.ProductAggregate, so a change to OrderDemo.CleanArch.Core.ProductAggregate can break OrderDemo.CleanArch.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanArch.UseCases.Cart.AddToCart can't break OrderDemo.CleanArch.Core.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.AddToCart uses OrderDemo.CleanArch.UseCases.Cart, so a change to OrderDemo.CleanArch.UseCases.Cart can break OrderDemo.CleanArch.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanArch.UseCases.Cart.AddToCart can't break OrderDemo.CleanArch.UseCases.Cart.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.Checkout uses OrderDemo.CleanArch.Core.CartAggregate, so a change to OrderDemo.CleanArch.Core.CartAggregate can break OrderDemo.CleanArch.UseCases.Cart.Checkout, while a change to OrderDemo.CleanArch.UseCases.Cart.Checkout can't break OrderDemo.CleanArch.Core.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.Checkout uses OrderDemo.CleanArch.Core.GuestUserAggregate, so a change to OrderDemo.CleanArch.Core.GuestUserAggregate can break OrderDemo.CleanArch.UseCases.Cart.Checkout, while a change to OrderDemo.CleanArch.UseCases.Cart.Checkout can't break OrderDemo.CleanArch.Core.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Cart.Checkout uses OrderDemo.CleanArch.Core.OrderAggregate, so a change to OrderDemo.CleanArch.Core.OrderAggregate can break OrderDemo.CleanArch.UseCases.Cart.Checkout, while a change to OrderDemo.CleanArch.UseCases.Cart.Checkout can't break OrderDemo.CleanArch.Core.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Products.List uses OrderDemo.CleanArch.UseCases, so a change to OrderDemo.CleanArch.UseCases can break OrderDemo.CleanArch.UseCases.Products.List, while a change to OrderDemo.CleanArch.UseCases.Products.List can't break OrderDemo.CleanArch.UseCases.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Products.List uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.UseCases.Products.List uses OrderDemo.CleanArch.UseCases.Products, so a change to OrderDemo.CleanArch.UseCases.Products can break OrderDemo.CleanArch.UseCases.Products.List, while a change to OrderDemo.CleanArch.UseCases.Products.List can't break OrderDemo.CleanArch.UseCases.Products.
Position
Below the diagonal: OrderDemo.CleanArch.UseCases.Products.List uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Infrastructure.Data.Queries uses OrderDemo.CleanArch.UseCases.Products, so a change to OrderDemo.CleanArch.UseCases.Products can break OrderDemo.CleanVertical.Infrastructure.Data.Queries, while a change to OrderDemo.CleanVertical.Infrastructure.Data.Queries can't break OrderDemo.CleanArch.UseCases.Products.
Position
Below the diagonal: OrderDemo.CleanVertical.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanVertical.UseCases.Cart.AddToCart can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanVertical.UseCases.Cart.AddToCart can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses OrderDemo.CleanVertical.UseCases.Cart, so a change to OrderDemo.CleanVertical.UseCases.Cart can break OrderDemo.CleanVertical.UseCases.Cart.AddToCart, while a change to OrderDemo.CleanVertical.UseCases.Cart.AddToCart can't break OrderDemo.CleanVertical.UseCases.Cart.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.Checkout uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.UseCases.Cart.Checkout, while a change to OrderDemo.CleanVertical.UseCases.Cart.Checkout can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.Checkout uses OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate can break OrderDemo.CleanVertical.UseCases.Cart.Checkout, while a change to OrderDemo.CleanVertical.UseCases.Cart.Checkout can't break OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.UseCases.Cart.Checkout uses OrderDemo.CleanVertical.Web.Domain.OrderAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.OrderAggregate can break OrderDemo.CleanVertical.UseCases.Cart.Checkout, while a change to OrderDemo.CleanVertical.UseCases.Cart.Checkout can't break OrderDemo.CleanVertical.Web.Domain.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.UseCases.Cart.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.Web.CartFeatures.AddToCart, while a change to OrderDemo.CleanVertical.Web.CartFeatures.AddToCart can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses a type in OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.Web.CartFeatures.AddToCart, while a change to OrderDemo.CleanVertical.Web.CartFeatures.AddToCart can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses OrderDemo.CleanVertical.Web.CartFeatures, so a change to OrderDemo.CleanVertical.Web.CartFeatures can break OrderDemo.CleanVertical.Web.CartFeatures.AddToCart, while a change to OrderDemo.CleanVertical.Web.CartFeatures.AddToCart can't break OrderDemo.CleanVertical.Web.CartFeatures.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.AddToCart uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.Web.CartFeatures.Checkout, while a change to OrderDemo.CleanVertical.Web.CartFeatures.Checkout can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses a type in OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate can break OrderDemo.CleanVertical.Web.CartFeatures.Checkout, while a change to OrderDemo.CleanVertical.Web.CartFeatures.Checkout can't break OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses OrderDemo.CleanVertical.Web.Domain.OrderAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.OrderAggregate can break OrderDemo.CleanVertical.Web.CartFeatures.Checkout, while a change to OrderDemo.CleanVertical.Web.CartFeatures.Checkout can't break OrderDemo.CleanVertical.Web.Domain.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.CartFeatures.Checkout uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.Infrastructure.Data uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.Infrastructure.Data uses OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data can't break OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.Infrastructure.Data uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.Infrastructure.Data uses OrderDemo.CleanVertical.Web.Domain.OrderAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.OrderAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data can't break OrderDemo.CleanVertical.Web.Domain.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a type in OrderDemo.CleanVertical.Web.Domain.CartAggregate.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses OrderDemo.CleanVertical.Web.Domain.CartAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.CartAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Config, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Config can't break OrderDemo.CleanVertical.Web.Domain.CartAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a type in OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Config, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Config can't break OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a type in OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses OrderDemo.CleanVertical.Web.Domain.ProductAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.ProductAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Config, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Config can't break OrderDemo.CleanVertical.Web.Domain.ProductAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a type in OrderDemo.CleanVertical.Web.Domain.OrderAggregate.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses OrderDemo.CleanVertical.Web.Domain.OrderAggregate, so a change to OrderDemo.CleanVertical.Web.Domain.OrderAggregate can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Config, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Config can't break OrderDemo.CleanVertical.Web.Domain.OrderAggregate.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Config uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.ProductFeatures.List uses OrderDemo.CleanVertical.Web.ProductFeatures, so a change to OrderDemo.CleanVertical.Web.ProductFeatures can break OrderDemo.CleanVertical.Web.ProductFeatures.List, while a change to OrderDemo.CleanVertical.Web.ProductFeatures.List can't break OrderDemo.CleanVertical.Web.ProductFeatures.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.ProductFeatures.List uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Queries uses OrderDemo.CleanArch.UseCases, so a change to OrderDemo.CleanArch.UseCases can break OrderDemo.CleanArch.Infrastructure.Data.Queries, while a change to OrderDemo.CleanArch.Infrastructure.Data.Queries can't break OrderDemo.CleanArch.UseCases.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Queries uses OrderDemo.CleanArch.UseCases.Products, so a change to OrderDemo.CleanArch.UseCases.Products can break OrderDemo.CleanArch.Infrastructure.Data.Queries, while a change to OrderDemo.CleanArch.Infrastructure.Data.Queries can't break OrderDemo.CleanArch.UseCases.Products.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Queries uses OrderDemo.CleanArch.Infrastructure.Data, so a change to OrderDemo.CleanArch.Infrastructure.Data can break OrderDemo.CleanArch.Infrastructure.Data.Queries, while a change to OrderDemo.CleanArch.Infrastructure.Data.Queries can't break OrderDemo.CleanArch.Infrastructure.Data.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
OrderDemo.CleanArch.Infrastructure.Data.Queries uses OrderDemo.CleanArch.UseCases.Products.List, so a change to OrderDemo.CleanArch.UseCases.Products.List can break OrderDemo.CleanArch.Infrastructure.Data.Queries, while a change to OrderDemo.CleanArch.Infrastructure.Data.Queries can't break OrderDemo.CleanArch.UseCases.Products.List.
Position
Below the diagonal: OrderDemo.CleanArch.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses OrderDemo.CleanVertical.Web.ProductFeatures, so a change to OrderDemo.CleanVertical.Web.ProductFeatures can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries can't break OrderDemo.CleanVertical.Web.ProductFeatures.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses OrderDemo.CleanVertical.Web.Infrastructure.Data, so a change to OrderDemo.CleanVertical.Web.Infrastructure.Data can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries can't break OrderDemo.CleanVertical.Web.Infrastructure.Data.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses a type in OrderDemo.CleanVertical.Web.ProductFeatures.List.
OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses OrderDemo.CleanVertical.Web.ProductFeatures.List, so a change to OrderDemo.CleanVertical.Web.ProductFeatures.List can break OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries, while a change to OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries can't break OrderDemo.CleanVertical.Web.ProductFeatures.List.
Position
Below the diagonal: OrderDemo.CleanVertical.Web.Infrastructure.Data.Queries uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 82% · Adequate · gated by D18 ·
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
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Immediately address the four leaked secrets, beginning with REDACTED, to secure sensitive credentials. Next, clean up the dependency landscape by resolving fourteen deprecated packages, seven prerelease dependencies, and two vulnerable components, prioritizing updates in Directory.Packages.props and the project files. Finally, establish a CI/CD pipeline to automatically build and test the codebase on every push and pull request to ensure ongoing stability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (4).
Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
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 — 17
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 — 295
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 — 155
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 89 of 95 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 95 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, 397 of 467 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
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 44 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.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file '04-Microservices/src/Nimble.Modulith.AppHost/Nimble.Modulith.AppHost.csproj' with message: '../Nimble.Modulith.ServiceDefaults/Nimble.Modulith.ServiceDefaults.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `05-CleanVertical/src/OrderDemo.CleanArch.Web/appsettings.json`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `01-VerticalSlice/src/OrderDemo.Api/Data/AppDbContext.cs`, `01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs`, `01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs`, … (+120 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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 (44 commit(s) sampled).
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (01-VerticalSlice/aspire/OrderDemo.AppHost/OrderDemo.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret 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.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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 (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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").
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.
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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
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.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
The LLM boundary
LLM-set scores this run (6): D19, D21, D22, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
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.
0 method(s) exceeded the cognitive complexity threshold of 15.
✓ On the Gold path — maintain.
Detailed fixes: d2_recommendation.md.
Do you agree with this assessment?
D3 · God Classes10.0 / 10Exemplary✓ 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.
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.
162 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Create.cs (2), GetById.cs (2), DimProduct.cs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Order.cs, EmailSettings.cs, Create.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with OrdersReport.cs, ProductSalesReport.cs, MimeKitEmailSender.cs. — One of this dimension's main actionable groups (8 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.8 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Off the main sequence: OrderDemo.CleanArch.Core (02-CleanArchitecture/src/OrderDemo.CleanArch.Core)02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderDemo.CleanArch.Core.csproj:1
Off the main sequence: Nimble.Modulith.Customers.Contracts (04-Microservices/src/Nimble.Modulith.Customers.Contracts) · ×804-Microservices/src/Nimble.Modulith.Customers.Contracts/Nimble.Modulith.Customers.Contracts.csproj:1
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling — start with OrderDemo.CleanArch.Core.csproj. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
D9 · Test Distribution9.4 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
11 test methods: 2 unit, 9 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (8), OrderDemo.AppHost.csproj (2), OrderDemo.Api.csproj. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 7 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
0 of 258 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 58 direct `PackageReference`(s), and 224 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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.
19 deducted debt markers + unmeasured dead symbols across 12959 LoC in the .NET projects (0.3/KLoC) → score 9.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 9 CommentedOutCode finding(s) in Explicit Debt — start with Extensions.cs (4), CustomWebApplicationFactory.cs (4), Program.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 TodoComment finding(s) in Explicit Debt — start with CustomerOrdersReport.cs (2), OrdersReport.cs (2), ProductSalesReport.cs (2). — One of this dimension's main actionable groups (8 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
49 projects, 515 source files, 13793 hand-written lines of code (12959 production / 834 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 5318 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 55 inter-project edges (build failed). Measured across 6 solutions loaded as one workspace: `04-Microservices/src/OrderDemo.ModulithMicroservice.slnx`, `03-ModularMonolith/src/OrderDemo.Modulith.slnx`, `02-CleanArchitecture/OrderDemo.CleanArch.slnx`, `05-CleanVertical/OrderDemo.CleanVertical.slnx`, `01-VerticalSlice/OrderDemo.VerticalSlice.slnx`, `05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderDemo.CleanArch.Core.sln`.
Resolve the 2 Shell project finding(s) in Solution Shape — start with Nimble.Modulith.Reporting.Contracts.csproj (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_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: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is excellent: it opens with a conference hook and an overview table mapping four architectural stages to their own solution and Aspire AppHost, plus a repository layout diagram. It also states prerequisites (.NET 10 SDK) and begins the Running a Stage section before clipping. The architecture/Docs markdown files are empty (no design docs), so any architecture guidance is missing from the visible content rather than being clipped. XML-doc coverage for Nimble.Modulith.* projects is low (<2%), reflecting sparse documentation.
Improve Documentation Quality — currently 7.0/10. — The repository's root README is excellent: it opens with a conference hook and an overview table mapping four architectural stages to their own solution and Aspire AppHost, plus a repository layout diagram. It also states prerequisites (.NET 10 SDK) and begins the Running a Stage section before clipping. The architecture/Docs markdown files are empty (no design docs), so any architecture guidance is missing from the visible content rather than being clipped. XML-doc coverage for Nimble.Modulith.* projects is low (<2%), reflecting sparse documentation.
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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStronggated by 1 serious finding◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
Inconsistent date type usage for the same semantic concept (Order Date) across related entities. OrderCreatedEvent uses DateOnly, while OrderDetails uses DateTime.
What to do
Resolve the 1 Inconsistent date type usage for the same semantic concept (Order Date)… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
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.
97 % of calls cross a namespace and 6 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret 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.
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).
semgrep found no security issues. semgrep hit a parse error in 125 file(s) — `01-VerticalSlice/src/OrderDemo.Api/Data/AppDbContext.cs` (line 6), `01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs` (lines 3–6, line 26), `01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs` (line 11), `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs` (line 6), `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs` (line 7), … (+120 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. In 122 of those file(s) — `01-VerticalSlice/src/OrderDemo.Api/Data/AppDbContext.cs`, `01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs`, `01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs`, … (+117 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
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 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.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with OrderDemo.CleanArch.AspireTests.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
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.
`OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases)` is a Application project but references `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/OrderDemo.CleanArch.UseCases.csproj:8
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartCommand.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate.Specifications`, `CartId`, `Product`, `ProductByIdSpec`, `ProductId`, …. The inward dependency rule is broken here. It is named again on lines 2, 3, 4, 8, 12, 18, 29. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `CartId`. The inward dependency rule is broken here. It is named again on line 5. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/CartDto.cs:1, 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartQuery.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.OrderAggregate`, `CartId`, `OrderId`. The inward dependency rule is broken here. It is named again on lines 2, 6, 8. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutCommand.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate`, `OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.OrderAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `GuestUser`, `Order`, …. The inward dependency rule is broken here. It is named again on lines 2, 3, 4, 5, 6, 12, 13, 19, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `CartByIdSpec`. The inward dependency rule is broken here. It is named again on lines 2, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:1
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate.Specifications`, `Product`, `ProductByIdSpec`. The inward dependency rule is broken here. It is named again on lines 4, 8, 13. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/Get/GetProductHandler.cs:3
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `ProductId`. The inward dependency rule is broken here. It is named again on line 7. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/Get/GetProductQuery.cs:3
This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `ProductId`. The inward dependency rule is broken here. It is named again on line 4. Depend on an abstraction the inner layer owns, implemented in the outer one. — 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/ProductDto.cs:1
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.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`ConfirmOrderHandler` (slice 'Orders') depends on `GetCustomerByIdQuery` from slice 'Customers'. — 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:28
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
Do you agree with this assessment?
C1 · Data Protection3.0 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
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.
Do you agree with this assessment?
DM10 · One transaction, one aggregate9.3 / 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.
`CheckoutHandler.Handle` saves `GuestUser`, `Order`, `Cart` 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. (×2) — 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:16, 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs:20
`Checkout.MapCheckoutEndpoint (route handler, line 13)` saves `GuestUser`, `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. — 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:13
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), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
`CartItem`'s public constructor takes `productId`, `quantity`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CartItem` 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. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:8, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:8, 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:8
`GuestUser`'s public constructor takes `email` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `GuestUser` 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. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/GuestUserAggregate/GuestUser.cs:5, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/GuestUserAggregate/GuestUser.cs:5, 05-CleanVertical/src/OrderDemo.CleanArch.Core/GuestUserAggregate/GuestUser.cs:5
`Product`'s public constructor takes `name`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Product` 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. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/ProductAggregate/Product.cs:5, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/ProductAggregate/Product.cs:5, 05-CleanVertical/src/OrderDemo.CleanArch.Core/ProductAggregate/Product.cs:5
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.
`Order.CustomerId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:10, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:10
`OrderItem.OrderId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:7, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:14
`OrderItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:8, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:15
`UserAddedToRoleEvent.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. (×2) — 04-Microservices/src/Nimble.Modulith.Users/Events/UserAddedToRoleEvent.cs:5, 03-ModularMonolith/src/Nimble.Modulith.Users/Events/UserAddedToRoleEvent.cs:5
`CartItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:15, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:15, 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:15
`Order.GuestUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:16, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/OrderAggregate/Order.cs:18, 05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:16
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.
Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.
Do you agree with this assessment?
DM4 · Rich vs anemic model7.4 / 10Strong✓ 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.
`Customer` 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. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5
`Order` 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. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6
`OrderItem` 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. (×2) — 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:5, 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:12
`CartItem` 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. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:3, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:3, 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:3
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.
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
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 clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
The parameters [productid, quantity, unitprice] travel together across 6 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/Cart.cs:11
What to do
Extract recurring primitive parameter clusters into value objects so the concept (and its rules) lives in one place.
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.
Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.
Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.
`SendEmailCommand` is shaped like a command (one imperative intent) but has 2 handlers. A command should have exactly one handler that owns the decision; multiple handlers means hidden fan-out and unclear ownership. If several things should react, raise an EVENT after the command succeeds and let them subscribe. — 04-Microservices/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5
What to do
Keep one handler per command (single owner); use events for the fan-out where many subscribers react.
Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).
Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.
`SendEmailCommand` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. (×2) — 04-Microservices/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5, 03-ModularMonolith/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5
What to do
Name events in the past tense — they record facts that already happened.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`CreateCustomerHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×2) — 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:17, 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:17
`AddOrderItemHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×2) — 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:12, 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:12
`ConfirmOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×2) — 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:13, 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:13
`CreateOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×2) — 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:16, 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:16
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
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.
`SendEmailAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/FakeEmailSender.cs:8, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/FakeEmailSender.cs:8
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×2) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs:14, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs:14
`HandleAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/Create/CreateEndpoint.cs:32
A placeholder e-mail address ("guest@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:29
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×10) — 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:54, 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:33, 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:25, …
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
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 a README to the 42 of 49 project(s) that lack one — worth up to 1.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.
1 ADR-shaped document(s) detected by content — `02-CleanArchitecture/README.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Only 28/49 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README advertises Docker containerisation, but no Dockerfile/compose file exists — searched for: `dockerfile`, `docker-compose`, `compose.yaml`, `compose.yml`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:55
04-Microservices/src/Nimble.Modulith.Email.Web/README.md runs `dotnet run --project Nimble.Modulith.AppHost` from `04-Microservices/src/Nimble.Modulith.Email.Web/` or the repository root, but `Nimble.Modulith.AppHost` is not there: the project is `04-Microservices/src/Nimble.Modulith.AppHost`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 04-Microservices/src/Nimble.Modulith.Email.Web/README.md:117
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists; 04-Microservices/src/Nimble.Modulith.Email.Web/README.md runs `dotnet run --project Nimble.Modulith.AppHost` from `04-Microservices/src/Nimble.Modulith.Email.Web/` or the repository root, but `Nimble.Modulith.AppHost` is not there: the project is `04-Microservices/src/Nimble.Modulith.AppHost`.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Only 24/31 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 31, 11 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().
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 evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. (×6) — 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:45, 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:55, 04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:49, …
What to do
Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 68 use(s) across 19,486 production line(s) (~3.5/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/AppDbContext.cs:26, 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
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.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×6) — 01-VerticalSlice/src/OrderDemo.Api/Program.cs:15, 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Program.cs:3, 03-ModularMonolith/src/Nimble.Modulith.Web/Program.cs:20, …
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
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.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×3) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/AppDbContext.cs:26, 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23
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.
`emailClient` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 17). Every use of it in `SendEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var emailClient = …;`), which releases it at the end of the scope on every path including a throw. (×2) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17, 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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 methods accept a CancellationToken so work can be cancelled (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 137/168 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken. (×10) — 04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:33, 04-Microservices/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24, 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:29, …
No CancellationToken parameter — this work can't be stopped early once started. (×14) — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:16, 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:9, 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:19, …
This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. (×7) — 01-VerticalSlice/src/OrderDemo.Api/CartFeature/AddToCart.cs:11, 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:13, 01-VerticalSlice/src/OrderDemo.Api/CartFeature/ConfirmPurchase.cs:13, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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 `ArgumentNullException` 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.
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 unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
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 a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items 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.
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.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. 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.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` suppressions per 1k syntax nodes — 30 suppression(s) across the 96831 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 33 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence 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.
D11 Test Reliability — Test reliability not measured — no test run produced results
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 125 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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, or wire coverage collection into CI, to enable this cross-layer check
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Dual write (no outbox): CreateCustomerHandler.Handle 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:17— `CreateCustomerHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): AddOrderItemHandler.Handle 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:12— `AddOrderItemHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): ConfirmOrderHandler.Handle 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:13— `ConfirmOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): CreateOrderHandler.Handle 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:16— `CreateOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): CreateCustomerHandler.Handle 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:17— `CreateCustomerHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): AddOrderItemHandler.Handle 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:12— `AddOrderItemHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): ConfirmOrderHandler.Handle 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:13— `ConfirmOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): CreateOrderHandler.Handle 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:16— `CreateOrderHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
NoWarnInCsproj 05-CleanVertical/Directory.Build.props:11— 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj 02-CleanArchitecture/Directory.Build.props:11— 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/OrderDemo.CleanArch.UseCases.csproj:8— `OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases)` is a Application project but references `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Serious — 295 finding(s)
X2 · Cancellation propagation· Async method without CancellationToken · ×24
Async method without CancellationToken: EnsureCustomersModuleDatabaseAsync 04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:33— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureProductsModuleDatabaseAsync 04-Microservices/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureReportingModuleDatabaseAsync 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:29— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureUsersModuleDatabaseAsync 04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:45— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureCustomersModuleDatabaseAsync 03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:33— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureProductsModuleDatabaseAsync 03-ModularMonolith/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureUsersModuleDatabaseAsync 03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:45— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: EnsureReportingModuleDatabaseAsync 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:29— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: ListAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:16— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:9— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PopulateTestDataAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendEmailAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendEmailAsync 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:15— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SeedDatabase 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:42— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: SeedDatabase 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:44— No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: ListAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Queries/ListProductsQueryService.cs:16— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/SeedData.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PopulateTestDataAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/SeedData.cs:21— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendEmailAsync 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/MimeKitEmailSender.cs:13— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ListAsync 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:16— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:9— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PopulateTestDataAsync 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendEmailAsync 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendEmailAsync 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:15— No CancellationToken parameter — this work can't be stopped early once started.
Duplicated block (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimProduct.cs:6— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimProduct.cs:6-14 | 04-Microservices/src/Nimble.Modulith.Reporting/Models/DimProduct.cs:6-14 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimProduct.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Models/DimProduct.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimProduct.cs:6` 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Email/Services/ChannelQueueService.cs:16— 03-ModularMonolith/src/Nimble.Modulith.Email/Services/ChannelQueueService.cs:16-24 | 04-Microservices/src/Nimble.Modulith.Email/Services/ChannelQueueService.cs:16-24 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Email/Services/ChannelQueueService.cs` and `04-Microservices/src/Nimble.Modulith.Email/Services/ChannelQueueService.cs` as WHOLE FILES: 100% 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. 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:14-22 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:14-22 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:13-21 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:13-21 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:12— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:12-20 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:12-20 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs` as WHOLE FILES: 100% 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. 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:14-22 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:14-22 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:14-22 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:14-22 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs` as WHOLE FILES: 100% 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. 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:11-19 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:11-19 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:13-21 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:13-21 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:11-19 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:11-19 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs` as WHOLE FILES: 100% 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. 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs:18— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs:18-26 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Delete.cs:18-26 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Delete.cs` as WHOLE FILES: 100% 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. 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 (9 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:31— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:31-39 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs:31-39 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs` as WHOLE FILES: this scan already matched 4 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. 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 (9 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenGuidIdValueGenerator.cs:13— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenGuidIdValueGenerator.cs:13-21 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenGuidIdValueGenerator.cs:14-22 — 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. 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 (9 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:84— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:84-92 | 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/GetCart.cs:67-75 — 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. 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 (9 lines × 2) 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs:107— 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs:107-115 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/GetById/GetByIdEndpoint.cs:73-81 — 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. 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.
Deprecated: Aspire.Dashboard.Sdk.linux-x64 — Aspire.Dashboard.Sdk.linux-x64 [9.5.2, — ) — the publisher's replacement is `9.5.2` Other,Legacy; migrate the reference to it.
Deprecated: Aspire.Hosting.Orchestration.linux-x64 — Aspire.Hosting.Orchestration.linux-x64 [9.5.2, — ) — the publisher's replacement is `9.5.2` Other,Legacy; migrate the reference to it.
Deprecated: Azure.Identity 02-CleanArchitecture/Directory.Packages.props:12— Azure.Identity 1.13.1 — Other
Deprecated: xunit 02-CleanArchitecture/Directory.Packages.props:41— xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6— 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6-13 | 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6-13 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Email/EmailSettings.cs:3— 03-ModularMonolith/src/Nimble.Modulith.Email/EmailSettings.cs:3-10 | 04-Microservices/src/Nimble.Modulith.Email/EmailSettings.cs:3-10 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Email/EmailSettings.cs` and `04-Microservices/src/Nimble.Modulith.Email/EmailSettings.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Email/EmailSettings.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:15— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:15-22 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs:15-22 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:12— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:12-19 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/GetById.cs:12-19 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:7— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:7-14 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/List.cs:7-14 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/List.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:15— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:15-22 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs:15-22 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs` as WHOLE FILES: this scan already matched 4 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 `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Models/Product.cs:3— 03-ModularMonolith/src/Nimble.Modulith.Products/Models/Product.cs:3-10 | 04-Microservices/src/Nimble.Modulith.Products/Models/Product.cs:3-10 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Models/Product.cs` and `04-Microservices/src/Nimble.Modulith.Products/Models/Product.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Products/Models/Product.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24— 03-ModularMonolith/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24-31 | 04-Microservices/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs:24-31 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Products/ProductsModuleExtensions.cs` as WHOLE FILES: 100% 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. 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) 03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:45— 03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:45-52 | 04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:45-52 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs` as WHOLE FILES: 100% 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. 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) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:16— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:16-23 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:16-23 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 138 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 (8 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.AddToCartValidator.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.AddToCartValidator.cs:9-16 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs:91-98 — 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. 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.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartCommand.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate.Specifications`, `CartId`, `Product`, `ProductByIdSpec`, `ProductId`, …. The inward dependency rule is broken here. It is named again on lines 2, 3, 4, 8, 12, 18, 29. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/CartDto.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `CartId`. The inward dependency rule is broken here. It is named again on line 5. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutCommand.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.OrderAggregate`, `CartId`, `OrderId`. The inward dependency rule is broken here. It is named again on lines 2, 6, 8. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate`, `OrderDemo.CleanVertical.Web.Domain.GuestUserAggregate.Specifications`, `OrderDemo.CleanVertical.Web.Domain.OrderAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `GuestUser`, `Order`, …. The inward dependency rule is broken here. It is named again on lines 2, 3, 4, 5, 6, 12, 13, 19, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `OrderDemo.CleanVertical.Web.Domain.CartAggregate.Specifications`, `CartByIdSpec`. The inward dependency rule is broken here. It is named again on lines 2, 11. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartQuery.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.CartAggregate`, `CartId`. The inward dependency rule is broken here. It is named again on line 5. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/Get/GetProductHandler.cs:3— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `OrderDemo.CleanVertical.Web.Domain.ProductAggregate.Specifications`, `Product`, `ProductByIdSpec`. The inward dependency rule is broken here. It is named again on lines 4, 8, 13. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/Get/GetProductQuery.cs:3— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `ProductId`. The inward dependency rule is broken here. It is named again on line 7. Depend on an abstraction the inner layer owns, implemented in the outer one.
Dependency-rule violation: OrderDemo.CleanArch.UseCases (05-CleanVertical/src/OrderDemo.CleanArch.UseCases) (Application) → OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web) (Web) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Products/ProductDto.cs:1— This Application file depends on the Web project `OrderDemo.CleanArch.Web (05-CleanVertical/src/OrderDemo.CleanArch.Web)`: it names `OrderDemo.CleanVertical.Web.Domain.ProductAggregate`, `ProductId`. The inward dependency rule is broken here. It is named again on line 4. Depend on an abstraction the inner layer owns, implemented in the outer one.
DM11 · Constructible invalid state· Constructible in an invalid state · ×9
Constructible in an invalid state: CartItem 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:8— `CartItem`'s public constructor takes `productId`, `quantity`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CartItem` 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: GuestUser 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/GuestUserAggregate/GuestUser.cs:5— `GuestUser`'s public constructor takes `email` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `GuestUser` 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: Product 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/ProductAggregate/Product.cs:5— `Product`'s public constructor takes `name`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Product` 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: CartItem 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:8— `CartItem`'s public constructor takes `productId`, `quantity`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CartItem` 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: GuestUser 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/GuestUserAggregate/GuestUser.cs:5— `GuestUser`'s public constructor takes `email` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `GuestUser` 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: Product 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/ProductAggregate/Product.cs:5— `Product`'s public constructor takes `name`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Product` 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: CartItem 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:8— `CartItem`'s public constructor takes `productId`, `quantity`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CartItem` 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: GuestUser 05-CleanVertical/src/OrderDemo.CleanArch.Core/GuestUserAggregate/GuestUser.cs:5— `GuestUser`'s public constructor takes `email` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `GuestUser` 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: Product 05-CleanVertical/src/OrderDemo.CleanArch.Core/ProductAggregate/Product.cs:5— `Product`'s public constructor takes `name`, `unitPrice` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Product` 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.
Anemic entity: Customer 04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5— `Customer` 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: Order 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6— `Order` 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: OrderItem 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:5— `OrderItem` 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: Customer 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5— `Customer` 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: Order 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:6— `Order` 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: OrderItem 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:12— `OrderItem` 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: CartItem 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:3— `CartItem` 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: CartItem 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:3— `CartItem` 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: CartItem 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:3— `CartItem` 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.
TodoComment 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:17— // TODO: Add proper authorization — 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 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:18— // TODO: Add proper authorization — 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 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:18— // TODO: Add proper authorization — 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 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:17— // TODO: Add proper authorization — 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 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:18— // TODO: Add proper authorization — 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 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:18— // TODO: Add proper authorization — 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 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/Create/CreateEndpoint.cs:14— // TODO: Add DbContext injection — 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 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/Create/CreateEndpoint.cs:35— // TODO: Use DbContext to create product — 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.
Duplicated block (12 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:17— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:17-28 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:17-28 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:17— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:17-28 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:17-28 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:13— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:13-24 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/MimeKitEmailSender.cs:15-26 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/MimeKitEmailSender.cs` as WHOLE FILES: 89% 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.
Duplicated block (12 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17-28 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17-28 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs` as WHOLE FILES: 89% 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 (12 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:41— 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:41-52 | 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:41-52 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs` as WHOLE FILES: 100% 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.
Duplicated block (12 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Email/Integrations/SendEmailCommandHandler.cs:16— 03-ModularMonolith/src/Nimble.Modulith.Email/Integrations/SendEmailCommandHandler.cs:16-27 | 04-Microservices/src/Nimble.Modulith.Email/Integrations/SendEmailCommandHandler.cs:16-27 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Email/Integrations/SendEmailCommandHandler.cs` and `04-Microservices/src/Nimble.Modulith.Email/Integrations/SendEmailCommandHandler.cs` as WHOLE FILES: 100% 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. 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) 03-ModularMonolith/src/Nimble.Modulith.Products/Data/ProductsDbContext.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Products/Data/ProductsDbContext.cs:13-24 | 04-Microservices/src/Nimble.Modulith.Products/Data/ProductsDbContext.cs:13-24 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Data/ProductsDbContext.cs` and `04-Microservices/src/Nimble.Modulith.Products/Data/ProductsDbContext.cs` as WHOLE FILES: 100% 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.
Duplicated block (12 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Logout.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Logout.cs:26-37 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Logout.cs:26-37 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Logout.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Logout.cs` as WHOLE FILES: 100% 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.
Prerelease dependency: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.EntityFrameworkCore.Design — Microsoft.EntityFrameworkCore.Design resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.AspNetCore.OpenApi — Microsoft.AspNetCore.OpenApi resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions resolves to 10.0.0-rc.2.25502.107, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Duplicated block (10 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:36— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:36-45 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:38-47 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenIntIdValueGenerator.cs` 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 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. 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:78— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:78-87 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:78-87 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs:6— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs:6-15 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs:6-15 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/ReportingDbContext.cs:6` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs:6— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs:6-15 | 04-Microservices/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs:6-15 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimCustomer.cs:6` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Events/UserAddedToRoleEventHandler.cs:15— 03-ModularMonolith/src/Nimble.Modulith.Users/Events/UserAddedToRoleEventHandler.cs:15-24 | 04-Microservices/src/Nimble.Modulith.Users/Events/UserAddedToRoleEventHandler.cs:15-24 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Events/UserAddedToRoleEventHandler.cs` and `04-Microservices/src/Nimble.Modulith.Users/Events/UserAddedToRoleEventHandler.cs` as WHOLE FILES: 100% 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.
Duplicated block (10 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:18— 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:18-27 | 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:18-27 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs` as WHOLE FILES: 100% 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. 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:59— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:59-68 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:59-68 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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.
Async endpoint handler without CancellationToken: /cart 01-VerticalSlice/src/OrderDemo.Api/CartFeature/AddToCart.cs:11— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /checkout 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:13— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /confirm-purchase 01-VerticalSlice/src/OrderDemo.Api/CartFeature/ConfirmPurchase.cs:13— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /cart/{cartId} 01-VerticalSlice/src/OrderDemo.Api/CartFeature/ViewCart.cs:12— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /orders 01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs:38— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /products/{id} 01-VerticalSlice/src/OrderDemo.Api/ProductFeature/GetProductById.cs:12— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /products 01-VerticalSlice/src/OrderDemo.Api/ProductFeature/ListProducts.cs:10— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Duplicated block (22 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:23— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:23-44 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:23-44 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:23` 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 (22 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:40— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:40-61 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:40-61 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs` as WHOLE FILES: 100% 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. 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) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:32— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:32-53 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:32-53 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:75— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:75-96 | 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:75-96 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs:40— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs:40-61 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Login.cs:40-61 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Login.cs` as WHOLE FILES: 100% 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. 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs:53— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs:53-74 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutEndpoint.cs:63-84 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutEndpoint.cs` 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 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. 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 (17 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderItemConfiguration.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderItemConfiguration.cs:11-27 | 04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderItemConfiguration.cs:11-27 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderItemConfiguration.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderItemConfiguration.cs` as WHOLE FILES: 100% 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 (17 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/UseCases/Commands/CreateUserCommandHandler.cs:15— 03-ModularMonolith/src/Nimble.Modulith.Users/UseCases/Commands/CreateUserCommandHandler.cs:15-31 | 04-Microservices/src/Nimble.Modulith.Users/UseCases/Commands/CreateUserCommandHandler.cs:15-31 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/UseCases/Commands/CreateUserCommandHandler.cs` and `04-Microservices/src/Nimble.Modulith.Users/UseCases/Commands/CreateUserCommandHandler.cs` as WHOLE FILES: 100% 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 (17 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs:9-25 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/CartItemConfiguration.cs:11-27 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/CartItemConfiguration.cs` as WHOLE FILES: 87% 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. 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 (17 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:60— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:60-76 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs:68-84 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs` as WHOLE FILES: 83% 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. 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 (17 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:15— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:15-31 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs:15-31 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Extensions/ResultExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 (17 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:16— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:16-32 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:18-34 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenIntIdValueGenerator.cs` 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 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. 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 (7 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs:3— 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs:3-9 | 04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs:3-9 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Address.cs:3` 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) 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5— 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5-11 | 04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5-11 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/CustomerAggregate/Customer.cs:5` 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:17— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:17-23 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/AppDbContext.cs:20-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs:30— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs:30-36 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Login.cs:30-36 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Login.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Login.cs` as WHOLE FILES: 100% 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. 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 (7 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs:31— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs:31-37 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Register.cs:31-37 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Register.cs` as WHOLE FILES: 100% 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. 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 (7 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:25— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:25-31 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:25-31 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs` as WHOLE FILES: 100% 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. 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.
P8 · Schema migrations· Schema created with EnsureCreated() outside the migrations · ×6
Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:45— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:55— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations 04-Microservices/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:49— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Users/UsersModuleExtensions.cs:49— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:45— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:55— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Duplicated block (25 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:24— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:24-48 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs:24-48 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/List.cs` as WHOLE FILES: 100% 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. 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 (25 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:43— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:43-67 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs:43-67 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs` as WHOLE FILES: this scan already matched 4 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. 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 (25 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:32— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:32-56 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:32-56 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (25 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/OptionConfigs.cs:13— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/OptionConfigs.cs:13-37 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/OptionConfigs.cs:13-37 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/OptionConfigs.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/OptionConfigs.cs` as WHOLE FILES: 86% 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 (25 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MediatorConfig.cs:12— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MediatorConfig.cs:12-43 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/MediatorConfig.cs:8-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `logger` to `Microsoft.Extensions.Logging.ILogger` in one and `ILogger` 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 (24 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/ListOrdersByDateHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/ListOrdersByDateHandler.cs:13-36 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/ListOrdersByDateHandler.cs:13-36 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/ListOrdersByDateHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/ListOrdersByDateHandler.cs` as WHOLE FILES: 100% 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 (24 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimCustomerConfig.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimCustomerConfig.cs:11-34 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimCustomerConfig.cs:11-34 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimCustomerConfig.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimCustomerConfig.cs` as WHOLE FILES: 100% 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 (24 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:123— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:123-146 | 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:123-146 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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 (24 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/GetById.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/GetById.cs:18-41 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/GetById/GetByIdEndpoint.cs:25-48 — 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. 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 (24 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:41— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:41-64 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs:41-64 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 (19 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Data/Config/ProductConfiguration.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Products/Data/Config/ProductConfiguration.cs:11-29 | 04-Microservices/src/Nimble.Modulith.Products/Data/Config/ProductConfiguration.cs:11-29 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Data/Config/ProductConfiguration.cs` and `04-Microservices/src/Nimble.Modulith.Products/Data/Config/ProductConfiguration.cs` as WHOLE FILES: 100% 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 (19 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:13-31 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:13-31 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs` as WHOLE FILES: 100% 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. 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 (19 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:28— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:28-46 | 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:30-48 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs` as WHOLE FILES: 87% 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:28` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:37— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:37-55 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/List.cs:37-55 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/List.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (14 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:18— 03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:18-31 | 04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:18-31 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs` as WHOLE FILES: 100% 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. 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 × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs:30— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs:30-43 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Delete.cs:30-43 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Delete.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Delete.cs` as WHOLE FILES: 100% 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. 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 × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimDate.cs:6— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimDate.cs:6-19 | 04-Microservices/src/Nimble.Modulith.Reporting/Models/DimDate.cs:6-19 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimDate.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Models/DimDate.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/DimDate.cs:6` 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 (14 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Profile.cs:24— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Profile.cs:24-37 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Profile.cs:24-37 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Profile.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Profile.cs` as WHOLE FILES: 100% 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. 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 (11 lines × 2) 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:51— 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:51-61 | 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:20-30 — 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 `05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:51` 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 (11 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductDetailsQueryHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductDetailsQueryHandler.cs:13-23 | 04-Microservices/src/Nimble.Modulith.Products/UseCases/Queries/GetProductDetailsQueryHandler.cs:13-23 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductDetailsQueryHandler.cs` and `04-Microservices/src/Nimble.Modulith.Products/UseCases/Queries/GetProductDetailsQueryHandler.cs` as WHOLE FILES: 100% 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 (11 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductPriceQueryHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductPriceQueryHandler.cs:13-23 | 04-Microservices/src/Nimble.Modulith.Products/UseCases/Queries/GetProductPriceQueryHandler.cs:13-23 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/UseCases/Queries/GetProductPriceQueryHandler.cs` and `04-Microservices/src/Nimble.Modulith.Products/UseCases/Queries/GetProductPriceQueryHandler.cs` as WHOLE FILES: 100% 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 (11 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:16— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:16-26 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:16-26 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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.
Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/AppDbContext.cs:26— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Duplicated block (33 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:25— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:25-57 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:25-57 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:25` 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 (33 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:23— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:23-55 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs:23-55 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/ListByDate.cs` as WHOLE FILES: 100% 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. 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 (33 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Email/SmtpEmailSender.cs:27— 03-ModularMonolith/src/Nimble.Modulith.Email/SmtpEmailSender.cs:27-59 | 04-Microservices/src/Nimble.Modulith.Email/SmtpEmailSender.cs:27-59 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Email/SmtpEmailSender.cs` and `04-Microservices/src/Nimble.Modulith.Email/SmtpEmailSender.cs` as WHOLE FILES: 100% 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 (30 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs:41— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs:41-70 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/Register.cs:41-70 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/Register.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/Register.cs` as WHOLE FILES: 100% 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. 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 (30 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:44— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:44-73 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:46-75 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs` 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. 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 (30 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:13— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:13-42 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs:31-60 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 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 (29 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:14-42 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:14-42 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs` as WHOLE FILES: 100% 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. 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 (29 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:58— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:58-86 | 04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs:58-86 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 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 (29 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/FactOrder.cs:7— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/FactOrder.cs:7-35 | 04-Microservices/src/Nimble.Modulith.Reporting/Models/FactOrder.cs:7-35 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/FactOrder.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Models/FactOrder.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Models/FactOrder.cs:7` 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 (21 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/ListCustomersHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/ListCustomersHandler.cs:13-33 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/ListCustomersHandler.cs:13-33 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/ListCustomersHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/ListCustomersHandler.cs` as WHOLE FILES: 100% 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 (21 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Web/LoggingBehavior.cs:22— 03-ModularMonolith/src/Nimble.Modulith.Web/LoggingBehavior.cs:22-42 | 04-Microservices/src/Nimble.Modulith.Web/LoggingBehavior.cs:22-42 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Web/LoggingBehavior.cs` and `04-Microservices/src/Nimble.Modulith.Web/LoggingBehavior.cs` as WHOLE FILES: 100% 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 (21 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:37— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:37-57 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/GetById.cs:37-57 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimProductConfig.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimProductConfig.cs:11-30 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimProductConfig.cs:11-30 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimProductConfig.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimProductConfig.cs` as WHOLE FILES: 100% 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 (20 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:11— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:11-30 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/GetById/GetCartHandler.cs:12-31 — 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. 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 (20 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:100— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:100-119 | 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:100-119 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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 (13 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:46— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:46-58 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs:64-76 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 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 (13 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/CustomersDbContext.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/CustomersDbContext.cs:14-26 | 04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/CustomersDbContext.cs:14-26 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/CustomersDbContext.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/CustomersDbContext.cs` as WHOLE FILES: 100% 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.
Duplicated block (13 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/CustomerAuthorizationService.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/CustomerAuthorizationService.cs:14-26 | 04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/CustomerAuthorizationService.cs:14-26 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/CustomerAuthorizationService.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/CustomerAuthorizationService.cs` as WHOLE FILES: 100% 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.
Sync-over-async (deadlock risk) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/AppDbContext.cs:26— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs:23— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:25— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:25-81 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:24-58 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:25-81 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:24-58 — 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) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:18— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:18-125 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:13-40 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:18-125 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:13-40 — 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 (37 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:90— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:90-126 | 04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs:90-126 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 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 (37 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:19— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs:19-55 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs:27-63 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/AddToCart.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartEndpoint.cs` as WHOLE FILES: 83% 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. 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 (35 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:20— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs:20-54 | 04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs:20-54 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Services/ReportService.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Services/ReportService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 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 (35 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:25— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:25-59 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartHandler.cs:27-61 — 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:25` 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 (32 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/CustomerConfiguration.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/CustomerConfiguration.cs:11-42 | 04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/CustomerConfiguration.cs:11-42 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/CustomerConfiguration.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/CustomerConfiguration.cs` as WHOLE FILES: 100% 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 (32 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/GetCart.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/GetCart.cs:18-49 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/GetById/GetByIdEndpoint.cs:24-55 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/GetCart.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/GetById/GetByIdEndpoint.cs` as WHOLE FILES: 86% 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 (27 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderConfiguration.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderConfiguration.cs:11-37 | 04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderConfiguration.cs:11-37 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderConfiguration.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Infrastructure/Data/Config/OrderConfiguration.cs` as WHOLE FILES: 100% 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 (27 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:14-40 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:14-40 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs` as WHOLE FILES: 100% 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. 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) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:30— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:30-52 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:30-52 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/InfrastructureServiceExtensions.cs:13— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/InfrastructureServiceExtensions.cs:13-35 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/InfrastructureServiceExtensions.cs:15-37 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/InfrastructureServiceExtensions.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/InfrastructureServiceExtensions.cs` 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 (18 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:59— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:59-76 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:27-44 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:59-76 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:27-44 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:59` 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 (18 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:61— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:61-78 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:40-57 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:61-78 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:40-57 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:14— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:14-31 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/EventDispatcherInterceptor.cs:14-31 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/EventDispatcherInterceptor.cs` as WHOLE FILES: 89% 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. 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 (18 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:62— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs:62-79 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs:80-97 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Products/List.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/List/ListEndpoint.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 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 × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:25— 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:25-34 | 05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:25-34 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/OrderAggregate/Order.cs:27-36 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs` as WHOLE FILES: 91% 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 (10 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:18-27 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs:18-27 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Queries/ListProductsQueryService.cs:18-27 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Queries/ListProductsQueryService.cs` 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.
Duplicated block (11 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:21— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:21-31 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:21-31 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/EventDispatcherInterceptor.cs:21-31 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs` as WHOLE FILES: 89% 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/EventDispatcherInterceptor.cs:21` 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 (11 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:18-28 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:18-28 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/MimeKitEmailSender.cs:20-30 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs` as WHOLE FILES: 89% 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/MimeKitEmailSender.cs:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs:6— 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs:6-12 | 05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs:6-12 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/OrderAggregate/OrderItem.cs:6-12 — 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs:6` 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 × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:20— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:20-26 | 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:20-26 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs:24-30 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 74 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 (6 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:35— 03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:35-40 | 04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs:35-40 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Customers/CustomersModuleExtensions.cs` as WHOLE FILES: 100% 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. 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 (6 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:35— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:35-40 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:35-40 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:35` 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.
DM10 · One transaction, one aggregate· One operation mutates 3 aggregates · ×2
One operation mutates 3 aggregates: CheckoutHandler.Handle 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:16— `CheckoutHandler.Handle` saves `GuestUser`, `Order`, `Cart` 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 3 aggregates: CheckoutHandler.Handle 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs:20— `CheckoutHandler.Handle` saves `GuestUser`, `Order`, `Cart` 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.
Hollow method — returns a constant without doing the work 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/FakeEmailSender.cs:8— `SendEmailAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Email/FakeEmailSender.cs:8— `SendEmailAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
IC1 · Incompleteness & stubs· Both branches are identical · ×2
Both branches are identical — the condition decides nothing 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs:14— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/ServiceConfigs.cs:14— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×2
Disposable created and abandoned in the method that made it 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17— `emailClient` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 17). Every use of it in `SendEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var emailClient = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Email/SmtpEmailSender.cs:17— `emailClient` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 17). Every use of it in `SendEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var emailClient = …;`), which releases it at the end of the scope on every path including a throw.
Cross-slice coupling: Orders → Customers 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:28— `ConfirmOrderHandler` (slice 'Orders') depends on `GetCustomerByIdQuery` from slice 'Customers'.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
Build failed — The target solution did not build cleanly (errors: 6), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0452: The type 'ProductId' must be a reference type in order to use it as parameter 'T' in the generic type or method 'ShouldBeNullExtensions.ShouldNotBeNull<T>(T?, string?)'; CS0234: The type or namespace name 'CleanArch' does not exist in the namespace 'OrderDemo' (are you missing an assembly reference?); CS0246: The type or namespace name 'ProductId' could not be found (are you missing a using directive or an assembly reference?).
D22 · Internal API Consistency· Inconsistent date type usage for the same semantic concept (Order Date) across related entities. OrderCreatedEvent uses DateOnly, while OrderDetails uses DateTime. · ×1
Inconsistent date type usage for the same semantic concept (Order Date) across related entities. OrderCreatedEvent uses DateOnly, while OrderDetails uses DateTime. — Standardize on a single date type (preferably DateOnly if time is not required, or DateTime if it is) across both OrderCreatedEvent and OrderDetails. (signatures: Nimble.Modulith.Customers.Contracts.OrderCreatedEvent.OrderDate (DateOnly) | Nimble.Modulith.Customers.Contracts.OrderDetails.OrderDate (DateTime))
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:13-74 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:14-85 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:17-83 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:12-60 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:13-42 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:13-74 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:14-85 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:17-83 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:12-60 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:13-42 — These 10 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 10 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 10 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:25— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:25-84 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:26-130 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:22-52 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:24-65 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:25-84 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:26-130 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:22-52 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:24-65 — These 8 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 8 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 8 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:29— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:29-52 | 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:31-56 | 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:31-53 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:29-52 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:31-56 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:31-53 — These 6 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 6 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 6 times.
Duplicated block (107 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:19— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:19-125 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:19-125 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs` as WHOLE FILES: 100% 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. 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 (97 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27-123 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27-123 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 138 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27` 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 (71 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:15— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:15-85 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:15-85 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 116 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 (66 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:18— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:18-83 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:18-83 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 128 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 (66–67 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:37— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:37-103 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:37-102 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs` as WHOLE FILES: 98% 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.
Duplicated block (65 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:35— 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:35-99 | 04-Microservices/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs:35-99 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs` and `04-Microservices/src/Nimble.Modulith.Users/Endpoints/ResetPassword.cs` as WHOLE FILES: 100% 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. 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 (61 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:14-74 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:14-74 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (60 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:26-85 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs:26-85 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Create.cs` as WHOLE FILES: 100% 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. 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 (59 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26-84 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26-84 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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 (56 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:26-81 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs:26-81 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 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 (55 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Email/EmailSendingBackgroundWorker.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Email/EmailSendingBackgroundWorker.cs:26-80 | 04-Microservices/src/Nimble.Modulith.Email/EmailSendingBackgroundWorker.cs:26-80 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Email/EmailSendingBackgroundWorker.cs` and `04-Microservices/src/Nimble.Modulith.Email/EmailSendingBackgroundWorker.cs` as WHOLE FILES: 100% 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 (53 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:19— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:19-71 | 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:19-71 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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 (48 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:13— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:13-60 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:13-60 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 93 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 (44 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/FactOrderConfig.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/FactOrderConfig.cs:11-54 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/FactOrderConfig.cs:11-54 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/FactOrderConfig.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/FactOrderConfig.cs` as WHOLE FILES: 100% 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 (38 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:18-55 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs:22-59 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 74 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 (36 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:31— 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:31-66 | 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:31-66 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs` as WHOLE FILES: 100% 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. 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 (34 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:25— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:25-58 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs:25-58 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Customers/GetById.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 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 (31 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs:18— 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs:18-48 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutEndpoint.cs:28-58 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Cart/Checkout.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutEndpoint.cs` 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 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. 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 (29 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:27— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:27-55 | 05-CleanVertical/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs:27-55 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs:31-59 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/Checkout/CheckoutHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 74 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 `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Checkout/CheckoutHandler.cs: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 `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 (28 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9-36 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/ProductConfiguration.cs:11-38 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/ProductConfiguration.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. 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 (26 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:11— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:11-36 | 04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs:11-36 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Data/Config/DimDateConfig.cs` as WHOLE FILES: 100% 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. 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 (25 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9-33 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9-33 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/ProductConfiguration.cs:11-35 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/ProductConfiguration.cs:9` 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 (23–24 lines × 8) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:52— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:52-74 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:63-85 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:60-83 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:38-60 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:52-74 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:63-85 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:60-83 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:38-60 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs` and `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:52` 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 (24 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs:10— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs:10-33 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs:10-33 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/OrderItemConfiguration.cs:13-36 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs` as WHOLE FILES: 86% 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 `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/OrderItemConfiguration.cs:13` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/OrderItemConfiguration.cs:12` calls `ThrowIfNull` and `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderItemConfiguration.cs:9` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:107— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:107-125 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:22-40 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:107-125 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Queries/GetCustomerByIdHandler.cs:22-40 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs` and `04-Microservices/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs` as WHOLE FILES: 100% 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Customers/Commands/CreateCustomerHandler.cs:107` 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 (21 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderConfiguration.cs:9-29 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderConfiguration.cs:9-29 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/OrderConfiguration.cs:11-31 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/OrderConfiguration.cs` as WHOLE FILES: 89% 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 (21 lines × 10) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:54— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:54-74 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:65-85 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:63-83 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:40-60 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:22-42 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:54-74 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/ConfirmOrderHandler.cs:65-85 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:63-83 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/DeleteOrderItemHandler.cs:40-60 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Queries/GetOrderByIdHandler.cs:22-42 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs` and `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:54` 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 (16 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26-41 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27-42 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:26-41 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:27-42 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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 (17 lines × 8) 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:68— 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:68-84 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:114-130 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:36-52 | 03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:49-65 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:68-84 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/Confirm.cs:114-130 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/DeleteItem.cs:36-52 | 04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/GetById.cs:49-65 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` and `04-Microservices/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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 `03-ModularMonolith/src/Nimble.Modulith.Customers/Endpoints/Orders/AddItem.cs:68` 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 (17 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:22— 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:22-38 | 03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:39-55 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs:22-38 | 04-Microservices/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs:39-55 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/AddOrderItemHandler.cs` and `03-ModularMonolith/src/Nimble.Modulith.Customers/UseCases/Orders/Commands/CreateOrderHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–17 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:32— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:32-46 | 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40-56 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:32-46 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40-56 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `req` to `CustomerOrdersReportRequest` in one and `OrdersReportRequest` 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 (16 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs:9-24 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs:9-24 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/CartItemConfiguration.cs:11-26 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartItemConfiguration.cs` as WHOLE FILES: 87% 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.
Duplicated block (15 lines × 2) 01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs:11— 01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs:11-25 | 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/LoggingBehavior.cs:11-25 — before extracting anything, compare `01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs` and `02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/LoggingBehavior.cs` as WHOLE FILES: 93% 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 × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartConfiguration.cs:9— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartConfiguration.cs:9-22 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartConfiguration.cs:9-22 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/CartConfiguration.cs:11-24 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartConfiguration.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/CartConfiguration.cs` 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. 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 × 4) 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:49— 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:49-59 | 02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/Get/GetCartHandler.cs:20-30 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/AddToCart/AddToCartHandler.cs:51-61 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/CartFeatures/GetById/GetCartHandler.cs:21-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `02-CleanArchitecture/src/OrderDemo.CleanArch.UseCases/Cart/AddToCart/AddToCartHandler.cs:49` 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 (9 lines × 3) 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:21— 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:21-29 | 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs:21-29 | 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/SeedData.cs:23-31 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/SeedData.cs` as WHOLE FILES: 86% 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 (8–9 lines × 4) 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40— 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40-48 | 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:39-46 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40-48 | 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs:39-46 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` and `04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 `03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `req` to `OrdersReportRequest` in one and `ProductSalesReportRequest` 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 × 10) 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:17— 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs:17-22 | 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/GetById.cs:14-19 | 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/List.cs:9-14 | 03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Update.cs:17-22 | 03-ModularMonolith/src/Nimble.Modulith.Products/Models/Product.cs:5-10 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs:17-22 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/GetById.cs:14-19 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/List.cs:9-14 | 04-Microservices/src/Nimble.Modulith.Products/Endpoints/Update.cs:17-22 | 04-Microservices/src/Nimble.Modulith.Products/Models/Product.cs:5-10 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Products/Endpoints/Create.cs` and `04-Microservices/src/Nimble.Modulith.Products/Endpoints/Create.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 (73 lines × 2) 02-CleanArchitecture/src/OrderDemo.CleanArch.ServiceDefaults/Extensions.cs:44— 02-CleanArchitecture/src/OrderDemo.CleanArch.ServiceDefaults/Extensions.cs:44-116 | 05-CleanVertical/src/OrderDemo.CleanArch.ServiceDefaults/Extensions.cs:44-116 — before extracting anything, compare `02-CleanArchitecture/src/OrderDemo.CleanArch.ServiceDefaults/Extensions.cs` and `05-CleanVertical/src/OrderDemo.CleanArch.ServiceDefaults/Extensions.cs` as WHOLE FILES: 100% 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.
Duplicated block (80 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.ServiceDefaults/Extensions.cs:47— 03-ModularMonolith/src/Nimble.Modulith.ServiceDefaults/Extensions.cs:47-126 | 04-Microservices/src/Nimble.Modulith.ServiceDefaults/Extensions.cs:47-126 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.ServiceDefaults/Extensions.cs` and `04-Microservices/src/Nimble.Modulith.ServiceDefaults/Extensions.cs` as WHOLE FILES: 100% 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.
Duplicated block (16 lines × 2) 03-ModularMonolith/src/Nimble.Modulith.Users/Data/UsersDbContext.cs:14— 03-ModularMonolith/src/Nimble.Modulith.Users/Data/UsersDbContext.cs:14-29 | 04-Microservices/src/Nimble.Modulith.Users/Data/UsersDbContext.cs:14-29 — before extracting anything, compare `03-ModularMonolith/src/Nimble.Modulith.Users/Data/UsersDbContext.cs` and `04-Microservices/src/Nimble.Modulith.Users/Data/UsersDbContext.cs` as WHOLE FILES: 100% 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.
End-of-life runtime: .NET net9.0 05-CleanVertical/tests/OrderDemo.CleanArch.AspireTests/OrderDemo.CleanArch.AspireTests.csproj:4— 05-CleanVertical/tests/OrderDemo.CleanArch.AspireTests/OrderDemo.CleanArch.AspireTests.csproj declares .NET net9.0 as this project's target framework, and .NET 9 STS, support ended 2026-05-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-05-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Off the main sequence: OrderDemo.CleanArch.Core (02-CleanArchitecture/src/OrderDemo.CleanArch.Core) 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderDemo.CleanArch.Core.csproj:1— OrderDemo.CleanArch.Core (02-CleanArchitecture/src/OrderDemo.CleanArch.Core): abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
DM10 · One transaction, one aggregate· One operation mutates 2 aggregates · ×1
One operation mutates 2 aggregates: Checkout.MapCheckoutEndpoint (route handler, line 13) 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:13— `Checkout.MapCheckoutEndpoint (route handler, line 13)` saves `GuestUser`, `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.
ED2 · Event/command shape· Command with 2 handlers · ×1
Command with 2 handlers: SendEmailCommand 04-Microservices/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5— `SendEmailCommand` is shaped like a command (one imperative intent) but has 2 handlers. A command should have exactly one handler that owns the decision; multiple handlers means hidden fan-out and unclear ownership. If several things should react, raise an EVENT after the command succeeds and let them subscribe.
Fake-async — async method never awaits 05-CleanVertical/src/OrderDemo.CleanArch.Web/ProductFeatures/Create/CreateEndpoint.cs:32— `HandleAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
Minor — 67 finding(s)
DM2 · Strongly-typed ids· Primitive id on a domain type · ×14
Primitive id on a domain type: Order.CustomerId 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:10— `Order.CustomerId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: OrderItem.OrderId 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:7— `OrderItem.OrderId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: OrderItem.ProductId 04-Microservices/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:8— `OrderItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: UserAddedToRoleEvent.UserId 04-Microservices/src/Nimble.Modulith.Users/Events/UserAddedToRoleEvent.cs:5— `UserAddedToRoleEvent.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.
Primitive id on a domain type: Order.CustomerId 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/Order.cs:10— `Order.CustomerId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: OrderItem.OrderId 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:14— `OrderItem.OrderId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: OrderItem.ProductId 03-ModularMonolith/src/Nimble.Modulith.Customers/Domain/OrderAggregate/OrderItem.cs:15— `OrderItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: UserAddedToRoleEvent.UserId 03-ModularMonolith/src/Nimble.Modulith.Users/Events/UserAddedToRoleEvent.cs:5— `UserAddedToRoleEvent.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.
Primitive id on a domain type: CartItem.ProductId 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:15— `CartItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: Order.GuestUserId 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:16— `Order.GuestUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: CartItem.ProductId 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/CartAggregate/CartItem.cs:15— `CartItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: Order.GuestUserId 05-CleanVertical/src/OrderDemo.CleanArch.Web/Domain/OrderAggregate/Order.cs:18— `Order.GuestUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: CartItem.ProductId 05-CleanVertical/src/OrderDemo.CleanArch.Core/CartAggregate/CartItem.cs:15— `CartItem.ProductId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
Primitive id on a domain type: Order.GuestUserId 05-CleanVertical/src/OrderDemo.CleanArch.Core/OrderAggregate/Order.cs:16— `Order.GuestUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Commented-out code 03-ModularMonolith/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:54— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:33— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:25— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:43— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:44— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:50— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:69— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:70— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Reporting/ReportingModuleExtensions.cs:54— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code 04-Microservices/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:33— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected 01-VerticalSlice/src/OrderDemo.Api/Program.cs:15— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected 03-ModularMonolith/src/Nimble.Modulith.Web/Program.cs:20— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected 04-Microservices/src/Nimble.Modulith.Email.Web/Program.cs:14— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected 04-Microservices/src/Nimble.Modulith.Web/Program.cs:20— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected 05-CleanVertical/src/OrderDemo.CleanArch.Web/Program.cs:6— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
Duplicated predicate 04-Microservices/src/Nimble.Modulith.ServiceDefaults/Extensions.cs:68— `!context.Request.Path.StartsWithSegments(HealthEndpointPath) && !context.Request.Path.StartsWithSegments(AlivenessEndpointPath)` appears character-identically in 2 files — 03-ModularMonolith/src/Nimble.Modulith.ServiceDefaults/Extensions.cs, 04-Microservices/src/Nimble.Modulith.ServiceDefaults/Extensions.cs. 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 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:54— `app.Environment.IsDevelopment() && dbOptions?.RecreateOnStartup == true` appears character-identically in 2 files — 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs. 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 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs:34— `f.OrderId == notification.OrderId && f.OrderItemId == item.Id` appears character-identically in 2 files — 03-ModularMonolith/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs, 04-Microservices/src/Nimble.Modulith.Reporting/Ingest/OrderCreatedEventHandler.cs. 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 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs:35— `field.Contains(',') || field.Contains('"') || field.Contains('\n')` appears character-identically in 2 files — 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs, 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/CsvFormatter.cs. 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 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs:37— `format == "csv" || acceptHeader.Contains("text/csv")` appears character-identically in 6 files — 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs, 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/OrdersReport.cs, 03-ModularMonolith/src/Nimble.Modulith.Reporting/Endpoints/Reports/ProductSalesReport.cs, 04-Microservices/src/Nimble.Modulith.Reporting/Endpoints/Reports/CustomerOrdersReport.cs. 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 04-Microservices/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs:53— `normalizedRoleName != "Admin" && normalizedRoleName != "Customer"` appears character-identically in 2 files — 03-ModularMonolith/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs, 04-Microservices/src/Nimble.Modulith.Users/Endpoints/AddRoleToUser.cs. 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 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs:18— `p.GetGetMethod()!.IsPublic && p.PropertyType == typeof(DbSet<TEntityBase>)` appears character-identically in 3 files — 02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs, 05-CleanVertical/src/OrderDemo.CleanArch.Infrastructure/Data/Config/VogenIntIdValueGenerator.cs, 05-CleanVertical/src/OrderDemo.CleanArch.Web/Infrastructure/Data/Config/VogenIntIdValueGenerator.cs. 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.
Shell project: Nimble.Modulith.Reporting.Contracts 04-Microservices/src/Nimble.Modulith.Reporting.Contracts/Nimble.Modulith.Reporting.Contracts.csproj— `Nimble.Modulith.Reporting.Contracts` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Nimble.Modulith.Reporting.Contracts 03-ModularMonolith/src/Nimble.Modulith.Reporting.Contracts/Nimble.Modulith.Reporting.Contracts.csproj— `Nimble.Modulith.Reporting.Contracts` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
ED3 · Event naming· Event not named in past tense · ×2
Event not named in past tense: SendEmailCommand 04-Microservices/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5— `SendEmailCommand` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: SendEmailCommand 03-ModularMonolith/src/Nimble.Modulith.Email.Contracts/SendEmailCommand.cs:5— `SendEmailCommand` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
README/code drift README.md:55— README advertises Docker containerisation, but no Dockerfile/compose file exists — searched for: `dockerfile`, `docker-compose`, `compose.yaml`, `compose.yml`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift 04-Microservices/src/Nimble.Modulith.Email.Web/README.md:117— 04-Microservices/src/Nimble.Modulith.Email.Web/README.md runs `dotnet run --project Nimble.Modulith.AppHost` from `04-Microservices/src/Nimble.Modulith.Email.Web/` or the repository root, but `Nimble.Modulith.AppHost` is not there: the project is `04-Microservices/src/Nimble.Modulith.AppHost`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
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/`.
misleading comment 02-CleanArchitecture/src/OrderDemo.CleanArch.Web/Configurations/MiddlewareConfig.cs:35— "Note this will drop Authorization headers" — delete - the comment is a restatement of the line and contradicts any real behavior; only remove it if the redirection actually drops auth
DM8 · Value-object opportunities· Primitive data clump · ×1
Primitive data clump: [productid, quantity, unitprice] 02-CleanArchitecture/src/OrderDemo.CleanArch.Core/CartAggregate/Cart.cs:11— The parameters [productid, quantity, unitprice] travel together across 6 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×1
Placeholder data left in code 01-VerticalSlice/src/OrderDemo.Api/CartFeature/Checkout.cs:29— A placeholder e-mail address ("guest@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `02-CleanArchitecture/README.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Logging is not universal — Only 24/31 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 31, 11 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 137/168 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.3 `!` suppressions per 1k syntax nodes — 30 suppression(s) across the 96831 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Off the main sequence: Nimble.Modulith.Customers.Contracts (04-Microservices/src/Nimble.Modulith.Customers.Contracts) 04-Microservices/src/Nimble.Modulith.Customers.Contracts/Nimble.Modulith.Customers.Contracts.csproj:1— Nimble.Modulith.Customers.Contracts (04-Microservices/src/Nimble.Modulith.Customers.Contracts): 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.
Off the main sequence: Nimble.Modulith.Email.Contracts (04-Microservices/src/Nimble.Modulith.Email.Contracts) 04-Microservices/src/Nimble.Modulith.Email.Contracts/Nimble.Modulith.Email.Contracts.csproj:1— Nimble.Modulith.Email.Contracts (04-Microservices/src/Nimble.Modulith.Email.Contracts): 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.
Off the main sequence: Nimble.Modulith.Products.Contracts (04-Microservices/src/Nimble.Modulith.Products.Contracts) 04-Microservices/src/Nimble.Modulith.Products.Contracts/Nimble.Modulith.Products.Contracts.csproj:1— Nimble.Modulith.Products.Contracts (04-Microservices/src/Nimble.Modulith.Products.Contracts): 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.
Off the main sequence: Nimble.Modulith.Users.Contracts (04-Microservices/src/Nimble.Modulith.Users.Contracts) 04-Microservices/src/Nimble.Modulith.Users.Contracts/Nimble.Modulith.Users.Contracts.csproj:1— Nimble.Modulith.Users.Contracts (04-Microservices/src/Nimble.Modulith.Users.Contracts): 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.
Off the main sequence: Nimble.Modulith.Customers.Contracts (03-ModularMonolith/src/Nimble.Modulith.Customers.Contracts) 03-ModularMonolith/src/Nimble.Modulith.Customers.Contracts/Nimble.Modulith.Customers.Contracts.csproj:1— Nimble.Modulith.Customers.Contracts (03-ModularMonolith/src/Nimble.Modulith.Customers.Contracts): 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.
Off the main sequence: Nimble.Modulith.Products.Contracts (03-ModularMonolith/src/Nimble.Modulith.Products.Contracts) 03-ModularMonolith/src/Nimble.Modulith.Products.Contracts/Nimble.Modulith.Products.Contracts.csproj:1— Nimble.Modulith.Products.Contracts (03-ModularMonolith/src/Nimble.Modulith.Products.Contracts): 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.
Off the main sequence: Nimble.Modulith.Email.Contracts (03-ModularMonolith/src/Nimble.Modulith.Email.Contracts) 03-ModularMonolith/src/Nimble.Modulith.Email.Contracts/Nimble.Modulith.Email.Contracts.csproj:1— Nimble.Modulith.Email.Contracts (03-ModularMonolith/src/Nimble.Modulith.Email.Contracts): 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.
Off the main sequence: Nimble.Modulith.Users.Contracts (03-ModularMonolith/src/Nimble.Modulith.Users.Contracts) 03-ModularMonolith/src/Nimble.Modulith.Users.Contracts/Nimble.Modulith.Users.Contracts.csproj:1— Nimble.Modulith.Users.Contracts (03-ModularMonolith/src/Nimble.Modulith.Users.Contracts): 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.
03-ModularMonolith: 4 contract type(s) expose producer-owned ids/enums — In 03-ModularMonolith, 4 contract type(s) (GetProductDetailsQuery, GetProductDetailsQuery, GetProductPriceQuery, GetProductPriceQuery) expose strong-typed ids/value objects (GetProductDetailsQuery, GetProductPriceQuery); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 125 file(s) — `01-VerticalSlice/src/OrderDemo.Api/Data/AppDbContext.cs`, `01-VerticalSlice/src/OrderDemo.Api/LoggingBehavior.cs`, `01-VerticalSlice/src/OrderDemo.Api/OrderFeature/GetOrders.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Core/OrderAggregate/OrderItem.cs`, `02-CleanArchitecture/src/OrderDemo.CleanArch.Infrastructure/Data/AppDbContext.cs`, … (+120 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a16209-295f-7bf0-8ccc-693607925016 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 102 field(s) across 4 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 17 · Warnings: 295 · Recommendations: 67 · Info: 88 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 05:15 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.